Re: [Flightgear-devel] That blaring voice...

[Wayne B. <wlb...@gm...>]

>the ATIS should only generate audio if a radio is tuned to an ATIS frequency.
>If not, I'd consider it as a bug.

This is correct and should not be changed.

>there were visual impaired users of flightgear

Yes, I remember some of this conversation and it was agreed to try to be more aware of the needs of all members of the community.

Maybe an automatic notification vocal stating a quick way to turn on impairment resources would be the way to go at startup, with the option to turn off the notification on future startups.

Wayne

________________________________
From: Torsten Dreyer <to...@t3...>
Sent: Monday, September 30, 2024 1:52 AM
To: fli...@li... <fli...@li...>
Subject: Re: [Flightgear-devel] That blaring voice...


IIRC (it's been a long time since I added the TTS system),
the ATIS should only generate audio if a radio is tuned to an ATIS frequency.
If not, I'd consider it as a bug.

That’s correct and working, but I think many aircraft default tune COM1 to nearest airport’s ATIS, so often once avionics power-up, either manually or through auto-start, the ATIS voice begins ‘immediately’.
Great, sounds correct to me.


The "welcome aboard" thing is a different thing, there should be a property
somewhere that controls if chat/help messages are generated as speech.

Right, and that option exists and even has a UI I think, but defaults to ON for reasons of accessibility. We could default to OFF and add a startup screen tip to enable voice readback?

A while ago, there were visual impaired users of flightgear, not sure if that behavior was an outcome of the discussion back then.

We should make a wise decision here.

Torsten