Hi, On a related note, you can set rdairplay to load logs in rdadmin -> hosts -> rdairplay
I think mines set to something like: %Y_%M_%D_LOG Might be easier to manage from one location rather than having it hard set in the launch script. On 2013-02-02 09:47, MICHAEL SMITH wrote: > Ah: really sorry. Despite spending a lot of time on this last night, > it turns out that my audio share isn't mounting before the script > runs > to start RdAirplay. Forcing the audio share to mount before running > the script solves this. Easy in retrospect. > > ------------------------- > FROM: MICHAEL SMITH <[email protected]> > TO: User discussion about the Rivendell Radio Automation System > <[email protected]> > SENT: Saturday, 2 February 2013, 8:38 > SUBJECT: [RDD] Autostart RdAirplay after power failure > > Hi everyone, > > Please can you help. I'm trying get RdAirplay to start on bootup. > (Ubuntu 12.04, Rivendell 2.2.0 Tryphon packages) > > I can get RdAirplay to start and load today's log with a script: > > rdairplay --log1=20`date +%y%m%d`:0+ > > This works fine when I boot the machine and run the script manually. > > However, when I add this script to the startup applications (with a > sleep whilst Jack etc... starts) RdAirplay starts but does not play > the log. In fact, pressing any of the playback buttons just turns > thems a red colour. No audio starts to play back, no countdown starts > etc... > > If I then close RdAirplay and run the script, everything springs to > life. > > I have tried making a Desktop icon (as per the wiki) > > http://rivendell.tryphon.org/wiki/Auto-Recovery_After_a_Power_Failure3 > But this has the same result. Icon referred to in startup > applications: RdAirplay opens but fails to play and needs a restart. > Launch this once booted and all works fine. > > Can anyone help please? > > Thank you in advance, > > Mike > > ------------------------- > FROM: Jay Ashworth <[email protected]> > TO: User discussion about the Rivendell Radio Automation System > <[email protected]> > SENT: Saturday, 2 February 2013, 0:59 > SUBJECT: Re: [RDD] Back timing > > ----- Original Message ----- >> From: "Alan Peterson" <[email protected] [1]> > >> Ah, I see... didn't notice the call-in part. >> That's what happens when fifty emails cross the screen in the few >> minutes before the work starts piling up in front of the production >> room door. >> My error. > > Nobody actually used that example before me; I was just making the > point > that "I need to find a way to hit hard time cues" is the sort of > issue > for > which "there are lots of ways to fudge that" isn't always a good > enough > answer. > > Since your "drift the network newscast" suggestion was so good, I had > to > try harder than usual. ;-) > > Cheers, > -- jra > -- > Jay R. Ashworth Baylink [email protected] [2] > Designer The Things I Think RFC 2100 > Ashworth & Associates http://baylink.pitas.com [3] 2000 Land Rover > DII > St Petersburg FL USA #natog +1 727 647 1274 > _______________________________________________ > Rivendell-dev mailing list > [email protected] [4] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev [5] > > _______________________________________________ > Rivendell-dev mailing list > [email protected] [6] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev [7] > > > > Links: > ------ > [1] mailto:[email protected] > [2] mailto:[email protected] > [3] http://baylink.pitas.com/ > [4] mailto:[email protected] > [5] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > [6] mailto:[email protected] > [7] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
