rafajuv wrote: ↑Mon Dec 07, 2020 9:54 am
thanks by your answer
the last version of lame i think is 3.100. its the best version? or not have diference than others like 3.99 or 3.98?
thanks
Latest version in official site is 3.100:
[External Link Removed for Guests]
But i use this web to get Windows builds, and there is a
3.100.1 build:
[External Link Removed for Guests]
Regarding Joint Stereo, some years ago i used
lame -b192 -q1 -ms --lowpass 19.5 command line switches to get 192Kbps encodings, forcing 2 channel encoding, as i read 15-20 years ago that Joint Stereo could add artifacts to the final result. That could make sense, as you are switching to Mono and Stereo several times per second.
However, LAME is JS-safe since many many years ago. That statement could make sense for lower bitrate encodings, for lower quality encoders, for low quality players, for slow computers, for low-end sound cards,... In real world conditions (higher bitrates, modern hardware,... and using LAME), Joint Stereo is safe, and most of LAME presets use JS. In fact JS saves space in lower quality frames to spend it on high quality frames.
I currently use only
lame --preset insane command line. If the source is a FLAC, then i use
flac -d to decompress it to WAV before using LAME. I have managed to build a BAT that does all and deletes the WAV, and modified the registry to get a context shell menu option in FLAC files. I mean...
- I use presets (insane for 320, extreme for highest quality VBR)
- I don't use external programs: only the official FLAC encoder/decoder and the official LAME encoder. Warning: Programs that rely on lame_enc.dll can't use the real power of LAME, as the DLL is/was limited to a bunch of encoding options (maybe it supports all presets, but lack of qval settings, and use default lowpass fiters). If you use an external program, it's better if it tries to load the EXE.