Date   

locked Decodes problem

 

I am running JTAlert 2.16.10. When I bring up the JTAlert app at least half the time the decodes window does not populate. If  I close the app and then immediately bring it up again the decodes window is populated or starts to populate. I have let it go unpopulated for 20 minutes or more and it still doesn't populate without restarting the app. Not the worse problem in the world but still a nuisance . 
Any ideas,
John  NA6Y


locked Wanted DXCCs V.2.16.10 Band 4 m

Jesus
 

Good afternoon, I see an error opening Wanted DXCCs .. on the 4 meter band, because the 160 meter band comes out.
I observed it in the previous version, 2.16.09 and it persists in this new version .....

Cordially,
Jesus, EA1YR


locked Re: Will not launch - error

Joe Roth
 
Edited

Still no go.
I deleted all the file & folders including those in localappdata.
Scanned and cleaned anything in the registry.
Re-booted, re-installed. Made sure no programs were running in the background. Got the same error with one minor change; instead of line 22238 it is now 22265.


locked Re: No Audio ] JTAlert 2.16.10

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

 

 

 

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


locked Alerts For My Location

David - AK2L
 

Is there a way to alert on my location?

For example, if someone is looking for my grid or my state, they might send:
     "CQ DM42..."
or
     "CQ AZ..."

David, AK2L
DM42, Arizona


locked No Audio ] JTAlert 2.16.10

chas cartmel
 

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


locked JTAlert 2.16.10 is available #Announcement #NewRelease

HamApps Support (VK3AMA)
 

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).


locked Re: Decode Window

n4mf@...
 

Thanks for the info. I'll play with removing the B4's and some others as Those do fill a lot of the window (as of 2 days ago using WSJT-X on a FTDX-101D since 7-26-2019 i have over 2800 FT-8 contacts) so I have a lot of B4's.

Thanks and 73,
MItch
N4MF


locked Re: Any Plans for JTalert to use Multicast?

Richard Dubey
 

Well, I guess it depends on the computer. Mine isn’t taxed very much while running HRD, HRD logger, Gridtracker, WSJT-x, JTAlert, a time sync, my browser with 8 or 10 tabs open, Netlogger (that just is always on in the background), and all the usual windows detritus. But my computers are older decommissioned CAD workstations I’ve built and “retired”.

I just like software to look as nice as it works.

On Jul 28, 2020, at 1:30 PM, Mike Rhodes <weightdn@gmail.com> wrote:

...but if you devote more processor power to "eye candy", what will happen to the performance of WSJT-X? It is already doing an unbelievable amount of crunching. I'm fine with using the power where it does the most good.

Mike / W8DN

On 7/28/2020 6:54 AM, Richard Dubey via groups.io wrote:
I had no use for the robot operations, I just wanted to see how much the interface changed. I wouldn’t mind seeing the resolution of WSJT-x (Visually) just prettied up a bit. A little more like SDRUno. Higher res waterfall, less windows looking, commonly activated button near each other, etc. I like the eye candy, lol. Wish I knew programming.

On Jul 28, 2020, at 6:20 AM, neil_zampella <neilz@techie.com> wrote:


There's that little bit they changed that allows for robot operations ... kinda goes against the wishes of the WSJT-X developers, as well as the FCC regulations in the US, and a few other countries regulations.

Neil, KN3ILZ



locked Re: Any Plans for JTalert to use Multicast?

Mike Rhodes
 

...but if you devote more processor power to "eye candy", what will happen to the performance of WSJT-X? It is already doing an unbelievable amount of crunching. I'm fine with using the power where it does the most good.

Mike / W8DN

On 7/28/2020 6:54 AM, Richard Dubey via groups.io wrote:
I had no use for the robot operations, I just wanted to see how much the interface changed. I wouldn’t mind seeing the resolution of WSJT-x (Visually) just prettied up a bit. A little more like SDRUno. Higher res waterfall, less windows looking, commonly activated button near each other, etc. I like the eye candy, lol. Wish I knew programming.

On Jul 28, 2020, at 6:20 AM, neil_zampella <neilz@techie.com> wrote:



There's that little bit they changed that allows for robot operations ... kinda goes against the wishes of the WSJT-X developers, as well as the FCC regulations in the US, and a few other countries regulations.

Neil, KN3ILZ


locked Re: Any Plans for JTalert to use Multicast?

Richard Dubey
 

I had no use for the robot operations, I just wanted to see how much the interface changed. I wouldn’t mind seeing the resolution of WSJT-x (Visually) just prettied up a bit. A little more like SDRUno. Higher res waterfall, less windows looking, commonly activated button near each other, etc. I like the eye candy, lol. Wish I knew programming.

On Jul 28, 2020, at 6:20 AM, neil_zampella <neilz@...> wrote:



There's that little bit they changed that allows for robot operations ... kinda goes against the wishes of the WSJT-X developers, as well as the FCC regulations in the US, and a few other countries regulations.

 

Neil, KN3ILZ


locked Re: Any Plans for JTalert to use Multicast?

neil_zampella
 

There's that little bit they changed that allows for robot operations ... kinda goes against the wishes of the WSJT-X developers, as well as the FCC regulations in the US, and a few other countries regulations.

 

Neil, KN3ILZ


locked Re: Any Plans for JTalert to use Multicast?

Richard Dubey
 

I see. Well I will uninstall WJST-z and replace with WSJT-x and hopefully everything will go back to normal. I wouldn’t have thought they changed so much that it would have rendered WJST-z non functional. Oh well. 

On Jul 28, 2020, at 3:39 AM, Michel <micheluze@...> wrote:

JTALERT is not compatible with WSJT-Z
JTALERT block all report sent and received by WSJT-Z.
You can use GRIDTRACKER and WSJT-Z only but not with JTALERT
73 Michel


