Another trick I’ve used is to set a cron event
to send an RML LL command to RDAirplay to load the next day’s log every night
at 11:58PM, then moved the legal ID from the last event of the hour to the
first, and made the midnight one not timed.
This way any over-scheduled music will be dumped when the next day’s log is
loaded, and the next event after whatever is playing at 11:58 pm will be the
legal ID leading into the midnight hour.
This also has the added benefit of bypassing the need to chain logs, especially
on slower machines. When I was using chained logs, we could have up to ten
seconds of dead air while RDAirplay loaded the next day’s log. Now that happens
in the background while music is playing, allowing for a seamless transition.
Get Outlook for iOS
On Wed, Jan 1, 2020 at 12:01 PM -0500,
"[email protected]"
<[email protected]> wrote:
Send Rivendell-dev mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Rivendell-dev digest..."
Today's Topics:
1. Happy New Years (Workino)
2. Re: Major Problems (Rob Landry)
3. Re: RSS via dropbox [WAS: RDCatch URL Invalid] (David Klann)
----------------------------------------------------------------------
Message: 1
Date: Tue, 31 Dec 2019 22:20:53 +0100
From: Workino
To: Rivendell-Dev
Subject: [RDD] Happy New Years
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
I would like to wish to every one in this list a really great Happy New Year
and a big thanks to Fred for his great job and support !!
?? Happy New Years ??
Gabriele
Sent from my iPhone
------------------------------
Message: 2
Date: Wed, 1 Jan 2020 09:40:24 -0500 (EST)
From: Rob Landry <[email protected]>
To: Mark Murdock
Cc: "'[email protected]'"
Subject: Re: [RDD] Major Problems
Message-ID:
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Make the legal ID an event in your clock, and schedule it at the end of
each hour (e.g. :59:50.0) as a Make Next timed event.
The one exception to this is the 11 PM hour; you can't run a Make Next
event so close to midnight without inviting trouble, so leave that one
untimed.
Rob
--
?????? ????? ????? ??? ?????? ???????
? Linus ??????? ??? ???? ??????;
??? ???????? Stallman ?? ???????? ??????,
?? ???? ? ?? ??????? ??? ?????????.
On Mon, 30 Dec 2019, Mark Murdock wrote:
>
> We were planning to put Rivendell on the air for the first time officially
> next Monday, but unless I can solve a major problem that came up Friday,
> it?s not going to happen. We use Music1 for our scheduling software, and
> it?s set up to generate Rivendell schedules, and seems to work fine. The
> trouble seems to be with the legal ID at the top of the hour. We
> overschedule our hours by a song or two, and we need the ID to run at or
> near the top of the hour after whatever is playing from the previous hour,
> and then throw out any songs or elements that are left over from the
> previous hour and go into the new hour. Scheduling the ID in Music1 had the
> ID running after everything from the previous hour had finished, obviously
> putting the ID too late. So, I tried scheduling the ID in RD, setting the
> ?Start at? time at the top of the hour and ticking the ?make next?
> selection. When I play it back in RDAirPlay and it gets to the ID, it will
> start to play it, and then totally crashes. RDAirPlay just quits. I?ve
> observed this several times. Maybe I don?t understand how the ?hard time?
> event works? I set the ?transition type? to Segue, if that makes any
> difference.
>
> ?
>
> Thanks for any help!
>
> ?
>
> Mark Murdock
>
> KAMB
>
> 90 E. 16th St.
>
> Merced, CA 95340
>
> (209) 723-1015
>
> [email protected]
>
> Website
>
> ?
>
>
>
------------------------------
Message: 3
Date: Wed, 01 Jan 2020 10:32:43 -0600
From: David Klann
To: Fred Gleason , User discussion about the
Rivendell Radio Automation System
Subject: Re: [RDD] RSS via dropbox [WAS: RDCatch URL Invalid]
Message-ID: <[email protected]>
Content-Type: text/plain; charset="UTF-8"
On Mon, 2019-12-23 at 13:18 -0500, Fred Gleason wrote:
> On Dec 23, 2019, at 12:02, David Klann wrote:
>
> > Are you saying that RDCatch might someday be capable of downloading
> > arbitrary
> > audio files using something like RSS links? I ask because I've written a
> > Rivendell add-on that allows users to specify a bunch of RSS feeds to
> > watch,
> > and (using cron) poll those URLs for new content (usually hourly), and
> > download the audio files to matching Rivendell dropboxes. I've been
> > recently
> > thinking about how this might be more tightly integrated into Rivendell
> > proper. The most likely place seems to be RDCatch.
>
> It?s unlikely that this functionality will ever exist in rdcatch(1), mostly
> because that module has a baked-in assumption that all audio operations are
> ?one-to-one? ?e.g. a Download comes from exactly one source file and is
> transferred to exactly one cart/cut destination.
>
> However, this sort of thing could fit well as a dropbox capability, as
> dropboxes *do* know how to deal with a ?many-to-many? world. In this case,
> instead of a Path Spec, we could take a URL that references an RSS object.
> Disposition of the referenced RSS enclosures could be handled just like any
> other dropbox setup.
>
> Anything else I?m missing?
>
Catching up and cleaning out my inbox for the new year...
Good point about incorporating such behavior into dropboxes! Maybe not missing
things, but ...
During a few years' experience with fetching audio files using RSS feeds, it
has become clear to me that the data behind the links do not always represent
reality. In those cases it's good to have thorough logging for
troubleshooting.
Thanks for your thoughts, and for your years of hard work keeping Rivendell
(and other radio station software) up to date and Open!
Best,
~David Klann
------------------------------
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
End of Rivendell-dev Digest, Vol 81, Issue 1
********************************************
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
