|
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..
toggle quoted messageShow quoted text
Norm - K7NWF
On Oct 23, 2020, at 11:26 AM, chas cartmel <chas@...> wrote:
|
|
|
|
locked
Re: Question
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:
|
|
|
|
locked
Re: Audible Alerts
HamApps Support (VK3AMA)
On 23/10/2020 5:04 pm, Norm Fasoletos
wrote:
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)
On 23/10/2020 6:42 am, Wes Elton wrote:
|
|
|
|
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:
|
|
|
|
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)
On 23/10/2020 6:42 am, Wes Elton wrote:
|
|
|
|
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:
|
|
|
|
locked
Re: #FT8/JTAlert
Wes Elton
Hi Jim,
toggle quoted messageShow quoted text
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,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:
|
|
|
|
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.
toggle quoted messageShow quoted text
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:
|
|
|
|
locked
Re: Strange UI phenomenon
Thanks Laurie. 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 Den fre 23 okt. 2020 kl 04:42 skrev HamApps Support (VK3AMA) <vk3ama.ham.apps@...>:
|
|
|
|
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:
|
|
|
|
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. 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. 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
|
|
|
|
locked
Re: #FT8/JTAlert
HamApps Support (VK3AMA)
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. de Laurie VK3AMA
|
|
|
|
locked
Re: #FT8/JTAlert
Jim N6VH
On 10/22/2020 12:42 PM, Wes Elton wrote:
Hi All,Wes, Go to Settings/Window. Click Show db (DXCC Name) 73, Jim N6VH
|
|
|