Date   

locked Re: V2.15.2 looses audio alerts

Gary - AC6EG <gdefeyter@...>
 

I found that v2.15.3 intermittently caused my alert sounds to "studder."  The alerts would sound great for a few minutes, but would then start to sound like the words were spoken underwater.  Once it started doing that, the only cure was to stop and restart the program.
I am using JTAlert on a Win7 Pro - 32bit desktop with WSJT-X v2.1.0 and a TS-590SG.  I've temporarily reverted back to JTAlert v2.15.1. 

de Gary - AC6EG   


locked Re: logging wrong frequency aafter QSO

John K9IJ
 

Tory,

The band logged is dependent on the band selected in WSJT. If that band is wrong, the QSO will still take place
but the band sent to JTAlert will be incorrect and then logged incorrectly to ACLog. Even if rig control is running
and the rig is on a different band.

John - K9IJ


On 11/16/2019 9:26 AM, Tory Wiedenkeller wrote:
I use N3FJP in conjunction with WSJT-X and JT-Alert. The WSJT-X is setup for rig control of my Icom 7300. I'm working almost entirely in FT8  among the: 80, 40, 20, 17m bands.
I've noticed on a few occasions now when I've logged a QSO, there is a discrepancy between the band/freq that N3FJP logs the QSO, and the actual band/freq the QSO took place on
For ex. I recently had a QSO with a station in Alaska on 40m band. Everything seemed to log into N3FJP fine, but when I went back and looked at this log, it showed the QSO actually took place on the 80m band rather than 40m
       So, I'm wondering if anyone knows why this would happen and how to fix this problem?  I'm getting emails from these stations telling me the info is wrong. Of course it is. N3FJP is not logging the data correctly.

-- 
No trees were killed in the sending of this message. However, a large number of electrons were terribly inconvenienced !

k9ij@...
Webmaster, Network Admin, Janitor


locked logging wrong frequency aafter QSO

Tory Wiedenkeller
 

I use N3FJP in conjunction with WSJT-X and JT-Alert. The WSJT-X is setup for rig control of my Icom 7300. I'm working almost entirely in FT8  among the: 80, 40, 20, 17m bands.
I've noticed on a few occasions now when I've logged a QSO, there is a discrepancy between the band/freq that N3FJP logs the QSO, and the actual band/freq the QSO took place on
For ex. I recently had a QSO with a station in Alaska on 40m band. Everything seemed to log into N3FJP fine, but when I went back and looked at this log, it showed the QSO actually took place on the 80m band rather than 40m
       So, I'm wondering if anyone knows why this would happen and how to fix this problem?  I'm getting emails from these stations telling me the info is wrong. Of course it is. N3FJP is not logging the data correctly.


locked File naming on site

Guy G4DWV 4X1LT
 

Hi,

Since the "HamApps" was dropped from the filename of JTAlert, the files for download have lost their consistency. That means I have to rename at least one to keep them together in my downloads.

Could either the old name be reinstated or could  "JTAlert" replace the "HamApps" in the other two?
--
73 de Guy G4DWV 4X1LT


locked Band activity - how long to close?

Ed
 

Hello,

Placing the cursor over the list of bands in the upper right hand corner of the JTalert window the activity per band listing pops up. What controls how long the popup stays open? Is there some action I can take to close it on demand?

Thank you,

Ed W2GHD


locked Re: V2.15.2 looses audio alerts

Rick Boswell
 

Yaay! 2.15.3 fixes my "no sound" problem with 2.15.2. Thanks!

Rick
K8EZB


locked New JTAlert 2.15.3 is available. #Announcement #NewRelease

HamApps Support (VK3AMA)
 

The Latest JTAlert version 2.15.3 is now available @ https://hamapps.com/JTAlert/

Significant in this release are fixes to non-playing audio plus other audio fixes and usability improvements.

Please review the Release notes at the end of this message.

de Laurie VK3AMA

The Release Notes...

  *** Includes Callsign database file version 2019-11-16 (2019-November-16)

  New Features:

    - Ability to select the Sound device to use for alerts via the "Sound" menu.

  Changes:

    - Toggle Sound on/off hotkey has been removed.

    - Country name change, Swaziland is now "Kingdom of Eswatini". This is a
       cosmetic change, the underlying dxcc number as used by the Dxcc Alert
       remains unchanged (# 468).

  Fixes:

    - Sound Card drop-down list in the Settings window not highlighting active
       selection after JTAlert restart.

    - Sound not playing for a small number of users.

    - Callsigns display not cleared for non FT8/FT4 modes (JT65, JT9, MSK144)
       at approximately 48 seconds of the current minute.

    - Installed callsign database version included with the JTAlert installer not
       shown in the Program Updates section of the Settings window when an older
       database was previously installed by the standalone Database installer.


de Laurie VK3AMA


locked Re: Normal behaviour?

Joe Subich, W4TV
 

On 2019-11-15 2:00 PM, Uwe wrote:

However, when I am working a new DXCC (by band or mode) JTAlert doesn't recognize this as "worked" unless I manually click on "Scan Log and Rebuild". >
Is that by design?
Yes, JTAlert does not update its database until "Scan Log and Rebuild".

Typically, one would not want to take an entity off the "needed" list
until receiving a card or confirmation by LotW. That would only be
recorded as a result of scanning the log.

73,

... Joe, W4TV


On 2019-11-15 2:00 PM, Uwe wrote:
Hi, I am using JTAlert 2.15.2 with logging enabled (Standard ADIF File). ADIF file contains all necessary information about DXCC, CQZ, ITUZ, State, QSL and so on. Scan Log and Rebuild also works fine so far. Setting under DXCC "Tracking" to one of the possible combinations fives always the intended logic.
However, when I am working a new DXCC (by band or mode) JTAlert doesn't recognize this as "worked" unless I manually click on "Scan Log and Rebuild".
Is that by design? Or am I doing something wrong?
At "Scan Log and Rebuild" / "Wanted DXCC" I've selected "No QSL Confirmation (Any Worked Station).
73 de Uwe, DG2YCB


locked Normal behaviour?

Uwe, DG2YCB
 

Hi, I am using JTAlert 2.15.2 with logging enabled (Standard ADIF File). ADIF file contains all necessary information about DXCC, CQZ, ITUZ, State, QSL and so on. Scan Log and Rebuild also works fine so far. Setting under DXCC "Tracking" to one of the possible combinations fives always the intended logic.

However, when I am working a new DXCC (by band or mode) JTAlert doesn't recognize this as "worked" unless I manually click on "Scan Log and Rebuild".

Is that by design? Or am I doing something wrong?

At "Scan Log and Rebuild" / "Wanted DXCC" I've selected "No QSL Confirmation (Any Worked Station).

73 de Uwe, DG2YCB


locked Re: V2.15.2 looses audio alerts

HB9CQK
 

Dear Laurie, I have the same issue with no audio in 2.15.2. I am using Flex radio and did not encounter any delay issues before. I am willing to test your fix as well.

Thank you very much and 73 de Frédéric, HB9CQK


locked Re: V2.15.2 looses audio alerts

HamApps Support (VK3AMA)
 

On 15/11/2019 9:12 am, John Petrocelli via Groups.Io wrote:
  The only "kink" I see is that sometimes when I restart the system, there will be no audio.  I simply, select the "Other" audio device (Not same sound device as radio !) and then close and restart JTAlert.  This works every time.
John,

Not remembering the selected Sound Device across JTAlert restarts is corrected in the next release. Check your email I have sent you a link to the latest build to test.

de Laurie VK3AMA


locked Re: V2.15.2 looses audio alerts

Dave Cole
 

Hi Mike,
That was me that reported the reload... I use a program called quickmix. It snapshots the entire audio setup, and will replace it. I was not in trouble shoot mode, so I just shotgunned it...

Now that I see a bug is active, I may move back one version till the new one is released...

I am also just starting to use a Windows 10 machine, (normally use Linux), so I am going through hoops trying to get back into the "Windows" mindset, God help me.

I had just assumed it was a BUOD error on my part...

BUOD = Bad User On Device... :)

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist
ARRL Asst. Director, NW Division, Technical Resources

On 11/14/19 12:53 PM, Mike Horn wrote:
I lost my audio alerts as well with version2.15.2.  I tried everything in the book; Windows audio settings, JTAlert settings, program start/restart, etc....but no dice.
Finally gave up and reverted to version2.15.1 and everything works fine.  I saw another post where someone used a software to reload his previous
Windows settings but does not specify what values changed (for those of us who do not utilize that software).  I have had no problems in the life of JTAlert
when upgrading so this has me baffled. I assume that the reversion indicates a changed Windows setting.  Hopefully someone will be able to identify the problem
so we can get back to upgrading.
Also, a heartfelt*thanks* to all those involved in the development of this fun software.
Mike N8FRI


locked Re: V2.15.2 looses audio alerts

John Petrocelli
 

Hello,

  As Laurie has said, this was released wit some limited testing.

   It works here very well (Running Win 7 64bit).

   The only "kink" I see is that sometimes when I restart the system, there will be no audio.  I simply, select the "Other" audio device (Not same sound device as radio !) and then close and restart JTAlert.  This works every time.
    I seem to need to switch back and forth from "Default Sound Device"  from/to "USB Audio".

    As a rule now, I ALWAYS do a "Test Sound Card" from the Settings drop down when I start JTAlert.  BTW, I have a monitor with internal speakers so that is the "Other" audio device that I mention.


Thanks again Laurie for all your GREAT work !!
John - WA2HIP
John R. Petrocelli - WA2HIP
¶¶¶¶¶¶¶¶¶¶
Primary Home Page:
   http://wa2hip.com
On 11/14/2019 9:16 PM, HamApps Support (VK3AMA) wrote:

On 15/11/2019 7:53 am, Mike Horn wrote:
I lost my audio alerts as well with version2.15.2.  I tried everything in the book; Windows audio settings, JTAlert settings, program start/restart, etc....but no dice.
Finally gave up and reverted to version2.15.1 and everything works fine.  I saw another post where someone used a software to reload his previous
Windows settings but does not specify what values changed (for those of us who do not utilize that software).  I have had no problems in the life of JTAlert
when upgrading so this has me baffled. I assume that the reversion indicates a changed Windows setting.  Hopefully someone will be able to identify the problem
so we can get back to upgrading.
Also, a heartfelt thanks to all those involved in the development of this fun software.
Mike N8FRI
Mike,

2.15.2 introduced a new audio library into the code. This was a rapid change (minimal testing) due to the excessive audio delays experienced by Flex users (5, 10 & 30 seconds) with 2.15.1. The new 2.15.2 library resolved the audio delay issues, but brought with it several bugs that have come to light since its introduction. Apparent non playing of audio is one of them. A new build of JTAlert that replaces this hastily added audio library is currently with the Test team. Check you email, I have sent you direct a link to the latest build, please test and report back.

de Laurie VK3AMA




locked Re: Can someone else help, please?

randybuckner
 


Thanks, Jim, we were indeed talking apples and oranges. All is well now.

-----Original Message-----
From: Jim N6VH <jpreston1@...>
To: Support <Support@HamApps.groups.io>
Sent: Thu, Nov 14, 2019 3:22 pm
Subject: Re: [HamApps] Can someone else help, please?



On 11/14/2019 8:08 AM, randybuckner via Groups.Io wrote:
> I have a Help, but it has no drop down menu. Thanks though.
> _._,_._,_

In JTAlert, if there is no drop-down menu when you click on the "?" or
"Help", there is something wrong. My first suggestion would be to
install the program again. If that doesn't work, download it again, and
then install it again. If one of those doesn't work, hopefully Laurie
will have an answer.

It just occurred to me, that we might be talking about two different
"Help" buttons. I was talking about the one on the main screen. If you
are referring to the one in the Settings/Alerts/Wanted US State screen,
there is no drop-down list on the Help buttion. However, if you click on
that Help button, it should take you to the main Help screen, where
there is a section called "Troubleshooting". It looks like the attached
picture.

73,

Jim N6VH







locked Re: Can someone else help, please?

Jim N6VH
 

On 11/14/2019 8:08 AM, randybuckner via Groups.Io wrote:
I have a Help, but it has no drop down menu. Thanks though.
_._,_._,_
In JTAlert, if there is no drop-down menu when you click on the "?" or "Help", there is something wrong. My first suggestion would be to install the program again. If that doesn't work, download it again, and then install it again. If one of those doesn't work, hopefully Laurie will have an answer.

