Hi, Michelangelo! Over 2GB support was requested for a long time.
http://sourceforge.net/tracker/index.php?func=detail&aid=849889&group_id=290&atid=100290 But it is quite hard to support it "flawlessly" (at least for me...) From: Alexander Leidinger <[EMAIL PROTECTED]> Subject: Re: [mp3encoder] lame and files larger than 2Gb Date: Thu, 29 Jan 2004 16:10:31 +0100 > On Thu, 29 Jan 2004 13:43:27 +0100 > "Michelangelo Nottoli" <[EMAIL PROTECTED]> wrote: > > > (question 1) > > > > can anyone suggest the correct #ifdefs for fopen/fopen64 calls? something > > like... > > > > #if defined(__unix__) || defined(__sun__) > > ...call fopen64 > > #else > > ..call fopen > > #endif > > > > sounds correct ? > > The should be a configure test for fopen64. If the function is available > it can get used. IMHO, it is not sufficient to replace fopen. You need to replace all the fseek(), ftell(), ... and variable type to store the result of ftell64() and so on. Of course, you should use configure for all of them. > > (question 3) > > > > do you think there is need to open the output stream also with fopen64 ? > > I think it would be better. Output may be bigger than input (when with --decode), so it is important. But, by default, the output of decoding is RIFF-wave which does not support over 2GB.... So we have to check the length of decoded data. -- Takehiro TOMINAGA // may the source be with you! _______________________________________________ mp3encoder mailing list [EMAIL PROTECTED] http://minnie.tuhs.org/mailman/listinfo/mp3encoder
