FYI, I tried jack_capture on a 64-Bit OS and used jack_freewheel so I didn't have to wait for hours for hitting the 2.1 GB "mark". jack_capture will output >>> Warning. 4GB limit on wav file almost reached. and the .wav file stops at 4GB. So it does seem to be a problem with the 32-bit version of jack_capture. This should be fixed, but in the meantime, I can recommend jack_timemachine for recording. jack_rec might also work. Best, J. On Wed, 9 Nov 2016 20:47:26 +0100 Johannes Kroll <j-kroll@xxxxxx> wrote: > On Wed, 9 Nov 2016 20:08:39 +0100 (CET) > "J. C." <julien@xxxxxxxxxxx> wrote: > > [...] > [...] > [...] > > No, but it could be a bug/misfeature in the software you are using for > recording. It could be related to an integer overflow when using a > 32-bit signed integer to keep track of file size or something similar. > In C, an 'int' would compile to a 32-bit or 64-bit variable according to > the word size of the target machine. As other possible causes don't > seem to apply, this seems likely. > > Can you try the recording with the same command line options on a > 64-bit OS, and with a 64-bit version of the same recording software? > _______________________________________________ > Linux-audio-user mailing list > Linux-audio-user@xxxxxxxxxxxxxxxxxxxx > http://lists.linuxaudio.org/listinfo/linux-audio-user _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
