Hi,
As a result of investigating issue 803 in FFMpeg (http://roundup.ffmpeg.org/roundup/ffmpeg/issue803), we found that in version 3.98.2, or in the latest CVS (tried 2008-01-29), the lame_encode_flush() sometimes return -1, but lame.h does not document it.
Version 3.98 does not return -1.
Is this a bug or an undocumented feature?
Regards and thanks for your support.
A negative return value signals a fatal error, in this case it signals "buffer too small".
Ciao Robert
Hi Victor,
it isn't really a bug inside LAME library, it's just not well documented in lame.h.
Ciao Robert
I've been experiencing this bug with a large number of various file formats, while it's not present at all in 3.97, so something in the new lame is causing this. I'll be interested in a solution, but in the meantime I've restricted all of our lame updates to 3.97.
Artem
http://beerpla.net
http://twitter.com/ArtemR
http://thread.gmane.org/gmane.comp.video.ffmpeg.devel/84314
could you please appease the FFMPEG devs so that current and future versions of Lame libraries do work with that bugless piece of software?
regards,
andrea
If I find some time, I'll add a workaround for the FFMPEG bug. Maybe it will be in 3.98.3, to be released sometime this year.
Note: FFMPEG seems to be calling lame_encode_flush in a loop, instead of once only.
I just committed to CVS some workaround for the FFMPEG bug. It's in to LAME 398 bug fix branch.
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).