Date   

locked JTAlert with UDP Multicast support available for testing #Beta

André C
 

Hello Laurie,  Do we need to delete our config file tui use the beta version ?


Garanti sans virus. www.avg.com


Le lun. 10 août 2020, à 15 h 04, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> a écrit :
Users who want to test UDP Multicast support provided by the current Beta build of JTAlert can try this build...

https://dnl.HamApps.com/Beta/JTAlert.2.16.10.build.0012.Beta.Setup.exe

Please report your experiences/observations with this build. I am keen to hear from DX Aggregator and Grid Tracker users when those applications have been correctly set to use the WSJT-X multicast IP address (NOT the JTAlert UDP resend feature) and running along-side JTAlert

Note: This is a Beta release and will cease functioning after 4 weeks.

From the release notes...
    - UDP Multicast: JTAlert now supports joining a UDP multicast group IP address
       when interacting with WSJT-X. This is automatic, using the settings as defined
       for each detected WSJT-X instance discovered running on the same PC as JTAlert.
       Multicast support across multiple PCs/Networks is not supported.
       Current JTAlert/WSJT-X setups, either single or multiple instance will operate
       as normal without any changes to WSJT-X settings.
       Users who want to take advantage of concurrently running applications like DX
       Aggregator or Grid Tracker along-side JTAlert will need to set the WSJT-X UDP
       Server to a valid Multicast IP (in the 239.0.0.0 to 239.255.0.0 range) and set
       those applications to use that IP address. JTAlert requires zero-configuration.

de Laurie VK3AMA


locked Re: Does JTA get along with Gridtracker ?

neil_zampella
 

You may want to take a look at the beta version that has added UDP multicasting support.

 

From the release notes:

 

- UDP Multicast: JTAlert now supports joining a UDP multicast group IP address
       when interacting with WSJT-X. This is automatic, using the settings as defined
       for each detected WSJT-X instance discovered running on the same PC as JTAlert.
       Multicast support across multiple PCs/Networks is not supported.
       Current JTAlert/WSJT-X setups, either single or multiple instance will operate
       as normal without any changes to WSJT-X settings.
       Users who want to take advantage of concurrently running applications like DX
       Aggregator or Grid Tracker along-side JTAlert will need to set the WSJT-X UDP
       Server to a valid Multicast IP (in the 239.0.0.0 to 239.255.0.0 range) and set
       those applications to use that IP address. JTAlert requires zero-configuration.

 

 


locked #Announcement : JTAlert with UDP Multicast support available for testing #Announcement

HamApps Support (VK3AMA)
 

Users who want to test UDP Multicast support provided by the current Beta build of JTAlert can try this build...

https://dnl.HamApps.com/Beta/JTAlert.2.16.10.build.0012.Beta.Setup.exe

Please report your experiences/observations with this build. I am keen to hear from DX Aggregator and Grid Tracker users when those applications have been correctly set to use the WSJT-X multicast IP address (NOT the JTAlert UDP resend feature) and running along-side JTAlert

Note: This is a Beta release and will cease functioning after 4 weeks.

From the release notes...
    - UDP Multicast: JTAlert now supports joining a UDP multicast group IP address
       when interacting with WSJT-X. This is automatic, using the settings as defined
       for each detected WSJT-X instance discovered running on the same PC as JTAlert.
       Multicast support across multiple PCs/Networks is not supported.
       Current JTAlert/WSJT-X setups, either single or multiple instance will operate
       as normal without any changes to WSJT-X settings.
       Users who want to take advantage of concurrently running applications like DX
       Aggregator or Grid Tracker along-side JTAlert will need to set the WSJT-X UDP
       Server to a valid Multicast IP (in the 239.0.0.0 to 239.255.0.0 range) and set
       those applications to use that IP address. JTAlert requires zero-configuration.

de Laurie VK3AMA


locked Re: Access setting without WSJT-X open

James Fuller N7VR <n7vr@...>
 

Every time I open JTALert with out WSJT-x running, I get an error message waiting for WSjt-x.
Only option is to wait or close.
I9m Fuller N7VR

On 8/10/2020 12:33 PM, Dave Garber wrote:
Why can't you?

sent by my LG phone

On Mon, Aug 10, 2020, 2:16 PM James Fuller N7VR via groups.io, <n7vr=n7vr.org@groups.io> wrote:
It would be nice if we could access settings for JTALERT when WSJT-x is
not open.

I often get requests to listen for a station attempting to complete an
award. I normally add the call sign to the wanted call sign list. This
notifies me when they are operating. I, also, like to change the
configuration of the link to programs like DXLABS, N1MM, Etc depending
on the upcoming operating situation. Having to bring up WSJT-x when the
radios are not on or disconnected is troublesome. Therefore I suggest
there be a way to access the settings without having WSJT-x up.

73

--
Jim Fuller
Montana Section Emergency Coordinator
N7VR -- http://www.n7vr.org
ARRL Life Member
CWOP-2 -- http://www.wxqa.com
Original ARECC contributor





