This what the Lame developer said : The rarewares builds look fine. When dMC still shows "3.98.4", then it seems you haven't replaced the correct file(s). IIRC, you'll have to use the CLI encoder from dMC, if you want to use LAME.exe.
I have only replaced "lame.exe". Isn't that enough?
(offtopic: i can't refer to my post specific because when i type the number sign (the symbol) it changes automatically in a star (*, as you can see) when i click "preview post". So it changes the url)
In the folder "C:\Program Files\Illustrate\dBpoweramp\encoder" is the file "mp3 (Lame).dll", and in the folder "C:\Program Files\Illustrate\dBpoweramp\encoder\mp3 (Lame)" is the file "lame.exe".
There is no file named "lame_enc.exe" in these folders.
Also no file "lame_enc.dll" in dBpoweramp.
Where do you find this file ? I have mp3 (Lame).dll in the encoder folder of dbpoweramp and lame_enc.dll or lame.exe in the lame downloaded folder
In the folder "C:\Program Files\Illustrate\dBpoweramp\encoder\mp3 (Lame)" is only the file "lame.exe". If in yours is also "lame_enc.dll" then this is probably placed by yourself trying to fix this problem.
I don't find the file "lame_enc.dll" in dBpoweramp.
(offtopic: can someone please fix that problem with the changing number sign (or hash key) that i said in my previous post when making messages)
If you replaced the LAME.exe in "encoder/mp3 (Lame)" sub-folder, do encode some random track. Use your file explorer and locate the newly created mp3. Move your mouse over that file and look what info dBpoweramp tooltip gives. When it shows "LAME 3.99.", then you are not using 3.98.4 anymore and your upgrade seems to be successful. Alternatively you can open the mp3 file with some HEX-Editor and jump to the end of file, near the end there should appear some "LAME3.99.1" ASCII text.
When i move my mouse over the file it shows LAME3.99. (no space between LAME and 3.99. , and no digit after the last point).
Why is this not visible in "dBpoweramp configuration" ?
Another question about the Windows Explorer pop-up information...
Under Encoder Settings, with LAME 3.98.4-encoded files dbpoweramp was able to detect and display the VBR setting as in "-V 2", "-V 4", etc. With 3.99.1-encoded files it shows only 'Variable Bitrate' and the file's average bitrate. Will it be possible to display the same encoding info with the next version of dbpa?
The lame header must not be written correctly in this new version, there should be nothing to change at dBpoweramps end as it has worked for the last 5 years on all versions.
The lame header must not be written correctly in this new version,
You said this before in post "14". Read my post (number) 17.
Originally posted by Spoon
there should be nothing to change at dBpoweramps end as it has worked for the last 5 years on all versions.
Well, it seems to be that there now is a problem.
It doesn't mean that it has been working for 5 years there still no problems can occur.
After i read your post (14) i 've asked a question about this on the hydrogenaudio forum. http://www.hydrogenaudio.org/forums/...t=150&p=775410 , post number 170.
In post 172 the question is answered by Robert (Lame developer).
I quote is answer again: The rarewares builds look fine. When dMC still shows "3.98.4", then it seems you haven't replaced the correct file(s). IIRC, you'll have to use the CLI encoder from dMC, if you want to use LAME.exe.
So the build (2011-11-11) looks fine now he says.
After the response of Robert i posted a reply in this thread (post 17).
I suppose you also want to solve this problem as soon as possible, and also want to implement the new version of Lame very soon? Or do you still want to continue working with the old version?
I discovered there is also a text file called "mp3 (Lame).txt", located at \dBpoweramp\Versions\Compression\ which contains the Lame version (currently set to "Lame 3.98.4"). I'm guessing that the contents of this text file is placed into the "Encoder" ID3 tag by dBpoweramp. So even if you replace the .exe file with a newer one, the ID3 tag will still refer to the older version unless you update this .txt file too - which is a bit of an annoyance, IMHO. I'd love to have an easier way of updating the version of Lame used by just dropping in a new .exe and not having to change anything else.
Comment