locked 2.2.0-rc1


Gary Gorniak
 

Installation of the 64 bit Windows version went flawlessly for me.  So far I have seen no issues.  One thing of note is that I seem to be decoding more signals that are close to the noise floor on the waterfall, in the -20 to -24 range.  Just an observation so far.  I have not quantified it.

 

As always, thanks to you and your team Joe for all the hard work!

 

73 de Gary – W9BS

 


Dave (NK7Z)
 

Same here, 64 bit, and I am seeing far deeper decodes than I have been in the past... Nicely done sirs!!

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

On 5/11/20 3:05 PM, Gary Gorniak wrote:
Installation of the 64 bit Windows version went flawlessly for me.  So far I have seen no issues.  One thing of note is that I seem to be decoding more signals that are close to the noise floor on the waterfall, in the -20 to -24 range.  Just an observation so far.  I have not quantified it.
As always, thanks to you and your team Joe for all the hard work!
73 de Gary – W9BS


Herb Blue - WB8ASI
 

Same here, and the real nice part is that the station on the other end is also getting deeper decodes that includes me !!!   Getting out better already so it seems.  Good stuff. 73 Herb WB8ASI

On May 11, 2020 at 9:16 PM Dave Cole < dave@...> wrote:


Same here, 64 bit, and I am seeing far deeper decodes than I have been
in the past... Nicely done sirs!!

73, and thanks,
Dave (NK7Z)
ARRL Volunteer Examiner
ARRL Technical Specialist
ARRL Asst. Director, NW Division, Technical Resources

On 5/11/20 3:05 PM, Gary Gorniak wrote:
Installation of the 64 bit Windows version went flawlessly for me.  So
far I have seen no issues.  One thing of note is that I seem to be
decoding more signals that are close to the noise floor on the
waterfall, in the -20 to -24 range.  Just an observation so far.  I have
not quantified it.

As always, thanks to you and your team Joe for all the hard work!

73 de Gary – W9BS





Dave (NK7Z)
 

I will be happy when folks start using this in general release... It will help.

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

On 5/11/20 6:35 PM, Herb Blue wrote:
Same here, and the real nice part is that the station on the other end is also getting deeper decodes that includes me !!!   Getting out better already so it seems.  Good stuff. 73 Herb WB8ASI
On May 11, 2020 at 9:16 PM Dave Cole < dave@... <mailto:dave@...>> wrote:


Same here, 64 bit, and I am seeing far deeper decodes than I have been
in the past... Nicely done sirs!!

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

On 5/11/20 3:05 PM, Gary Gorniak wrote:
Installation of the 64 bit Windows version went flawlessly for me.  So
far I have seen no issues.  One thing of note is that I seem to be
decoding more signals that are close to the noise floor on the
waterfall, in the -20 to -24 range.  Just an observation so far.  I have
not quantified it.

As always, thanks to you and your team Joe for all the hard work!

73 de Gary – W9BS




Jim Brown
 

As the old race car drivers would say, "it's quick!" That first set of decodes is happening before the end of the TX interval, which, for most signals, allows me to keep Call First turned off and still select a caller before the TX interval begins. This is a GREAT improvement!

I do notice that JTAlert needs some work to keep up. I trust that Laurie will be cracking on it.

73, Jim K9YC


Herb Blue - WB8ASI
 

Hey Jim,   It is quick, and I'm liking it.  So far for me it seems Laurie is still in the race. Was watching and the JTA Decodes Window seems to move right along with the WSJTX decodes.  I'm the one who is the slowpoke at this point. 73 Herb WB8ASI

On May 12, 2020 at 12:16 AM Jim Brown < k9yc@...> wrote:


As the old race car drivers would say, "it's quick!" That first set of
decodes is happening before the end of the TX interval, which, for most
signals, allows me to keep Call First turned off and still select a
caller before the TX interval begins. This is a GREAT improvement!

I do notice that JTAlert needs some work to keep up. I trust that Laurie
will be cracking on it.

73, Jim K9YC


Jim Shorney
 

I'll second that. Running nicely in Kubuntu 18. Not maxing out any CPU threads and markedly more perky.

