Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Bill Somerville]

On 01/05/2019 21:09, Christoph Berg wrote:

If that doesn't help then I can send you an instrumented version of WSJT-X
to track the CAT communication in detail, or explain how to enable that in
your own build.

I guess it's WSJT_TRACE_CAT && WSJT_TRACE_CAT_POLLS? I can try that
tomorrow.


Hi Christoph,

setting those options ON will work for a  debug configuration build. To 
get the trace working in a release configuration build you need 
WSJT_QDEBUG_IN_RELEASE=ON, and you can have the debug trace redirected 
to a file by setting WSJT_QDEBUG_TO_FILE=ON (the trace will be appended 
to /tmp/WSJT-X_trace.log). Another option that can help is 
WSJT_HAMLIB_VERBOSE_TRACE=ON , set that and you will get the equivalent 
of -v for the Hamlib trace.


73
Bill
G4WJS.

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Christoph Berg]

Re: Bill Somerville 2019-04-30 

> I don't recall if the Icom IC-706 Mk0 can accept CAT commands while
> transmitting, I doubt it as it has pretty primitive CAT control. Make sure
> that you have "Settings->General->Allow Tx frequency changes while
> transmitting" unchecked. You can also try simplifying the CAT communications
> by selecting "Settings->Radio->Mode->None", you would then set the rig to
> USB manually.

Hi Bill,

changing frequency while transmitting works, so that doesn't seem to
be the problem. CAT works generally, it just fails sometimes in random
places so I think the cause is more like wsjtx issuing too many
commands too fast, or not waiting long enough for a retry.

Rarely, there seems to be a burst of rx/tx switches happening very
fast for half a second. (Much less frequent than the "normal"
communication failures.)

> If that doesn't help then I can send you an instrumented version of WSJT-X
> to track the CAT communication in detail, or explain how to enable that in
> your own build.

I guess it's WSJT_TRACE_CAT && WSJT_TRACE_CAT_POLLS? I can try that
tomorrow.

Thanks,
Christoph


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Bill Somerville]

On 30/04/2019 20:35, Christoph Berg wrote:

Unchecking the WSPR band hopping checkbox fixed the random band
changes for me as well. I'm now also back to a bearable amount of rig
communication errors, so FT4 is actually usable now.

The error detail varies a bit, one example is Rig Communication Error:
Hamlib error: Communication timed out while opening connection to rig

I've also seen "Hamlib error: Communication timed out while sending
frequency to rig" (paraphrased)


Hi Christoph,

Joe has fixed the unintended interaction between WSPR band-hopping mode 
and FT4 mode for the next release. Thanks to you and the others 
reporting the issue and tracking down this surprising regression.


I don't recall if the Icom IC-706 Mk0 can accept CAT commands while 
transmitting, I doubt it as it has pretty primitive CAT control. Make 
sure that you have "Settings->General->Allow Tx frequency changes while 
transmitting" unchecked. You can also try simplifying the CAT 
communications by selecting "Settings->Radio->Mode->None", you would 
then set the rig to USB manually.


If that doesn't help then I can send you an instrumented version of 
WSJT-X to track the CAT communication in detail, or explain how to 
enable that in your own build.


Thanks for pushing this RC to Debian/experimental!

73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Christoph Berg]

Re: To wsjt-devel@lists.sourceforge.net 2019-04-30 
<20190430070450.gb28...@msg.df7cb.de>
> > your assumption is correct, unexplained rig control errors are a sign of
> > serious CAT issues. Which rig, what error inc. details, what settings?
> 
> IC706 (not MK-something), via rigctld.
> 
> With FT8/2.0.1, I have never had it randomly jump bands, or change
> frequency, it would just occasionally disable TX, sometimes without a
> popup, sometimes with a popup. That level of problems was manageable
> and not even really annoying. I can share error details once I'm back
> at home tonight.

Unchecking the WSPR band hopping checkbox fixed the random band
changes for me as well. I'm now also back to a bearable amount of rig
communication errors, so FT4 is actually usable now.

The error detail varies a bit, one example is Rig Communication Error:
Hamlib error: Communication timed out while opening connection to rig

I've also seen "Hamlib error: Communication timed out while sending
frequency to rig" (paraphrased)


On a side note, QSO success rate feels lower than on FT8; there were
several stations that didn't hear me while their signal was clearly
visible on the waterfall. Reliable communication was possible with
stations with positive signal readings, or maybe better than -4.
Everything below that was difficult, though some -10 stations worked
as well. On FT8, everything better than -12 is often a guarantee for
success, everything below -18 is a gamble. (I'm probably exaggerating
the readings a bit, but it does feel like the difference is more than
the 4.x dB announced in the whitepaper.)

Thanks,
Christoph

PS: 2.1.0-rc5 uploaded to Debian/experimental


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Andi Malek]

Hi All!

When I first started transmitting in FT4-mode on 20m this morning to answer a 
CQ, my RIG changed to another frequency band. This happened after each 
transmission, like reported here on the list by some other stations too.

I found out that changing the mode to WSPR, unticking the box ‚Band hopping‘ 
and change back to FT4 solved the problem for me.

Using: WIN10 64 Bit, FT-817 CAT controlled, of course V2.1.0. RC5.

73s de Andy, oe3dmb


Von: Christoph Berg
Gesendet: Dienstag, 30. April 2019 09:09
An: wsjt-devel@lists.sourceforge.net
Betreff: Re: [wsjt-devel] WSJT-X 2.1.0-rc5

Re: Bill Somerville 2019-04-29 
<0e3a78ef-8583-b7ec-0eeb-b7f11fab5...@classdesign.com>
> On 29/04/2019 22:16, Christoph Berg wrote:
> > Maybe my rig control is much more instable than the occasional "Rig
> > control error" popups suggest
> 
> Hi Christoph,
> 
> your assumption is correct, unexplained rig control errors are a sign of
> serious CAT issues. Which rig, what error inc. details, what settings?

IC706 (not MK-something), via rigctld.

With FT8/2.0.1, I have never had it randomly jump bands, or change
frequency, it would just occasionally disable TX, sometimes without a
popup, sometimes with a popup. That level of problems was manageable
and not even really annoying. I can share error details once I'm back
at home tonight.

73, Christoph


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Christoph Berg]

Re: Bill Somerville 2019-04-29 
<0e3a78ef-8583-b7ec-0eeb-b7f11fab5...@classdesign.com>
> On 29/04/2019 22:16, Christoph Berg wrote:
> > Maybe my rig control is much more instable than the occasional "Rig
> > control error" popups suggest
> 
> Hi Christoph,
> 
> your assumption is correct, unexplained rig control errors are a sign of
> serious CAT issues. Which rig, what error inc. details, what settings?

IC706 (not MK-something), via rigctld.

With FT8/2.0.1, I have never had it randomly jump bands, or change
frequency, it would just occasionally disable TX, sometimes without a
popup, sometimes with a popup. That level of problems was manageable
and not even really annoying. I can share error details once I'm back
at home tonight.

73, Christoph


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Dan Malcolm]

All is not without problems.  I didn't have any know pending updates, and 
WSJT-X 2.0.1 is working again but I am left with an echo.  Audio enhancements 
are turned off, and the echo persists.  Unless you have something off the top 
of your head, I rather not eat up forum bandwidth on this issue.  I will find a 
fix somewhere.

Thanks Bill

__
Dan – K4SHQ

-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Monday, April 29, 2019 7:19 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X 2.1.0-rc5

Hi Dan,

glad to here that as I have nothing else! Windows 10 seems to behave very badly 
when there are pending updates to install.

73
Bill
G4WJS.

On 30/04/2019 01:15, Dan Malcolm wrote:
> Should have done this before asking. A reboot of the computer did the trick.  
> Thanks Bill.
>
> __
> Dan – K4SHQ
>
> -Original Message-
> From: Dan Malcolm [mailto:k4...@outlook.com]
> Sent: Monday, April 29, 2019 6:58 PM
> To: 'WSJT software development' 
> Subject: Re: [wsjt-devel] WSJT-X 2.1.0-rc5
>
> Voicemeeter Banana
>
> __
> Dan – K4SHQ
>
>
> -Original Message-
> From: Bill Somerville [mailto:g4...@classdesign.com]
> Sent: Monday, April 29, 2019 4:52 PM
> To: wsjt-devel@lists.sourceforge.net
> Subject: Re: [wsjt-devel] WSJT-X 2.1.0-rc5
>
> On 29/04/2019 22:43, Dan Malcolm wrote:
>> Just installed WSJT-X 2.1.0 RC5 x64 on my Win10 x64 machine.  Tx works and 
>> seems to be OK, but something rerouted audio from VMB to my system speakers. 
>>  No audio received by WSJT-X (either in RC5 or 2.0.2 ) , but I can sure hear 
>> the caterwauling in the speakers.  The best I can tell, Win10's wonderful 
>> audio routing system (App volume and device preferences) is set correctly.  
>> FWIW I am running VMB 2.0.4.7.
>>
>> Prior to installing RC5 everything was working fine.
>>
>> __
>> Dan – K4SHQ
> Hi Dan,
>
> what is VMB?
>
> 73
> Bill
> G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[V. Scott Moore via wsjt-devel]

Gents:

Thanks for the responses.  Will put that one in the trash and go to quiet mode 
till the next release . . . . 

Scott
W1SSN

> On Apr 29, 2019, at 20:15, David Tiller  wrote:
> 
> To avoid the OS X crash, manually enter a fake 3 character grid and then the 
> call of the other station. At that point everything works as expected 
> (generate msgs, etc). 
> 



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[David Tiller]

To avoid the OS X crash, manually enter a fake 3 character grid and then the 
call of the other station. At that point everything works as expected (generate 
msgs, etc). 

> On Apr 29, 2019, at 20:00, Dan Malcolm  wrote:
> 
> Voicemeeter Banana
> 
> __
> Dan – K4SHQ
> 
> 
> -Original Message-
> From: Bill Somerville [mailto:g4...@classdesign.com] 
> Sent: Monday, April 29, 2019 4:52 PM
> To: wsjt-devel@lists.sourceforge.net
> Subject: Re: [wsjt-devel] WSJT-X 2.1.0-rc5
> 
>> On 29/04/2019 22:43, Dan Malcolm wrote:
>> Just installed WSJT-X 2.1.0 RC5 x64 on my Win10 x64 machine.  Tx works and 
>> seems to be OK, but something rerouted audio from VMB to my system speakers. 
>>  No audio received by WSJT-X (either in RC5 or 2.0.2 ) , but I can sure hear 
>> the caterwauling in the speakers.  The best I can tell, Win10's wonderful 
>> audio routing system (App volume and device preferences) is set correctly.  
>> FWIW I am running VMB 2.0.4.7.
>> 
>> Prior to installing RC5 everything was working fine.
>> 
>> __
>> Dan – K4SHQ
> 
> Hi Dan,
> 
> what is VMB?
> 
> 73
> Bill
> G4WJS.
> 
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[rjai...@gmail.com]

Hi Joe and team,

So far so good. Testing remote with my Flex-6700 and using remote DAX,
under Parallels in Windows. You definitely notice the sensitivity
drop. But I made some QSOs on 80m. So far so good. I see PSKReporter
is taking and parsing the reports as well without issue.

73
Ria, N2RJ

On Mon, 29 Apr 2019 at 14:09, Joe Taylor  wrote:
>
> To:   Users of WSJT-X -- especially those interested in radio contesting
> From: WSJT Development Group
>
> By now most of you know about the FT4 protocol under development for
> eventual release in WSJT-X 2.1.0.  The new mode is particularly
> optimized for use in radio contesting.
>
> FT4 is mostly like FT8, but is 2.5 x faster, uses 1.8 x the bandwidth,
> and is 4.6 dB less sensitive.  Many other details are summarized in "The
> FT4 Protocol for Digital Contesting", available here:
> http://physics.princeton.edu/pulsar/k1jt/FT4_Protocol.pdf
> Links to translations in other languages are available on the WSJT-X web
> page:
> http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
>
> Release candidate WSJT-X 2.1.0-rc5 is intended for beta-testing through
> June 7, 2019.  Please note that the FT4 mode should NOT be used in the
> ARRL June VHF QSO Party (June 8-10) or ARRL Field Day (June 22-23).
>
> We have done our best to provide suggested operating frequencies for the
> test period consistent as far as possible with world-wide band plans and
> existing usage.  Please note that thanks to good user feedback, some of
> these frequencies are different from those suggested in the document
> linked above.
>
> Default frequencies currently recommended for FT4 are as follows:
>
> Band   MHzNotes
> -
> 803.575   (3.568 MHz in Region 3)
> 407.047
> 30   10.140
> 20   14.080
> 17   18.104
> 15   21.140
> 12   24.919
> 10   28.180
>   6   50.318
>   2  144.170
>
> FT4 is designed for contesting, but it will likely find some use for
> normal QSOs as well, especially during the beta test period.  In the
> coming month we hope to receive useful feedback on the user interface,
> message sequencing, interaction with logging programs, etc.  Probably
> it's best to use "normal" (non-contest) messages except during the
> mock-contest practice sessions scheduled for  - 0100 UTC on May 9
> and May 14, and (if needed) June 5.
>
> Downloadable installation packages for WSJT-X 2.1.0-rc5 under Windows,
> Linux, and macOS are available on the WSJT-X web page:
>
> http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
>
> Windows users will discover that WSJT-X v2.1.0 has been made available
> as a 64-bit MS Windows build for 64-bit versions of Windows since Vista.
> This veraion has one known defect. The audio input device level will be
> reset to 100% when WSJT-X is started, when the input audio device is
> changed, and when switching to a new configuration. This is a Qt
> framework defect that we have reported and is being fixed in a future
> release; until then users should take care to set the device audio level
> back to 0dB or lower depending on requirements. Note that many sound
> cards and chips have real gain ahead of the ADC, as much as 14dB, which
> will be turned to the maximum due to this defect and is usually
> undesirable when using WSJT-X.
>
> Despite this annoying defect, we recommend the 64-bit version of WSJT-X
> on MS Windows as it has significant advantages in decoding speed.
>
> -- 73 from Joe, K1JT; Steve, K9AN; and Bill, G4WJS
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel



-- 
Ria Jairam, N2RJ
Director, Hudson Division
ARRL - The national association for Amateur Radio™
+1.973.594.6275
https://hudson.arrl.org
n...@arrl.org


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Dan Malcolm]

Voicemeeter Banana

__
Dan – K4SHQ


-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Monday, April 29, 2019 4:52 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X 2.1.0-rc5

On 29/04/2019 22:43, Dan Malcolm wrote:
> Just installed WSJT-X 2.1.0 RC5 x64 on my Win10 x64 machine.  Tx works and 
> seems to be OK, but something rerouted audio from VMB to my system speakers.  
> No audio received by WSJT-X (either in RC5 or 2.0.2 ) , but I can sure hear 
> the caterwauling in the speakers.  The best I can tell, Win10's wonderful 
> audio routing system (App volume and device preferences) is set correctly.  
> FWIW I am running VMB 2.0.4.7.
>
> Prior to installing RC5 everything was working fine.
>
> __
> Dan – K4SHQ

Hi Dan,

what is VMB?

73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Bill Somerville]

On 30/04/2019 00:17, Ron Koenig wrote:
I understand the Reason for the moving buttons... But the box is 
jumping between 3 screens, not just the buttons.. Never going to work 
out in a contest. 


Hi Ron,

that's not supposed to happen. Are you saying that each time the "Log 
QSO" dialog pops up it is on a different monitor?


73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Ron Koenig]

I understand the Reason for the moving buttons... But the box is jumping
between 3 screens, not just the buttons.. Never going to work out in a
contest.

On Mon, Apr 29, 2019, 4:54 PM Bill Somerville  wrote:

> On 29/04/2019 22:43, Dan Malcolm wrote:
> > Just installed WSJT-X 2.1.0 RC5 x64 on my Win10 x64 machine.  Tx works
> and seems to be OK, but something rerouted audio from VMB to my system
> speakers.  No audio received by WSJT-X (either in RC5 or 2.0.2 ) , but I
> can sure hear the caterwauling in the speakers.  The best I can tell,
> Win10's wonderful audio routing system (App volume and device preferences)
> is set correctly.  FWIW I am running VMB 2.0.4.7.
> >
> > Prior to installing RC5 everything was working fine.
> >
> > __
> > Dan – K4SHQ
>
> Hi Dan,
>
> what is VMB?
>
> 73
> Bill
> G4WJS.
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5 Configuration Settings is a "Mess"

[Marco Calistri]

Il 29/04/19 18:35, Bill Somerville ha scritto:
> On 29/04/2019 22:28, Marco Calistri wrote:
>> I've compiled and installed WSJT-X 2.1.0-rc5.tgz without any issue on a
>> opensuse Tumbleweed system, but all my attempts of cloning my standard
>> release settings, have caused me just frustration!
> 
> Hi Marco,
> 
> this tells me you are probably using a KDE desktop. See item 9 in the
> v2.1.0 RC5 User Guide FAQ chapter:
> 
> http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.1.0-rc5.html#FAQ
> 
> 
> Let me know if it sorts out your issues please?
> 
> 73
> Bill
> G4WJS.

Hi Bill,
Thanks for your fast response!

No, I'm using XFCE Desktop, not KDE and I have not a
~/.config/kdeglobals in my system.

I found the file *kdeglobals* into the following subdir of my home dir:

1 - /home/marco/.kde/share/config/

2 - /home/marco/.kde4/share/config/

Then I suppose item 9 it is not my case, also because I cannot say that
Menu→Configurations misbehave, it behaves correctly and it responds as
expected but it doesn't works as described in WSJT-X FT4 instructions
for cloning the existing configs.

Never mind Bill, it is not a major issue for me now that I know how to
resolve it.

Just curious to know if others using WSJT-X on Linux and XFCE, are
facing same issue as I described.

Best regards!


-- 

73 de Marco, PY1ZRJ (former IK5BCU)


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Bill Somerville]

On 29/04/2019 22:43, Dan Malcolm wrote:

