I've gotten some variations in MP3 encoding using dBpowerAMP and RazorLame front-ends. First of all, I ran into the issue of using a different version of the LAME encoder with each product, 3.90.3 with RazorLame and 3.92 (I think) with dMC. So, I backed up the lame_enc.dll file in the dBpowerAMP\Compression\Lame directory and copied my 3.90.3 version of the same file into it.
I encoded a WAV file that is 36,755MB in size to MP3 with dMC first, using the "Alt Preset Standard" option from the Advanced Options menu. The bitrate ended up being an average of 199kbps (VBR, of course), and the filesize is 5196MB. The file info says it was encoded with LAME 3.90. (Assuming/hoping that meant 3.90.3.)
I encoded the same WAV to MP3 with RazorLame, also using Lame v3.90.3 and --alt-preset standard. That file ended up being encoded at an average of 220kbps, with a filesize of 5738MB. The file info also says Lame version 3.90, so I'm pretty sure this really means 3.90.3 as well (since RazorLame says it's using 3.90.3 in its dialog box while encoding).
So, what I am wondering is:
--1-- Is dBpowerAMP only using the LAME encoder I copied to its \Compression\Lame directory (v3.90.3), or does the "Mp3 (Lame).dll" in the \Compression directory do anything to affect encoding as well?
--2-- If the encoder version dMC is using IS the same as the one RazorLame is using, then why would the resulting file sizes (and average bitrates) be different? Could one/both of the front-ends be using some additional command-line options other than simply --alt-preset standard?
The results are consistant, by the way, as I re-encoded the files the same way three times just to be sure.