73

-Jim
NU0C

On Mon, 11 May 2020 21:16:49 -0700
"Jim Brown" <k9yc@...> wrote:

As the old race car drivers would say, "it's quick!" That first set of
decodes is happening before the end of the TX interval, which, for most
signals, allows me to keep Call First turned off and still select a
caller before the TX interval begins. This is a GREAT improvement!

I do notice that JTAlert needs some work to keep up. I trust that Laurie
will be cracking on it.

73, Jim K9YC


Jim Brown
 

On 5/11/2020 9:25 PM, Herb Blue wrote:
JTA Decodes Window seems to move right along with the WSJTX decodes. I'm the one who is the slowpoke at this point.
I wrote badly. By "keep up," I mean he needs to catch up with the new beta to fix the problem noted.

73, Jim K9YC


Herb Blue - WB8ASI
 

Jim,  I missed the problem noted.   In this thread? 


JTAlert Support (VK3AMA)
 

On 12/05/2020 2:35 pm, Jim Brown wrote:
By "keep up," I mean he needs to catch up with the new beta to fix the problem noted.

73, Jim K9YC
What problem is that that JTAlert needs to fix?
What is happening with the Beta that requires a JTAlert change/fix?
I'm confused, I don't see anything in this message thread that relates to a JTAlert deficiency.

de Laurie VK3AMA


JTAlert Support (VK3AMA)
 

On 12/05/2020 2:16 pm, Jim Brown wrote:
I do notice that JTAlert needs some work to keep up. I trust that Laurie will be cracking on it.

73, Jim K9YC
Exactly, what do you mean by "to keep up"? What are you experiencing?

Also, please keep in mind, I don't get any early access to the WSJT-X betas. I only get access after it has gone public, and with time-zone differences, most users have access to the software several hours before I do. When I do get to download WSJT-X it is only then that I can do any sort of JTAlert  testing.

de Laurie VK3AMA


Herb Blue - WB8ASI
 

All working fine/great here.  JTA 2.16.5, WSJTX 2.2.0-rc1, Log4OMv2 2.5.0.0, Win10 64 bit, TS-590SG, OmniRig, Good night. 73 Herb WB8ASI

On May 12, 2020 at 1:08 AM "HamApps Support (VK3AMA)" <vk3ama.ham.apps@...> wrote:

On 12/05/2020 2:16 pm, Jim Brown wrote:
I do notice that JTAlert needs some work to keep up. I trust that Laurie will be cracking on it.

73, Jim K9YC
Exactly, what do you mean by "to keep up"? What are you experiencing?

Also, please keep in mind, I don't get any early access to the WSJT-X betas. I only get access after it has gone public, and with time-zone differences, most users have access to the software several hours before I do. When I do get to download WSJT-X it is only then that I can do any sort of JTAlert  testing.

de Laurie VK3AMA



 


Jim Brown
 

On 5/11/2020 9:56 PM, HamApps Support (VK3AMA) wrote:
On 12/05/2020 2:35 pm, Jim Brown wrote:
By "keep up," I mean he needs to catch up with the new beta to fix the problem noted.

73, Jim K9YC
What problem is that that JTAlert needs to fix?
What is happening with the Beta that requires a JTAlert change/fix?
I'm confused, I don't see anything in this message thread that relates to a JTAlert deficiency.
Hi Laurie. I'm the guy who noted issues, but didn't describe it.

What I'm seeing is that JTA works until I make a QSO and am prompted to log it. Logging fails, no error message, and no decodes. The fix is to quit JTA, restart, and wait a bit, and I get decodes.

There may be other things that cause it to stop, but I haven't IDENTIFIED any others.

When I saw this, I immediately upgraded (about 4 hours ago), and the issues are still there.

I'm logging to DXKeeper, and JTA has been flawless for a year or more.

73, Jim K9YC


Jim Preston N6VH
 

On 5/11/2020 11:54 PM, Jim Brown wrote:
On 5/11/2020 9:56 PM, HamApps Support (VK3AMA) wrote:
On 12/05/2020 2:35 pm, Jim Brown wrote:
By "keep up," I mean he needs to catch up with the new beta to fix the problem noted.

