[ADXA] JTAlert 2.50.2

[sbranyan at cox.net]

>> But he never could copy CW at a rate of even 5 WPM!<< 
Guilty as charged, San. My 67 yo brain loves cw skimmer. Da di-di-dah 

Working with software updates is whole lot easier than drilling code for hours a day. hihi

73
Scott


-----Original Message-----
From: Sandy Hutson [mailto:k5yy1 at cox.net] 
Sent: Wednesday, June 23, 2021 5:49 PM
To: sbranyan at cox.net; 'ADXA'
Subject: RE: [ADXA] JTAlert 2.50.2

Scott: 

Says a lot as to why I will never get on the FT8/FT4 or such inaudible modes. They serve a purpose if SSB or CW can not be heard in the -5 to 0 dB range, narrow bandwidths. But there are so many reports of those on the FT8 system having constant update changes and disruptions of the software, and when actually operating those softwares out there, the DX station or DXpeditions may be using different systems of how and where to call and such… and what reports to give that indicate an “OK” QSO or not. Some don’t know until actually seeing a log update on a website or on Club Log.. At least on CW or SSB or RTTY I know when I am in the log 98% of the time. 😁

 

I do admire the efforts and sympathize with the depressive moments many FT8 ops have in trying to make SUBaudible signal “contacts via a software system that updates too often it seems. Too many hours spent by the new FT8 guys especially, in just getting a QSO and fighting the reasons why contacts are not being made, etc etc … I won’t go into the many reasons people have in continuing in or dropping out of the software modes. I like to hear what I am working, and on my team DXpeditions my SSB rates are usually 5-6 QSOs a minute if big pileups and up to 6 if working the polite JA stations. CW was a bit slower for me personally but usually 4-5 Qs a minute if good separation “listening up” or going by call areas. I guess one day “software” in sub-audible modes can answer several a minute, but will the chasers on the other side “see” their call or know a contact exists? And will the DXpedition software see a good high % of “confirms” on their system? .. Final confirmations make take a few minutes, so you gotta keep “LOOKING” at a PC screen’s data… ☹ 

 

Again, I appreciate Scott’s persistence in his new hobby of ham radio and his willingness to find out a “fix” in software screwups that are not his fault usually.  I am in the group of guys who wonder why many times very audible signals are present and more SSB, CW or RTTY is not being used. If that trend continues, we are in for a further decline in audible modes of operation. If signals are way down in the -20 to -5 dB range, then I 100% understand having a software program listen for you and convert to a QSO system of contacts that nobody knew was possible 5 years ago. But if someone is totally deaf I understand CW and SSB are not possible, so FT modes are OK. If a person is blind then FT modes are useless but SSB and CW can be heard and logged by brail systems out there for decades, like W5TIZ, Dick Freeling, did for years and was on the DXCC Honor Roll. Our ham hobby and making contacts has taken on a new system and seems like one that will keep changing every few months and software “updates” will be needed.  SSB and Morse Code will not need updating from what we have known for many decades. And I do not mean to bring in the Morse Code “readers” situation either!! 😊  Had a ham acquaintance who used a code reader to work CW DXCC years ago. He dropped ham radio as a hobby in 1992 and passed away 2 years ago. But he never could copy CW at a rate of even 5 WPM! Guess the ‘reader’ had an early software inside that was ‘new’ to ham radio.  73 to all ADXA members. 

 

San K5YY   >>  in this crazy hobby since 1957 and like most aspects of it… hmmm  😉 👍

 

Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986>  for Windows 10

 

From: sbranyan at cox.net
Sent: Wednesday, June 23, 2021 9:34 AM
To: 'ADXA' <mailto:ADXA at mailman.qth.net> 
Subject: [ADXA] JTAlert 2.50.2

 

It's been frustrating over the past month with JTAlert updates. The developer redesigned the Call Alert Window in 2.50.1 requiring installation of Windows NET 5 Desktop Runtime app. I started having issues with the call alert window closing and opening up when TXing in WSJT-X. WSJT-X would then crash in at the start of the QSO! 

 

I looked on their group discussion page, and the developer had no help other than the usual, "It's the antivirus software. Disable it. Norton is especially bad." OK. I'm not going there. Been down that road too many times. 

 

Another week or so past and I was still having issues with crashes. Dev said Windows Runtime had sent out an auto update 5.07 and that was the culprit. So I uninstalled 5.07 and reinstalled 5.06 runtime. Problem solved until runtime auto installed 5.07 again. Dev said to turn off auto updates. Sorry, but if your software doesn't work, it doesn't work. Dev then said to turn off the sound notifications and that would be a temporary fix. I did as suggested. But WSJT-X still crashed. So I uninstalled runtime and JTalert. WSJT-X crashed a few more time until I rebooted. Then it seemed to run stable. 

 

Yesterday, JTAlert came out with 2.50.2. I installed it last night and tested it all evening. Smooth as silk. Dev said it was able to address the issues with a component of Runtime so that it and JTAlert finally play nicely together. So I am hoping it's resolved. 

 

The new call alert window takes some getting used to but has some nice features I am still exploring. For one, it has unlimited call alert capacity so it doesn't stop alerting after the window box fills. You just scroll down to see more of the window and alerts if there are a bunch all at once. It does run very smoothly with no hiccups like the most recent versions. 

 

I am a big proponent of keeping windows and apps up-to-date. Sure, there will be issues, but it's the only way to stay safe online and take advantage of new features. Small software developers have a big job keeping up-to-date with windows releases, and this was an example of how it sometimes just takes patience until the developer can work the issues out. 

 

So last night I was able go back to sound alerts and to chase JW and XT2AW--unsuccessfully but I had some shots. I did pick up ES and EI on 5W.  So my QRP DXCC pursuit stands at 65 LOTW confirms in mid-April. JTAlert is a big help to me and I am glad it is back to working well. 

 

One other note. I was listening to FT8 frequencies the other night just to check propagation. I was surprised how many times I heard JTAlert call alerts on the freq. So there are hams out there who don't have their audio settings set right and the windows sounds are TXing on the freq. I heard this on different frequencies, so it seems to be a general problem. Read the manual if you have question on this. 

 

Both my audio output and input selections under settings in WSJT-X are set to USB Audio Codec. And under Windows sound settings, output (speakers) is set to Realtek High Definition Audio and input (microphone) set to USB Audio Codec. If your windows output is on audio codec, it will TX your windows sounds on the air! 

 

That is all.

 

73,

Scott/W5AAJ