Keep in mind these are only work arounds not fix its:

It sounds like the record doesn't segue to the log change over. So I'd schedule any recording in RDCatch or change the last item (before log change) in the log to audio with a segue.

Or another senario is to have the likes of a log roll-over ID with extended backing theme or something in the Aux deck or hotkeys. The Aux deck is fired from the main log then the main log conintues on to load the next days log. The first item in the next days log could be a macro cart to fade out the Aux deck/stop and pause the main log for a few seconds while the aux deck is fading. This a complicated messy way around it, but it would fill in a variable time space while loading logs around. If possible, I'd use an ID on the sound panel if it can be faded out from a macro cart in the main log instead of using the aux deck with another log.

The last option of course, is to have some way for RD to load the logs faster. Unfortunately if RDAirplay is busy loading logs and the logs are qutie fiddly full of stuff it's going to take time to start the next log. I'm not used to this personally with automation systems at log change over but I have voiced ID with a long segue scheduled before log change over, and the opener on the next log has a decent intro time.

But the best fix would be how RDAirplay handles this. I noticed years ago I had to get an even faster computer for segues because as RDAirplay did a scan for timed events evey so often RDAirplay's interface would pause a split second and as it did, if a segue happened to fall on the same time period the segue was put on hold until RDAirplay was done doing it's other business. Not the best idea but for most part segues don't fall during RDAirplay background routines.



----- Original Message ----- From: "Rick" <[email protected]>
To: "Gavin Stephens" <[email protected]>
Sent: Thursday, March 13, 2014 1:57 PM
Subject: Re: [RDD] silence at log rotation



it's a hard timed "make next" on the last log item every day, so I do not have any skipping issues as this logic excudes this problem but I am very interested how you use RDCatch to get the change over get away, since it is impossible for me to see the exact time of this change over upfront

Gavin Stephens schreef op 13-3-2014 3:17:
Be careful you don't have the last item in a log with the exact same start time each day. Otherwise you could end up skipping a day.

You maybe better to have the last item as a segue then the record as the first item in the next log followed by a stop marker of sorts so you're not loading logs at the end of the record. Unless you want the recording to have no song fading when it starts?

You could also use RDCatch for the timed record to get it away from log change over.


Cheers,
Gavin.


----- Original Message ----- From: "Rick" <[email protected]>
To: <[email protected]>
Sent: Thursday, March 13, 2014 12:26 PM
Subject: Re: [RDD] silence at log rotation



I use segue and the last item in the overscheduled log is always a hard timed record but always a different one ofcourse

Gavin Stephens schreef op 13-3-2014 2:00:
How do you guys transistion to the next log? I noticed the bigger teh log the longer the delay so I always use segue to the next log.



----- Original Message ----- From: "Dan Gruner" <[email protected]>
To: "Rick" <[email protected]>
Cc: "User discussion about the Rivendell Radio Automation System" <[email protected]>
Sent: Thursday, March 13, 2014 11:36 AM
Subject: Re: [RDD] silence at log rotation


I have exactly the same issue - although the silence tends to vary from anything up to 10 secs. Very annoying!

Dan Gruner
Loud Audio

Office: 01963 406102
24hr Mobile: 07590 044386

On 12 Mar 2014, at 23:07, Rick <[email protected]> wrote:


On a dual core on 10% CPU I have about 10 seconds of silence at 00:00 when the log rotates to the next day. I am sure others have solved this a long time ago, so perhaps anybody can tell me how to solve this or share his solution?


_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev


_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev



_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Reply via email to