73, Jim K9YC
What problem is that that JTAlert needs to fix?
What is happening with the Beta that requires a JTAlert change/fix?
I'm confused, I don't see anything in this message thread that relates to a JTAlert deficiency.
Hi Laurie. I'm the guy who noted issues, but didn't describe it.

What I'm seeing is that JTA works until I make a QSO and am prompted to log it. Logging fails, no error message, and no decodes. The fix is to quit JTA, restart, and wait a bit, and I get decodes.

There may be other things that cause it to stop, but I haven't IDENTIFIED any others.

When I saw this, I immediately upgraded (about 4 hours ago), and the issues are still there.

I'm logging to DXKeeper, and JTA has been flawless for a year or more.

73, Jim K9YC
Jim,

I'm using WSJT-X 2.2.0-rc1 with JTAlert 2.16.5 and everything is working fine here. No problems with logging to Log4OM.

73,

Jim N6VH


Jack Dennett VE7DFJ
 

working great here as well. 

Jack
VE7DFJ


Hasan Schiers N0AN
 

Gary,
I am seeing the same thing on 20m crowded band. I am seeing MANY more -19 to -23 decodes than I ever have before in a typical sequence. 

At 1800z, 20m, I am seeing almost no positive SNR's, and even those are just +2 to +4...35 decodes per sequence or more.

My general impressions:

1. Many more total decodes per sequence
2. Many more -17 or weaker decodes per sequence.
3. Much faster decoding and presentation of same.
4. Double peak of CPU use at the two points:

At the 11 second blue light mark: 75%
At the 2nd blue light: 40%
Idling (prior to 11 sec): 7%

Intel Core I5-3470  3.2 GHz , 8 GB Ram Win10 Pro, DxLabSuites, JTAlert, Multiple Tabs of Browser window open

Very impressive, indeed!
73, N0AN
Hasan


On Mon, May 11, 2020 at 5:05 PM Gary Gorniak <w9bs@...> wrote:

Installation of the 64 bit Windows version went flawlessly for me.  So far I have seen no issues.  One thing of note is that I seem to be decoding more signals that are close to the noise floor on the waterfall, in the -20 to -24 range.  Just an observation so far.  I have not quantified it.

 

As always, thanks to you and your team Joe for all the hard work!

 

73 de Gary – W9BS

 



Hasan Schiers N0AN
 

...and one other note:

Far fewer -24 decodes than I typically get. I don't know if the scale has changed or what, but the difference is striking. I have always gotten several per sequence on 20m no matter what time of day. I just operated for half an hour and saw a total of two -24 decodes.

73, N0AN

Hasan


On Wed, May 13, 2020 at 1:24 PM Hasan Schiers N0AN via groups.io <hbasri.schiers6=gmail.com@groups.io> wrote:
Gary,
I am seeing the same thing on 20m crowded band. I am seeing MANY more -19 to -23 decodes than I ever have before in a typical sequence. 

At 1800z, 20m, I am seeing almost no positive SNR's, and even those are just +2 to +4...35 decodes per sequence or more.

My general impressions:

1. Many more total decodes per sequence
2. Many more -17 or weaker decodes per sequence.
3. Much faster decoding and presentation of same.
4. Double peak of CPU use at the two points:

At the 11 second blue light mark: 75%
At the 2nd blue light: 40%
Idling (prior to 11 sec): 7%

Intel Core I5-3470  3.2 GHz , 8 GB Ram Win10 Pro, DxLabSuites, JTAlert, Multiple Tabs of Browser window open

Very impressive, indeed!
73, N0AN
Hasan


On Mon, May 11, 2020 at 5:05 PM Gary Gorniak <w9bs@...> wrote:

Installation of the 64 bit Windows version went flawlessly for me.  So far I have seen no issues.  One thing of note is that I seem to be decoding more signals that are close to the noise floor on the waterfall, in the -20 to -24 range.  Just an observation so far.  I have not quantified it.

 

As always, thanks to you and your team Joe for all the hard work!

 

73 de Gary – W9BS