Just installed WSJT-X 2.1.0 RC5 x64 on my Win10 x64 machine.  Tx works and 
seems to be OK, but something rerouted audio from VMB to my system speakers.  
No audio received by WSJT-X (either in RC5 or 2.0.2 ) , but I can sure hear the 
caterwauling in the speakers.  The best I can tell, Win10's wonderful audio 
routing system (App volume and device preferences) is set correctly.  FWIW I am 
running VMB 2.0.4.7.

Prior to installing RC5 everything was working fine.

__
Dan – K4SHQ


Hi Dan,

what is VMB?

73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Dan Malcolm]

Just installed WSJT-X 2.1.0 RC5 x64 on my Win10 x64 machine.  Tx works and 
seems to be OK, but something rerouted audio from VMB to my system speakers.  
No audio received by WSJT-X (either in RC5 or 2.0.2 ) , but I can sure hear the 
caterwauling in the speakers.  The best I can tell, Win10's wonderful audio 
routing system (App volume and device preferences) is set correctly.  FWIW I am 
running VMB 2.0.4.7. 

Prior to installing RC5 everything was working fine.

__
Dan – K4SHQ

-Original Message-
From: Christoph Berg [mailto:c...@df7cb.de] 
Sent: Monday, April 29, 2019 4:16 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X 2.1.0-rc5

Re: James Shaver 2019-04-29 
> I’m on 20 meters - After about 2-3 minutes of operating, I’m seeing the mode 
> getting changed back to FT8 and my frequency is jumping to 14.074.  This 
> appears to be random (though it still shows the “FT4” configuration as being 
> selected).  Selecting FT4 as the mode does not put me back to 14.080 but 
> closing the program and reopening brings me back to where I need to be. A 
> reboot appears to have cured this but FYI in case anyone else is 
> experiencing a similar issue.  

I have a similar problem. I was manually tuning to 7,047 and everything seemed 
normal (apart from the occasional "Rig control error" popups that I had always 
popping up every 10 minutes or so).
But when I added the FT4 freqs to the configuration, the program started 
randomly changing bands, mostly after the end of the TX cycle.
I could complete a few QSOs on 30m and 20m, but after every second TX cycle or 
so, it would jump to the 80m or 40m FT4 freqs.

Maybe my rig control is much more instable than the occasional "Rig control 
error" popups suggest, but wsjtx 2.0.x was able to ignore most of them. Now it 
seems that it jumps bands on each of them.

I have true rig split mode active, which worked fine in 2.0.x.

Christoph


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5 Configuration Settings is a "Mess"

[Bill Somerville]

On 29/04/2019 22:28, Marco Calistri wrote:

I've compiled and installed WSJT-X 2.1.0-rc5.tgz without any issue on a
opensuse Tumbleweed system, but all my attempts of cloning my standard
release settings, have caused me just frustration!


Hi Marco,

this tells me you are probably using a KDE desktop. See item 9 in the 
v2.1.0 RC5 User Guide FAQ chapter:


http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.1.0-rc5.html#FAQ

Let me know if it sorts out your issues please?

73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT-X 2.1.0-rc5 Configuration Settings is a "Mess"

[Marco Calistri]

Hello,

Sorry to use a not "very elegant word" in the subject, but I had not
found a better term to explain...

I've compiled and installed WSJT-X 2.1.0-rc5.tgz without any issue on a
opensuse Tumbleweed system, but all my attempts of cloning my standard
release settings, have caused me just frustration!

It happens exactly what happened on all the previous WSJT-X releases:

If you try to clone your settings and rename it then all the fields
inside the configuration fields (new or former) are empty: no call, no
grid, no radio, no anything!

In addition at any attempt of creating a config, there are new ones
available so that the configuration drop-down menu get filled of several
ones (all with their field empty!).

Good that I saved a rescue "WSJT-X.ini" on my computer so I've been able
to quickly resume my usual parameters, but this configuration
copy/cloning issue is really frustrating and I hope it being isolated
just on my system, due a possible error I make every time :-(

I will test the new RC5 version beside the above occurrence and I'll
report here if I find some other problem.

Thanks to all the devs team for the new version and for the progress
WSJT-X is having along the time.


-- 

73 de Marco, PY1ZRJ (former IK5BCU)


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Enrique Scheuer]

Win 10 64 bit IC 7300. changing bands constantly when calling. Anyone had
it also ?

de Enrique
PY2CP

Em seg, 29 de abr de 2019 às 18:23, Bill Somerville 
escreveu:

> On 29/04/2019 22:16, Christoph Berg wrote:
> > Maybe my rig control is much more instable than the occasional "Rig
> > control error" popups suggest
>
> Hi Christoph,
>
> your assumption is correct, unexplained rig control errors are a sign of
> serious CAT issues. Which rig, what error inc. details, what settings?
>
> 73
> Bill
> G4WJS.
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[David Tiller]

I also see a crash. In my case I'm not using FT4 - this is in FT8 mode. If I 
double-click on a CQ-ing station to work them, I get the following stack trace 
(Full trace attached):

