You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the activation flow for “On Air” mode follows this logic:
flowchart TD
A[Activate On-Air] --> B{Before Start Time?}
B -- Yes --> C[Show Modal: 'Activate Rundown?']
C --> D[Reset and Activate]
B -- No --> E{Past end time?}
E -- Yes --> F[Show warning modal]
F --> G[Direct Activate]
E -- No --> G[Direct Activate]
Loading
In non-linear productions, where timing is less critical than in linear productions, the current flow can cause unintended disruptions, as it isn’t clear from the modal shown before the expected start time that the rundown will also reset. Whereas in a linear production the user may likely not be aware of this mechanism and is likely to perform a manual reset before activating anyway.
The goal is to provide a safer and more transparent activation process, by allowing users to decide if they want to reset and activate, or just activate the rundown while keeping the playhead position in place.
Proposal
To improve this experience, we propose updating the activation flow to offer the user a choice between Activate “On Air” and Reset and Activate “On Air”. The default action should be Activate ”On Air” to avoid an unintended rundown reset.
In all modals that currently trigger the resetAndActivate action, we propose updating the UI to show two options:
Activate “On Air” - Activates “On Air” mode without resetting the rundown.
Reset and Activate “On Air” - Activates “On Air” mode and resets the rundown.
By selecting Activate “On Air”, the playhead position remains and avoids any disruptive changes. Choosing Reset and Activate “On Air” proceeds with the existing reset-and-activate functionality for cases where users explicitly want to reset the rundown.
This change aims to improve the user experience by:
Providing a non-disruptive default activation option.
Allowing users to reset only when explicitly chosen.
Keeping the behavior consistent in every phase of a production
Process
The Sofie Team will evaluate this RFC and open up a discussion about it, usually within a week.
RFC created
Sofie Team has evaluated the RFC
A workshop has been planned
RFC has been discussed in a workshop
A conclusion has been reached, see comments in thread
The text was updated successfully, but these errors were encountered:
Hello!
Thanks for this RFC! Sorry for not replying sooner, we've been super busy for the past weeks.
Our initial thoughts on the suggestion is that it looks good, but we'll need some more time to check in with our producers.
I estimate that we should be able to get back to you with a definite reply on January the 17th.
/Rannveig (NRK Sofie team)
About Me
This RFC is posted on behalf of the BBC.
Use Case
Currently, the activation flow for “On Air” mode follows this logic:
In non-linear productions, where timing is less critical than in linear productions, the current flow can cause unintended disruptions, as it isn’t clear from the modal shown before the expected start time that the rundown will also reset. Whereas in a linear production the user may likely not be aware of this mechanism and is likely to perform a manual reset before activating anyway.
The goal is to provide a safer and more transparent activation process, by allowing users to decide if they want to reset and activate, or just activate the rundown while keeping the playhead position in place.
Proposal
To improve this experience, we propose updating the activation flow to offer the user a choice between Activate “On Air” and Reset and Activate “On Air”. The default action should be Activate ”On Air” to avoid an unintended rundown reset.
In all modals that currently trigger the
resetAndActivate
action, we propose updating the UI to show two options:By selecting Activate “On Air”, the playhead position remains and avoids any disruptive changes. Choosing Reset and Activate “On Air” proceeds with the existing reset-and-activate functionality for cases where users explicitly want to reset the rundown.
This change aims to improve the user experience by:
Process
The Sofie Team will evaluate this RFC and open up a discussion about it, usually within a week.
The text was updated successfully, but these errors were encountered: