Re: [RDD] ID Scheduling Problem Resolved

[Fred Gleason]

On Dec 29, 2020, at 15:12, Mark Murdock  wrote:

> After making these modifications the logs are importing perfectly! If you’re 
> having any similar problems you may need to customize your import template 
> also. Go to this page for info about “Inline Event Scheduling Parameters:”
>  
> http://opsguide.rivendellaudio.org/html/sect.rdadmin.manage_services.html#sect.rdadmin.manage_services.general.inline_event_scheduling_parameters
>  
> 
A little extra background here: Rivendell’s log importer has always had the 
ability to read event duration, but prior to the addition of the “Inline Event 
Start/Length” mode, not much use was actually made of the data so read. 
However, if you’re using this new mode, supplying accurate event durations will 
be critical for getting good results.

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

[RDD] ID Scheduling Problem Resolved

[Mark Murdock]

Y'all may recall that on the 23rd I posted about a problem with Rivendell 3.5 
importing our Music 1 logs correctly. The import using RDLogManager was failing 
due to some issue with our Voice Track markers. I made sure the "Inline Event 
Start/Length" value (in RDAdmin - Manager Services) was changed from "Relative 
Position" to "From Scheduler File." Also I made sure that the "Insert Voice 
Track String" was "VT." Still there was a problem. After looking at our 
database and Music 1 log, Fred gave me this solution:

==
Your Music1 schedule file has the event length field in a slightly different 
location from that called for in the Music1 importer layout. To fix it, run 
RDAdmin and open the configuration for the 'Production' service. Then, in the 
'Music Data Import' section, touch the 'Copy to Custom' button, then change the 
following settings:

Length - Hours: 60 : 1
Length - Minutes:62 : 2
Length - Seconds:65 : 2

and then touch 'OK'.

After doing that, your sample log data for 3 Jan 2021 appears to generate 
perfectly.
===

After making these modifications the logs are importing perfectly! If you're 
having any similar problems you may need to customize your import template 
also. Go to this page for info about "Inline Event Scheduling Parameters:"

http://opsguide.rivendellaudio.org/html/sect.rdadmin.manage_services.html#sect.rdadmin.manage_services.general.inline_event_scheduling_parameters

Thanks much to Fred!

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] ID Scheduling Problem

[Fred Gleason]

On Dec 23, 2020, at 11:52, Mark Murdock  wrote:

> We just updated yesterday to 3.5, and just discovered that the schedules 
> created for the new year are putting all of the legal IDs at the end of the 
> log. We use Music1 for music and traffic scheduling, and the IDs are inserted 
> by RDLogManager. This has been working fine until now. If I look at the log 
> in RDLogEdit the Estimated Time for each song and item is there, but if I 
> bring up the log in the Voice Tracker all of the items are scheduled for 
> “00:00”00.” The text log generated by Music1 looks fine. In RDAirPlay the log 
> listing is blank in the field for Estimated Time. Obviously we need to 
> resolve this problem right away. Any ideas?

The schedule file parser in v3.5.0 has been significantly ‘tightened up’. It’s 
a long story, but in previous versions, there were two ways that placement for 
‘inline events’ (such as voice tracks, marker inserts and such) could be 
calculated: explicitly, or by relation to the surrounding events; with the 
parser automatically determining which approach to use. This approach turned 
out to be fraught and difficult to troubleshoot as one was never sure which 
approach was actually being used.

So, as of v3.5.0, you need to explicitly state which approach should be used, 
on a per-Service basis. You can find detailed information about these settings 
in the Operations Guide, online at:


http://opsguide.rivendellaudio.org/html/sect.rdadmin.manage_services.html#sect.rdadmin.manage_services.general.inline_event_scheduling_parameters

It’s quite likely that your issue will be solved by changing the Inline Event 
settings.

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

[RDD] ID Scheduling Problem

[Mark Murdock]

I sent out an email about this a few minutes ago with a screenshot, but it was 
too big and I got an automated reply that it had to be approved by the 
moderator, so here's another message without the screenshot.
We just updated yesterday to 3.5, and just discovered that the schedules 
created for the new year are putting all of the legal IDs at the end of the 
log. We use Music1 for music and traffic scheduling, and the IDs are inserted 
by RDLogManager. This has been working fine until now. If I look at the log in 
RDLogEdit the Estimated Time for each song and item is there, but if I bring up 
the log in the Voice Tracker all of the items are scheduled for "00:00"00." The 
text log generated by Music1 looks fine. In RDAirPlay the log listing is blank 
in the field for Estimated Time. Obviously we need to resolve this problem 
right away. 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