On May 12 18:49:57, D.Cottle@xxxxxxxx wrote: > I pretty much got it to work, but new question: SoX stops on its own. I can’t see any reason. This has happened when recording from the interface to my laptop, from my internal speaker on laptop, and on our Mac Minis at school. After about 30 minutes of recording 8 channels to a single file, it simply stops and returns “done.” Why would this happen? What exactly is the sox command line? Is there enough space where you are writing? > Yes, I split the .CAF files with a script (AppleScript that sends > a shell script with sox) every hour to aif. Hwo exactly are you recording the CAF files in the first place? How are you restarting this CAF recording? Surely you don't record one endless file. How exactly are you splitting the caf files to the aif files? > We then save the .CAF files just in case for a few days. > Our staff works with the aif files and hardly ever deals with the .CAF. > The odd limitation is that Logic can only record about 13 hours. > I don’t know why there is this limitation where CAFs can run for days, > if I understand correctly. Is that a limitaion of Logic for sure? Could that be a limitation of the CAF format? (BTW, why are you uisng CAF?) > We reset Logic once every day > (with scripts, and lose about 400 ms). How do you records 24/7 then, if the recording stops after 13 hours? You would imho be better off recording with sox directly, putting something like 0 * * * * $PATH/rec -c 8 /some/where/$DATE-HOUR.caf trim 3600 in your crontab and leave the Logic Pro scripting out of it. > We also record silence but then use sox to analyze the hour blocks and throw away silent hours. This is slightly inefficient, since there might only be 3 minutes of usable material in an otherwise silent file. So why are you recording everything all the time? > Before Logic we used Audio Companion, which allows you to turn > the recording on and off based on silence, sox can do that to. but then a long pause in a compostion might fool the recording. > The Logic method allows exact time frames. Is some timestamp stored in the CAF file? > It could be that SoX will do everything we need. That’s why I’m investigating it. We know Logic. It gives us meters for every room, with peak indicators, which we can check visually or remotely using screen share. You mean, there is a human operator overseeing the recording? What is the point in automatizing the one recording command? > It has an input monitor so we can listen to each room individually. > Most important I can pick and choose what input streams it records > and it outputs individual stereo tracks. You said you record all the rooms 24/7 ... > Mostly my staff understands Logic and while SoX might allow similar functionality, I don’t understand it as well, and we know Logic. The biggest advantage os using sox for this, imho, is that it's a commandline tool, trivialy scriptable; recording one hour, saving it in a file appropriately named, and starting another, is a crontab oneliner. > rec -c 8 -b 16 -r 48k /Volumes/CAF3/test.caf > Oddly, it gives me this error: > rec WARN formats: can't set 8 channels; using 18 > And it reports: > Input File : 'default' (coreaudio) > Channels : 18 > Sample Rate : 48000 > Precision : 32-bit > Sample Encoding: 32-bit Signed Integer PCM > Even so, it does record just 8 channels at 16 bit. I believe the error message means SoX was unable to set the audio device itself to be providing 8 channels, and is getting the whole 18 channels instead; but it creates an 8ch file out of it (using the first 8), as instructed. In other words, without the -c 8, SoX would be writing 1n 18ch file, using what it is given. > I then split it with another terminal window and: > ~/sox/sox /Volumes/CAF3/test.caf /Volumes/CAF3/test2.aif remix 1 2 trim 0 60 You can put that in your crontab too, so that this happens after every chunk recording is finished. > So proof of concept, but: My current issue: why does SoX stop on its own? No idea. Run it with rec -V5 and post the debug messages. _______________________________________________ Sox-users mailing list Sox-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/sox-users