It just occurred to me, that we might be talking about two different "Help" buttons. I was talking about the one on the main screen. If you are referring to the one in the Settings/Alerts/Wanted US State screen, there is no drop-down list on the Help buttion. However, if you click on that Help button, it should take you to the main Help screen, where there is a section called "Troubleshooting". It looks like the attached picture.

73,

Jim N6VH


locked Re: JT Alert 2.14.5 FT4 Problem With Remembering States

randybuckner
 

I solved my own problem, and it must be a glitch in the programming. I tried almost everything, because it wasn't remembering, wasn't changing colors, and alerting on everything. When I moved my countries wanted to countries not wanted, all of a sudden my states starting working, colors changed, and I got it remembering states not wanted. Why this had anything to do with moving countries to the not wanted column is anyone's guess, but I think is is a glitch in the program. FWIW.



-----Original Message-----
From: Laurie, VK3AMA <hamapps.support@...>
To: Support <Support@HamApps.groups.io>
Sent: Thu, Nov 14, 2019 1:03 pm
Subject: Re: [HamApps] JT Alert 2.14.5 FT4 Problem With Remembering States


On 14/11/2019 7:21 pm, randybuckner via Groups.Io wrote:
> So where exactly is this troubleshooting section located? I don’t see
> it on quick perusal.

Its in the JTAlert Help File.

de Laurie VK3AMA





locked Re: V2.15.2 looses audio alerts

HamApps Support (VK3AMA)
 

On 15/11/2019 7:53 am, Mike Horn wrote:
I lost my audio alerts as well with version2.15.2.  I tried everything in the book; Windows audio settings, JTAlert settings, program start/restart, etc....but no dice.
Finally gave up and reverted to version2.15.1 and everything works fine.  I saw another post where someone used a software to reload his previous
Windows settings but does not specify what values changed (for those of us who do not utilize that software).  I have had no problems in the life of JTAlert
when upgrading so this has me baffled. I assume that the reversion indicates a changed Windows setting.  Hopefully someone will be able to identify the problem
so we can get back to upgrading.
Also, a heartfelt thanks to all those involved in the development of this fun software.
Mike N8FRI
Mike,

2.15.2 introduced a new audio library into the code. This was a rapid change (minimal testing) due to the excessive audio delays experienced by Flex users (5, 10 & 30 seconds) with 2.15.1. The new 2.15.2 library resolved the audio delay issues, but brought with it several bugs that have come to light since its introduction. Apparent non playing of audio is one of them. A new build of JTAlert that replaces this hastily added audio library is currently with the Test team. Check you email, I have sent you direct a link to the latest build, please test and report back.

de Laurie VK3AMA


locked Re: V2.15.2 looses audio alerts

Mike N8FRI
 

I lost my audio alerts as well with version2.15.2.  I tried everything in the book; Windows audio settings, JTAlert settings, program start/restart, etc....but no dice.
Finally gave up and reverted to version2.15.1 and everything works fine.  I saw another post where someone used a software to reload his previous
Windows settings but does not specify what values changed (for those of us who do not utilize that software).  I have had no problems in the life of JTAlert
when upgrading so this has me baffled. I assume that the reversion indicates a changed Windows setting.  Hopefully someone will be able to identify the problem
so we can get back to upgrading.
Also, a heartfelt thanks to all those involved in the development of this fun software.
Mike N8FRI


locked jt alert sound stopped working for me, too

Jeff Otterson
 

My audio alerts stopped working in JTAlert, too.  2.15.2 on Windows 10 pro 1903

I have tried the following:

* change the sound card, exit jtalert, change the sound card back (to "Speakers (high definition audio device)")
* DX keeper and system sounds are configured for "Speakers (high definition audio device)", Joe DX talks, windows dings wor
* uninstall jtalert, delete configurations, re-install.  still no sound.
* task manager shows JTAlert V2 Alert Manager process is running

I sure wish I could make it ding and talk again.

Any ideas?

Thanks

Jeff n1kdo


locked Re: Worked B4 Color Isn't Changing

WA8RZR - Jan Blair
 

Laurie,

As a follow-up, I fell back to Version 2.14.5 and the Worked B4 indication is working correctly again. Nothing else was changed in my computer environment.

Thanks again for all your effort on this wonderful tool.

73,

Jan Blair
WA8RZR