I use linux command line recorder called arecord to record audio for a fixed period and then spit the created file out to a 320k mp3 when finished. I use crontab to schedule it. It starts at 1 min to the hour and appends the date / time in the month to the file name. The 50 second sleep means the actual recording starts 10 seconds before the top of the hour. That way It overlaps the next hours recording. I run 2 scripts... one for the even hours and one for the odd hours.
I hope someone finds this usefull. Many thanks Geoff #!/bin/bash # Special recording program to record audio for logging purposes and convert to mp3. sleep 50 CURRENTevenTIME00=`date +%H_%M` # arecord records 44.100 cd quality audio for duration 3610 seconds (1 hour 10 seconds) arecord -d3610 -r44100 -f cd -t wav -c2 /mnt/sdb1/share/wav/$CURRENTevenTIME00.wav sleep 10 lame -b 320 -m j /mnt/sdb1/share/wav/$CURRENTevenTIME00.wav /mnt/sdb1/share/mp3/$CURRENTevenTIME00.mp3 On 9/23/14, Rick <[email protected]> wrote: > This is not RDD-specific or anything. > > It happened to us (HD died from the 24x7 recording activity). > > We were using a WinXP system running BUTT to feed Shoutcast. > > BUTT had a record option, but it was clunky, so my tech added a $99 utility > for recording (sorry, I don't remember the product). Hourly recordings > going to a data drive (on the XP box) that was then shared on the LAN. > > The hourly recording activity ran the data drive so hard (constantly writing > every few seconds) it finally started corrupting. > This caused BSoDs for the XP box, bringing down the primary function of > feeding Shoutcast. > > I rebuilt that box and said "no recording anymore; recording shall not take > down the stream feed". > > We had a manual Tascam recorder workaround for quite awhile, but I wanted to > figure out a way to do the automated recordings again, and it was an > opportunity to figure out how to do it with Linux. > > I thought about SSDs, but I was reluctant to put one in for constant > thrashing, and remembered my old DOS days when RAMdisks were used to > compensate for slow HDs. > > I thought PERFECT! RAM IS designed to be thrashed for the life of the > system, let's do it that way! > > The rest fell into place one the plan was set :) > > Cheers, > Rick > KMUZ Engineering > > > > ________________________________ > From: Rob Landry <[email protected]> > To: Rick <[email protected]> > Cc: "Kevin, Natalia, Stacey and Rochelle" <[email protected]>; > "[email protected]" <[email protected]>; 'User > discussion about the Rivendell Radio Automation System' > <[email protected]> > Sent: Monday, September 22, 2014 4:02 AM > Subject: Re: [RDD] Looking for Looping Software to record Broadcast > > > > > > > > On Sun, 21 Sep 2014, Rick wrote: > >> - Everything recorded to ramdisk, then moved to physical HD once hourly >> recording is complete (prevents killing your HD by constantly writing to >> it >> during recording). > > I've never encountered that problem. Where did you learn about it? > > > Rob _______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
