dBpoweramp Release 13.1

[bhoar]

Re: dBpoweramp Release 13.1

Anything else than EAC?

I used both EAC and Nero DiscSpeed in testing C2 capabilities via firewire. The fact that both were seeing valid C2 error flag data on several firewire drives (with dbpoweramp failing the C2 test and failing to rip tracks on the same drives) helped in tracking down some potential roadblocks in dbpa's approach that spoon is looking into at the moment.

-brendan

[tbooty]

Re: dBpoweramp Release 13.1

for me when i convert my lossless music to mp3, with the lame 3.98, it's converting only to joint stereo.
even when it specifically says convert to "stereo"

i tried it with automatic and it was joint stereo
and i tried it with joint stereo and it was joint stereo.

anyone else noticing this?

[Spoon]

Re: dBpoweramp Release 13.1

Select the dual channel.

[ffm76600]

Re: dBpoweramp Release 13.1

for me when i convert my lossless music to mp3, with the lame 3.98, it's converting only to joint stereo.
even when it specifically says convert to "stereo"

i tried it with automatic and it was joint stereo
and i tried it with joint stereo and it was joint stereo.

anyone else noticing this?

Yes use the dual channel mode ! It's ok for me :smile2:

[bhoar]

Re: dBpoweramp Release 13.1

for me when i convert my lossless music to mp3, with the lame 3.98, it's converting only to joint stereo.
even when it specifically says convert to "stereo"

i tried it with automatic and it was joint stereo
and i tried it with joint stereo and it was joint stereo.

anyone else noticing this?

FYI, with the default joint stereo setting at normal bitrates, lame 3.98 decides on a frame-by-frame basis whether to use strict stereo or mid-side stereo encoding. Basically, joint stereo will tend to give you a significantly higher quality file than forcing strict stereo for nearly all music.

-brendan

[Teknojnky]

Re: dBpoweramp Release 13.1

recent JS thread @ HA

http://www.hydrogenaudio.org/forums/index.php?showtopic=64531

[Spoon]

Re: dBpoweramp Release 13.1

Update 21st July

ID Tag + CD Ripper: Better handling of comments with CRLF and display of such. In Tag Editor carriage breaks shown as {CR}{LF}

Use this version with the latest beta codecs (flac, etc) and all line break issues will be gone (in id tags).

[Shivek]

Re: dBpoweramp Release 13.1

I've got two questions here:

1.) Since I have no idea what is Join Stereo or Dual Channel when converting my FLAC files to MP3 with LAME 3.98, should I just leave it as Auto?

2.) When will dBpoweramp 13.1 full (not BETA) will be available for download?

Thanks in advance.

[bhoar]

Re: dBpoweramp Release 13.1

spoon, will we see any updates on the way firewire is handled with respect to possible better C2 support in 13.1? Now that the composermax is functional this would be HUGE!

Hi spoon. How's the improved support for C2 over firewire (and perhaps certain previously difficult SATA and/or USB interfaces) going?

-brendan

[Spoon]

Re: dBpoweramp Release 13.1

Auto is best for mp3.
R13.1 will be about 4-8 weeks

----

C2 over firewire: soon

[Shivek]

Re: dBpoweramp Release 13.1

Auto is best for mp3.
R13.1 will be about 4-8 weeks

----

C2 over firewire: soon

Thanks for the quick response.

[bcat]

Re: dBpoweramp Release 13.1

Hi Spoon. I think I've found a bug in R13.1. dBpoweramp doesn't work with files on a network share if the path name contains certain accented characters, like "ē" (U+0113).

As an example, there's an album on my file server that I can access from my desktop at the path "\\Zach\music\Lossless\Dogs of Peace\{spēak}". If I open that folder in Windows Explorer, the path displays properly and I can access the FLAC files it contains. dBpoweramp, on the other hand, cannot. If open Explorer's properties window for one of the files, the Audio Properties and ID-Tag tabs are displayed, but all the fields are completely blank. If I try to convert them to another format, I get an "error opening file" message. Finally, if I select the folder in the Batch Converter, I don't get any errors, but it shows up empty.

There are two other things I've noticed about this. First, this problem occurs with some paths containing accented characters, but not with others. I can access files at "\\Zach\music\Lossless\Béla Fleck & the Flecktones\The Hidden Land" just fine, for example. (Could this be because "é" is contained in the Windows-1252 character set but "ē" is not?) Second, this problem only occurs when the files are stored on the network. If I copy the "{spēak}" folder to my desktop, everything works perfectly.

[LtData]

Re: dBpoweramp Release 13.1

dMC has never worked properly with network drives unless you map them as a local drive. If you map it as a local drive, does it work better?

Edit: see below

[bcat]

Re: dBpoweramp Release 13.1

dMC has never worked properly with network drives unless you map them as a local drive. If you map it as a local drive, does it work better.

Yeah, it seems to work if I map it as a drive. Still, I don't think I should have to do that. Network share support is touted as a new feature in the R13 changelog for the Batch Converter, and it works perfectly for every album except the one that happens to have an "ē" character in its network path.

[LtData]

Re: dBpoweramp Release 13.1

My mistake, I missed that in the changelog and, as I don't convert over the network, didn't notice that. So you are using the Batch Converter to select these files, or are you trying to right-click and "Convert To"?