Page 2 of 2

Re: Updating LAME codec

Posted: Sun Feb 17, 2019 8:56 am
by PG
Do you know another application that can embed a picture at the front of the mp3 file (where iTunes needs to find them), while still having the lame header? (the right name being the 'xing' header).
This is where I failed when I tried.

Re: Updating LAME codec

Posted: Sun Feb 17, 2019 10:25 am
by bob99
PG wrote:
Sun Feb 17, 2019 8:56 am
Do you know another application that can embed a picture at the front of the mp3 file (where iTunes needs to find them), while still having the lame header? (the right name being the 'xing' header). This is where I failed when I tried.
-
Foobar 2000.
- -
I think there are probably more.
-
PG, the weird thing about this is that all of the programs add EXACTLY the same 4 items (plus the header), as if it's just one command that gets you there. In the LAME command line program it is one command, the -t switch, which suppresses the header and 3 of the 4 info lines (delay, padding, and accurate length). Without any switches, all of those, including the header, are there by default.

Re: Updating LAME codec

Posted: Sun Feb 17, 2019 11:00 am
by bob99
PG wrote:
Sun Feb 17, 2019 8:56 am
Do you know another application that can embed a picture at the front of the mp3 file (where iTunes needs to find them), while still having the lame header? (the right name being the 'xing' header).
This is where I failed when I tried.
However I found out today that Foobar uses the LAME exe. But I'll look at the programs using a dll and see what the situation is.

Re: Updating LAME codec

Posted: Sun Feb 17, 2019 11:21 pm
by bob99
PG wrote:
Sun Feb 17, 2019 8:56 am
Do you know another application that can embed a picture at the front of the mp3 file (where iTunes needs to find them), while still having the lame header? (the right name being the 'xing' header).
This is where I failed when I tried.
Acoustica 7 can do it, and they use a LAME dll. Acoustica and Reaper use exactly the same dll, libmp3lame.dll v3.99.2.5. I don't know where they got it but their dll's are identical. And the dll works in Wavelab if renamed, but like I said the header is not added in Wavelab. I'll post screenshots later.

Re: Updating LAME codec

Posted: Mon Feb 18, 2019 8:26 am
by PG
I guess this is the problem. The header (and tail) need to be added by WaveLab because of the enhanced meta-data support of WaveLab. Therefore, this can't work out of the box and some special processing would need to be implemented.

Re: Updating LAME codec

Posted: Wed Feb 27, 2019 1:08 pm
by bob99
PG wrote:
Mon Feb 18, 2019 8:26 am
I guess this is the problem. The header (and tail) need to be added by WaveLab because of the enhanced meta-data support of WaveLab. Therefore, this can't work out of the box and some special processing would need to be implemented.
Thanks PG. I appreciate that Wavelab has to cover a lot of metadata cases on Windows and Mac with various filetypes, but I really hope this can be implemented, because I had a run-in with accurate length myself a few days ago. All of the programs using LAME that are capable of adding cover art use an xing header and LAME INFO tag and have this solved for iTunes. Amazon is still using LAME and I don't foresee that changing, and they make more MP3 files than anybody. Ideally Wavelab would decode LAME files with LAME, because LAME and Fraunhofer really don't appear to be very compatible when it comes to accurate length and gapless decoding each other. If that was done, Wavelab would be back and forth accurate length compatible with other DAWs like Reaper that use LAME. iTunes seems to be one of the only programs that can handle decoding both, but it has it's own special routines for dealing with gapless and accurate length.

Re: Updating LAME codec

Posted: Wed Feb 27, 2019 2:28 pm
by PG
Ideally Wavelab would decode LAME
Lame does not included a decoder. But it is sometimes associated with one called mpg123.

Don't forget that Fraunhofer created the mp3 format. On another hand, lame is not a well maintained project. For example, last version I tried 3.1 did not build successfully on Mac.
Putting some effort to support some non-official version which is not well maintained either, is difficult.

Now, I know this Lame version is popular, because of historical reasons (availability), therefore I don't discard your POV.