Bing80, the 2GB limit has to do with AIFF: an AIFF file consists a series of "chunks" for audio and for other data -- metadata, cover art, whatever you (or rather, whatever the application you're using) like. Each chunk may be no more than 2GB long, and the by now rather ancient specification says that thare must be exactly one audio chunk. So you're stuck. I can only suggest that, if you can bear to lose some high frequency information from your mixes (and if your sound input hardware supports it) you sample at 32 or 22.05kHz instead of 44.1.
As far as MP3 output goes, I believe the issue's legal: if you sell software that can encode MP3s, you've got to pay a licence fee to Thompson. That, the paperwork, and especially the possibility that an up-front payment may be required, is a strong disincentive for shareware authors to support MP3 output. Some do, though: Audio Hijack Pro, for example.
Existing users, log in. New users, create a free account. Lost password?
Re: 2GB filesize and MP3 - domo
Bing80, the 2GB limit has to do with AIFF: an AIFF file consists a series of "chunks" for audio and for other data -- metadata, cover art, whatever you (or rather, whatever the application you're using) like. Each chunk may be no more than 2GB long, and the by now rather ancient specification says that thare must be exactly one audio chunk. So you're stuck. I can only suggest that, if you can bear to lose some high frequency information from your mixes (and if your sound input hardware supports it) you sample at 32 or 22.05kHz instead of 44.1.As far as MP3 output goes, I believe the issue's legal: if you sell software that can encode MP3s, you've got to pay a licence fee to Thompson. That, the paperwork, and especially the possibility that an up-front payment may be required, is a strong disincentive for shareware authors to support MP3 output. Some do, though: Audio Hijack Pro, for example.
Reply to This
Monday, February 09 2004 @ 07:31 AM PST