[ADXA] JTAlert 2.50.2

Thu Jun 24 11:59:37 EDT 2021

Jay, these are great points.  As you know, I am deep into technology in the
banking sector, and certainly try to keep up with technology around the ham
shack.  I have been frustrated with FT8, I get it working then
something changes and it is back to the drawing board.  As you mention, a
lot of it is around the sound card interface, even with my IC-9100 that has
a direct USB connection and eliminates my SignalLink.  For me, it is a
decision about how to spend my operating time . . . reconfiguring windows
or calling CQ?

I will say that the future is clearly web based applications that don't
rely on a particular hardware configuration, but instead leverage the
browser. But I know that development for this level (especially for
software that is given away for free) is more complex.  Like you, I use
DXLabs, and N1MM, can't think of doing a contest without N1MM, for example.

The beautiful thing about our hobby is that there's something for
everyone!  I would never say "you shouldn't do thus" because I want
everyone to have fun!

I so appreciate these conversations, and the civility that runs through
them.

73,

Trent
N4DTF

On Wed, Jun 23, 2021 at 8:32 PM Jay Bromley <jayw5jay at cox.net> wrote:

> Hi San,
>
> We live in a world now that everything that runs on software will need an
> update every so often.  From Lawn mowers to even your 7600 Icom, hi.  In
> the latter case, not doing the firmware updates one is losing advance
> performance features and bug fixes!
>
>
>
> It may seem like FT8 is confusing or we don’t know when a contact is made
> or confirmed, but those are special circumstances!  Like running N1MM with
> WSJT-X in a contest.  I will almost guarantee the fix is in the works for
> the next contest using that software combo.  Think of it like this, a 3rd
> party software is adding or linking to another one piece of software that
> is not under their control.  So it takes some feedback from each other to
> fix and iron out the bugs.    While I did comment a few weeks back on the
> N1MM/WSJT-X software was hard to know if there was a confirmation during
> that contest, the same thing would have happened in SSB or CW with fade out
> conditions.  That was on 6m during a contest with weird conditions.  They
> were there 15 seconds and gone not to be seen or heard again.
>
>
>
> Last night I ran about 100 FT8 QSOs on 17m and I can guarantee all or
> nearly all of them are 100 % worked/confirmed.  Even in the past with CW
> and SSB I had the NIL a few times and I know I got the TU on CW, hi.
>
>
>
> This isn’t JTA or WSJT-X that is broke.  It is Windows .NET frame that is
> breaking with their upgrades so now everyone needs to catch up or wait
> until MS gets their act together.
>
>
>
> Here is a typical example on what can happen:
> https://www.windowslatest.com/2021/05/14/latest-windows-10-update-issue-is-trashing-audio-quality/
>
>
>
> Since most if not all digital modes rely on sound card audio of some type,
> this is going to be a way of life.  There are fixes in the mean time for
> it.  The main thing is to delay the upgrades on Windows and maybe if needed
> go back to an earlier NET frame.  SDR radios they have also been effected
> by this as well.
>
>
>
> BTW I am using the latest software on everything here, including Win10
> Pro.  I am using DXlab, Gridtracker, WSJT-X, JTAlert, HDSDR, and Thetis
> another SDR.  Most of this is mission critical around an Icom 7610.  So I
> am running around 12 programs all at once with an old computer, hi.  I am
> ashamed to say how old!  I need to upgrade, pun intended.
>
>
>
> There is nothing to fear, but the unknown of not knowing.  My very good
> friend Curt KI5AK in Houston also has a thing about upgrades.  We are the
> same age and grew up together so I am not talking behind his back.  IIWII!
> I am not sure where this “don’t upgrade” or try something new came from?
> However if he were to upgrade my old 7700 I sold him many years ago, in so
> many ways it would be a completely new radio for FREE!  This I am not
> kidding, it would add a new audio scope, waterfall he currently doesn’t
> have and point-n-click for the signals on the 7700 bandscope.  That is just
> the stuff I remember!  Plus improved APF for CW!  No telling how many
> undocumented bug fixes in there as well.  I even sent him a thumb drive
> with the firmware in the right directory.  It would take him less than 5
> minutes to completely get new radio!  Less if I was there doing and I have
> offered.  Still he has this mental image that it might break something on
> his beloved IC7700.
>
>
>
> I have 3 HF radios here and they all are on the current or latest
> firmware.  Elecraft to Icom here and they all get the latest/greatest
> releases.  I can only think of one time each that needed a revision and
> both times were not deal breakers that kept me off the air.
>
>
>
> I will agree we had more on the air time back when we were using Drake
> lines with no computers.  Not sure we had more fun, especially during a low
> end of a solar cycle??
>
>
>
> 73 de w5jay/jay..
>
>
>
>
>
>
>
> *From:* adxa-bounces at mailman.qth.net <adxa-bounces at mailman.qth.net> *On
> Behalf Of *Sandy Hutson
> *Sent:* Wednesday, June 23, 2021 6:04 PM
> *To:* w5zn at w5zn.org
> *Cc:* 'ADXA' <ADXA at mailman.qth.net>
> *Subject:* Re: [ADXA] JTAlert 2.50.2
>
>
>
> Joel…Even that statement perplexes me! HI 😊
>
> Guess mentally and at my advanced age my mind gets confused almost daily
> about old commonly known things. Now where did I put that or why did I come
> from the radio room to the kitchen to tell my wife something or what did I
> have planned today if not written down, etc…. HI   Wud rather be alive and
> forgetful than passing away too soon I guess.
>
> 73 and will check into the JTnon-Alert firmware with “x” submonitor
> alert.. hmmm  Overall, I like QUICK QSOs and knowing things went well for
> 7-8 seconds. 😂
>
> San
>
>
>
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
> Windows 10
>
>
>
> *From: *w5zn at w5zn.org
> *Sent: *Wednesday, June 23, 2021 5:52 PM
> *To: *Sandy Hutson <k5yy1 at cox.net>
> *Cc: *sbranyan at cox.net; 'ADXA' <ADXA at mailman.qth.net>
> *Subject: *Re: [ADXA] JTAlert 2.50.2
>
>
>
> San,
>
> Do NOT confuse the FT8 software in the WSJT-x suite with the JTAlert
> software.
>
> Two separate animals.
>
> 73 Joel W5ZN
>
>
>
> On 2021-06-23 16:48, Sandy Hutson wrote:
>
> 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' <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
>
>
>
>
>
> ______________________________________________________________
> ADXA mailing list
> Home: http://mailman.qth.net/mailman/listinfo/adxa
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:ADXA at mailman.qth.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
>
>
> ______________________________________________________________
> ADXA mailing list
> Home: http://mailman.qth.net/mailman/listinfo/adxa
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:ADXA at mailman.qth.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html

-- 
Trent Fleming

 My blog on banking topics:

www.bankinginsights.blogspot.com

My web site

        www.trentfleming.com

Follow me on FaceBook
        www.facebook.com/thetechnologyadvisor

Follow me on Twitter
        www.twitter.com/techadvisor
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qth.net/pipermail/adxa/attachments/20210624/55cdf043/attachment-0001.html>