No Audio ] JTAlert 2.16.10
toggle quoted messageShow quoted text
Signals appearing on the application as normal
All alerts enabled
No sound on my install/reinstall, has been Ok on previous versions.
Have restarted from ‘cold’ after reinstall.
All updates (sound/calls) up to date
Volume @ 49%
All sound files installed, no audio after testing individually
Test soundcard – no output
Audio elsewhere OK
App does not appear on audio mixer
I blame Microsoft Windozy, but whatever…
From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of HamApps Support (VK3AMA)
Sent: 29 July 2020 21:30
Subject: [Special] [HamApps] JTAlert 2.16.10 is available #Announcement #NewRelease
The latest JTAlert version 2.16.10 is now available @ https://hamapps.com/JTAlert/
de Laurie VK3AMA
*** Includes Callsign database file version 2020-07-28 (2020-Jul-28)
- Lotw adif files: The QSL_RCVD fields used by LoTW are now treated as
LOTW_QSL_RCVD fields. If the Adif file header indicates the file was sourced
from LoTW, the QSL_RCVD to LOTW_QSL_RCVD translation is automatic.
- Band Activity Display: Has been renamed to Mode Activity Display.
- Windows notification sounds: The single sound option (introduced with 2.16.9)
has been extended to two independant sound/volume options. One sound for
"Errors & Failure" and the other for "Success & Information" notifications.
- Windows user names with accented characters: Functions, like Band Activity,
Text Messages, Sound play, not working when the %localappdata% path contained
accented characters (Windows user name has these characters, eg. Jesús).
Caused by a defect in a 3rd party code library that applied incorrect Json
data encoding to accented characters sent to the JTAlertV2.Manager process.
This email has been scanned by BullGuard antivirus protection.
Join Support@HamApps.groups.io to automatically receive all group messages.