ElvishArtisan / rivendell

A full-featured radio automation system targeted for use in professional broadcast and media environments
208 stars 64 forks source link

(3.x) Music Beds and Voice Overs #340

Open deltecent opened 5 years ago

deltecent commented 5 years ago

There is a discussion on Facebook that has brought up how to handle music beds with voice overs.

I started on a "Fade and Go" macro that didn't quite work as expected.

Michelle Bradley did a nice picture of what people are wanting:

49344420_10219113706534617_768094457814843392_n

This brings up a couple of questions:

1) Is the best way to handle this through a macro? 2) Is the best way to handle this through another segue type, one that segues to the next element in the list and fades whatever is still playing? 3) Something else?

I would love to see this feature in 3.0, since we want to use it without music beds, but I understand it will probably need to wait for 3.1+.

Fred, if you would weigh in on this, I can start re-working in the direction you recommend.

deltecent commented 5 years ago

After thinking about this, what about adding 2 new segue types:

1) BUMPER - I do not know if it possible to do this, but when the cart with a BUMPER segue type hits its segue marker and the next event fires, reset its segue marker to the length of the next event and its length to that time + 1 second. This could be used for carts over bumper music. What would be even better is to make the 1 second time configurable so the BUMPER segue type could also be used for donuts. 2) TALK - When selecting a cut, find the least recently played cut that will fit in the next event's talk time. This could be used for playing a cart over music intros.

deltecent commented 5 years ago

I got quite a way along with the TALK segue type but ran into a problem. I was assuming I could grab the talk length from the next event, but since the cut isn't determined until the event is started, there's no way to know what the talk length is actually going to be.

setEvent()
{
  if trans type is TALK {
    get a cut that's shorter than the talk length of the next event
  }
}

Since it's possible for the next event to have multiple cuts, no can do. Thinking....