VM Regions Near 0:
-->
__TEXT 00010268-000102b48000 [ 4896K] r-x/rwx 
SM=COW  /Users/USER/*/wsjtx.app/Contents/MacOS/wsjtx

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libgfortran.5.dylib   0x000107e432da _gfortran_concat_string + 
23
1   org.k1jt.wsjtx 0x0001027c2c3d azdist_ + 93
2   org.k1jt.wsjtx 0x0001026e7cd5 
MainWindow::on_dxGridEntry_textChanged(QString const&) + 389
3   org.k1jt.wsjtx 0x0001026f7a72 
MainWindow::qt_metacall(QMetaObject::Call, int, void**) + 82
4   org.qt-project.QtCore 0x000107958bfd 
QMetaObject::activate(QObject*, int, int, void**) + 1773
5   org.qt-project.QtWidgets   0x000106b59684 0x106a05000 + 1394308
6   org.qt-project.QtCore 0x00010795914c 
QMetaObject::activate(QObject*, int, int, void**) + 3132
7   org.qt-project.QtWidgets   0x000106b5b186 
QWidgetLineControl::finishChange(int, bool, bool) + 614
8   org.qt-project.QtWidgets   0x000106b5c31a 
QWidgetLineControl::internalSetText(QString const&, int, bool) + 570
9   org.qt-project.QtWidgets   0x000106b53cef 0x106a05000 + 1371375
10  org.k1jt.wsjtx 0x00010273269a 
MainWindow::processMessage(DecodedText const&, QFlags) + 
13658
11  org.k1jt.wsjtx 0x0001026d5a54 
MainWindow::doubleClickOnCall(QFlags) + 820
12  org.k1jt.wsjtx 0x0001026d5d0c 
MainWindow::doubleClickOnCall2(QFlags) + 76
13  org.qt-project.QtCore 0x000107958dbb 
QMetaObject::activate(QObject*, int, int, void**) + 2219
14  org.k1jt.wsjtx 0x000102697b5e 
DisplayText::mouseDoubleClickEvent(QMouseEvent*) + 62
15  org.qt-project.QtWidgets   0x000106a51612 QWidget::event(QEvent*) + 
466
16  org.qt-project.QtWidgets   0x000106af8fdd QFrame::event(QEvent*) + 
45
17  org.qt-project.QtCore 0x0001079281a4 
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) + 148
18  org.qt-project.QtWidgets   0x000106a158d8 
QApplicationPrivate::notify_helper(QObject*, QEvent*) + 248
19  org.qt-project.QtWidgets   0x000106a18748 
QApplication::notify(QObject*, QEvent*) + 7336
20  org.k1jt.wsjtx 0x00010278feb2 (anonymous 
namespace)::ExceptionCatchingApplication::notify(QObject*, QEvent*) + 18
21  org.qt-project.QtCore 0x000107927ef4 
QCoreApplication::notifyInternal2(QObject*, QEvent*) + 212
22  org.qt-project.QtWidgets   0x000106a16210 
QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, 
QWidget**, QPointer&, bool, bool) + 896
23  org.qt-project.QtWidgets   0x000106a70aae 0x106a05000 + 441006
24  org.qt-project.QtWidgets   0x000106a6f795 0x106a05000 + 436117
25  org.qt-project.QtWidgets   0x000106a158ed 
QApplicationPrivate::notify_helper(QObject*, QEvent*) + 269
26  org.qt-project.QtWidgets   0x000106a16cf2 
QApplication::notify(QObject*, QEvent*) + 594

--
David Tiller
Sr. Architect/Lead Consultant | CapTech
(804) 304-0638 | 
dtil...@captechconsulting.com



On Apr 29, 2019, at 3:34 PM, George J. Molnar 
mailto:geo...@molnar.tv>> wrote:

Bill, this may help…

After the initial MacOS crash,


 I have been able to reproduce the crash in MacOS by entering a 4-character 
grid. Upon typing the 4th character, the app crashes. A callsign alone doesn’t 
crash it, even if Generate Standard Messages is clicked. Imagine this would 
support the app crashing on double click to reply, as that populates the grid 
field, too.

Geo/KF2T



On Apr 29, 2019, at 3:20 PM, Bill Somerville 
mailto:g4...@classdesign.com>> wrote:

On 29/04/2019 20:14, Gary Rogers wrote:

I’m unable to get the new version to work with Mac OS, will not open and get an 
immediate crash notification

Gary KO3F


Hi Gary,

if the crash report looks like the one reported by Michael above then thanks 
for the issue report, we are looking into it. The dump would contain a stack 
trace starting like this:

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libgfortran.5.dylib 0x000113d622da 
_gfortran_concat_string + 23
1   org.k1jt.wsjtx  0x00010e6e0c3d azdist_ + 93
2   org.k1jt.wsjtx  0x00010e605cd5 
MainWindow::on_dxGridEntry_textChanged(QString const&) + 389
3   org.k1jt.wsjtx  0x00010e615a72 
MainWindow::qt_metacall(QMetaObject::Call, int, void**) + 82


If it is a different crash then please provide the crash report details.

73
Bill
G4WJS.

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Bill Somerville]

On 29/04/2019 22:16, Christoph Berg wrote:

Maybe my rig control is much more instable than the occasional "Rig
control error" popups suggest


Hi Christoph,

your assumption is correct, unexplained rig control errors are a sign of 
serious CAT issues. Which rig, what error inc. details, what settings?


73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Christoph Berg]

Re: James Shaver 2019-04-29 
> I’m on 20 meters - After about 2-3 minutes of operating, I’m seeing the mode 
> getting changed back to FT8 and my frequency is jumping to 14.074.  This 
> appears to be random (though it still shows the “FT4” configuration as being 
> selected).  Selecting FT4 as the mode does not put me back to 14.080 but 
> closing the program and reopening brings me back to where I need to be. A 
> reboot appears to have cured this but FYI in case anyone else is 
> experiencing a similar issue.  

I have a similar problem. I was manually tuning to 7,047 and
everything seemed normal (apart from the occasional "Rig control
error" popups that I had always popping up every 10 minutes or so).
But when I added the FT4 freqs to the configuration, the program
started randomly changing bands, mostly after the end of the TX cycle.
I could complete a few QSOs on 30m and 20m, but after every second TX
cycle or so, it would jump to the 80m or 40m FT4 freqs.

Maybe my rig control is much more instable than the occasional "Rig
control error" popups suggest, but wsjtx 2.0.x was able to ignore most
of them. Now it seems that it jumps bands on each of them.

I have true rig split mode active, which worked fine in 2.0.x.

Christoph


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[David Tiller]

I also see the mode reverting to FT8.

Following the instructions, I set the mode to FT4. I then go into the frequency 
settings and reset them. When I exit that screen, the mode has been reset to 
FT8.

--
David Tiller
Sr. Architect/Lead Consultant | CapTech
(804) 304-0638 | 
dtil...@captechconsulting.com



On Apr 29, 2019, at 3:26 PM, Alois Windpassinger 
mailto:alois.windpassin...@gmail.com>> wrote:

hi Gary,
here the same trouble with Mac-OS High Sierra...program crashes and is sending 
a report to Apple...hi
 gl 73 de Alois, dl8rbl

Am Mo., 29. Apr. 2019 um 21:18 Uhr schrieb Gary Rogers 
mailto:cgaryrogers...@gmail.com>>:
I’m unable to get the new version to work with Mac OS, will not open and get an 
immediate crash notification

Gary KO3F

> On Apr 29, 2019, at 3:08 PM, Bill Somerville 
> mailto:g4...@classdesign.com>> wrote:
>
> On 29/04/2019 20:05, James Shaver wrote:
>> Hey Bill - I’ll click on the mode menu, select “FT4” and the mode will 
>> remain in FT8 mode until I close WSJTX down and reopen it.
>>
>> 73,
>>
>> Jim S.
>> N2ADV
>
> Hi Jim,
>
> that seems unlikely. Are you sure you are not looking at the configuration 
> name, perhaps you have a configuration selected on that machine called "FT8".
>
> 73
> Bill
> G4WJS.
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Alois Windpassinger
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Patrick 9A5CW]

Hi,
Win 7 64bit, WSJT-X 64bit.
Enterening a new freq in the freq list.
Mode change from FT4 to FT8 by pressing OK in the settings menu.
The same happens when i delete new stored freq.

Everything others works ok so far, can see many users already migrated to
FT4.
Best regards and RR73 9A5CW

pon, 29. tra 2019. 20:09 Joe Taylor  je napisao:

> To:   Users of WSJT-X -- especially those interested in radio contesting
> From: WSJT Development Group
>
> By now most of you know about the FT4 protocol under development for
> eventual release in WSJT-X 2.1.0.  The new mode is particularly
> optimized for use in radio contesting.
>
> FT4 is mostly like FT8, but is 2.5 x faster, uses 1.8 x the bandwidth,
> and is 4.6 dB less sensitive.  Many other details are summarized in "The
> FT4 Protocol for Digital Contesting", available here:
> http://physics.princeton.edu/pulsar/k1jt/FT4_Protocol.pdf
> Links to translations in other languages are available on the WSJT-X web
> page:
> http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
>
> Release candidate WSJT-X 2.1.0-rc5 is intended for beta-testing through
> June 7, 2019.  Please note that the FT4 mode should NOT be used in the
> ARRL June VHF QSO Party (June 8-10) or ARRL Field Day (June 22-23).
>
> We have done our best to provide suggested operating frequencies for the
> test period consistent as far as possible with world-wide band plans and
> existing usage.  Please note that thanks to good user feedback, some of
> these frequencies are different from those suggested in the document
> linked above.
>
> Default frequencies currently recommended for FT4 are as follows:
>
> Band   MHzNotes
> -
> 803.575   (3.568 MHz in Region 3)
> 407.047
> 30   10.140
> 20   14.080
> 17   18.104
> 15   21.140
> 12   24.919
> 10   28.180
>   6   50.318
>   2  144.170
>
> FT4 is designed for contesting, but it will likely find some use for
> normal QSOs as well, especially during the beta test period.  In the
> coming month we hope to receive useful feedback on the user interface,
> message sequencing, interaction with logging programs, etc.  Probably
> it's best to use "normal" (non-contest) messages except during the
> mock-contest practice sessions scheduled for  - 0100 UTC on May 9
> and May 14, and (if needed) June 5.
>
> Downloadable installation packages for WSJT-X 2.1.0-rc5 under Windows,
> Linux, and macOS are available on the WSJT-X web page:
>
> http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
>
> Windows users will discover that WSJT-X v2.1.0 has been made available
> as a 64-bit MS Windows build for 64-bit versions of Windows since Vista.
> This veraion has one known defect. The audio input device level will be
> reset to 100% when WSJT-X is started, when the input audio device is
> changed, and when switching to a new configuration. This is a Qt
> framework defect that we have reported and is being fixed in a future
> release; until then users should take care to set the device audio level
> back to 0dB or lower depending on requirements. Note that many sound
> cards and chips have real gain ahead of the ADC, as much as 14dB, which
> will be turned to the maximum due to this defect and is usually
> undesirable when using WSJT-X.
>
> Despite this annoying defect, we recommend the 64-bit version of WSJT-X
> on MS Windows as it has significant advantages in decoding speed.
>
> -- 73 from Joe, K1JT; Steve, K9AN; and Bill, G4WJS
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Dana Myers]

On 4/29/2019 12:45 PM, Black Michael via wsjt-devel wrote:

Need a small cosmetic change to add FT4 to the Advanced Tab.
And when switching to FT4 should there be a check for a Special Activity to be selected?  I see a lot of testers already not 
using a contest mode.


We're not in a contest or mock-contest, so of course we're not running a 
contest mode.
The setup directions might be a little ambiguous :-)

73,
Dana  K6JQ

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Bill Somerville]

On 29/04/2019 20:26, Alois Windpassinger wrote:

hi Gary,
here the same trouble with Mac-OS High Sierra...program crashes and is 
sending a report to Apple...hi

 gl 73 de Alois, dl8rbl


Hi Alois,

there is no point sending WSJT-X crash reports to Apple, they don't want 
them. Either click "Ignore" on the initial crash message if you know 
what caused it, or view the report and send us the crash report in a 
message here, then click "Don't send".


73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Bill Somerville]

On 29/04/2019 20:45, Black Michael via wsjt-devel wrote:

Need a small cosmetic change to add FT4 to the Advanced Tab.
And when switching to FT4 should there be a check for a Special 
Activity to be selected?  I see a lot of testers already not using a 
contest mode.



Hi Mike,

please note this paragraph in the release announcement:

"FT4 is designed for contesting, but it will likely find some use for 
normal QSOs as well, especially during the beta test period. In the 
coming month we hope to receive useful feedback on the user interface, 
message sequencing, interaction with logging programs, etc.  Probably 
it's best to use "normal" (non-contest) messages except during the 
mock-contest practice sessions scheduled for  - 0100 UTC on May 9 
and May 14, and (if needed) June 5."


73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Black Michael via wsjt-devel]

Need a small cosmetic change to add FT4 to the Advanced Tab. And when switching 
to FT4 should there be a check for a Special Activity to be selected?  I see a 
lot of testers already not using a contest mode.




de Mike W9MDB___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Enrique Scheuer]

Win10 64 bit now changing  alone from 21110 to 14080 after abt. 5 to 10
calls. Already checked any non desired band split setting.

de Enrique
PY2CP

Em seg, 29 de abr de 2019 às 16:38, George J. Molnar 
escreveu:

> Bill, this may help…
>
> After the initial MacOS crash,
>
>
>  I have been able to reproduce the crash in MacOS by entering a
> 4-character grid. Upon typing the 4th character, the app crashes. A
> callsign alone doesn’t crash it, even if Generate Standard Messages is
> clicked. Imagine this would support the app crashing on double click to
> reply, as that populates the grid field, too.
>
> Geo/KF2T
>
>
>
> On Apr 29, 2019, at 3:20 PM, Bill Somerville 
> wrote:
>
> On 29/04/2019 20:14, Gary Rogers wrote:
>
> I’m unable to get the new version to work with Mac OS, will not open and get 
> an immediate crash notification
>
> Gary KO3F
>
> Hi Gary,
>
> if the crash report looks like the one reported by Michael above then
> thanks for the issue report, we are looking into it. The dump would contain
> a stack trace starting like this:
>
> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
> 0   libgfortran.5.dylib   0x000113d622da 
> _gfortran_concat_string + 23
> 1   org.k1jt.wsjtx0x00010e6e0c3d azdist_ + 93
> 2   org.k1jt.wsjtx0x00010e605cd5 
> MainWindow::on_dxGridEntry_textChanged(QString const&) + 389
> 3   org.k1jt.wsjtx0x00010e615a72 
> MainWindow::qt_metacall(QMetaObject::Call, int, void**) + 82
>
> If it is a different crash then please provide the crash report details.
>
> 73
> Bill
> G4WJS.
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[George J. Molnar]

Bill, this may help…

After the initial MacOS crash, 


 I have been able to reproduce the crash in MacOS by entering a 4-character 
grid. Upon typing the 4th character, the app crashes. A callsign alone doesn’t 
crash it, even if Generate Standard Messages is clicked. Imagine this would 
support the app crashing on double click to reply, as that populates the grid 
field, too.

Geo/KF2T



> On Apr 29, 2019, at 3:20 PM, Bill Somerville  wrote:
> 
> On 29/04/2019 20:14, Gary Rogers wrote:
>> I’m unable to get the new version to work with Mac OS, will not open and get 
>> an immediate crash notification
>> 
>> Gary KO3F
> Hi Gary,
> 
> if the crash report looks like the one reported by Michael above then thanks 
> for the issue report, we are looking into it. The dump would contain a stack 
> trace starting like this:
> 
> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
> 0   libgfortran.5.dylib   0x000113d622da 
> _gfortran_concat_string + 23
> 1   org.k1jt.wsjtx0x00010e6e0c3d azdist_ + 93
> 2   org.k1jt.wsjtx0x00010e605cd5 
> MainWindow::on_dxGridEntry_textChanged(QString const&) + 389
> 3   org.k1jt.wsjtx0x00010e615a72 
> MainWindow::qt_metacall(QMetaObject::Call, int, void**) + 82
> If it is a different crash then please provide the crash report details.
> 
> 73
> Bill
> G4WJS.
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Alois Windpassinger]

hi Gary,
here the same trouble with Mac-OS High Sierra...program crashes and is
sending a report to Apple...hi
 gl 73 de Alois, dl8rbl

Am Mo., 29. Apr. 2019 um 21:18 Uhr schrieb Gary Rogers <
cgaryrogers...@gmail.com>:

> I’m unable to get the new version to work with Mac OS, will not open and
> get an immediate crash notification
>
> Gary KO3F
>
> > On Apr 29, 2019, at 3:08 PM, Bill Somerville 
> wrote:
> >
> > On 29/04/2019 20:05, James Shaver wrote:
> >> Hey Bill - I’ll click on the mode menu, select “FT4” and the mode will
> remain in FT8 mode until I close WSJTX down and reopen it.
> >>
> >> 73,
> >>
> >> Jim S.
> >> N2ADV
> >
> > Hi Jim,
> >
> > that seems unlikely. Are you sure you are not looking at the
> configuration name, perhaps you have a configuration selected on that
> machine called "FT8".
> >
> > 73
> > Bill
> > G4WJS.
> >
> >
> >
> > ___
> > wsjt-devel mailing list
> > wsjt-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>


-- 
Alois Windpassinger
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Bill Somerville]

On 29/04/2019 20:14, Gary Rogers wrote:

I’m unable to get the new version to work with Mac OS, will not open and get an 
immediate crash notification

Gary KO3F


Hi Gary,

if the crash report looks like the one reported by Michael above then 
thanks for the issue report, we are looking into it. The dump would 
contain a stack trace starting like this:


Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libgfortran.5.dylib 0x000113d622da 
_gfortran_concat_string + 23
1   org.k1jt.wsjtx  0x00010e6e0c3d azdist_ + 93
2   org.k1jt.wsjtx  0x00010e605cd5 
MainWindow::on_dxGridEntry_textChanged(QString const&) + 389
3   org.k1jt.wsjtx  0x00010e615a72 
MainWindow::qt_metacall(QMetaObject::Call, int, void**) + 82

If it is a different crash then please provide the crash report details.

73
Bill
G4WJS.

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Ron Koenig]

Win 10 64 Bit Change Anything and mode / band changes to FT-8, did not
happen in RC4


On Mon, Apr 29, 2019, 2:12 PM Bill Somerville  wrote:

> On 29/04/2019 20:05, James Shaver wrote:
> > Hey Bill - I’ll click on the mode menu, select “FT4” and the mode will
> > remain in FT8 mode until I close WSJTX down and reopen it.
> >
> > 73,
> >
> > Jim S.
> > N2ADV
>
> Hi Jim,
>
> that seems unlikely. Are you sure you are not looking at the
> configuration name, perhaps you have a configuration selected on that
> machine called "FT8".
>
> 73
> Bill
> G4WJS.
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Gary Rogers]

I’m unable to get the new version to work with Mac OS, will not open and get an 
immediate crash notification

Gary KO3F

> On Apr 29, 2019, at 3:08 PM, Bill Somerville  wrote:
> 
> On 29/04/2019 20:05, James Shaver wrote:
>> Hey Bill - I’ll click on the mode menu, select “FT4” and the mode will 
>> remain in FT8 mode until I close WSJTX down and reopen it.
>> 
>> 73,
>> 
>> Jim S.
>> N2ADV
> 
> Hi Jim,
> 
> that seems unlikely. Are you sure you are not looking at the configuration 
> name, perhaps you have a configuration selected on that machine called "FT8".
> 
> 73
> Bill
> G4WJS.
> 
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[James Shaver]

I’m in the correct configuration of FT4.  It is only my Win7 32 bit machine.  
My Win 7 Pro 64 Bit and my Win 10 machines don’t have any issue after selecting 
FT4 as the mode.  

73,

Jim S. 
N2ADV (ex KD2BIP)

> On Apr 29, 2019, at 3:08 PM, Bill Somerville  wrote:
> 
>> On 29/04/2019 20:05, James Shaver wrote:
>> Hey Bill - I’ll click on the mode menu, select “FT4” and the mode will 
>> remain in FT8 mode until I close WSJTX down and reopen it.
>> 
>> 73,
>> 
>> Jim S.
>> N2ADV
> 
> Hi Jim,
> 
> that seems unlikely. Are you sure you are not looking at the configuration 
> name, perhaps you have a configuration selected on that machine called "FT8".
> 
> 73
> Bill
> G4WJS.
> 
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Enrique Scheuer]

Win 10 everything Ok Calling 21140 but no takers.
de Enrique
PY2CP

Em seg, 29 de abr de 2019 às 16:07, George J. Molnar 
escreveu:

> Rebooted - same issue. Relaunch allows app to start, and receives well.
> Double clicking to respond causes a crash every time.
>
>
> On Apr 29, 2019, at 2:59 PM, George J. Molnar  wrote:
>
> Confirm N2ADV’s observation, and the MacOS issue. Am rebooting now to see
> what clears…
>
>
> *George J Molnar*
> KF2T, Arlington, Virginia, USA
>
>
> Please note my new email: George@Molnar.*TV*
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Bill Somerville]

On 29/04/2019 20:05, James Shaver wrote:
Hey Bill - I’ll click on the mode menu, select “FT4” and the mode will 
remain in FT8 mode until I close WSJTX down and reopen it.


73,

Jim S.
N2ADV


Hi Jim,

that seems unlikely. Are you sure you are not looking at the 
configuration name, perhaps you have a configuration selected on that 
machine called "FT8".


73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Bill Somerville]

On 29/04/2019 19:18, Michael Johnston wrote:

I’m new to this list, so I’m not sure what the protocol is for reporting bugs. 
Please redirect me as appropriate.

I’ve just downloaded and installed RC5 on a Mac running OSX Mojave (10.14.3). 
(I previously had WSJT-X 2.0.1 installed). The app crashes at startup, with a 
popup dialog box saying ‘WSJT-X quit unexpectedly.” The stack trace is below.


Process:   wsjtx [34825]
Path:  /Applications/wsjtx.app/Contents/MacOS/wsjtx
Identifier:org.k1jt.wsjtx
Version:   v2.1.0-rc5 (2.1.0-rc5)
Code Type: X86-64 (Native)
Parent Process:??? [1]
Responsible:   wsjtx [34825]
User ID:   501

Date/Time: 2019-04-29 14:17:12.131 -0400
OS Version:Mac OS X 10.14.3 (18D109)
Report Version:12
Anonymous UUID:B1ED34EC-8FF8-B795-1683-7639C5437ADC

Sleep/Wake UUID:   3E5BFD17-9D21-4A10-A0DC-21720D0ED10C

Time Awake Since Boot: 340 seconds
Time Since Wake:   94 seconds

System Integrity Protection: enabled

Crashed Thread:0  Dispatch queue: com.apple.main-thread

Exception Type:EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:   KERN_INVALID_ADDRESS at 0x
Exception Note:EXC_CORPSE_NOTIFY

Termination Signal:Segmentation fault: 11
Termination Reason:Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [34825]

VM Regions Near 0:
-->
 __TEXT 00010e59e000-00010ea66000 [ 4896K] r-x/rwx 
SM=COW  /Applications/wsjtx.app/Contents/MacOS/wsjtx

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libgfortran.5.dylib 0x000113d622da 
_gfortran_concat_string + 23
1   org.k1jt.wsjtx  0x00010e6e0c3d azdist_ + 93
2   org.k1jt.wsjtx  0x00010e605cd5 
MainWindow::on_dxGridEntry_textChanged(QString const&) + 389
3   org.k1jt.wsjtx  0x00010e615a72


Hi Michael,

this is exactly the right place to report issues, and thanks for the 
issue report. I have managed to reproduce it and am looking into it 
right now.


73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[James Shaver]

Hey Bill - I’ll click on the mode menu, select “FT4” and the mode will remain 
in FT8 mode until I close WSJTX down and reopen it.  

73,

Jim S. 
N2ADV 

> On Apr 29, 2019, at 2:57 PM, Bill Somerville  wrote:
> 
> Hi Jim,
> 
> in what way doesn't it work on the 32-bit version? Are you saying that the 
> "Menu->Mode->FT4" button is not functioning?
> 
> 73
> Bill
> G4WJS.
> 
>> On 29/04/2019 19:54, James Shaver wrote:
>> Hey Bill - on my Win10 64 bit machine that works but on my Win7 Home (32 
>> bit) machine, it won’t resolve for me unless I restart.  
>> 
>> 73,
>> 
>> Jim S. 
>> N2ADV (ex KD2BIP)
>> 
 On Apr 29, 2019, at 2:49 PM, Bill Somerville  wrote:
 
 On 29/04/2019 19:38, James Shaver wrote:
 Follow up - mode gets changed back to FT8 if I got into the settings and 
 change anything (for example, checking the box “Alternate F1-F6 bindings” 
 and clicking OK returns the mode to FT8 and FT4 mode, even if selected, 
 won’t work until the program is closed and restarted.
>>> Hi Jim,
>>> 
>>> thanks for the issue report, I can confirm this is a defect. Clicking the 
>>> "OK" button to leave the Settings dialog will take the mode out of FT4 and 
>>> set FT8. You can work around this by selecting FT4 mode again.
>>> 
>>> 73
>>> Bill
>>> G4WJS.
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[George J. Molnar]

Rebooted - same issue. Relaunch allows app to start, and receives well. Double 
clicking to respond causes a crash every time.


> On Apr 29, 2019, at 2:59 PM, George J. Molnar  wrote:
> 
> Confirm N2ADV’s observation, and the MacOS issue. Am rebooting now to see 
> what clears…
> 
> 
> George J Molnar
> KF2T, Arlington, Virginia, USA
> 
> 
> Please note my new email: geo...@molnar.tv
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[George J. Molnar]

Confirm N2ADV’s observation, and the MacOS issue. Am rebooting now to see what 
clears…


George J Molnar
KF2T, Arlington, Virginia, USA


Please note my new email: geo...@molnar.tv

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Dana Myers]

On 4/29/2019 11:54 AM, James Shaver wrote:

Hey Bill - on my Win10 64 bit machine that works but on my Win7 Home (32 bit) 
machine, it won’t resolve for me unless I restart.


Confirm the work-around works on my W10 64-bit machine.
Only 32-bit machines I have left are embedded controllers ;-)

73,
Dana  K6JQ

thanks for the issue report, I can confirm this is a defect. Clicking the "OK" 
button to leave the Settings dialog will take the mode out of FT4 and set FT8. You can 
work around this by selecting FT4 mode again.






___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Bill Somerville]

Hi Jim,

in what way doesn't it work on the 32-bit version? Are you saying that 
the "Menu->Mode->FT4" button is not functioning?


73
Bill
G4WJS.

On 29/04/2019 19:54, James Shaver wrote:

Hey Bill - on my Win10 64 bit machine that works but on my Win7 Home (32 bit) 
machine, it won’t resolve for me unless I restart.

73,

Jim S.
N2ADV (ex KD2BIP)


On Apr 29, 2019, at 2:49 PM, Bill Somerville  wrote:


On 29/04/2019 19:38, James Shaver wrote:
Follow up - mode gets changed back to FT8 if I got into the settings and change 
anything (for example, checking the box “Alternate F1-F6 bindings” and clicking 
OK returns the mode to FT8 and FT4 mode, even if selected, won’t work until the 
program is closed and restarted.

Hi Jim,

thanks for the issue report, I can confirm this is a defect. Clicking the "OK" 
button to leave the Settings dialog will take the mode out of FT4 and set FT8. You can 
work around this by selecting FT4 mode again.

73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Enrique Scheuer]

Calling now on  21140. No ( bad) news up to now.

de Enrique
PY2CP

Em seg, 29 de abr de 2019 às 15:53, Dana Myers  escreveu:

> On 4/29/2019 11:30 AM, James Shaver wrote:
> > I’m on 20 meters - After about 2-3 minutes of operating, I’m seeing the
> mode getting changed back to FT8 and my frequency is jumping to 14.074.
> This appears to be random (though it still shows the “FT4” configuration as
> being selected).  Selecting FT4 as the mode does not put me back to 14.080
> but closing the program and reopening brings me back to where I need to be.
> A reboot appears to have cured this but FYI in case anyone else is
> experiencing a similar issue.
>
> I see the mode pop back to FT4 any time I change a setting in File>Settings
>
> > Also, I’m already seeing quite a few people that have skipped step 8 in
> the setup instructions.
> Yes, you are...  ;-)
>
> 73,
> Dana
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[James Shaver]

Hey Bill - on my Win10 64 bit machine that works but on my Win7 Home (32 bit) 
machine, it won’t resolve for me unless I restart.  

73,

Jim S. 
N2ADV (ex KD2BIP)

> On Apr 29, 2019, at 2:49 PM, Bill Somerville  wrote:
> 
>> On 29/04/2019 19:38, James Shaver wrote:
>> Follow up - mode gets changed back to FT8 if I got into the settings and 
>> change anything (for example, checking the box “Alternate F1-F6 bindings” 
>> and clicking OK returns the mode to FT8 and FT4 mode, even if selected, 
>> won’t work until the program is closed and restarted.
> 
> Hi Jim,
> 
> thanks for the issue report, I can confirm this is a defect. Clicking the 
> "OK" button to leave the Settings dialog will take the mode out of FT4 and 
> set FT8. You can work around this by selecting FT4 mode again.
> 
> 73
> Bill
> G4WJS.
> 
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Dana Myers]

On 4/29/2019 11:30 AM, James Shaver wrote:

I’m on 20 meters - After about 2-3 minutes of operating, I’m seeing the mode 
getting changed back to FT8 and my frequency is jumping to 14.074.  This 
appears to be random (though it still shows the “FT4” configuration as being 
selected).  Selecting FT4 as the mode does not put me back to 14.080 but 
closing the program and reopening brings me back to where I need to be. A 
reboot appears to have cured this but FYI in case anyone else is 
experiencing a similar issue.


I see the mode pop back to FT4 any time I change a setting in File>Settings


Also, I’m already seeing quite a few people that have skipped step 8 in the 
setup instructions.

Yes, you are...  ;-)

73,
Dana



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Michael Johnston]

I’m new to this list, so I’m not sure what the protocol is for reporting bugs. 
Please redirect me as appropriate.

I’ve just downloaded and installed RC5 on a Mac running OSX Mojave (10.14.3). 
(I previously had WSJT-X 2.0.1 installed). The app crashes at startup, with a 
popup dialog box saying ‘WSJT-X quit unexpectedly.” The stack trace is below.


Process:   wsjtx [34825]
Path:  /Applications/wsjtx.app/Contents/MacOS/wsjtx
Identifier:org.k1jt.wsjtx
Version:   v2.1.0-rc5 (2.1.0-rc5)
Code Type: X86-64 (Native)
Parent Process:??? [1]
Responsible:   wsjtx [34825]
User ID:   501

Date/Time: 2019-04-29 14:17:12.131 -0400
OS Version:Mac OS X 10.14.3 (18D109)
Report Version:12
Anonymous UUID:B1ED34EC-8FF8-B795-1683-7639C5437ADC

Sleep/Wake UUID:   3E5BFD17-9D21-4A10-A0DC-21720D0ED10C

Time Awake Since Boot: 340 seconds
Time Since Wake:   94 seconds

System Integrity Protection: enabled

Crashed Thread:0  Dispatch queue: com.apple.main-thread

Exception Type:EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:   KERN_INVALID_ADDRESS at 0x
Exception Note:EXC_CORPSE_NOTIFY

Termination Signal:Segmentation fault: 11
Termination Reason:Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [34825]

VM Regions Near 0:
--> 
__TEXT 00010e59e000-00010ea66000 [ 4896K] r-x/rwx 
SM=COW  /Applications/wsjtx.app/Contents/MacOS/wsjtx

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libgfortran.5.dylib 0x000113d622da 
_gfortran_concat_string + 23
1   org.k1jt.wsjtx  0x00010e6e0c3d azdist_ + 93
2   org.k1jt.wsjtx  0x00010e605cd5 
MainWindow::on_dxGridEntry_textChanged(QString const&) + 389
3   org.k1jt.wsjtx  0x00010e615a72 
MainWindow::qt_metacall(QMetaObject::Call, int, void**) + 82
4   org.qt-project.QtCore   0x00011387abfd 
QMetaObject::activate(QObject*, int, int, void**) + 1773
5   org.qt-project.QtWidgets0x000112a75684 0x112921000 + 1394308
6   org.qt-project.QtCore   0x00011387b14c 
QMetaObject::activate(QObject*, int, int, void**) + 3132
7   org.qt-project.QtWidgets0x000112a77186 
QWidgetLineControl::finishChange(int, bool, bool) + 614
8   org.qt-project.QtWidgets0x000112a7831a 
QWidgetLineControl::internalSetText(QString const&, int, bool) + 570
9   org.qt-project.QtWidgets0x000112a6fcef 0x112921000 + 1371375
10  org.k1jt.wsjtx  0x00010e6316cc 
MainWindow::readSettings() + 1436
11  org.k1jt.wsjtx  0x00010e61d76d 
MainWindow::MainWindow(QDir const&, bool, MultiSettings*, QSharedMemory*, 
unsigned int, QSplashScreen*, QWidget*) + 31901
12  org.k1jt.wsjtx  0x00010e6abe35 main + 6613
13  libdyld.dylib   0x7fff5e830ed9 start + 1

Thread 1:
0   libsystem_pthread.dylib 0x7fff5ea233f8 start_wqthread + 0
1   ??? 0x54485244 0 + 1414025796

Thread 2:
0   libsystem_pthread.dylib 0x7fff5ea233f8 start_wqthread + 0
1   ??? 0x54485244 0 + 1414025796

Thread 3:
0   libsystem_pthread.dylib 0x7fff5ea233f8 start_wqthread + 0
1   ??? 0x54485244 0 + 1414025796

Thread 4:
0   libsystem_pthread.dylib 0x7fff5ea233f8 start_wqthread + 0
1   ??? 0x54485244 0 + 1414025796

Thread 5:
0   libsystem_pthread.dylib 0x7fff5ea233f8 start_wqthread + 0
1   ??? 0x54485244 0 + 1414025796

Thread 6:
0   libsystem_pthread.dylib 0x7fff5ea233f8 start_wqthread + 0
1   ??? 0x54485244 0 + 1414025796

Thread 7:
0   libsystem_pthread.dylib 0x7fff5ea233f8 start_wqthread + 0
1   ??? 0x54485244 0 + 1414025796

Thread 8:
0   libsystem_pthread.dylib 0x7fff5ea233f8 start_wqthread + 0
1   ??? 0x54485244 0 + 1414025796

Thread 9:: Qt bearer thread
0   libsystem_kernel.dylib  0x7fff5e9722ee poll + 10
1   org.qt-project.QtCore   0x0001138a00a0 
qt_safe_poll(pollfd*, unsigned int, timespec const*) + 608
2   org.qt-project.QtCore   0x0001138a1897 
QEventDispatcherUNIX::processEvents(QFlags) + 903
3   org.qt-project.QtCore   0x00011384555f 
QEventLoop::exec(QFlags) + 431
4   org.qt-project.QtCore   0x00011368220c QThread::exec() + 140
5   org.qt-project.QtCore   0x000113683183 0x113661000 + 139651
6   libsystem_pthread.dylib 

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Bill Somerville]

On 29/04/2019 19:38, James Shaver wrote:

Follow up - mode gets changed back to FT8 if I got into the settings and change 
anything (for example, checking the box “Alternate F1-F6 bindings” and clicking 
OK returns the mode to FT8 and FT4 mode, even if selected, won’t work until the 
program is closed and restarted.


Hi Jim,

thanks for the issue report, I can confirm this is a defect. Clicking 
the "OK" button to leave the Settings dialog will take the mode out of 
FT4 and set FT8. You can work around this by selecting FT4 mode again.


73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[James Shaver]

Hey, Bill - thanks.  See my last note re: same :)

73,

Jim S. 
N2ADV (ex KD2BIP)

> On Apr 29, 2019, at 2:38 PM, Bill Somerville  wrote:
> 
>> On 29/04/2019 19:30, James Shaver wrote:
>> Also, I’m already seeing quite a few people that have skipped step 8 in the 
>> setup instructions.
> 
> Hi Jim,
> 
> that is consistent with Joe's release announcement, see the last sentence 
> here:
> 
> "FT4 is designed for contesting, but it will likely find some use for normal 
> QSOs as well, especially during the beta test period. In the coming month we 
> hope to receive useful feedback on the user interface, message sequencing, 
> interaction with logging programs, etc.  Probably it's best to use "normal" 
> (non-contest) messages except during the mock-contest practice sessions 
> scheduled for  - 0100 UTC on May 9 and May 14, and (if needed) June 5."
> 
> 73
> Bill
> G4WJS.
> 
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Bill Somerville]

On 29/04/2019 19:30, James Shaver wrote:

Also, I’m already seeing quite a few people that have skipped step 8 in the 
setup instructions.


Hi Jim,

that is consistent with Joe's release announcement, see the last 
sentence here:


"FT4 is designed for contesting, but it will likely find some use for 
normal QSOs as well, especially during the beta test period. In the 
coming month we hope to receive useful feedback on the user interface, 
message sequencing, interaction with logging programs, etc.  Probably 
it's best to use "normal" (non-contest) messages except during the 
mock-contest practice sessions scheduled for  - 0100 UTC on May 9 
and May 14, and (if needed) June 5."


73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[James Shaver]

Follow up - mode gets changed back to FT8 if I got into the settings and change 
anything (for example, checking the box “Alternate F1-F6 bindings” and clicking 
OK returns the mode to FT8 and FT4 mode, even if selected, won’t work until the 
program is closed and restarted.  

Also as a follow up to my below about step 8 - looks like the release email has 
a slight conflict with the PDF - perhaps the PDF with the setup instructions 
should be modified?  

73,

Jim S. 
N2ADV (ex KD2BIP)

> On Apr 29, 2019, at 2:30 PM, James Shaver  wrote:
> 
> I’m on 20 meters - After about 2-3 minutes of operating, I’m seeing the mode 
> getting changed back to FT8 and my frequency is jumping to 14.074.  This 
> appears to be random (though it still shows the “FT4” configuration as being 
> selected).  Selecting FT4 as the mode does not put me back to 14.080 but 
> closing the program and reopening brings me back to where I need to be. A 
> reboot appears to have cured this but FYI in case anyone else is 
> experiencing a similar issue.  
> 
> Also, I’m already seeing quite a few people that have skipped step 8 in the 
> setup instructions.  
> 
> 73,
> 
> Jim S. 
> N2ADV (ex KD2BIP)
> 
>> On Apr 29, 2019, at 2:05 PM, Joe Taylor  wrote:
>> 
>> To:   Users of WSJT-X -- especially those interested in radio contesting
>> From: WSJT Development Group
>> 
>> By now most of you know about the FT4 protocol under development for 
>> eventual release in WSJT-X 2.1.0.  The new mode is particularly optimized 
>> for use in radio contesting.
>> 
>> FT4 is mostly like FT8, but is 2.5 x faster, uses 1.8 x the bandwidth, and 
>> is 4.6 dB less sensitive.  Many other details are summarized in "The FT4 
>> Protocol for Digital Contesting", available here:
>> http://physics.princeton.edu/pulsar/k1jt/FT4_Protocol.pdf
>> Links to translations in other languages are available on the WSJT-X web 
>> page:
>> http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
>> 
>> Release candidate WSJT-X 2.1.0-rc5 is intended for beta-testing through June 
>> 7, 2019.  Please note that the FT4 mode should NOT be used in the ARRL June 
>> VHF QSO Party (June 8-10) or ARRL Field Day (June 22-23).
>> 
>> We have done our best to provide suggested operating frequencies for the 
>> test period consistent as far as possible with world-wide band plans and 
>> existing usage.  Please note that thanks to good user feedback, some of 
>> these frequencies are different from those suggested in the document linked 
>> above.
>> 
>> Default frequencies currently recommended for FT4 are as follows:
>> 
>> Band   MHzNotes
>> -
>> 803.575   (3.568 MHz in Region 3)
>> 407.047
>> 30   10.140
>> 20   14.080
>> 17   18.104
>> 15   21.140
>> 12   24.919
>> 10   28.180
>> 6   50.318
>> 2  144.170
>> 
>> FT4 is designed for contesting, but it will likely find some use for normal 
>> QSOI’m on 20 meters - After about 2-3 minutes of operating, I’m seeing the 
>> mode getting changed back to FT8 and my frequency is jumping to 14.074.  
>> This appears to be random (though it still shows the “FT4” configuration as 
>> being selected).  Selecting FT4 as the mode does not put me back to 14.080 
>> but closing the program and reopening brings me back to where I need to be. 
>> A reboot appears to have cured this but FYI in case anyone else is 
>> experiencing a similar issue.  
> 
> Also, I’m already seeing quite a few people that have skipped step 8 in the 
> setup instructions.  
> 
> 73,
> 
> Jim S. 
> N2ADV (ex KD2BIP)
> 
>> On Apr 29, 2019, at 2:05 PM, Joe Taylor  wrote:
>> 
>> To:   Users of WSJT-X -- especially those interested in radio contesting
>> From: WSJT Development Group
>> 
>> By now most of you know about the FT4 protocol under development for 
>> eventual release in WSJT-X 2.1.0.  The new mode is particularly optimized 
>> for use in radio contesting.
>> 
>> FT4 is mostly like FT8, but is 2.5 x faster, uses 1.8 x the bandwidth, and 
>> is 4.6 dB less sensitive.  Many other details are summarized in "The FT4 
>> Protocol for Digital Contesting", available here:
>> http://physics.princeton.edu/pulsar/k1jt/FT4_Protocol.pdf
>> Links to translations in other languages are available on the WSJT-X web 
>> page:
>> http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
>> 
>> Release candidate WSJT-X 2.1.0-rc5 is intended for beta-testing through June 
>> 7, 2019.  Please note that the FT4 mode should NOT be used in the ARRL June 
>> VHF QSO Party (June 8-10) or ARRL Field Day (June 22-23).
>> 
>> We have done our best to provide suggested operating frequencies for the 
>> test period consistent as far as possible with world-wide band plans and 
>> existing usage.  Please note that thanks to good user feedback, some of 
>> these frequencies are different from those suggested in the document linked 
>> above.
>> 
>> Default frequencies currently recommended for FT4 are as follows:
>> 
>> Band   MHzNotes
>> 

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[James Shaver]

I’m on 20 meters - After about 2-3 minutes of operating, I’m seeing the mode 
getting changed back to FT8 and my frequency is jumping to 14.074.  This 
appears to be random (though it still shows the “FT4” configuration as being 
selected).  Selecting FT4 as the mode does not put me back to 14.080 but 
closing the program and reopening brings me back to where I need to be. A 
reboot appears to have cured this but FYI in case anyone else is 
experiencing a similar issue.  

Also, I’m already seeing quite a few people that have skipped step 8 in the 
setup instructions.  

73,

Jim S. 
N2ADV (ex KD2BIP)

> On Apr 29, 2019, at 2:05 PM, Joe Taylor  wrote:
> 
> To:   Users of WSJT-X -- especially those interested in radio contesting
> From: WSJT Development Group
> 
> By now most of you know about the FT4 protocol under development for eventual 
> release in WSJT-X 2.1.0.  The new mode is particularly optimized for use in 
> radio contesting.
> 
> FT4 is mostly like FT8, but is 2.5 x faster, uses 1.8 x the bandwidth, and is 
> 4.6 dB less sensitive.  Many other details are summarized in "The FT4 
> Protocol for Digital Contesting", available here:
> http://physics.princeton.edu/pulsar/k1jt/FT4_Protocol.pdf
> Links to translations in other languages are available on the WSJT-X web page:
> http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
> 
> Release candidate WSJT-X 2.1.0-rc5 is intended for beta-testing through June 
> 7, 2019.  Please note that the FT4 mode should NOT be used in the ARRL June 
> VHF QSO Party (June 8-10) or ARRL Field Day (June 22-23).
> 
> We have done our best to provide suggested operating frequencies for the test 
> period consistent as far as possible with world-wide band plans and existing 
> usage.  Please note that thanks to good user feedback, some of these 
> frequencies are different from those suggested in the document linked above.
> 
> Default frequencies currently recommended for FT4 are as follows:
> 
> Band   MHzNotes
> -
> 803.575   (3.568 MHz in Region 3)
> 407.047
> 30   10.140
> 20   14.080
> 17   18.104
> 15   21.140
> 12   24.919
> 10   28.180
> 6   50.318
> 2  144.170
> 
> FT4 is designed for contesting, but it will likely find some use for normal 
> QSOs as well, especially during the beta test period.  In the coming month we 
> hope to receive useful feedback on the user interface, message sequencing, 
> interaction with logging programs, etc.  Probably it's best to use "normal" 
> (non-contest) messages except during the mock-contest practice sessions 
> scheduled for  - 0100 UTC on May 9 and May 14, and (if needed) June 5.
> 
> Downloadable installation packages for WSJT-X 2.1.0-rc5 under Windows, Linux, 
> and macOS are available on the WSJT-X web page:
> 
> http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
> 
> Windows users will discover that WSJT-X v2.1.0 has been made available as a 
> 64-bit MS Windows build for 64-bit versions of Windows since Vista. This 
> veraion has one known defect. The audio input device level will be reset to 
> 100% when WSJT-X is started, when the input audio device is changed, and when 
> switching to a new configuration. This is a Qt framework defect that we have 
> reported and is being fixed in a future release; until then users should take 
> care to set the device audio level back to 0dB or lower depending on 
> requirements. Note that many sound cards and chips have real gain ahead of 
> the ADC, as much as 14dB, which will be turned to the maximum due to this 
> defect and is usually undesirable when using WSJT-X.
> 
> Despite this annoying defect, we recommend the 64-bit version of WSJT-X on MS 
> Windows as it has significant advantages in decoding speed.
> 
>-- 73 from Joe, K1JT; Steve, K9AN; and Bill, G4WJS
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT-X 2.1.0-rc5

[Joe Taylor]

To:   Users of WSJT-X -- especially those interested in radio contesting
From: WSJT Development Group

By now most of you know about the FT4 protocol under development for 
eventual release in WSJT-X 2.1.0.  The new mode is particularly 
optimized for use in radio contesting.


FT4 is mostly like FT8, but is 2.5 x faster, uses 1.8 x the bandwidth, 
and is 4.6 dB less sensitive.  Many other details are summarized in "The 
FT4 Protocol for Digital Contesting", available here:

http://physics.princeton.edu/pulsar/k1jt/FT4_Protocol.pdf
Links to translations in other languages are available on the WSJT-X web 
page:

http://physics.princeton.edu/pulsar/k1jt/wsjtx.html

Release candidate WSJT-X 2.1.0-rc5 is intended for beta-testing through 
June 7, 2019.  Please note that the FT4 mode should NOT be used in the 
ARRL June VHF QSO Party (June 8-10) or ARRL Field Day (June 22-23).


We have done our best to provide suggested operating frequencies for the 
test period consistent as far as possible with world-wide band plans and 
existing usage.  Please note that thanks to good user feedback, some of 
these frequencies are different from those suggested in the document 
linked above.


Default frequencies currently recommended for FT4 are as follows:

Band   MHzNotes
-
803.575   (3.568 MHz in Region 3)
407.047
30   10.140
20   14.080
17   18.104
15   21.140
12   24.919
10   28.180
 6   50.318
 2  144.170

FT4 is designed for contesting, but it will likely find some use for 
normal QSOs as well, especially during the beta test period.  In the 
coming month we hope to receive useful feedback on the user interface, 
message sequencing, interaction with logging programs, etc.  Probably 
it's best to use "normal" (non-contest) messages except during the 
mock-contest practice sessions scheduled for  - 0100 UTC on May 9 
and May 14, and (if needed) June 5.


Downloadable installation packages for WSJT-X 2.1.0-rc5 under Windows, 
Linux, and macOS are available on the WSJT-X web page:


http://physics.princeton.edu/pulsar/k1jt/wsjtx.html

Windows users will discover that WSJT-X v2.1.0 has been made available 
as a 64-bit MS Windows build for 64-bit versions of Windows since Vista. 
This veraion has one known defect. The audio input device level will be 
reset to 100% when WSJT-X is started, when the input audio device is 
changed, and when switching to a new configuration. This is a Qt 
framework defect that we have reported and is being fixed in a future 
release; until then users should take care to set the device audio level 
back to 0dB or lower depending on requirements. Note that many sound 
cards and chips have real gain ahead of the ADC, as much as 14dB, which 
will be turned to the maximum due to this defect and is usually 
undesirable when using WSJT-X.


Despite this annoying defect, we recommend the 64-bit version of WSJT-X 
on MS Windows as it has significant advantages in decoding speed.


-- 73 from Joe, K1JT; Steve, K9AN; and Bill, G4WJS


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT-X 2.1.0-rc5 questions

[Saku]

HI !

Few questions about new release and FT4

    - I assume the core of UDP does not change (at least a lot). What 
is the "mode letter" selected for FT4 in #2, Decode message ?


    - Will v2.10-rc5's  N1MM+ UDP message contain ADIF tags  STX, SRX, 
STXString, SRXString ?


   - Does ContestExchange still consist of RST and S(R/T)X (+possible 
S(T/R)XString{locator or state}) or is exchange just exchange and RST 
(or SNR)  only at it's own place ?



--
Saku
OH1KH



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel