[LAU] Using commandline app to mark/detect sounds above a threshold

[Ralf Mardorf]

On Tue, 8 Nov 2016 16:38:21 +0100, Kjetil Matheussen wrote:
>>The OP claims that no files larger than 2.1G were produced when
>>using  
>
>libsndfile.
>
>
>Are you trolling? OP did not claim that libsndfile was to blame.

Are you trolling? I didn't claim that! [1]

>No one has. Don't try to twist what people write so that it
>
>sounds like something else.

You do, I don't. I only want to learn what does cause the issue, to
avoid, that the same happens to friends or me, if we need to record for
such a long time, too.

Anyway, what could have been the culprit?

>> However, it doesn't matter what you wanted to point out, important
>> only  
>
>> is that, if neither libsndfile, nor wav does cause the issue the OP
>> experienced, then something else most cause the trouble. Right?  
>
>
>I don't know why it stopped at 2GB. Maybe it's something in the jackrec
>
>program, but that's unrelated since we were talking about jack_capture,
>
>not jackrec. And in jack_capture, the limit is 4GB (jack_capture also
>uses
>
>libsndfile). I know this quite well since I'm the author of
>jack_capture, and I've
>
>tested the 4GB barrier many times to ensure jack_capture handles it
>correctly.

So we still don't know the cause of the issue. That's all I want to
know.

Regards,
Ralf


[1]

If you read your original mail, then the OP pointed out that the wav
files were not larger than 2.1GB and that libsndfile was used. You
claim that wav is the limiting factor:

On Tue, 8 Nov 2016 15:05:24 +0100, Kjetil Matheussen wrote:
>>
>> On 07.11.2016 11:32, J. C. wrote:  
>> > Hey hey,
>> > I tried to record over long periods of time (7-9 hours), using
>> > jack_rec,  
>> which  
>> > apparently relies on libsndfile for writing audiofiles. I started
>> > out  
>> using  
>> > .wav, which broke off after 6:12:49 (2.1G). Next time, I tried
>> > using the  
>> file  
>> > extension .w64, which yielded the same result.
>> >
>> > So, which format, or extension, would work for such periods of
>> > time?  
>>
>> Have you tried with jack_capture?
>>
>> It uses libsndfile, too for codecs, but can dump raw samples to disk
>> if you tell
>> it to.
>>
>> So, if libsndfile should be the limiting factor, try dumping the raw
>> frames and
>> later analyze those.
>>
>>  
>libsndfile is not the limiting factor. It's the wav format that doesn't
>support large files.
>(The "raw" format is also handled by libsndfile, but again, libsndfile
>is not to blame here,
>so that doesn't matter.)
>
>
>
>>   jack_capture -f raw -b FLOAT snoring.bin
>>
>>  
>Besides this option (and -f w64 and -f CAF which has been suggested),
>jack_capture continue writing to new files in case you try to write
>more data than
>is supported, so you can even use the default wav format for large
>files.