Nicholas Gilbert Posted December 3, 2019 at 06:34 AM Posted December 3, 2019 at 06:34 AM Just wanting to report what seems to be a persistent issue in Australian jurisdictions. Voice ATIS is connectible and tuneable, but no audio plays. I suspect it's the text to speech synthesis that is failing. ATIS is handled through Euroscope. No audio plays in AFV nor through vPilot or other clients. Other ATC frequencies work fine. Any ideas? Is there anything client side that can be done, or is it server side only? Link to comment Share on other sites More sharing options...
Nestor Perez Posted December 3, 2019 at 10:43 AM Posted December 3, 2019 at 10:43 AM What happens if you use "YSSY_ATIS" instead of "SY_ATIS"? Me. Link to comment Share on other sites More sharing options...
Nicholas Gilbert Posted December 4, 2019 at 06:21 AM Author Posted December 4, 2019 at 06:21 AM It forces SY_ATIS in AFV. I.e, if I type in "yssy_atis" and then the freq "126.250" into the dialogue boxes, it forces SY_ATIS in the afv window when it loads. But tbh, I don't think that's the issue, as it has previously worked when it has done that. The no voice issue hasn't been a problem since launch, only noticed it in the last couple of weeks. Hence why I thought it might be an issue with the voice synthesis for our region specifically. EDIT: Actually, just checked some others (LGAV_ATIS, EGHQ KRNO) and no others work except for KRNO, which I [Mod - Happy Thoughts]ume is because the US uses vATIS. When I checked the other day some European atis were working but it seems not today. Link to comment Share on other sites More sharing options...
Nestor Perez Posted December 4, 2019 at 08:15 AM Posted December 4, 2019 at 08:15 AM It can definitely be the ATIS Bot indeed. We'll have a look. Thx for the heads up! Me. Link to comment Share on other sites More sharing options...
Sean Harrison Posted December 4, 2019 at 08:57 AM Posted December 4, 2019 at 08:57 AM I use VRC and vATIS almost exclusively on the SYD-1 server. I can’t get a VATPAC atis to play, yet PGUM works fine. Could it be the way VATPAC has set up the back end, eg YSSY_ATIS being forced to SY_ATIS (how could that even work) In AFV if I use PGUM_ATIS that is what I get, not GUM, or UM Sean C1/O P3 Link to comment Share on other sites More sharing options...
Nicholas Gilbert Posted December 5, 2019 at 07:03 AM Author Posted December 5, 2019 at 07:03 AM Not sure if that's the issue, Sean. Putting in KRNO_ATIS shortens it to RNO_atis but it plays back fine. And I've observed the issue more widely at this point than just Australia. Link to comment Share on other sites More sharing options...
Sean Harrison Posted December 5, 2019 at 07:05 AM Posted December 5, 2019 at 07:05 AM Ah ok. My bad. Sean C1/O P3 Link to comment Share on other sites More sharing options...
Gary Oliver Posted December 5, 2019 at 12:53 PM Posted December 5, 2019 at 12:53 PM ATIS bot server had a small sulk... It has since been restarted. Link to comment Share on other sites More sharing options...
Nicholas Gilbert Posted December 9, 2019 at 08:29 AM Author Posted December 9, 2019 at 08:29 AM Can confirm the issue is still extant. The AFV map seems to reliably indicate whether voice is working. For instance, I can get Queenstown in New Zealand voice corectly (NZQN_ATIS) which was an Auto generated atis with no ATC online. All the Australian ATIS (YMML YBBN and YSSY) were not working (one user didn't set the primary frequency for their ATIS but the other two were fine.) ATIS for VHHH and UTTT (Uzbekistan) were both listenable. UTTT was set by ATC but seemed to use the same text to speech voiuce as the auto vatsim ATIS. VHHH was using a different voice. Tested 0825z. Link to comment Share on other sites More sharing options...
Nicholas Gilbert Posted December 11, 2019 at 02:38 AM Author Posted December 11, 2019 at 02:38 AM Any further ideas on this persistent issue? Link to comment Share on other sites More sharing options...
Tristan Garratt Posted December 13, 2019 at 09:15 AM Posted December 13, 2019 at 09:15 AM Any further ideas on this persistent issue? Sadly it looks like VATPAC will have to use text atis for a while. Tristan Garratt VATPAC C1 Link to comment Share on other sites More sharing options...
Nicholas Gilbert Posted December 16, 2019 at 06:34 AM Author Posted December 16, 2019 at 06:34 AM Any further ideas on this persistent issue? Sadly it looks like VATPAC will have to use text atis for a while. Seems resolved today. No idea why or when or how, but they seem to be working today. Link to comment Share on other sites More sharing options...
Recommended Posts