Well, I apologize ... was searching more and found another user who reported same issue and Laurie confirmed this is an issue in the new release.  Guess I will be updating to a .6 as soon as released.

73, W6TWH

More people having this issue, or is it only me?

Wouldn't enjoy FT8 with ACL if it wasn't for JTAlert.  I have noticed, I think after the .5 upgrade, that the call-sign pop-up information seems to be missing International Country Names like an LUxxxx would say Argentina.  I get CQ Zone, distance, etc but I don't see Country codes or name.  Once I select the pop-up, ACL will do a QRZ lookup and fill in the blanks.  Just liked to see the expanded data in the pop-up call-sign.  Have I missed something?  Running all current versions of supporting databases.  Apologies in advance if I have missed the obvious?
Thomas, W6TWH

Laurie,

Thank you for the quick reply. I've performed the Test Sound operation both using the Sound On/Off drop-down menu and via the "Test Play" button of the Settings window for new DXCC, state, etc.

I'm confused by the statement  "Performing a Test Sound operation should not close any open windows". I expect it was prompted by my saying "However a warning sound is played  and an error message displayed asking me if I want to leave without saving changes". I had made changes to the 'play sound' conditions resulting in the 'do you want to save changes' window but may not have made myself clear. How I can make clearer what happened?

JTALERT, I couldn't get along without it and appreciate all the work you've done for our benefit.

Ed W2GHD

I'm using JTALERT 2.16.5 under WIN 10. Sounds are enabled. In JTALERT the output sound card selection is the Realtek High Def audio source. When running sound card test no output is heard. However a warning sound is played  and an error message displayed asking me if I want to leave without saving changes. I assume Windows is playing the sound. Device Manager indicates the sound device is working properly.

Suggestions appreciated.

Ed W2GHD

Performing a Test Sound operation should not close any open windows. It simply sends a UDP message to the always running (hidden) JTALertV2.Manager process.

Where are you performing the Test Sound operation? Is it via the "Sound -> Test Sound Output" menu of the main JTAlert window or via the "Test Play" button of the Settings window?

de Laurie VK3AMA

Hello,

I'm using JTALERT 2.16.5 under WIN 10. Sounds are enabled. In JTALERT the output sound card selection is the Realtek High Def audio source. When running sound card test no output is heard. However a warning sound is played  and an error message displayed asking me if I want to leave without saving changes. I assume Windows is playing the sound. Device Manager indicates the sound device is working properly.

Suggestions appreciated.

Ed W2GHD

Hi Laurie, I don't know if this is an already known issue, or is it only me.
It is not a big issue but the Decodes window (F9) is not consequent.
I always start JTAlert with the Decodes window active, but every second time the window ia populated and the next it is empty.
Also just closing the window and open it again via View F9  works like a Toggle swich. One time ON the next time OFF, etc.
The window it self always opens.
Just to inform you.

73, Nico PA1NS

--

They are separate modes.

I started with JT65 and JT9 for HF, and I can look back at what I did. Thanks to K1JT who adapted his technology to the HF spectrum. 

For my interests, technically and operating, I can see the evolution of the technology. My interest is QRP.

Are you aware WSJT-X is up to 2.2.0 - RC1 ?

Peter
W1UU

Hi Laurie,

I looked up the correct term - "Title Bar". The text  "[9] Analog out 07-08 (AudioFire 12)" appeared there. I haven't seen the same or similar text there since. I guess I should have snipped it. I'll do so if I see it again.  I should also add that alerts were being issued through ports 03-04, and WSJT-X was set to ports 11-12 (right) for audio to the radio. 

73,

Chris

Good morning Laurie,

In JTAlert v. 2.16.5 is there the possibility of eliminating some of the bands (not interesting for me) appearing in the window  "Callsign TX/Rx per band"  ?
Thanks

Carlo  IK2RPE

Removal of unneeded Bands is on the TODO list, but with the complexities of the JTAlertV2 series code, it is unlikely to be implemented until JTAlertV3.

de Laurie VK3AMA

Just to follow up, it is now 2 days since I wrote this up in the Log4OM forum.  It was not a know problem and the fix is in their new 2.6.1 release today.  Can't ask for any better than that!

Tom NS8K

Good to hear Tom.
Thanks for raising this with the Log4OM people.

de Laurie VK3AMA

I noticed in the JTAlert 2.16.5 banner it says "[9] Analog out 07-08 (AudioFire 12)", whilst the settings dialog says "[2] Analog out 03-04 (AudioFire 12)". Settings is correct. It's inconsistent unless I'm missing something. It's probably not a common issue as most people probably don't use 12 port sound interfaces but I thought I might as well report it anyway.

73,
Chris VE3NRT

What is this banner your referring to? Is it the listing under the Sounds menu or the dropdown list in the Settings window? Those two entries should match.

de Laurie VK3AMA

Running WSJT-X v 2.16.5

ZW5STAYHOME on 20m FT4 is showing up in red text on a yellow
background.  Tooltip says:

- Wanted DXCC
- Wanted Prefix

1.  I've worked a ton of stations in Brazil on 20 meters.
2.  I do not have the Prefix alert enabled.
3.  ZW5STAYHOME is not a wanted callsign

That looks correct to me.
The Tooltip shows a DXCC Alert was generated and the color Red on Yellow is the default coloring for the DXCC Alert.

While you have worked may Brazilian Stations on 20m have any been confirmed in your Log? The JTAlert Log Scan will only remove an entity from the Wanted Lists after a suitable QSO has been found in your log with the required (per your settings) confirmation(s) set.

Also, the default mode tracking is "by individual Mode", so JTAlert keeps track of Wanted entities on a per mode basis. Perhaps you don't have an 20m FT4 confirmed Brazilian in your Log, only FT8 stations.

de Laurie VK3AMA

Just to follow up, it is now 2 days since I wrote this up in the Log4OM forum.  It was not a know problem and the fix is in their new 2.6.1 release today.  Can't ask for any better than that!

Tom NS8K

Running WSJT-X v 2.16.5

ZW5STAYHOME on 20m FT4 is showing up in red text on a yellow
background. Tooltip says:

- Wanted DXCC
- Wanted Prefix

1. I've worked a ton of stations in Brazil on 20 meters.
2. I do not have the Prefix alert enabled.
3. ZW5STAYHOME is not a wanted callsign

Is this a parsing error in WSJT-X?

--
Jim Reisert AD1C, <jjreisert@...>, http://www.ad1c.us