Date   

locked Re: 8-character Gridsquare

HamApps Support (VK3AMA)
 

On 23/10/2020 8:12 pm, onaka@... wrote:
I want the PSK reporter display to not overlap with the local station.
For this reason,  WSJT-X Gridsquare is set to 8 characters.
From Version 2.16.14, the attached warning is displayed when starting JTAlert.
Is it possible to stop the warning?
JA4JOE

JTAlert has long had the Grid mismatch warning, not just with 2.16.14.

WSJT-X and JTAlert both restrict Grids to 6 characters maximum.

WSJT-X doesn't allow for entering of more than 6 characters on the main window or in its Settings window. Similarly, JTAlert doesn't allow for more that 6 characters.

Since 8 character grids are not conveyed on air via FT8 or any of the other supported modes, I don't see any reason to extend JTAlert to use 8 character Grids.

Your only solution to this is to remove the 8 character edit you applied to the WSJT-X ini file.

I don't see how PSKReporter is relevant.

de Laurie VK3AMA


locked Re: Strange UI phenomenon

HamApps Support (VK3AMA)
 

On 23/10/2020 5:13 pm, Björn SM7IUN wrote:
Thanks Laurie.

I reported the audio device naming issue here in March and Panos SV1GRN confirmed it.

In the thread the problem was initially believed to be about remembering settings but it 
was really about character sets. Perhaps the later parts of that thread went past you.

The workaround we found was to replace the name of the audio device assigned by 
Windows to a name containing only plain ASCII characters.

Windows' default name for an output audio device contains non-ASCII characters in many 
languages. "Speaker" is "Högtalare" in Swedish etc. If you try to use a device with such a 
name you will get a pop-up "Cannot locate the last used sound output device" every time 
you start the program, forcing you to select it once again. 

JTAlert seems to replace non-ASCII characters in the device name with a question 
mark. (See below). This is the likely reason for it not being correctly remembered.

If you rename your own speaker to something with umlauts or diacriticals you should 
be able to easily reproduce this.

73

Björn SM7IUN

Thanks Björn

An alternative to renaming the device in Windows (not all drivers allow for that change) is to use a virtual audio device pair like the free version of VB-Audio (https://vb-audio.com/Cable/) and having one end pointing at your device and have JTAlert using the other end.

Somewhat related, some audio devices go to sleep after a period of inactivity and then when coming out of sleep the first part of the sound (that triggered coming out of sleep) is missed. This is very common with Nvidia HDMI devices which go to sleep after only ~ 5 seconds. I have used the VB-Audio pair technique to prevent the HDMI device going to sleep and causing the first part of a sound being truncated.

de Laurie VK3AMA


locked Re: Audible Alerts

Norm Fasoletos <norm.k7nwf@...>
 

Yes I have selected a sound file for each alert and tested it...works, except when someone call me..

Norm - K7NWF



On Oct 23, 2020, at 11:26 AM, chas cartmel <chas@...> wrote:



You say settings OK. Can I assume you have selected each of the sound files for each alert?


73 Charlie

G4EST

www.g4est.me.uk

Stay safe out there

 

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of HamApps Support (VK3AMA)
Sent: 23 October 2020 18:24
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Audible Alerts

 

On 23/10/2020 5:04 pm, Norm Fasoletos wrote:

I have all the settings correct, when I test the sound "calling you" it works fine, I hear it. When someone calls me, I get a visual indication in red but no sound.

 

Not sure where to look further?

 

Norm - K7NWF


Norm,

Your settings image looks fine.

Please use the "Help" -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis.

de Laurie VK3AMA


locked Re: Question

Neil Foster
 

Thanks Laurie for pointing me in the right direction...now fixed
73 and stay well
Neil   N4FN


locked Re: Audible Alerts

chas cartmel
 

You say settings OK. Can I assume you have selected each of the sound files for each alert?


73 Charlie

G4EST

www.g4est.me.uk

Stay safe out there

 

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of HamApps Support (VK3AMA)
Sent: 23 October 2020 18:24
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Audible Alerts

 

On 23/10/2020 5:04 pm, Norm Fasoletos wrote:

I have all the settings correct, when I test the sound "calling you" it works fine, I hear it. When someone calls me, I get a visual indication in red but no sound.

 

Not sure where to look further?

 

Norm - K7NWF


Norm,

Your settings image looks fine.

Please use the "Help" -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis.

de Laurie VK3AMA


locked Re: Audible Alerts

HamApps Support (VK3AMA)
 

On 23/10/2020 5:04 pm, Norm Fasoletos wrote:
I have all the settings correct, when I test the sound "calling you" it works fine, I hear it. When someone calls me, I get a visual indication in red but no sound.

Not sure where to look further?

Norm - K7NWF

Norm,

Your settings image looks fine.

Please use the "Help" -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis.

de Laurie VK3AMA


locked #FT8/JTAlert

Wes Elton
 

Hi Mike,

Got it😊!

Many thanks Mike, appreciate your help.

73,

Wes.

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Michael Black via groups.io
Sent: 23 October 2020 13:22
To: Support@HamApps.groups.io
Subject: Re: [HamApps] #FT8/JTAlert

 

It's not under Decodes....it's on the Window menu -- the one with the red box around it.

 

Mike W9MDB

 

 

 

 

On Friday, October 23, 2020, 07:20:13 AM CDT, Wes Elton <wes@...> wrote:

 

 

Hi Laurie,

 

Many thanks for the speedy response.

 

I’m running JTAlert version 2.16.4.

 

Under Window/Decodes the page displayed only shows Enable Decodes which is checked with, at the bottom of the page, Display Options which are unchecked. Checking them doesn’t make the required change. There are no Extended Display options in view.

 

Apologies if I’m missing something obvious!

 

Regards,

Wes.GW3RIH.

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: 22 October 2020 21:14
To: Support@HamApps.groups.io
Subject: Re: [HamApps] #FT8/JTAlert

 

On 23/10/2020 6:42 am, Wes Elton wrote:

Can someone please advise where I can find the settings info that will enable received signal strength to appear beneath calls in the callsign display lines.
I've searched the help files but see anything relevant.

Cheers,

Wes.
GW3RIH.



de Laurie VK3AMA


locked Re: #FT8/JTAlert

Wes Elton
 

Hi Laurie,

 

Found it😊! I was making the mistake of clicking where your cursor was not on the word windows.

As ever, thanks for your help and for the superb JTAlert software.

Much appreciated.

Stay safe OM.

73,

Wes.

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: 22 October 2020 21:14
To: Support@HamApps.groups.io
Subject: Re: [HamApps] #FT8/JTAlert

 

On 23/10/2020 6:42 am, Wes Elton wrote:

Can someone please advise where I can find the settings info that will enable received signal strength to appear beneath calls in the callsign display lines.
I've searched the help files but see anything relevant.

Cheers,

Wes.
GW3RIH.



de Laurie VK3AMA


locked 8-character Gridsquare

onaka@...
 

I want the PSK reporter display to not overlap with the local station.
For this reason,  WSJT-X Gridsquare is set to 8 characters.
From Version 2.16.14, the attached warning is displayed when starting JTAlert.
Is it possible to stop the warning?
JA4JOE


locked Re: #FT8/JTAlert

Michael Black
 

It's not under Decodes....it's on the Window menu -- the one with the red box around it.

Mike W9MDB




On Friday, October 23, 2020, 07:20:13 AM CDT, Wes Elton <wes@...> wrote:


Hi Laurie,

 

Many thanks for the speedy response.

 

I’m running JTAlert version 2.16.4.

 

Under Window/Decodes the page displayed only shows Enable Decodes which is checked with, at the bottom of the page, Display Options which are unchecked. Checking them doesn’t make the required change. There are no Extended Display options in view.

 

Apologies if I’m missing something obvious!

 

Regards,

Wes.GW3RIH.

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: 22 October 2020 21:14
To: Support@HamApps.groups.io
Subject: Re: [HamApps] #FT8/JTAlert

 

On 23/10/2020 6:42 am, Wes Elton wrote:

Can someone please advise where I can find the settings info that will enable received signal strength to appear beneath calls in the callsign display lines.
I've searched the help files but see anything relevant.

Cheers,

Wes.
GW3RIH.



de Laurie VK3AMA


locked #FT8/JTAlert

Wes Elton
 

Hi Laurie,

 

Many thanks for the speedy response.

 

I’m running JTAlert version 2.16.4.

 

Under Window/Decodes the page displayed only shows Enable Decodes which is checked with, at the bottom of the page, Display Options which are unchecked. Checking them doesn’t make the required change. There are no Extended Display options in view.

 

Apologies if I’m missing something obvious!

 

Regards,

Wes.GW3RIH.

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: 22 October 2020 21:14
To: Support@HamApps.groups.io
Subject: Re: [HamApps] #FT8/JTAlert

 

On 23/10/2020 6:42 am, Wes Elton wrote:

Can someone please advise where I can find the settings info that will enable received signal strength to appear beneath calls in the callsign display lines.
I've searched the help files but see anything relevant.

Cheers,

Wes.
GW3RIH.



de Laurie VK3AMA


locked Re: #FT8/JTAlert

Wes Elton
 

Hi Jim,

Thanks for the info. Laurie has told me the same thing but within the window/decode settings there is no Extended Display/show db option☹!

I'm clearly missing something and have asked Laurie for further advice.

Stay sake OM.
73,
Wes.
GW3RIH

-----Original Message-----
From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Jim N6VH
Sent: 22 October 2020 20:52
To: Support@HamApps.groups.io
Subject: Re: [HamApps] #FT8/JTAlert


On 10/22/2020 12:42 PM, Wes Elton wrote:
Hi All,
Can someone please advise where I can find the settings info that will
enable received signal strength to appear beneath calls in the
callsign display lines.
I've searched the help files but see anything relevant.

Cheers,

Wes.
GW3RIH.
Wes,

Go to Settings/Window. Click Show db (DXCC Name)

73,

Jim N6VH


locked Re: Audible Alerts

neil_zampella
 

Is another alert being triggered?   Are you calling CQ?  Is this during a current QSO?

Neil, KN3ILZ


On Fri, Oct 23, 2020 at 02:04 AM, Norm Fasoletos wrote:

I have all the settings correct, when I test the sound "calling you" it works fine, I hear it. When someone calls me, I get a visual indication in red but no sound.
 
Not sure where to look further?
 
Norm - K7NWF
Hide quoted text

 

On Thu, Oct 22, 2020 at 12:17 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 23/10/2020 1:06 am, Norm Fasoletos wrote:
I am having a problem with an audible alert for my call sign. When I receive a call from another station, no alert. I have my call sign alert on, did a test from the software and it works, however, when another station calls me, I get so sound alert. My other alerts for new states, new grids, etc work just fine.

Your help is appreciated ...

73

Norm - K7NWF 

If JTAlert is showing the "Own Call" alert coloring but not producing the audio alert than likely you don't have the sound file set for the Alert. If the coloring is also not working than you likely don't have a Callsign set or an incorrect Callsign set for the Alert. See the Settings window, "Alerts -> Own Call" section.

de Laurie VK3AMA

 

 

 

 


locked Re: Audible Alerts

Darrell Carothers
 

As I was given helpful advice, you have to assign each alert to a sound file. This is done under view I believe. That is how I fixed mine. Someone helped me so I am trying to pay it forward.

Darrell
N5FTW 

Sent from my over-rated IPhone 7 Plus.  Any Mis-spellings or grammar errors are due to my IPhone auto correct feature.

On Oct 23, 2020, at 01:04, Norm Fasoletos <norm.k7nwf@...> wrote:


I have all the settings correct, when I test the sound "calling you" it works fine, I hear it. When someone calls me, I get a visual indication in red but no sound.

Not sure where to look further?

Norm - K7NWF

On Thu, Oct 22, 2020 at 12:17 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 23/10/2020 1:06 am, Norm Fasoletos wrote:
I am having a problem with an audible alert for my call sign. When I receive a call from another station, no alert. I have my call sign alert on, did a test from the software and it works, however, when another station calls me, I get so sound alert. My other alerts for new states, new grids, etc work just fine.

Your help is appreciated ...

73

Norm - K7NWF 

If JTAlert is showing the "Own Call" alert coloring but not producing the audio alert than likely you don't have the sound file set for the Alert. If the coloring is also not working than you likely don't have a Callsign set or an incorrect Callsign set for the Alert. See the Settings window, "Alerts -> Own Call" section.

de Laurie VK3AMA

<IMG_1961.jpg>


locked Re: Strange UI phenomenon

Björn SM7IUN
 

Thanks Laurie.

I reported the audio device naming issue here in March and Panos SV1GRN confirmed it.

In the thread the problem was initially believed to be about remembering settings but it 
was really about character sets. Perhaps the later parts of that thread went past you.

The workaround we found was to replace the name of the audio device assigned by 
Windows to a name containing only plain ASCII characters.

Windows' default name for an output audio device contains non-ASCII characters in many 
languages. "Speaker" is "Högtalare" in Swedish etc. If you try to use a device with such a 
name you will get a pop-up "Cannot locate the last used sound output device" every time 
you start the program, forcing you to select it once again. 

JTAlert seems to replace non-ASCII characters in the device name with a question 
mark. (See below). This is the likely reason for it not being correctly remembered.

If you rename your own speaker to something with umlauts or diacriticals you should 
be able to easily reproduce this.

73

Björn SM7IUN

image.png


Den fre 23 okt. 2020 kl 04:42 skrev HamApps Support (VK3AMA) <vk3ama.ham.apps@...>:

On 22/10/2020 7:31 pm, Björn SM7IUN wrote:
From time to time I find the "Help" menu replaced by the name of a newly connected audio device.

Is this intentional? I assume not.

Also, JTAlert seems to suffer from the inability to handle UTF-8 in device names of which some are 
created by default in non-English Windows. The different effects of this have been reported previously.

Björn SM7IUN

image.png


No it is not intentional.
It is due to a code defect in the creation of additional sound device selection menus when a new audio device is detected. When this occurs, your only recourse is to restart JTAlert.

What is this "inability to handle UTF-8 in device names" problem? What is not working?

de Laurie VK3AMA


locked Re: Audible Alerts

Norm Fasoletos <norm.k7nwf@...>
 

I have all the settings correct, when I test the sound "calling you" it works fine, I hear it. When someone calls me, I get a visual indication in red but no sound.

Not sure where to look further?

Norm - K7NWF

On Thu, Oct 22, 2020 at 12:17 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 23/10/2020 1:06 am, Norm Fasoletos wrote:
I am having a problem with an audible alert for my call sign. When I receive a call from another station, no alert. I have my call sign alert on, did a test from the software and it works, however, when another station calls me, I get so sound alert. My other alerts for new states, new grids, etc work just fine.

Your help is appreciated ...

73

Norm - K7NWF 

If JTAlert is showing the "Own Call" alert coloring but not producing the audio alert than likely you don't have the sound file set for the Alert. If the coloring is also not working than you likely don't have a Callsign set or an incorrect Callsign set for the Alert. See the Settings window, "Alerts -> Own Call" section.

de Laurie VK3AMA


locked Re: Strange UI phenomenon

HamApps Support (VK3AMA)
 

On 22/10/2020 7:31 pm, Björn SM7IUN wrote:
From time to time I find the "Help" menu replaced by the name of a newly connected audio device.

Is this intentional? I assume not.

Also, JTAlert seems to suffer from the inability to handle UTF-8 in device names of which some are 
created by default in non-English Windows. The different effects of this have been reported previously.

Björn SM7IUN

image.png


No it is not intentional.
It is due to a code defect in the creation of additional sound device selection menus when a new audio device is detected. When this occurs, your only recourse is to restart JTAlert.

What is this "inability to handle UTF-8 in device names" problem? What is not working?

de Laurie VK3AMA


locked Re: Question

HamApps Support (VK3AMA)
 

On 23/10/2020 8:09 am, Neil wrote:
I have asked this before and apologize for asking again but I lost the reply, sorry about that.
In JT alert on 12m (it seems band specific) the alert box has a yellow background that carries over to WSJT-X spots. How do I remove the yellow from JT Alert. I know it is likely a filter but where to find it and turn it off??
Thanks
Neil   N4FN

If you're getting Callsign coloring it is because the Alert that corresponds to that color was triggered. You cannot remove specific colors except by disabling the associated Alert on the Band in question.

If you are still using the default colors, a yellow background indicates either a Dxcc or US State Alert, the text color identifies which (red = dxcc, black= state). You can see your current Alert color settings quickly via the "Alert Types Summary Window"
   

JTAlert is alerting you to something that is needed on 12m per your current requirements. If you don't want to see those alerts on 12m, turn off the 12m band for the Alert or adjust its Band Tracking to "Amy Band" and hopefully the reason for the Alert (say dxcc or State) has already been confirmed on another Band.

de Laurie VK3AMA


locked Question

Neil <n4fn.neil@...>
 

I have asked this before and apologize for asking again but I lost the reply, sorry about that.
In JT alert on 12m (it seems band specific) the alert box has a yellow background that carries over to WSJT-X spots. How do I remove the yellow from JT Alert. I know it is likely a filter but where to find it and turn it off??
Thanks
Neil   N4FN


locked Re: JTAlert Decodes Window

 

Thanks Laurie. I didn't, but I do now! Hi. Works fine. Just getting set up on a new computer and to much to remember at 80 yrs old. Hi

John   NA6Y