Hi All I tried using RDcatch as a logger also with out success. This is what I did using Centos install disk as a standalone PC:
Take 1 1. Set up all the hours to record with start and end time 2. Connected off air audio feed into input 1 and 2 of the sound card 3. Fist hour would record using input 1 then the second hour would use input 2. This way I would not have a gap between hours. 4. Upload the hour once recorded into a local folder with appropriate name eg 2012-11-12-1300 etc... What I found: Hour was never the same length, always a few seconds different to what I should be. Checked ntp clock, audio syncing Take 2 Same as above expect I used recording length of 1 hour instead of end time What I found: Same as above, recordings where never the same length. I then increased the recording time by 15 seconds, as some recordings in my case could vary that much. The recordings then were anywhere between 1hour and 1hour and 15 seconds. But then I checked it again after a week and one of the recordings was under 1 hour even with a 15 second buffer. Conclusion I since have gone back to using a windows base logger :-( :-( Thanks Stan On 10/11/12 12:06 AM, Todd Baker wrote: > Hi Nathan, > > We use RDCATCH on dedicated logging archiving machines here, and have run > into a few rather upsetting problems. > > We have seen our recordings end 2-8 seconds early consistently, and also of > late have had a even more perplexing problem. Say we have four recording > ending (4 hour recordings each) at 11:00AM. There are also 2 more recordings > starting at 11:00AM. At the appointed time, the recording ends but RDCATCH > has to write all of the ending data via NFS, and start the new recordings at > the same time. This used to work perfectly but suddenly stopped working. We > would have a drop out of 5 - 12 seconds THROUGHOUT the network (many studios > running here - but usually atleast 5 studios broadcasting/recording). > > We looked at network traffic, switches, etc. and have not seemed to find the > culprit (Note: the Rivendell system did not change in any way, but is also an > older version - 1.5.2). > > Solution for now was staggering the recording so everything was not happening > at once. However this has been an ongoing issue for us even withstanding the > newest glitch. > > So, we may be looking at finding another way to capture our recordings other > than the ways we do it now....Obviously a network wide dropout is not > something we want... > > Hope this give you food for thought. If anybody else has seen this type of > behavior please feel free to chime in. > > Best Of Luck, > > Todd Baker > Radio Free Asia , Washington DC > > > ----- Original Message ----- > From: "Nathan Steele" <[email protected]> > To: "User discussion about the Rivendell Radio Automation System" > <[email protected]> > Sent: Friday, November 9, 2012 10:18:42 AM > Subject: Re: [RDD] OT: Rotter question > > As always, the obvious eludes me.... > > Does anyone use rdcatch in this way or has anyone tried it and why did > you switch..... > > Nathaniel C. Steele > Assistant Chief Engineer/Technical Director > WTRM-FM / TheCrossFM > > On 11/9/2012 8:20 AM, Alan Peterson wrote: >> No one's mentioned it yet, so I may as well break the silence... >> >> Would there be anything wrong or improper in using RD Catch on a dedicated >> logging/archiving machine instead? It's already been built for you (on the >> appliance disk), works right out'a the box, and is designed to handle >> multiple inputs. >> >> Just sayin'.... >> >> -AP >> _______________________________________________ >> Rivendell-dev mailing list >> [email protected] >> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev >> >> >> > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
