Hi.

I'm using twolame 0.3.10b from RareWares and when encoding LONG tracks (more than 1:33:12) the encoder always quits at 1:33:12. What's wrong? The disc space is still sufficient (12gb free), so there must be a problem with the encoder, right?

If 1h33m12s of audio is encoded at 384 kbps, it's (93*60)+12 seconds * 384000 bitspersecond = 214732800 bits

log(214732800) / log (2) = 30.999895

This seems too much of a coincidence. It basically appears that 2^31 bits is too many to handle (or if the bitrate is 192 kbps then it's 2^30 bits).

Most Microsoft file systems before NTFS have big trouble with 2 GiB files = 2,147,483,648 Bytes (not bits), which is a coincidental number, but in bits, it is 17,179,869,184 bits, so a different number and not the cause of the problem.

Powers of two are indicative of a software problem.

Try encoding from the command line.

[edit]....more reading, less replying required....[/edit]

strange, it seems there was something wrong with the input. I used a WAV 32-bit float 48kHz (3072kbps) decoded from an AAC (MP4) using foobar. Now I decoded the same file with FAAD from RareWares now using "faad -b 4 -o o:\temp.wav x.mp4" and the WAV file came out at the same size, but somehow it now encodes the complete track... strange /-:

93 minutes & 12.40533 seconds of 3072 kbps is exactly at the 2 GiB limit of FAT32. Possibly Foobar2000 is decoding onto a FAT32 partition temporarily (e.g. wherever fb2k is installed) before passing to toolame, while FAAD is decoding onto a NTFS partition (your O:\ drive)?

If not, there's a possible limitation/bug in foobar2000 that could be reported. Otherwise, it could be solved by putting foobar2000 on an NTFS partition or (if possible?) getting fb2k to store its temporary files on the NTFS partition.

FAT32 has a 4 GB limit. All my disks except 1 are FAT32.

My apologies, according to
http://en.wikipedia.org/wiki/File_Allocation_Table
it's FAT16 that has a 2 GB limit on file size, while indeed FAT32 has a 4 GB limit.