if it says accuraterip passed with others while using burst mode, does it mean its just as accurate as using secure mode???

about the lame mp3 options: Is fast mode here the same as the vbr new option? just curious cause it says lower quality and i thought vbr new was better quality in most cases

I would say that it is MORE accurate than secure mode.

There is no difference. So long as there weren't any re-reads, the passes are done in burst regardless of the mode selected.

I will try my best as I have switched to using dbpoweramp R12 as my CD ripping:

1. Yes, that means it is accurate. CDs don't always need to be ripped in secure mode for them to be secure, as long as the accuraterip results match up then everything is fine.

2. I have been wondering this myself. There are three Lame mp3 encoding options: normal, fast (lower quality), and slow (higher quality). I would assume that normal add the --vbr-new option as I thought it was the default in Lame 3.97 (which dbpoweramp R12 uses). However, I am not 100% sure as to what each of the settings does. I would like to pick a command that is the same as "-V 2 --vbr-new" but I can't quite seem to find that. I found the -V 2 part but I cannot find the option for --vbr-new (or the proper encoding quality).

OK, never mind. It appears that dbpoweramp music converter (dmc for short) uses Lame 3.97 and by default uses the --vbr-new encoding scheme. Choosing the different encoding quality levels means nothing as dmc will always use --vbr-new. I guess it has the same affect as choosing the quality levels in EAC, they mean absolutely nothing when using command lines. I received this information from this thread and this thread on the dmc forums.

1. so i guess if it fails doing accurate rip, i should switch to secure mode or should i leave it in secure mode so it can use both accurate rip and the softwares secure mode at the same time?

2. the dbpoweramp threads that are linked above don't say anything about the difference between the slow normal and fast options and the people there are still not very clear whether they are using vbr new. they just seem like they are saying it is new because they are using ver 3.97

Have a look at this page:
http://www.dbpoweramp.com/secure-ripper.htm

Specifically the part that says:

Earlier on it specifies that these are done in burst mode:

I'm not making this stuff up.

Now if it fails AccurateRip and you're using burst mode, simply switch over to test mode and rip again. If the CRCs change from black to green then you ripped the same thing twice in a row (the same as doing test and copy using EAC). If any track has a CRC in red then there was an error either with the copy pass, test pass or both. In this case dBpowerAMP's secure mode may get you an accurate rip.

But to say burst is more accurate than secure in dBpowerAMP is absolutely incorrect. In the world of EAC it isn't correct either as it really depends on the condition of the disc being ripped and the drive doing the ripping.

Yeah they do, they state "We are using the new lame, so all switches are 'New' The shown text next to -v is just there to help the transition to the newer v presets, they mean nothing." This means that, no matter what encoding quality you pick, it will always use --vbr-new. The official dmc devs don't discuss the encoding quality selections but other users though. If you look at the first thread I linked and go to the second page, you will see where one user ripped a song in EAC (using --vbr-new) and ripped a song in dmc at the same setting, both file sizes came out to be the same.

I did this experiment last night. I ripped a track using EAC and the Lame.exe file to -V 2 --vbr-new and I ripped a track using dmc to -V 2 with the encoding set to normal. Both had roughly the same file size, the dmc rip was about 0.01MB bigger because of the added ID3 tag information that wasn't in the EAC rip. So, if all else fails, conduct a test for yourself to see if the file sizes come out to be the same. If they match up (or are very close in file size) then you know the settings in dmc are correct.

All lame encodes are VBR new.

As far as secure ripping, secure mode of dbpoweramp will be as fast as burst if can be verified by accuraterip, so you loose nothing by doing secure ripping if that is your end goal.

How does the 'encoding' drop down function in comparison to vbr new.

To wit: encoding options = A) Normal, B) Slow (High Quality), C) Fast (Low Quality)

This is seemingly a point of confusion for more than a few, including myself.

What does 'encoding' correlate on a command line or -v option.

If there is no difference between the 3 selections, why does it exist on the form?

no, he is talking about the options for: normal, fast (lower quality), and slow (higher quality).

I have wondered that myself.

The question is when we run lame.exe, --vbr-new, is it running on normal, fast (lower quality), or slow (higher quality)?

When using lame.exe it will be using normal (quality of 5, I am guesing). Fast translates to a quality of 7, and slow is quality 2.

From lame documentation:

internal algorithm selection. True quality is determined by the bitrate
but this variable will effect quality by selecting expensive or cheap algorithms.
quality=0..9. 0=best (very slow). 9=worst.
recommended: 2 near-best quality, not too slow
5 good quality, fast
7 ok quality, really fast

Edit: Never mind, I think you answered the question. Still, what is the best encoding option to select? Normal, Slow, or Fast? I have selected normal and fast for testing and the file size differences are minimal.

this is the q option right? or qval? ex q for eac giving lame preset fast standard is 2 and qval is 3

I think so (do not have lame.exe at hand to check)