[RDD] Major Problems

[Mark Murdock]

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
m...@celebrationradio.com
Website

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Major Problems

[Jacob Niemand]

Mark,

Here’s the way I do it:

I have one event in one clock that is scheduled in all my grids.

The one event:
The event “Music Import” has use hard start time checked and make next
selected.
Then under IMPORT has “from music” selected.  Import carts scheduled 00:00
prior and 59:59 after.  Imported carts have a “segue” transition

That is the one event in my one clock.

Rivendell will then make the “music import link” at the top of every hour
in the log the have a hard start time of the top of that hour with a make
next cue.

It works great for me!
Jake





On Mon, Dec 30, 2019 at 10:51 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
>
> m...@celebrationradio.com
>
> Website 
>
>
> ___
> Rivendell-dev mailing list
> Rivendell-dev@lists.rivendellaudio.org
> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
>
-- 
96.7kram
P.O. Box 332
109 North 1st Street
Montevideo, MN 56265
__
320-321-9671
www.967kram.com
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Major Problems

[Robert Jeffares]

Hi Mark,

go into RDLogManager and edit events and delete the event you created 
for the top of the hour ID.


Create a new event Top of the Hour ID or whatever you want to call it.

Check at the Hard Start Time and Make Next AND touch Services List and 
make sure your service [default Production] is selected


by moving it from left to right.

Sometimes services are in there twice, delete both tap save then re 
enter the Service then tap save.


I give timed events a Red colour.

tap save and exit.

Sounds like you have just one Clock. Check the Event is there at TOH

Rebuild the logs

Bob should be your fathers brother.


Comment:

Look in Services list to see whats there now.

By delete and re enter you eliminate any MySQL or MariaDB issues that 
may have accumulated as you fiddled.


regards

Robert



On 31/12/19 5:51 am, 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. 16^th St.

Merced, CA 95340

(209) 723-1015

m...@celebrationradio.com 

Website 


___
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

Re: [RDD] Major Problems

[Jonathan Cohen]

I’ve seen this very behaviour in 3.2.0 but I’ve only tested it with my rather 
Rube Golberg like Ubuntu build, so assumed it was that. Rivendell gets to the 
top of the hour and on the “make next” event does a “core dumped" qstring.h, 
line 699 error. I’ve opened a ticket but not yet been able to do a backtrace.

 
While I’m a bit out of my depth here, if this happens on 3.2.0 maybe try 2.19.2 
and see if the same thing happens?

 
Best regards

Jonathan

First 105.1 FM Oxford, UK

 
From: rivendell-dev-boun...@lists.rivendellaudio.org 
[mailto:rivendell-dev-boun...@lists.rivendellaudio.org] On Behalf Of Mark 
Murdock
Sent: 30 December 2019 16:51
To: 'rivendell-dev@lists.rivendellaudio.org'
Subject: [RDD] Major Problems

 
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

m...@celebrationradio.com <mailto:m...@celebrationradio.com> 

Website

 

___



Rivendell-dev mailing list



Rivendell-dev@lists.rivendellaudio.org 
<mailto:Rivendell-dev@lists.rivendellaudio.org> 



http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev 
<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

Re: [RDD] Major Problems

[Rob Landry]

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

m...@celebrationradio.com

Website

 


___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Major Problems

[Pab Sungenis]

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, 
"rivendell-dev-requ...@lists.rivendellaudio.org" 
 wrote:










Send Rivendell-dev mailing list submissions to
rivendell-dev@lists.rivendellaudio.org

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
rivendell-dev-requ...@lists.rivendellaudio.org

You can reach the person managing the list at
rivendell-dev-ow...@lists.rivendellaudio.org

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: <23ee7b02-9d2c-4199-bd84-519f82ec1...@gmail.com>
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 <41001...@interpring.com>
To: Mark Murdock 
Cc: "'rivendell-dev@lists.rivendellaudio.org'"

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
> 
> m...@celebrationradio.com
> 
> 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: <7fac868e430b7f170f6569e7c7ad3d902e53d9c9.ca...@linux.com>
Content-Type: text/plain; charset="UTF-8"


On Mon, 2019-12-23 at 13:18 -0500, Fred Gleason wrote

Re: [RDD] Major Problems

[Fred Gleason]

On Jan 1, 2020, at 12:39, Pab Sungenis  wrote:

> 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. 

Instead of a crontab event, you could also use a Macro Cart event in 
rdcatch(1), which gives you to-the-second resolution while also keeping things 
within the Rivendell database. (Things that rely on external commands like 
crond(8) have a tendency to get mislaid when doing hardware upgrades or other 
’system level’ changes).

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Major Problems

[Chuck]

  Confirming that we also put the ID as the first event of the next
hour, not the last event of the previous hour.  We were getting
occasional dropped ID's at the midnight cross-over if it was the last
event, but no drops when it's the first of the next hour.

  We also use 2 logs--Main is music with about 430 songs for a day and
an 'advance to' marker to move the playlist along so it is close to
midnight for the crossover.  Stopsets and program length material is in
Aux 1 with macro commands for switching between them.  How we do this
is explained here:


http://caspian.paravelsystems.com/pipermail/rivendell-dev/2017-March/025572.html

  Using 2 logs keeps us from having to spend man hours with log timing-
-as an all-volunteer station, we just do not have that kind of
manpower.  Log loading takes about 1 second with our music and
spot/program load, which--once at midnight--is no big deal for us (we
are a non-comm), but the cron job for log loading may be something we
should look at.

--Chuck

On Wed, 1 Jan 2020 17:39:22 + (UTC)
Pab Sungenis  wrote:

> Subject: Re: [RDD] Major Problems
> 
> 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.?
> 

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

[RDD] Major Problems getting worse

[Mark Murdock]

Thanks very much to the couple of people who have offered ideas for solving my 
Legal ID scheduling issue. Now RDLog Manager is no longer importing my music 
logs. The logs generated by Music1 are there, and the setup is correct in 
RDAdmin, but now it does not show that there is a music log to import. When I 
test the import in Admin it works fine. I'm almost ready to quit messing with 
Rivendell. Any ideas?

Thanks,

Mark Murdock
KAMB
90 E. 16th St.
Merced, CA 95340
(209) 723-1015
m...@celebrationradio.com
Website

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Major Problems getting worse

[Fred Gleason]

On Dec 30, 2019, at 19:08, Mark Murdock  wrote:

> Thanks very much to the couple of people who have offered ideas for solving 
> my Legal ID scheduling issue. Now RDLog Manager is no longer importing my 
> music logs. The logs generated by Music1 are there, and the setup is correct 
> in RDAdmin, but now it does not show that there is a music log to import.

What color are the ‘Available’ and ‘Merged’ indicators in the Generate Log 
dialog?

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev