I may not be understanding, but we always use Riv dropbox importation for our library with no issues. I also run rdimport for programs downloaded from another source. At the top of each hour, I make the legal ID a hard start/make next and over fill the hour with songs. We place any longer or critical programs earlier in the hour so there is no chance of long overruns, but it never cuts off any audio file. It just won't play anything that won't be able to start before the top of the hour, so extra songs at the end are skipped. This causes our legal ID to vary by a few seconds to a couple minutes after the TOH, but we find this to be trouble free. We don't air any programs longer than 57 min.
I used to play a TOH time announcement with a hard start/start immediately and then the legal ID which was very precise, running a fade down macro in Aux Log for each hour but some listeners wondered why we faded out songs so we dropped that. Tom Van Gorkom Radio Esperanza Engineering, KRIO AM/FM, KOIR FM Office: 956-380-8150 Cell: 865-803-7427 Rio Grande Bible Institute 4300 S US Hwy 281 Edinburg, TX 78539 On Mon, Mar 5, 2018 at 8:09 AM, David Backovsky <[email protected]> wrote: > Yeah, I've already found this issue before, so I changed almost all > transitions to Play instead of Segue. From what I understood segue can > interrupt, so it has two meanings you can edit "segues" manually on a track > by track basis, or set "segue" transitions which fade but also interrupt > (if i understood correctly). I don't take risks with logs, so I add a > manual log chain with RDLogEdit everyday, we had continuous issues with > automatic log chaining and I don't trust it. If you know how to schedule a > log chain event in a clock please let me know... > > We play News at the top of every hour from 11 - 18, so I have a BBC style > countdown that interrupts the previous event and then goes into the news. > How would I make a long fade on that event, manually inside the cart/cut or > event? Or is it a segue transition (and you set a long "manual" or "forced" > segue in RDAirplay settings? > > Best, > > David > > On Mon, Mar 5, 2018 at 2:58 PM, <[email protected]> wrote: > >> >> Are you using "segue" or "play" transitions? If you're getting unexpected >> transitions from one event to the next, unexplainable by the presence of >> timed events in your log, try changing all "segue" transitions to "play". >> >> Re: hard starts at the top of the hour: do they absolutely have to be >> right at the top of the hour? If so, you'll need to put some sort of "fill >> event" at the end of each hour, such as instrumental music or an >> old-fashioned interval signal (e.g "Shiroka strana moya rodnaya") and set >> the fade time to three or four seconds to make a gentle fade-out. >> >> At WSCS and the other WCN stations, there is exactly one hard start each >> day, in the middle of the night, preceded by a long piece of fill music; >> the rest of the day is programmed to time out naturally as close as >> possible to the top of each hour. This works, but not so well that we would >> be able to catch CBS news live at the top of the hour. >> >> Oh, and don't put a hard start or a make-next anywhere near midnight, >> unless you know what you're doing. I don't know how many times I've had >> calls from people wondering why their stations were running Wednesday's log >> on Tuesday. >> >> >> Rob >> >> -- >> Я там, где ребята толковые, >> Я там, где плакаты "Вперёд", >> Где песни рабочие новые >> Страна трудовая поёт. >> >> On Mon, 5 Mar 2018, D. B. .B. B. wrote: >> >> Thanks for the replies. We don't use dropboxes, we import files directly >>> from the local drive. I always check segment length when importing >>> against >>> the original file. I am 100% sure the files are interrupted, because >>> later >>> they would play at their correct length. I overschedule music and I >>> tried to >>> use Hard Times - Make Next to ensure that priority events played out. >>> But I >>> think that the best solution is to give extra breathing room in the >>> clocks >>> to important events. I try to use "anchors" on top of the hour like a >>> Hard >>> Time - Start Immediately with a news countdown or a second of silence to >>> anchor the broadcast. I'm not sure how to make it when overscheduling so >>> that the broadcast is on schedule without at least a song at the end of >>> the >>> hour being interrupted by an "anchor" event. >>> >>> Best, >>> >>> David >>> >>> On Mon, Mar 5, 2018 at 12:49 PM, <[email protected]> wrote: >>> On Sun, 4 Mar 2018, D. B. .B. B. wrote: >>> >>> I am working with Rivendell for a community radio >>> station and have >>> encountered some issues with tracks - songs and >>> shows - being interrupted >>> halfway through. It sometimes happens that a longer >>> segment is simply >>> interrupted without warning and another starts >>> playing. This happens for >>> both hard time and non-hard time events. Can one >>> make an event >>> uninterruptable? >>> >>> >>> Are the events truly being interrupted? Or have the audio files >>> somehow been truncated? >>> >>> What happens if you try to play one in rdlibrary? Does the >>> actual length of the file correspond to the length Rivendell >>> claims? >>> >>> At stations where long files were uploaded to a dropbox via the >>> Internet, I used to see rdimport grab a file while it was still >>> uploading, resulting in a truncated file. I stopped setting up >>> dropboxes in Rivendell, instead running a Perl script to invoke >>> rdimport only after asertaining that the last modification time >>> on the file isat least 30 seconds ago. >>> >>> >>> Rob >>> >>> -- >>> Я там, где ребята толковые, >>> Я там, где плакаты "Вперёд", >>> Где песни рабочие новые >>> Страна трудовая поёт. >>> >>> >>> >>> I try to schedule as closely as I can but we have very >>> different lengths of songs in our library, and it >>> seems that often instead >>> of skipping the next song it will jump into it >>> interrupting. This is a >>> serious concern because we have some original >>> content that has now been >>> twice interrupted mid-air without warning. What >>> could be the cause of this >>> and how can this be avoided? >>> >>> Thanks, >>> >>> David B. >>> >>> >>> >>> >>> >>> > > _______________________________________________ > 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
