|
Laurie 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…
Charlie G4EST www.g4est.me.uk
From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of HamApps Support (VK3AMA)
Sent: 29 July 2020 21:30
To: Support@HamApps.groups.io
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
Release Notes.
2.16.10 (28-Jul-2020)
*** Includes Callsign database file version 2020-07-28 (2020-Jul-28)
New Features:
- 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.
Changes:
- 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.
Fixes:
- 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.
(2.15.1 defect).
This email has been scanned by BullGuard antivirus protection.
|
|
|
Joseph Baker <joebaker324@...>
Did you select your sounds file under windows notifications on JT alert?
On Thu, 30 Jul 2020 at 12:48, chas cartmel < chas@...> wrote: Laurie 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…
Charlie G4EST www.g4est.me.uk The latest JTAlert version 2.16.10 is now available @ https://hamapps.com/JTAlert/
de Laurie VK3AMA
Release Notes.
2.16.10 (28-Jul-2020)
*** Includes Callsign database file version 2020-07-28 (2020-Jul-28)
New Features:
- 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.
Changes:
- 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.
Fixes:
- 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.
(2.15.1 defect).
This email has been scanned by BullGuard antivirus protection.
-- Sent from iPhone 8 Plus
|
|
|
Yep - Win10 changes the audio settings to those it wants instead of the ones I want.
Did you select your sounds file under windows notifications on JT alert? On Thu, 30 Jul 2020 at 12:48, chas cartmel < chas@...> wrote: Laurie 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…
Charlie G4EST www.g4est.me.uk The latest JTAlert version 2.16.10 is now available @ https://hamapps.com/JTAlert/
de Laurie VK3AMA
Release Notes.
2.16.10 (28-Jul-2020)
*** Includes Callsign database file version 2020-07-28 (2020-Jul-28)
New Features:
- 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.
Changes:
- 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.
Fixes:
- 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.
(2.15.1 defect).
This email has been scanned by BullGuard antivirus protection.
Sent from iPhone 8 Plus
|
|
|
See if you have JTAlertV2 Manger running in your task manager.
You should also see it in the About box
================================ UDP Ports used -------------------------------- JTAlert_AL.exe : 60906 JTAlertV2.Manager.exe : 57255 JTAlertV2.Decodes.exe :
On Thursday, July 30, 2020, 05:50:35 PM CDT, D. Scott MacKenzie <kb0fhp@...> wrote:
Yep - Win10 changes the audio settings to those it wants instead of the ones I want. Did you select your sounds file under windows notifications on JT alert? On Thu, 30 Jul 2020 at 12:48, chas cartmel < chas@...> wrote: Laurie 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…
Charlie G4EST www.g4est.me.uk The latest JTAlert version 2.16.10 is now available @ https://hamapps.com/JTAlert/
de Laurie VK3AMA
Release Notes.
2.16.10 (28-Jul-2020)
*** Includes Callsign database file version 2020-07-28 (2020-Jul-28)
New Features:
- 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.
Changes:
- 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.
Fixes:
- 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.
(2.15.1 defect).
This email has been scanned by BullGuard antivirus protection.
Sent from iPhone 8 Plus
|
|
|
Thanks for response.
No idea what you mean. The files were selected using the JTAlert dialogue and were working previously. They were still present.
Regardless of sound files the test sound card should still have provided output.
Charlie G4EST www.g4est.me.uk
From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Joseph Baker
Sent: 30 July 2020 13:16
To: Support@hamapps.groups.io
Subject: Re: [HamApps] No Audio ] JTAlert 2.16.10 Did you select your sounds file under windows notifications on JT alert? On Thu, 30 Jul 2020 at 12:48, chas cartmel <chas@...> wrote: Laurie 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…
Charlie G4EST www.g4est.me.uk The latest JTAlert version 2.16.10 is now available @ https://hamapps.com/JTAlert/
de Laurie VK3AMA
Release Notes. 2.16.10 (28-Jul-2020)
*** Includes Callsign database file version 2020-07-28 (2020-Jul-28)
New Features:
- 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.
Changes:
- 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.
Fixes:
- 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.
(2.15.1 defect). This email has been scanned by BullGuard antivirus protection.
--
This email has been scanned by BullGuard antivirus protection.
|
|
|
Thanks My ‘about info’:
UDP Ports used -------------------------------- JTAlert_AL.exe : 57336 JTAlertV2.Manager.exe : 52432 JTAlertV2.Decodes.exe :
JTAlertV2 Manager running (see attachment), but not shown in the volume mixer (as in my 1st post).
All alerts point to the correct location and sound files exist HOWEVER they do not play individually under Media Player so now suspect it maybe media player issue although having changed the default to VLC where audio works still no audio from JTAlert. Other .wav files will not play either…
On the assumption that JTAlert will ignore the default and always point to Media Player then this must be the issue. Will attempt to repair windows ‘bit by bit’.
Charlie G4EST www.g4est.me.uk
From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Michael Black via groups.io
Sent: 30 July 2020 23:53
To: Support@HamApps.groups.io
Subject: Re: [HamApps] No Audio ] JTAlert 2.16.10 See if you have JTAlertV2 Manger running in your task manager. You should also see it in the About box ================================ -------------------------------- JTAlertV2.Manager.exe : 57255 On Thursday, July 30, 2020, 05:50:35 PM CDT, D. Scott MacKenzie <kb0fhp@...> wrote: Yep - Win10 changes the audio settings to those it wants instead of the ones I want. Did you select your sounds file under windows notifications on JT alert? On Thu, 30 Jul 2020 at 12:48, chas cartmel <chas@...> wrote: Laurie 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…
Charlie G4EST www.g4est.me.uk The latest JTAlert version 2.16.10 is now available @ https://hamapps.com/JTAlert/
de Laurie VK3AMA
Release Notes. 2.16.10 (28-Jul-2020)
*** Includes Callsign database file version 2020-07-28 (2020-Jul-28)
New Features:
- 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.
Changes:
- 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.
Fixes:
- 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.
(2.15.1 defect). This email has been scanned by BullGuard antivirus protection.
--
This email has been scanned by BullGuard antivirus protection.
|
|
|
Update: Restored the computer to 4 days ago, JTAlert was OK then, but no difference here.
Still will not play anything via media player, error RPC server unavailable.
Continuing investigation. Charlie G4EST www.g4est.me.uk
From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of chas cartmel
Sent: 31 July 2020 09:08
To: Support@HamApps.groups.io
Subject: Re: [HamApps] No Audio ] JTAlert 2.16.10 Thanks My ‘about info’:
UDP Ports used -------------------------------- JTAlert_AL.exe : 57336 JTAlertV2.Manager.exe : 52432 JTAlertV2.Decodes.exe :
JTAlertV2 Manager running (see attachment), but not shown in the volume mixer (as in my 1st post).
All alerts point to the correct location and sound files exist HOWEVER they do not play individually under Media Player so now suspect it maybe media player issue although having changed the default to VLC where audio works still no audio from JTAlert. Other .wav files will not play either…
On the assumption that JTAlert will ignore the default and always point to Media Player then this must be the issue. Will attempt to repair windows ‘bit by bit’.
Charlie G4EST www.g4est.me.uk From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Michael Black via groups.io
Sent: 30 July 2020 23:53
To: Support@HamApps.groups.io
Subject: Re: [HamApps] No Audio ] JTAlert 2.16.10 See if you have JTAlertV2 Manger running in your task manager. You should also see it in the About box ================================ -------------------------------- JTAlertV2.Manager.exe : 57255 On Thursday, July 30, 2020, 05:50:35 PM CDT, D. Scott MacKenzie <kb0fhp@...> wrote: Yep - Win10 changes the audio settings to those it wants instead of the ones I want. Did you select your sounds file under windows notifications on JT alert? On Thu, 30 Jul 2020 at 12:48, chas cartmel <chas@...> wrote: Laurie 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…
Charlie G4EST www.g4est.me.uk The latest JTAlert version 2.16.10 is now available @ https://hamapps.com/JTAlert/
de Laurie VK3AMA
Release Notes. 2.16.10 (28-Jul-2020)
*** Includes Callsign database file version 2020-07-28 (2020-Jul-28)
New Features:
- 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.
Changes:
- 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.
Fixes:
- 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.
(2.15.1 defect). This email has been scanned by BullGuard antivirus protection.
--
This email has been scanned by BullGuard antivirus protection. This email has been scanned by BullGuard antivirus protection.
|
|
|
I just installed JTAlert 2:16:10 from 2.14.2 on my win 7 pro 64 bit
machine and my previously working sounds are no longer playing on
JTAlert. The sound files are still in the correct location and
Winamp will play them. JTAlert is pointed to the right sound file
and to the right sound device but the sounds do not play and the
Test Sound buttons do not play any sounds either.
If I select Sound Off and then press Test Sound Output, I get the
error window and a windows sound
Is there an easy way to go back to version 2.14.2 ?
thanks Mark N1UK
toggle quoted messageShow quoted text
On 31-Jul-20 5:07 AM, chas cartmel
wrote:
Update:
Restored the
computer to 4 days ago, JTAlert was OK then, but no
difference here.
Still will not
play anything via media player, error RPC server
unavailable.
Continuing investigation.
Charlie
G4EST
www.g4est.me.uk
Thanks
My ‘about info’:
UDP Ports used
--------------------------------
JTAlert_AL.exe
: 57336
JTAlertV2.Manager.exe
: 52432
JTAlertV2.Decodes.exe :
JTAlertV2 Manager running (see attachment), but not shown in
the volume mixer (as in my 1st post).
All alerts point to the correct location and sound files
exist HOWEVER they do not play individually under Media
Player so now suspect it maybe media player issue although
having changed the default to VLC where audio works still no
audio from JTAlert. Other .wav files will not play either…
On the assumption that JTAlert will ignore the default and
always point to Media Player then this must be the issue.
Will attempt to repair windows ‘bit by bit’.
Charlie
G4EST
www.g4est.me.uk
See
if you have JTAlertV2 Manger running in your task
manager.
You
should also see it in the About box
================================
--------------------------------
JTAlertV2.Manager.exe
: 57255
On
Thursday, July 30, 2020, 05:50:35 PM CDT, D. Scott
MacKenzie <kb0fhp@...> wrote:
Yep
- Win10 changes the audio settings to those it
wants instead of the ones I want.
Did
you select your sounds file under windows
notifications on JT alert?
On
Thu, 30 Jul 2020 at 12:48, chas cartmel
<chas@...>
wrote:
Laurie
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…
Charlie
G4EST
www.g4est.me.uk
The
latest JTAlert version 2.16.10 is
now available @ https://hamapps.com/JTAlert/
de Laurie VK3AMA
Release Notes.
2.16.10 (28-Jul-2020)
*** Includes Callsign database
file version 2020-07-28
(2020-Jul-28)
New Features:
- 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.
Changes:
- 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.
Fixes:
- 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.
(2.15.1 defect).
This
email has been scanned by BullGuard
antivirus protection.
--
This email has been scanned by BullGuard
antivirus protection.
This email has been scanned by BullGuard antivirus
protection.
|
|
|
Mark
I found the issue was with Windows media player itself as it just hung when trying to play any wave sound files from anywhere directly.
I went through SFC /scannow routine, DSIM analysis, and restore to 3 days previous to the error, no change. Also tried SAFE mode.
This morning I did a repair / in place install of Windows 10, and again not resolved.
I found a workaround by setting the defaults to ‘Groove music’. VLC and others would not play JTAlerts but this one worked.
Hope this helps
73 Charlie G4EST www.g4est.me.uk
From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Mark Robinson
Sent: 01 August 2020 19:30
To: Support@HamApps.groups.io
Subject: Re: [HamApps] No Audio ] JTAlert 2.16.10 I just installed JTAlert 2:16:10 from 2.14.2 on my win 7 pro 64 bit machine and my previously working sounds are no longer playing on JTAlert. The sound files are still in the correct location and Winamp will play them. JTAlert is pointed to the right sound file and to the right sound device but the sounds do not play and the Test Sound buttons do not play any sounds either.
If I select Sound Off and then press Test Sound Output, I get the error window and a windows sound
Is there an easy way to go back to version 2.14.2 ?
thanks Mark N1UK
On 31-Jul-20 5:07 AM, chas cartmel wrote: Update: Restored the computer to 4 days ago, JTAlert was OK then, but no difference here.
Still will not play anything via media player, error RPC server unavailable.
Continuing investigation. Charlie G4EST www.g4est.me.uk Thanks My ‘about info’:
UDP Ports used -------------------------------- JTAlert_AL.exe : 57336 JTAlertV2.Manager.exe : 52432 JTAlertV2.Decodes.exe :
JTAlertV2 Manager running (see attachment), but not shown in the volume mixer (as in my 1st post).
All alerts point to the correct location and sound files exist HOWEVER they do not play individually under Media Player so now suspect it maybe media player issue although having changed the default to VLC where audio works still no audio from JTAlert. Other .wav files will not play either…
On the assumption that JTAlert will ignore the default and always point to Media Player then this must be the issue. Will attempt to repair windows ‘bit by bit’.
Charlie G4EST www.g4est.me.uk See if you have JTAlertV2 Manger running in your task manager. You should also see it in the About box ================================ -------------------------------- JTAlertV2.Manager.exe : 57255 On Thursday, July 30, 2020, 05:50:35 PM CDT, D. Scott MacKenzie <kb0fhp@...> wrote: Yep - Win10 changes the audio settings to those it wants instead of the ones I want. Did you select your sounds file under windows notifications on JT alert? On Thu, 30 Jul 2020 at 12:48, chas cartmel <chas@...> wrote: Laurie 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…
Charlie G4EST www.g4est.me.uk The latest JTAlert version 2.16.10 is now available @ https://hamapps.com/JTAlert/
de Laurie VK3AMA
Release Notes. 2.16.10 (28-Jul-2020)
*** Includes Callsign database file version 2020-07-28 (2020-Jul-28)
New Features:
- 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.
Changes:
- 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.
Fixes:
- 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.
(2.15.1 defect). This email has been scanned by BullGuard antivirus protection.
--
This email has been scanned by BullGuard antivirus protection. This email has been scanned by BullGuard antivirus protection.
|
|
|
I loaded version 2.14.2 back over the latest version and now the
sound is working again.
toggle quoted messageShow quoted text
On 01-Aug-20 2:29 PM, Mark Robinson
wrote:
I just installed JTAlert 2:16:10 from 2.14.2 on my win 7 pro 64
bit machine and my previously working sounds are no longer playing
on JTAlert. The sound files are still in the correct location
and Winamp will play them. JTAlert is pointed to the right sound
file and to the right sound device but the sounds do not play and
the Test Sound buttons do not play any sounds either.
If I select Sound Off and then press Test Sound Output, I get the
error window and a windows sound
Is there an easy way to go back to version 2.14.2 ?
thanks Mark N1UK
On 31-Jul-20 5:07 AM, chas cartmel
wrote:
Update:
Restored the
computer to 4 days ago, JTAlert was OK then, but no
difference here.
Still will not
play anything via media player, error RPC server
unavailable.
Continuing investigation.
Charlie
G4EST
www.g4est.me.uk
Thanks
My ‘about
info’:
UDP Ports used
--------------------------------
JTAlert_AL.exe
: 57336
JTAlertV2.Manager.exe
: 52432
JTAlertV2.Decodes.exe :
JTAlertV2 Manager running (see attachment), but not shown
in the volume mixer (as in my 1st post).
All alerts point to the correct location and sound files
exist HOWEVER they do not play individually under Media
Player so now suspect it maybe media player issue although
having changed the default to VLC where audio works still
no audio from JTAlert. Other .wav files will not play
either…
On the assumption that JTAlert will ignore the default and
always point to Media Player then this must be the issue.
Will attempt to repair windows ‘bit by bit’.
Charlie
G4EST
www.g4est.me.uk
See
if you have JTAlertV2 Manger running in your task
manager.
You
should also see it in the About box
================================
--------------------------------
JTAlertV2.Manager.exe
: 57255
On
Thursday, July 30, 2020, 05:50:35 PM CDT, D. Scott
MacKenzie <kb0fhp@...>
wrote:
Yep
- Win10 changes the audio settings to those it
wants instead of the ones I want.
Did
you select your sounds file under
windows notifications on JT alert?
On
Thu, 30 Jul 2020 at 12:48, chas
cartmel <chas@...>
wrote:
Laurie
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…
Charlie
G4EST
www.g4est.me.uk
The
latest JTAlert version 2.16.10 is
now available @ https://hamapps.com/JTAlert/
de Laurie VK3AMA
Release Notes.
2.16.10 (28-Jul-2020)
*** Includes Callsign database
file version 2020-07-28
(2020-Jul-28)
New Features:
- 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.
Changes:
- 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.
Fixes:
- 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.
(2.15.1 defect).
This
email has been scanned by BullGuard
antivirus protection.
--
This email has been scanned by
BullGuard antivirus protection.
This email has been scanned by BullGuard antivirus
protection.
|
|
|
 Mark, couple of things.
