ElvishArtisan / rivendell

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

Make default transition type per log machine/per host and not per host. #896

Open zotz opened 1 year ago

zotz commented 1 year ago

In rdvairplayd and rdairplay, allow for the default transition type to be per log machine and not just one overall transition type for the host.

Currently:

rdadmin->manage hosts->edit host->rdairplay has a dropdown called "Default Trans. Type" which has 3 options: Play, Segue, Stop.

I propose having this option being distinct for the main and bots aux log machines as well as the vlog machines.

One possible crazy thought: Have this an option come from the grid or hour that created the loaded log if that is how it was created. (I don't think this makes sense but wanted to include it in case it prompted a bright idea for someone.)

ElvishArtisan commented 1 year ago

In rdvairplayd and rdairplay, allow for the default transition type to be per log machine and not just one overall transition type for the host.

Interesting idea. I could see this as being useful in some scenarios.

One possible crazy thought: Have this an option come from the grid or hour that created the loaded log if that is how it was created. (I don't think this makes sense but wanted to include it in case it prompted a bright idea for someone.)

That's a bit out-of-scope for those data sources. 'Default transition' is a configuration setting, not a scheduling attribute. Mixing those two together could get confusing real quickly.

While we're canvassing the options, one of the new features in v4.x is Bypass Mode, which makes it possible to generate a complete log (including transition type and hard times) from external data.