Segue from playlist to overlay

[andrerotgans]

Hi Bernd,

Two questions about the same thing. I probably just do something wrong, but can't figure out what.

1. I've scheduled commercial overlays at the top of the hour, ending at **.59.44. When segueing from the running playlist to this overlay, it uses a fade of three seconds to a rather low level, after that the overlay will start. The overlay-countdown counts down to the start of that fade. Is there a way to shorten/adjust that fade ? At this moment is sounds rather foolish, as if somebody first bring down the fader to a very low level and starts the commercials.

2. Almost the same thing happens at the bottom of the hour. I've scheduled a local-news-overlay, starting 'soft'. The overlay will show 180 seconds in advance, I allow it to start early and it has a max start delay of also 180 seconds. I set the mixing time to zero in order to let it start at the 'next' cue of the song playing at that moment. That way this overlay will start somewhere between **.27 and **.33, but it will not interrupt the running song. Problem : it isn't starting at the 'next' cue of the running song, but will wait until the 'out' cue. This is not what I want, and also not what is set up in the mixing time dialog, as far as I know ?

I'm using v3.0.11.47

Kind regards,

André

[radio42]

to 1)
the track currently playling determines the effective Fade-Out length being used!
This is either the "Manual Fading (Fade-Out Length)" from the general mixing settings or the specific being set per media type.
By default this length is 5 sec.
The 'Mixing Time' of the overlay then determines the effective start of the overlay playout.
Start of Overlay = FadeOutLength - MixTime
E.g. when the Fade-Out length is 5 sec. and the Mixing Time is 1000 ms - then the current track is faded out for 4 seconds until the overlay effectively starts.
As such you might control the Fade-Out time per media type.

2)
Oh yes, there is a shot bug in it, which only happens (as you described), if the 'Soft' overlay is effectively triggered early.
When you set the Mixing Time to zero (0) and the overlay would be triggered regular (late) all is fine, but if it's triggered early then it indeed doesn't start with the Next cue point, but with the Cue-Out cue point (which is wrong).

I'll fix that in the next release!

[andrerotgans]

Thanks, I'm gonna experiment with #1 and I'm looking forward to the update for #2 !

Regards,

André

[radio42]

In v3.0.11.48 the Program/Overlay Mixing was optimized/enhanced:

The 'Mixing Time' defines the mix time in milliseconds between two programs/overlays (which is the overlapping time of the last track of the previous playlist and the first track of the next playlist/overlay).
When a new script is started 'Soft' the first track of that script is played this milliseconds before the last track of the current script is cued out.
Set to 0 to start the next program with the 'Next' cue-point of the last track of the previous script.
When the program/overlay is started 'Fixed' the fade-out time is by default determined by the mixing settings of the current playing track of the playlist and this value defines the segue (overlapping) time. But when using a negative value this will now define a fixed fade-out time!

Meaning, if you define a negative 'Mixing Time' with an 'EndsAt' entry, the fade-out and mixing uses exactly this time:
Example:
When the 'Mixing Time' is set to -2000 this means:
The total fade-out and mixing time will take 2 seconds (after 60% of that total time the next track is being played).