Re: Testers needed for current SVN version of LAME

Thanks, Thomas. That issue is resolved. Embarrased to admit to having 
forgotten to change compile directive from "HAVE_MPGLIB" to 
"HAVE_MPG123" in the lame frontend project!

Question for Alex:

Decode output messages now look like:
[quote]
F:\Test-lame>lame --decode 011.mp3
input:  011.mp3  (44.1 kHz, 2 channels, MPEG-1 Layer III)
output: 011.wav  (16 bit, Microsoft WAVE)
skipping initial 1105 samples (encoder+decoder delay)
skipping final 1151 samples (encoder padding-decoder delay)
Frame# 16811/16811  320 kbps   MS
Could not close audio input file

F:\Test-lame>
[end-quote]

Error is output from 'get_audio.c', line 2015.

Anything I'm missing?

TIA

John

On 30/08/2020 13:12, Thomas Orgis via Lame-dev wrote:
> Am Sun, 30 Aug 2020 12:28:18 +0100
> schrieb John Edwards via Lame-dev <[email protected]>:
>
>> It functions perfectly well except that the output wave file is 1152
>> samples shorter than it should be on my test file. The "skipping
>> initial" and "skipping final" messages are the same but "Frame# " shows
>> "9782/9782    32 kbps   MS" with libmpg123 and "9784/9784 32 kbps   MS"
>> with the standard mpglib compile.
> Could it be that libmpg123 parses the Info frame, for example? I am
> actually not sure right now which metadata processing the mpglib fork
> does, as I was only occupied with replacing it;-) You should compare
> with your initial uncompressed file for which output is more
> appropriate. I'd expect just some added silence missing.
>
>
> Alrighty then,
>
> Thomas
>
>
> _______________________________________________
> Lame-dev mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/lame-dev



_______________________________________________
Lame-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lame-dev