-- 
Jim Fuller
Montana Section Emergency Coordinator
N7VR -- http://www.n7vr.org
ARRL Life Member
CWOP-2 -- http://www.wxqa.com
Original ARECC contributor


locked Re: Access setting without WSJT-X open

Dave Garber
 

Why can't you?

sent by my LG phone

On Mon, Aug 10, 2020, 2:16 PM James Fuller N7VR via groups.io, <n7vr=n7vr.org@groups.io> wrote:
It would be nice if we could access settings for JTALERT when WSJT-x is
not open.

I often get requests to listen for a station attempting to complete an
award. I normally add the call sign to the wanted call sign list. This
notifies me when they are operating. I, also, like to change the
configuration of the link to programs like DXLABS, N1MM, Etc depending
on the upcoming operating situation. Having to bring up WSJT-x when the
radios are not on or disconnected is troublesome. Therefore I suggest
there be a way to access the settings without having WSJT-x up.

73

--
Jim Fuller
Montana Section Emergency Coordinator
N7VR -- http://www.n7vr.org
ARRL Life Member
CWOP-2 -- http://www.wxqa.com
Original ARECC contributor





locked Re: Does JTA get along with Gridtracker ?

Jamie GOLLY
 
Edited

The answer is yes. 
 
Take a look at how I made it work, disregarding the radio settings itself. 
 

 
 



GL, Jamie
K6NGN 
 

On Aug 10, 2020, at 10:23 AM, Román Toledo via groups.io <rtoledo2002@...> wrote:

Sorry if this is not the place.  it's just that I just installed Gridtracker and noticed JTA  seemed to be disconnected or disabled by GRID

any replies are welcomed

thanks


locked Access setting without WSJT-X open

James Fuller N7VR <n7vr@...>
 

It would be nice if we could access settings for JTALERT when WSJT-x is not open.

I often get requests to listen for a station attempting to complete an award. I normally add the call sign to the wanted call sign list. This notifies me when they are operating. I, also, like to change the configuration of the link to programs like DXLABS, N1MM, Etc depending on the upcoming operating situation. Having to bring up WSJT-x when the radios are not on or disconnected is troublesome. Therefore I suggest there be a way to access the settings without having WSJT-x up.

73

--
Jim Fuller
Montana Section Emergency Coordinator
N7VR -- http://www.n7vr.org
ARRL Life Member
CWOP-2 -- http://www.wxqa.com
Original ARECC contributor


locked Re: Logging confusion

John Holmes W9ILY
 

That is really great news, Laurie. The current importer was a huge improvement and I'm looking forward to the next one. As you know, my log is rather large, over 225,000 now.
73,
John W9ILY


locked Does JTA get along with Gridtracker ?

Román Toledo
 

Sorry if this is not the place.  it's just that I just installed Gridtracker and noticed JTA  seemed to be disconnected or disabled by GRID

any replies are welcomed

thanks


locked Re: Signal report display

Jim N6VH
 


On 8/10/2020 7:08 AM, VE3JI wrote:
Hi All

is there any way to display the signal report on the JTAlert call sign block ??

Ian , VE3JI 
_._,_._,_


Ian,

Try this - go to Settings/Manage Settings/Window. Check Show db (DXCC Name). See attached picture. Hope this helps.

73,

Jim N6VH


locked Re: 2.16.10 showing as 2.15.3 in "Program Updates"

Joe Bennett
 

On Sun, Aug 9, 2020 at 09:43 PM, HamApps Support (VK3AMA) wrote:
Try deleting the JTAlert.ini file located at %localappdata%\HamApps
Excellent!!! Worked like a charm.

When looking at the file date of the .ini file, it reminded me that this was not a fresh install of 2.16.10. I did have a previous version of JTAlert on this machine. Most likely 2.15.3...

Thank you for your help!



-Joe
KA3NAM


locked Signal report display

VE3JI
 

Hi All

is there any way to display the signal report on the JTAlert call sign block ??

Ian , VE3JI 


locked Re: No Audio ] JTAlert 2.16.10

Mark Robinson
 

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.

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

 

From: Mark Robinson [mailto:markrob@...]
Sent: 09 August 2020 23:04
To: G4EST@...
Subject: Re: [HamApps] No Audio ] JTAlert 2.16.10

 

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

 

 

 

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

 

 

 

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

 

================================

UDP Ports used

--------------------------------

JTAlert_AL.exe        : 60906

JTAlertV2.Manager.exe : 57255

JTAlertV2.Decodes.exe : 

 

 

Inline image

 

 

 

 

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.

 

On Thu, Jul 30, 2020, 15:15 Joseph Baker <joebaker324@...> wrote:

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

 

 

 

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.

For more info visit www.bullguard.com

--

Sent from iPhone 8 Plus

 

This email has been scanned by BullGuard antivirus protection.

For more info visit www.bullguard.com

 

This email has been scanned by BullGuard antivirus protection.

For more info visit www.bullguard.com

 

 



locked Re: Would like to Add Propagation Mode and meteor shower to Logged QSO

KD7YZ Bob
 

