It's Centos 6 on a homebuild system (quality Intel motherboard, Kingston RAM and so on) Since it seems that no has experienced this, it could be that the system is "stressed" when I'm voicetracking in the log running in RDairplay. So Monday I will try a fresh restart of the system before voicetracking, and see if it makes a difference
2015-03-18 22:21 GMT+01:00 Cowboy <c...@cwf1.com>: > On Wednesday 18 March 2015 05:08:16 pm Morten Krarup Nielsen wrote: > > If I promise we're only voicetracking, when the talent can't be in studio > > at the time of broadcast, > > You don't have to justify. > I was merely answering a question. ;) > > > maybe somebody will give me a hint of the > > stability of RDairplay (when voicetracking in the log currently running) > > Version, OS, hardware ?? > > I know of this being done, never without "problems" but those > problems had nothing to do with the system. > ( operator error, due the time constraint overwhelming the operator ) > > -- > Cowboy > > http://cowboy.cwf1.com > _______________________________________________ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev >
_______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