Double decoding if a frequent occurrence is usually overloading of the audio input either at the transmitting station of within your own system. Might be informative to check levels. .JTAlert has no influence on that at it only receives data from WSJTX via UDP.
Groove Music is a separate program and is ‘selectable’ as a default within Settings (start menu sidebar)/Apps/default apps.. No idea if this program is available on Windows 7 though. See later
It happened overnight on my system and even a restore to an earlier Windoze ‘checkpoint’ and a subsequent Windows in place rebuild didn’t fix it. I have now reset the default to WMP and retried the audio via ‘test sound card’ and individual alert sound files within JTAlertX and it works again. Audio files are now played through WMP as expected. I have not touched the system since my last post on the issue so any changes must have been via a Windoze buggeritupdate. Really confused all the same. I am also surprised Laurie didn’t comment on this issue.
A few have commented on audio issues since the last update so this silence on the matter is out of character. Hope this helps 73 Charlie G4EST www.g4est.me.uk Stay safe out there
|
|
|
What I mean by double decoding is the new feature of WSJTX. It
decodes a bunch of FT8 signals and then right at the end of the time
slot, it might add a few more decodes to the list. When I was
running JTAlert 2.14.2 it plays the sounds correctly but over writes
the callsign display with the remainder decodes at the end of the
time slot. Version 2.16.10 correctly appends the end of slot
decodes to the display. Show it shows all stations decoded during
and at the end of th etime slot.
My JTAlertV2.Manager.exe seems to be loaded and running OK.
toggle quoted messageShow quoted text
On 10-Aug-20 4:23 AM, G4EST wrote:
Mark, couple of
things.
Double decoding if a frequent occurrence is usually
overloading of the audio input either at the transmitting
station of within your own system. Might be informative to
check levels. .JTAlert has no influence on that at it only
receives data from WSJTX via UDP.
Groove Music is a separate program and is ‘selectable’ as a
default within Settings (start menu sidebar)/Apps/default
apps.. No idea if this program is available on Windows 7
though. See later
It happened
overnight on my system and even a restore to an earlier
Windoze ‘checkpoint’ and a subsequent Windows in place
rebuild didn’t fix it.
I have now
reset the default to WMP and retried the audio via ‘test
sound card’ and individual alert sound files within
JTAlertX and it works again. Audio files are now
played through WMP as expected. I have
not touched the system since my last post on the issue so any
changes must have been via a Windoze buggeritupdate. Really
confused all the same.
I am also
surprised Laurie didn’t comment on this issue.
A few have commented on audio issues since the last update
so this silence on the matter is out of character.
Hope this helps
73 Charlie
G4EST
www.g4est.me.uk
Stay safe out there
Hi Charlie,
Thank you for your help. I went back to an earlier version of
JTAlert in which the sound works perfectly but it is giving me
issues with the double decoding of WSJTX, so I am going to try
the latest version of JTAlert again.
Did you find out that Windows Media Player was playing the
JTAlert sounds. Is the "Groove Music" s setting in Windows
media Player ? Any hints would be helpful. I am running Win
7 on my ham pc so I hope the same applies as your Win 10
machine.
I was surprised that we didn't hear from the software author
about this issue.
73 Mark N1UK
On 01-Aug-20 4:14 PM, chas cartmel wrote:
Mark
I found the issue was with Windows media player itself as
it just hung when trying to play any wave sound files from
anywhere directly.
I went through SFC /scannow routine, DSIM analysis, and
restore to 3 days previous to the error, no change. Also
tried SAFE mode.
This morning I did a repair / in place install of Windows
10, and again not resolved.
I found a workaround by setting the defaults to ‘Groove
music’. VLC and others would not play JTAlerts but this
one worked.
Hope this helps
73 Charlie
G4EST
www.g4est.me.uk
I just
installed JTAlert 2:16:10 from 2.14.2 on my win 7 pro 64
bit machine and my previously working sounds are no longer
playing on JTAlert. The sound files are still in the
correct location and Winamp will play them. JTAlert is
pointed to the right sound file and to the right sound
device but the sounds do not play and the Test Sound buttons
do not play any sounds either.
If I select Sound Off and then press Test Sound Output, I
get the error window and a windows sound
Is there an easy way to go back to version 2.14.2 ?
thanks Mark N1UK
On 31-Jul-20 5:07 AM, chas cartmel
wrote:
Update:
Restored the
computer to 4 days ago, JTAlert was OK then, but no
difference here.
Still will
not play anything via media player, error RPC server
unavailable.
Continuing investigation.
Charlie
G4EST
www.g4est.me.uk
Thanks
My ‘about
info’:
UDP Ports used
--------------------------------
JTAlert_AL.exe
: 57336
JTAlertV2.Manager.exe
: 52432
JTAlertV2.Decodes.exe :
JTAlertV2 Manager running (see attachment), but not
shown in the volume mixer (as in my 1st
post).
All alerts point to the correct location and sound files
exist HOWEVER they do not play individually under Media
Player so now suspect it maybe media player issue
although having changed the default to VLC where audio
works still no audio from JTAlert. Other .wav files will
not play either…
On the assumption that JTAlert will ignore the default
and always point to Media Player then this must be the
issue. Will attempt to repair windows ‘bit by bit’.
Charlie
G4EST
www.g4est.me.uk
See
if you have JTAlertV2 Manger running in your task
manager.
You
should also see it in the About box
================================
--------------------------------
JTAlertV2.Manager.exe
: 57255
On
Thursday, July 30, 2020, 05:50:35 PM CDT, D. Scott
MacKenzie <kb0fhp@...>
wrote:
Yep
- Win10 changes the audio settings to those
it wants instead of the ones I want.
Did
you select your sounds file under
windows notifications on JT alert?
On
Thu, 30 Jul 2020 at 12:48, chas
cartmel <chas@...>
wrote:
Laurie
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…
Charlie
G4EST
www.g4est.me.uk
The
latest JTAlert version 2.16.10
is now available @ https://hamapps.com/JTAlert/
de Laurie VK3AMA
Release Notes.
2.16.10 (28-Jul-2020)
*** Includes Callsign database
file version 2020-07-28
(2020-Jul-28)
New Features:
- 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.
Changes:
- 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.
Fixes:
- 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.
(2.15.1 defect).
This
email has been scanned by
BullGuard antivirus protection.
--
This email has been scanned by
BullGuard antivirus protection.
This email has been scanned by
BullGuard antivirus protection.
|
|
|
