Add a priority setting option to the voice broadcast function

[FrSky-GX]

Whether it is necessary to set priority for voice broadcasting, it is specific data broadcasting that can be executed first, welcome your comments.

[mawzthefinn]

Definitely useful, you want something like a VFR warning to override a general playback.

[bsongis-frsky]

We can do that, but it raises 2 questions:

1) what is the list of audio prompts which would have this "priority flag"

• VFR warning
• RSSI warnings
• SWR warning

2) what would we do when such a prompt is requested?

• we clear the queue (existing prompts in the queue will be all discarded)
• we continue the current prompt (but remember a sentence can be cut)
• we introduce a new layer in the audio mixer for those prompts and they are played in the same time, but louder

[strgaltdel]

which kind of announcements should get "priority flags" ? only predefined ones like tx undervoltage / RSSI Warninsg etc.. or even user defined ones? (like via LSW "rules" triggered SF's)

my personal understanding:

i would like to get alarms (and warnings) as soon as possible.

in a non existing "perfect world":

• there would be 4 different flags to categorize priorities

(1) highest / alarms, "desaster pending", like extreme low tx Voltage / RSSI / VFAS Value (2) urgent / warnings, "pay attention, something maybe wrong" like low Voltages / RSSI's ... (3) standard / informational, like typical, customized telemetry value callouts (4) lowest prio/ redundant character, like "gear down" announcement after activating a switch, more a "plausibility check"

just my 2 cents:

• as soon as an alarm occures, active or queued standard / low prio announcements should be terminated, Alarm should be played immediatly
• in case an alarm is triggered during a "warning call out", please play the warning until end and then play the alarm(s); maybe an overlayed "acknowledge signal" for a pending alarm would be fine >> airbus cockpit warning sound ...(-;
• in case active warnings and alarms are in a queue, play them in priorized order
• dependent on changing values, an alarm (prio 1) could be degraded into a warning (prio 2), i would NOT say that a new callout is needed
• in case a formerly triggered warning (prio 2) or alarm (prio1) vanishes completely, another "OK" acknolegememnt would be fine
• as mentioned, freedome for users to priorize even SF-callouts would be fine
• maybe a new SF could be introduced: "play all active Alarms & Warnings" (prio 1&2 callouts) so after a minute or more after getting Alarms / warnings, the user could cross-check problematic situations if he is in question of "still active warnings"

[bsongis-frsky]

I reopeen this issue which is not completed. I am still don't know what should be done, there are too many use cases. The proposal from @strgaltdel seems to me too much complex. I would like something easier ...

[Wolepo]

It would probably suffice if the current announcements were turned down and the warning overlaid. The current announcement could then be over, but that would be the lesser evil.

[bsongis-frsky]

Agreed

[Wolepo]

Addendum: Pilots should be able to declare voice announcements as important in addition to the warnings from the system in the special functions.