locked Re: Any Plans for JTalert to use Multicast?

Michel
 

JTALERT is not compatible with WSJT-Z
JTALERT block all report sent and received by WSJT-Z.
You can use GRIDTRACKER and WSJT-Z only but not with JTALERT
73 Michel


locked Re: Any Plans for JTalert to use Multicast?

HamApps Support (VK3AMA)
 

On 28/07/2020 12:54 am, W1SPS via groups.io wrote:
Or is it not working because JTAlert doesn't do multicast yet?

JTAlertV2 does not support multicast UDP. This is due to a lack of UDP multicast functionality in the AutoIT compiler used to create JTAlertV2.

de Laurie VK3AMA


locked Re: Decode Window

HamApps Support (VK3AMA)
 

On 27/07/2020 11:49 am, n4mf@... wrote:
Any chance at getting the decode window to do more than a 4 x 9 grid. 40M here routinely fills the 4 x 9 window and I see stuff not in the rx window not listed?

Mitch
N4MF

The 4x9 Callsigns display of the main JTAlert window is not the Decodes Window. That is a separate window and is NOT limited to a maximum of 36 callsigns.

Rather than extending the display beyond 36 callsigns, the better option is to restrict the number of callsigns displayed at the end of a period. Fewer displayed callsigns, based on your specific needs, is a better solution allowing for quicker recognition of potential QSO candidates. Try restricting the display by using one or more of the Alert Filters. Don't display B4s and enabling display of Alert generating Callsigns only are good candidates. Get rid of the Callings that you don't have interest in, especially when the Bands are full.

Extending the current 4x9 display (as currently implemented) is on the todo list, but very unlikely to be implemented.

de Laurie VK3AMA



locked Re: Decode Window

neil_zampella
 

Laurie has said that this will be available in version 3, if he ever gets the time to work on it after fixing requests and changes in v2 :)   However, it cannot be implemented in v2.x.x.

 

Neil, KN3ILZ


locked Re: Any Plans for JTalert to use Multicast?

Michael Black
 

Laurie hasn't announce a date yet. A bit hard to predict me thinkst.

Mike W9MDB




On Monday, July 27, 2020, 12:43:48 PM CDT, Richard Dubey via groups.io <w1sps@...> wrote:


Any ETA, just curious

On Jul 27, 2020, at 12:19 PM, Michael Black via groups.io <mdblack98@...> wrote:


JTAlert V2 does not do multicast.  V3 will when released.

Mike W9MDB




On Monday, July 27, 2020, 11:06:56 AM CDT, W1SPS via groups.io <w1sps@...> wrote:


Hello,
Been having an issue setting up Gridtracker and JTAlert.
I have WSJT-z (yes "z") UDP 127.0.0.1 Port 2237 (with the three boxes checked)
I have JTAlert set up (In the application section, under WSJT-x) to rebroadcast UDP to 127.0.0.1 Port 2234
I have Gridtracker set up to receive UDP on port 2234. Whenever I try to enable multicast the IP box is red if I put in 127.0.0.1, However if I put in 224.0.0.1 then it's green (of course it doesn't match what is in JTAlert).
Would I have to change the rebroadcast from JTAlert to 224.0.0.1 port 2234
Or is it not working because JTAlert doesn't do multicast yet? (or does it?) I had heard some discussion that was planned for a future release but I'm not sure how old the discussion was.
73
W1SPS


locked Re: Any Plans for JTalert to use Multicast?

Richard Dubey
 

Any ETA, just curious

On Jul 27, 2020, at 12:19 PM, Michael Black via groups.io <mdblack98@...> wrote:


JTAlert V2 does not do multicast.  V3 will when released.

Mike W9MDB




On Monday, July 27, 2020, 11:06:56 AM CDT, W1SPS via groups.io <w1sps@...> wrote:


Hello,
Been having an issue setting up Gridtracker and JTAlert.
I have WSJT-z (yes "z") UDP 127.0.0.1 Port 2237 (with the three boxes checked)
I have JTAlert set up (In the application section, under WSJT-x) to rebroadcast UDP to 127.0.0.1 Port 2234
I have Gridtracker set up to receive UDP on port 2234. Whenever I try to enable multicast the IP box is red if I put in 127.0.0.1, However if I put in 224.0.0.1 then it's green (of course it doesn't match what is in JTAlert).
Would I have to change the rebroadcast from JTAlert to 224.0.0.1 port 2234
Or is it not working because JTAlert doesn't do multicast yet? (or does it?) I had heard some discussion that was planned for a future release but I'm not sure how old the discussion was.
73
W1SPS


locked Re: Any Plans for JTalert to use Multicast?

Michael Black
 

JTAlert V2 does not do multicast.  V3 will when released.

Mike W9MDB




On Monday, July 27, 2020, 11:06:56 AM CDT, W1SPS via groups.io <w1sps@...> wrote:


Hello,
Been having an issue setting up Gridtracker and JTAlert.
I have WSJT-z (yes "z") UDP 127.0.0.1 Port 2237 (with the three boxes checked)
I have JTAlert set up (In the application section, under WSJT-x) to rebroadcast UDP to 127.0.0.1 Port 2234
I have Gridtracker set up to receive UDP on port 2234. Whenever I try to enable multicast the IP box is red if I put in 127.0.0.1, However if I put in 224.0.0.1 then it's green (of course it doesn't match what is in JTAlert).
Would I have to change the rebroadcast from JTAlert to 224.0.0.1 port 2234
Or is it not working because JTAlert doesn't do multicast yet? (or does it?) I had heard some discussion that was planned for a future release but I'm not sure how old the discussion was.
73
W1SPS

6061 - 6080 of 36987