Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Consolidate Next Transition actions #74

Open
arikorn opened this issue Feb 13, 2025 · 1 comment
Open

Feature: Consolidate Next Transition actions #74

arikorn opened this issue Feb 13, 2025 · 1 comment
Milestone

Comments

@arikorn
Copy link

arikorn commented Feb 13, 2025

In my struggles to make clear names for the various next transition/on air action (and feedback, to a lesser extent), I've come to the conclusion that consolidating them into two actions should make things clearer and more consistent:

Action 1: 'Next Transition: Set "next" status (KEY, DSK, BKGD)
Options:
Layer: KEY, DSK, BKGD
Action: On, Off, Toggle, On PVW, Off PVW.
Description: 'On/Off/Toggle is equivalent to pressing the button on the GoStream, so its consequence depends on the state of "On Air", the last two options ensure that the behavior in PVW occurs independently of the state of "On Air"'

(N.B. the last two options will be disabled if BKGD layer is selected.)

Action 2: 'Next Transition: Set "On Air" Status'
Options:
Layer: KEY, DSK
Action: On, Off, Toggle, On PGM, Off PGM.
Description: 'On/Off/Toggle is equivalent to pressing the button on the GoStream, so it will affect both PVW and PGM, the last two options ensure that the behavior in PGM occurs independently of the state of the "Tie" button'

If approved, this will be included in my PR on Next Transition actions (#45, #54, #55, #66, etc.)

@fa1k3n
Copy link
Collaborator

fa1k3n commented Feb 14, 2025

agree with this. BUT these action should start with "MixEffect" not "Next transition" ....
And the old actions controlling these keys should be marked deprecated regardless of their current working status

@fa1k3n fa1k3n added this to the V1.4.0 milestone Feb 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants