From: <no...@so...> - 2002-08-08 08:52:36
|
Bugs item #586522, was opened at 2002-07-25 17:40 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100290&aid=586522&group_id=290 Category: configure/Makefiles Group: Quality >Status: Closed Resolution: None Priority: 5 Submitted By: Chris Barker (ctbarker32) Assigned to: Alexander Leidinger (aleidinger) Summary: DJGPP makefile problem & 3.92 zero bytes Initial Comment: Hi, I'm new to working with the lame source code. Problem 1: I installed the latest DJGPP compiler and setup and tested with simple programs that it works. I then attempted to compile the Lame 3.92 code using the supplied DJGPP makefile which produced all sorts of errors and did not compile. All of this is under Windows 2000, RC2 btw. Problem 2: I use Feurio for cd burning. Upon upgrading to Lame 3.92 from 3.90 Feurio started to report that there were extra bytes (83?) at the start of the Lame 3.92 produced MP3 files. I contacted Feurio support and they stated that Lame 3.92 puts "zero bytes" into the MP3 files. I downgraded to 3.90 and things are back to normal. Any help would be appreciated. Thanks. -CB ---------------------------------------------------------------------- >Comment By: Alexander Leidinger (aleidinger) Date: 2002-08-08 10:52 Message: Logged In: YES user_id=90585 I think I committed a fix for problem 1 to the CVS. Feel free to open a new bug report if not. ---------------------------------------------------------------------- Comment By: Alexander Leidinger (aleidinger) Date: 2002-07-27 01:50 Message: Logged In: YES user_id=90585 Problem 2: This is because LAME inserts some additional information there. If Feurio uses the Dll it has to call the beWriteVBRHeader() function even if it's not encoded with VBR because a never LAME writes an INFO tag. They can do this independend of the used version of LAME because this function does nothing bad if the version of LAME doesn't has this new feature and the file is encoded with CBR. Problem 1: Without a copy of the error messages we can't know what the problem may be. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100290&aid=586522&group_id=290 |