On 8/9/2020 15:26, Jim - N4ST wrote:
...doesn’t the logged mode already tell
you which is which? Although logging a MSK144 QSO does not guarantee
that the propagation mode was meteor scatter, but JTAlert wouldn't be
capable of that distinction either.
Well, I am not seeing a changed Propagation Mode ... just what's
"Default" propagation or, if left Blank, no Propagation Mode.

So, one rig may be FT8 on 10m, or JT9G on 10m, while the other is
pounding away on 6m in MSK144 mode. Also thus in M/S.

From time to time I like to see what I achieved on meteor scatter. But
if I forget to change the TR (Tropo) then a sort won't reveal much
that's correct.

I previously asked this on WSJT-x and it was politely suggested I ask here.

A POP-UP for logging comes up at the R
the appropriate time in the QSO. I could change the Prop-Mode there.
Others told me that was generated by JTAlert.

Whatever shows up at the logging-point, also has the Power output box
... I have to change that from rig to rig ... and I do.


thanks for replying.


--
73
Bob KD7YZ
AMSAT LM #901


locked Re: No Audio ] JTAlert 2.16.10

chas cartmel
 

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

 

 


locked JTAlert with UDP Multicast support available for testing

HamApps Support (VK3AMA)
 

Users who want to test UDP Multicast support provided by the current Beta build of JTAlert can try this build...

https://dnl.HamApps.com/Beta/JTAlert.2.16.10.build.0012.Beta.Setup.exe

Please report your experiences/observations with this build. I am keen to hear from DX Aggregator and Grid Tracker users when those applications have been correctly set to use the WSJT-X multicast IP address (NOT the JTAlert UDP resend feature) and running along-side JTAlert

Note: This is a Beta release and will cease functioning after 4 weeks.

From the release notes...
    - UDP Multicast: JTAlert now supports joining a UDP multicast group IP address
       when interacting with WSJT-X. This is automatic, using the settings as defined
       for each detected WSJT-X instance discovered running on the same PC as JTAlert.
       Multicast support across multiple PCs/Networks is not supported.
       Current JTAlert/WSJT-X setups, either single or multiple instance will operate
       as normal without any changes to WSJT-X settings.
       Users who want to take advantage of concurrently running applications like DX
       Aggregator or Grid Tracker along-side JTAlert will need to set the WSJT-X UDP
       Server to a valid Multicast IP (in the 239.0.0.0 to 239.255.0.0 range) and set
       those applications to use that IP address. JTAlert requires zero-configuration.

de Laurie VK3AMA


locked Re: 2.16.10 showing as 2.15.3 in "Program Updates"

HamApps Support (VK3AMA)
 

On 10/08/2020 1:12 pm, Joe Bennett via groups.io wrote:
Wondering where I went wrong on this one. I did a fresh install of 2.16.10 on Windows 10.0.19041 and in the title bar of the JTAlert window does say 2.16.10 but the text at the top of the window is appended with "(Updates)". When I look at "Program Updates" it shows I'm running 2.15.3 and that an update for 2.16.10 is available. I did an uninstall and a reinstall but came up with the same behavior. Otherwise, it looks like everything is working OK...

Can't say it's a big deal, but was wondering if anyone had any ideas what I might be doing wrong?


-Joe
KA3NAM
Joe,

Try deleting the JTAlert.ini file located at %localappdata%\HamApps

de Laurie VK3AMA


locked 2.16.10 showing as 2.15.3 in "Program Updates"

Joe Bennett
 

Wondering where I went wrong on this one. I did a fresh install of 2.16.10 on Windows 10.0.19041 and in the title bar of the JTAlert window does say 2.16.10 but the text at the top of the window is appended with "(Updates)". When I look at "Program Updates" it shows I'm running 2.15.3 and that an update for 2.16.10 is available. I did an uninstall and a reinstall but came up with the same behavior. Otherwise, it looks like everything is working OK...

Can't say it's a big deal, but was wondering if anyone had any ideas what I might be doing wrong?




-Joe
KA3NAM


locked Re: JTAlert does crash rem 2

HamApps Support (VK3AMA)
 

On 10/08/2020 1:09 am, asobel@... wrote:
This morning, I did complete rebuilding my computer on an SSD disk. Unintentionally I did also rebuild the HRD Logbook using ADIF file backup similar to your description. 12 hours later, there was no fail. I hope it will stay so. Be sure, I will let you know if it fails

Good news!

de Laurie VK3AMA


locked Re: Logging confusion

HamApps Support (VK3AMA)
 

On 10/08/2020 12:55 am, John Holmes W9ILY wrote:
Thanks, Laurie. I figured that was the way to do it and glad you confirmed.
73,

John W9ILY
John,

FYI, A very near future JTAlert build utilizes a new ADIF file importer that is an improvement over the current importer, which as you know was a significant improvement over the old importer that took several minutes to process one of your large adif files.

The
current importer took ~18.6 secs (9.8K recs/sec) while the new importer took ~11.8 secs (15.5K recs/sec) to process one of your old 183K QSO files. That's a ~ 45% speed improvement!

Output window for current importer...
   

Output window for upcoming importer...
   


de Laurie VK3AMA

6221 - 6240 of 37288