[wsjt-devel] Green Goalposts in SF

[George J Molnar via wsjt-devel]

In order to help operators “get the hint” that they must set their receivers so 
that the sync tone is at 750 Hz, may I suggest that the green goalposts be made 
immobile and centered on 750 Hz? 

I’m guessing that several of the “it doesn’t decode” complaints are from users 
with frequency accuracy less than the required +/- 100 Hz.

George/KF2T

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

[wsjt-devel] FT4 and Hold TX

[George J Molnar via wsjt-devel]

Possible bug in 2.6.1 (MacOS)
Regardless of the status of the “Hold TX” checkbox, transmit frequency stays 
locked. This can lead to calling your next contact of the previous one’s 
frequency. 

George J Molnar
College Park, Maryland
KF2TFM19ma

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

Re: [wsjt-devel] Hashed callsign collisions?

[George J Molnar via wsjt-devel]

I had the same thing happen - as if the hash is the same for both /0 and /7, so 
they both respond.



George J Molnar, KF2T
FM19ma - Maryland, USA







> On Jan 20, 2023, at 3:56 PM, Jon Anhold via wsjt-devel 
>  wrote:
> 
> I was just on 20m trying to work W1AW/7, and W1AW/0 answered me, twice - is 
> this a known issue with longer/hashed callsigns?
> 
> 
> 
> 73 de KM8V Jon
> ___
> 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] Unable to find how to reset Q65A default Tx duration (defaults to 30 sec and my operating requires 60 seconds)

[George J Molnar via wsjt-devel]

If your need is immediate, I would recommend downloading rc5, which is still 
available at Sourceforge. That should keep you going until 2.6.1 is out. As a 
Mac user, download the dmg-suffixed file.

https://sourceforge.net/projects/wsjt/files/wsjtx-2.6.0-rc5/



George J Molnar, KF2T
(202) 288-8000
FM19ma - Maryland, USA




> On Jan 8, 2023, at 3:45 PM, David Schmocker via wsjt-devel 
>  wrote:
> 
> Everyone
> My apologies for dual emails on this single problem.  But to clearly 
> communicate the need, I am currently needing to know (essential requirement) 
> how to change the Q65 primary/current operating duration (defaults 30 sec); 
> how do I then change it to 60 sec so I can operate? 
>  
> Then part 2 (nice to have) is how does one change the default (where is the 
> Mac equivalent of Windows WSJTX.ini file)?   Thank you 
>  
> Very 73,
> Dave

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

Re: [wsjt-devel] Unable to find an App at the Apple App web site

[George J Molnar via wsjt-devel]

Not entirely sure of your issue, but I am presuming you were able to download the distribution file from the WSJT Home Page 
(princeton.edu) and opened it. Were you able to drag the WSJT-X icon to the Applications folder (a shortcut is provided), AND 
then follow the Readme instructions explicitly, especially as they concern entering data using the "Terminal" app, 
which is included in every MacOS.Finally, you will need to go to the Applications folder, right click on WSJT-X and 
"Open" it. A security dialog will pop up asking if you really want to do this. Yes, you do. If you've followed 
these steps, you should be good to go. Proceed with entering your call, grid, and radio/audio setups, per the  manual.Good 
luck & enjoy!George J Molnar, KF2TOn Feb 14, 2022, at 2:14 PM, Michael Mertes via wsjt-devel 
 wrote:Hi I was able to download the program and initiate the first few steps.  The 
next step is to open the WSJT-X App, I was unable to find an App at the Apple App Store or through link available when the 
program is double clicked in the Applications section of my Mac mini.  Can you help?StartMail makes private and encrypted 
email easy. Try it here for free!Receive a 50% discount on a new subscription through the referral program.Content-Type: 
text/plain; charset="us-ascii"MIME-Version: 1.0Content-Transfer-Encoding: 7bitContent-Disposition: 
inline___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.5.3 GA Release for macOS

[George J Molnar via wsjt-devel]

Working without incident on my M1 Mac mini under Monterey 12.0.1. 

George J Molnar
College Park, Maryland 
KF2T | FM19ma



> On Dec 13, 2021, at 1:31 PM, Joe Taylor via wsjt-devel 
>  wrote:
> 
> Hi John,
> 
>> On 12/13/2021 1:17 PM, John Stengrevics WA1EAZ via wsjt-devel wrote:
>> 
>> My thanks to John Nelson for this.  However, does this Mac installation 
>> package work with macOS Monterey 12.0.1 running on a M1X chip?
> 
> You just reminded me why I should not have changed "for macOS 10.13 through 
> 11" to "for macOS 10.13 and later" on the web page.
> 
> I have now changed it back.  For more details (and possibly a prognosis 
> concerning support for macOS 12.0.1) we will need input from a knowledgeable 
> mac user, perhaps G4KLA, K9AN, or another volunteer?
> 
>-- Joe, K1JT
>> 73,
>> John
>> WA1EAZ
>>>> On Dec 13, 2021, at 9:37 AM, Joe Taylor via wsjt-devel 
>>>>  wrote:
>>> 
>>> John Nelson, G4KLA, has kindly prepared a macOS installation package for 
>>> WSJT-X 2.5.3.  A download link has been posted on the WSJT-X web page:
>>> https://physics.princeton.edu//pulsar/k1jt/wsjtx.html
>>> 
>>> We hope that installation packages for other OS varieties and the 
>>> source-code tarball can be made available in the near future.
>>> 
>>>  -- 73 from Joe, K1JT; Steve, K9AN; and Nico, IV3NWV
>>> 
>>> 
>>> ___
>>> 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


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

Re: [wsjt-devel] Good old-fashioned Grids-Only mode

[George J Molnar via wsjt-devel]

My suggestion is not to banish reports. The software can (and should) determine 
SNR, display it and report it up the spotter path. No harm at all. The valuable 
data on PSKReporter, HamSpots, etc., would remain intact. The SNR would just 
not be part of the default over-the-air VHF+ exchange.

The suggestion is to enable “grids only” QSOs at VHF and above, with the focus 
on helping rovers, capitalizing on short openings, and meteor scatter. On 2m in 
North America, at least, CM is the de facto standard for 2m and above ms 
already. Having the software support it as default without a Cabrillo log and 
“CQ TEST” would help. The latter especially if directed CQs or QSX modes (e.g. 
CQ 160) are desired.

By streamlining the default VHF+ contact sequence, we would also gain improved 
compatibility between contest mode users and those not using CM (either by 
setting or different software). Sequence confusion should be kept to a minimum. 

George J Molnar
College Park, Maryland
KF2T | FM19ma
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Good old-fashioned Grids-Only mode

[George J Molnar via wsjt-devel]

Going back to my original suggestion - I do not seek to banish signal reports 
for those that want them, certainly. Only set the -default- VHF condition to 
grids-only QSOs. This would have the immediate advantage of substantially 
untying the mess that crops up too often between users in CM working those not 
in CM, or with different software.

In the case of R1 QSO practice, without judging the merits of the R1 Handbook, 
it would seem that in this case, the non-default condition could be set to 
reports, just as all special operating conditions contacts are treated as 
exceptions to the default. 

European ops - I am very curious about the real world use here. If I work you 
on 6m Es during the CQ Worldwide Contest, which requires just a grid, is our 
contact valid? The rules state “Signal reports are not required and should not 
be included in the log entry.” Do any of your contests contacts count? I’m 
confused and would like to understand better.

Very 73,

George J Molnar
College Park, Maryland
KF2T | FM19ma___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Good old-fashioned Grids-Only mode

[George J Molnar via wsjt-devel]

Thanks for that info, Bill. So, if I work a R1 station in CM, the contact is 
not valid for him? That’s very unfortunate.

Still, could the option be applied for R2 and R3? Seems like we could build it 
into a configuration somehow?

George J Molnar
College Park, Maryland
KF2T | FM19ma


> On Aug 1, 2021, at 12:59 PM, Bill Somerville via wsjt-devel 
>  wrote:
> 
> 
> On 01/08/2021 16:44, George J Molnar via wsjt-devel wrote:
>> Submitted for discussion…
>> 
>> Would it make sense to make the default sequence for VHF+ operation the 
>> “Contest Mode” style with no signal reports, no “CQ TEST” and no contest log 
>> being generated? Good old-fashioned Grids-Only mode. We don’t need signal 
>> reports on weak signal or Es VHF work, where the intent is to have a valid 
>> contact in minimum time. 
>> 
>> We can probably eliminate the “VHF and above” features checkbox, too. There 
>> does seem to be confusion around it, sometimes. Just have the application 
>> default to VHF settings, grids only, above 29.700 MHz.  If “Special 
>> Activity” is selected, then the appropriate TEST message can be generated 
>> along with opening a Cabrillo log.
>> 
>> I’m not advocating changing the below-50 MHz setting, since I think the 
>> howls would be large and sustained. 
>> 
>> Thoughts?
>> 
>> 
>> George J Molnar, KF2T
>> College Park, Maryland, USA
> George,
> 
> that is a non-starter in Region 1 at least since the Region 1 VHF handbook 
> defines a QSO to include a piece of QSO specific information being exchanged 
> and confirmed. A grid square does not meet that criteria. OTOH the grid 
> square is not required by that definition of a QSO.
> 
> 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] Good old-fashioned Grids-Only mode

[George J Molnar via wsjt-devel]

Submitted for discussion…

Would it make sense to make the default sequence for VHF+ operation the 
“Contest Mode” style with no signal reports, no “CQ TEST” and no contest log 
being generated? Good old-fashioned Grids-Only mode. We don’t need signal 
reports on weak signal or Es VHF work, where the intent is to have a valid 
contact in minimum time. 

We can probably eliminate the “VHF and above” features checkbox, too. There 
does seem to be confusion around it, sometimes. Just have the application 
default to VHF settings, grids only, above 29.700 MHz.  If “Special Activity” 
is selected, then the appropriate TEST message can be generated along with 
opening a Cabrillo log.

I’m not advocating changing the below-50 MHz setting, since I think the howls 
would be large and sustained. 

Thoughts?


George J Molnar, KF2T
College Park, Maryland, USA






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

Re: [wsjt-devel] Possible feature request, time skew notification?

[George J Molnar via wsjt-devel]

Wouldn’t a simple glance at the Wide Graph provide clear evidence of timing 
errors? Even without WWV, GPS, or software changes, it seems trivial to 
identify the error and walk in a correction.

George J Molnar
College Park, Maryland 
KF2T | FM19ma



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

Re: [wsjt-devel] 2.5rc1 Averaging Issue

[George J Molnar]

Thank you, Joe.

George J Molnar
College Park, Maryland
(202) 288-8000
KF2T | FM19ma


> On Jun 25, 2021, at 9:39 AM, Joe Taylor  wrote:
> 
> Hi George,
> 
> You're looking at the wrong window for averaged Q65 decodes.
> 
> The user option "View | Message averaging  F7" displays a pop-up window that 
> is used to display message averaging information in JT65 and JT4 modes.  This 
> window has no function in Q65 mode.
> 
> For Q65, as described in the referenced tutorial:  "On the Decode
> menu select Fast, Enable averaging, and Auto Clear Avg after decode."
> 
> As shown in the tutorial's screen shot, the "Average Decodes" window is 
> simply the right-hand window on the main screen.
> 
>-- 73, Joe, K1JT
> 
>> On 6/24/2021 3:24 PM, George J Molnar wrote:
>> Thanks, Joe, for the reply.
>> I did conduct the process found in the tutorial. The 30A exercise does work 
>> when the program is launched in Q65 mode. 022800 -23  0.3 1010 :   K1JT K9AN 
>> R-16 q03 is returned. Whenever I switch to another mode (for example, 
>> FT8) and attempt to return to Q65, the F7 “Message Averaging” option is 
>> grayed out. The process completes with 022800 -24   0.3 1010 :  K1JT K9AN 
>> R-16 q09 returned. No data is shown in the pop-up averaging window, 
>> regardless of which test is conducted.
>> Apologies for the lack of clarity in my first message, the F7 pop-up was the 
>> issue I should have specified. Also, the same results are obtained using 
>> 2.4GA.
>> *George J Molnar
>> College Park, Maryland*
>> *KF2T | FM19ma*
>>>> On Jun 24, 2021, at 12:05 PM, Joe Taylor  wrote:
>>> 
>>> Hi George,
>>> 
>>> On 6/24/2021 11:47 AM, George J Molnar KF2T wrote:
>>>> I run 2.5rc1 on a Mac M1 machine. Q65 averaging is usually not available, 
>>>> with the menu option grayed out. On the occasion I can select it (usually 
>>>> upon startup), no traffic populates the averaging window.
>>>> Didn’t mention it earlier, assuming it’s part of the early development 
>>>> “get to it later” agenda. Do enjoy Q65 very much.
>>> 
>>> "Usually not available" sounds very odd.
>>> 
>>> Did you try to go through the short Q65 tutorial starting at the top of 
>>> page 3 of the "Quick-Start Guide to Q65" ??
>>> 
>>> Have you compared WSJT-X 2.4.0 and WSJT-X 2.5.0-rc1 in this respect, on 
>>> your Mac M1?
>>> 
>>>-- 73, Joe, K1JT
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] 2.5rc1 Averaging Issue

[George J Molnar]

Thanks, Joe, for the reply.

I did conduct the process found in the tutorial. The 30A exercise does work 
when the program is launched in Q65 mode. 022800 -23  0.3 1010 :  K1JT K9AN 
R-16 q03 is returned. Whenever I switch to another mode (for example, FT8) 
and attempt to return to Q65, the F7 “Message Averaging” option is grayed out. 
The process completes with 022800 -24  0.3 1010 :  K1JT K9AN R-16 q09 
returned. No data is shown in the pop-up averaging window, regardless of which 
test is conducted.

Apologies for the lack of clarity in my first message, the F7 pop-up was the 
issue I should have specified. Also, the same results are obtained using 2.4GA.


George J Molnar
College Park, Maryland
KF2T | FM19ma


> On Jun 24, 2021, at 12:05 PM, Joe Taylor  wrote:
> 
> Hi George,
> 
>> On 6/24/2021 11:47 AM, George J Molnar KF2T wrote:
>> I run 2.5rc1 on a Mac M1 machine. Q65 averaging is usually not available, 
>> with the menu option grayed out. On the occasion I can select it (usually 
>> upon startup), no traffic populates the averaging window.
>> Didn’t mention it earlier, assuming it’s part of the early development “get 
>> to it later” agenda. Do enjoy Q65 very much.
> 
> "Usually not available" sounds very odd.
> 
> Did you try to go through the short Q65 tutorial starting at the top of page 
> 3 of the "Quick-Start Guide to Q65" ??
> 
> Have you compared WSJT-X 2.4.0 and WSJT-X 2.5.0-rc1 in this respect, on your 
> Mac M1?
> 
>-- 73, Joe, K1JT
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] 2.5rc1 Averaging Issue

[George J Molnar]

I run 2.5rc1 on a Mac M1 machine. Q65 averaging is usually not available, with 
the menu option grayed out. On the occasion I can select it (usually upon 
startup), no traffic populates the averaging window.

Didn’t mention it earlier, assuming it’s part of the early development “get to 
it later” agenda. Do enjoy Q65 very much.

73

George J Molnar
College Park, Maryland
KF2T | FM19ma

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

[wsjt-devel] WSJT-X Development and AVX

[George J Molnar]

I’d definitely support development using AVX (and other) enhancements. 
Definitely “advancing the radio art.” An older version, without ongoing 
development, could always be posted for those with older machines. Such older 
machines probably need to be phased out in many cases; this could provide an 
incentive. 

I’m running with a Mac M1, and everything is very smooth right now.

The extra software capabilities sound promising.

George J Molnar
College Park, Maryland
KF2T | FM19ma___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Band Activity Colours this year only

[George J Molnar]

Could always go to the File menu, and select “Erase wsjtx_log.adi.” 

If that’s too difficult, there may be larger issues to address.



George J Molnar
College Park, Maryland, USA






> On May 17, 2021, at 6:31 AM, OG55W  wrote:
> 
> I am using the same method as Reino and it is very simple!
>  
> 73 Keijo OG5O
>  
> From: Derek Turner via wsjt-devel <>
> Sent: Monday, May 17, 2021 1:15 PM
> To: 'WSJT software development' <>
> Cc: Derek Turner <>
> Subject: Re: [wsjt-devel] Band Activity Colours this year only
>  
> Thankyou Reino
>  
> This is too difficult for my user.
>  
> I was hoping that one of our excellent and ingenious developers would come up 
> with a way of doing it with software.
>  
> Inside the client even?
>  
> 73 de G4SWY DEL +++
>  
> On Sunday, 16 May 2021, 20:14:54 BST, Reino Talarmo 
>  wrote:
>  
>  
> Hi,
> Simplest could be to rename the current wsjtx_log.adi to any suitable name 
> say wsjtx_log_210516.adi. When you open wsjt-x next time all previous worked 
> before information is no more displayed. A new wsjtx_log.adi file is 
> automatically prepared for you.
> If you want whole of this year as starting point you may edit / divide the 
> current wsjtx_log.adi using any text editor and name the one starting from 
> your preferred date to wsjtx_log.adi as well.
> 73, Reino OH3mA
>  
> Lähettäjä: Derek Turner via wsjt-devel 
> [mailto:wsjt-devel@lists.sourceforge.net] 
> Lähetetty: 16 May 2021 21:13
> Vastaanottaja: WSJT Software Development 
> Kopio: Derek Turner 
> Aihe: [wsjt-devel] Band Activity Colours this year only
> 
>  
> Dear Developers
> 
>  
> Now that the Sporadic E season is in full swing on Six meters, I want to 
> start again with square hunting for 2021 and make the Band  Activity colours 
> display only this year's ?
> 
>  
> What can be done ?
> 
>  
> 73  de G4SWY DEL +++
> 
>  
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net <>
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel 
> <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



smime.p7s
Description: S/MIME cryptographic signature
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Problem running wsjt-x in 2 instances

[George J Molnar]

Each instance is treated as an island - the logs and settings are kept 
separately. You can set up configuration details to match your color coding up, 
but they will still look to two different logs.


George J Molnar
College Park, Maryland, USA






> On May 12, 2021, at 1:41 PM, Agustin Bendamio via wsjt-devel 
>  wrote:
> 
> When the program is executed at the same time, on the same PC, and two 
> different frequencies, in the second instance the CQ, s appear all in green. 
> The second instance does not differentiate between new (blue) or previously 
> worked stations. Blue never appears. Anyone have a solution ?.
> 
> Sorry for the off-topic
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel



smime.p7s
Description: S/MIME cryptographic signature
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.4.0-rc3 Audio Issue - Issue Persists on MacOS As Well

[George J Molnar]

Another report of the rc3 MacOS audio issue as well. Flex 6600, SmartSDR for 
Mac 1.4.34, and Intel Mac mini OS 11.2.3.

Not always reproducible, but relatively frequent.


George J Molnar, KF2T
College Park, Maryland, USA





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

Re: [wsjt-devel] Problem with WSJT-X 2.4.0-rc2 Mac Version

[George J Molnar]

Same apparent CAT problem as WA1EAZ reports. But it seems resolved at the 
moment.

Running Flex 6600, Mac mini with Big Sur (11.2.2) and SmartSDR for Mac 1.4.34. 
Had been okay for a while monitoring, then the transmit problem crept in. 
Normal sequence transmit, but the PTT issues and delays reported by WA1EAZ. 

Error: Hamlib error: IO error
rig_get_vfo: returning -6(IO error)
elapsed_ms: elapsed_msecs=1
elapsed_ms:
elapsed_msecs=1)rig.c(2490):rig_get_vfo
return while testing getting current VFO

Closed everything and started again. Did not reload any software. No change.
Cleared the Radio settings, starting from my saved “clean” default setup 
(before any configuration) and tried again. Works now. 

Odd.

George J Molnar
College Park, Maryland
(202) 288-8000
KF2T | FM19ma___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Possibly another clue (terminal window text leading up to Segmentation fault: 11)

[George J Molnar]

What happens when you take step #1 only, then press enter? That should launch 
the app just fine. 

I built an Automator action to do just that, and haven’t had a single issue.


George J Molnar, KF2T
College Park, Maryland, USA






> On Feb 28, 2021, at 9:38 AM, David Schmocker  wrote:
> 
> Everyone:
> Thank you so much for the help here. 
>  
> Here’s (1st time) some text leading up to the fatal “Segmentation fault: 11” 
> in terminal window.  
>  
> This Segmentation fault: 11   displays in terminal window every time WSJT-X 
> crashes. 
>  
> Last login: Sun Feb 28 06:41:47 on ttys000
> Davids-Mac-mini:~ davidschmocker$ /Applications/wsjtx.app/Contents/MacOS/wsjtx
> objc[935]: Class FIFinderSyncExtensionHost is implemented in both 
> /System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit 
> (0x7fffac6a13f0) and 
> /System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride
>  (0x12e7d7f50). One of the two will be used. Which one is undefined.
> Segmentation fault: 11
> Davids-Mac-mini:~ davidschmocker$ 
>  
>  
> Sequence of events leading up to this:
> Launched WSJT-X using terminal window: 
> /Applications/wsjtx.app/Contents/MacOS/wsjtx
> navigating to pull-down menu: File-Open which delivered dialog box #1:
> 2a) 
> 2b) I pressed “OK” and then got dialog box #2
> 3a) 
> 3b) I pressed “OK” and then I was routed to the directory path containing log 
> files, etc.
>  
>  
> Finally, in the terminal window I noticed this text (same as above)
>  
> Last login: Sun Feb 28 06:41:47 on ttys000
> Davids-Mac-mini:~ davidschmocker$ /Applications/wsjtx.app/Contents/MacOS/wsjtx
> objc[935]: Class FIFinderSyncExtensionHost is implemented in both 
> /System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit 
> (0x7fffac6a13f0) and 
> /System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride
>  (0x12e7d7f50). One of the two will be used. Which one is undefined.
> Segmentation fault: 11
> Davids-Mac-mini:~ davidschmocker$ 
>  
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel 
> <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] ft8 not decode I can decode ft4

[George J Molnar]

Moon, we will need a little more than “it doesn’t work” to help you out. I 
presume you have checked your audio paths and clock? Can you provide more 
details of your installation and the specific problem?

George, KF2T

> On Feb 20, 2021, at 3:09 PM, Donald Rossman  wrote:
> 
> I have ft8 2.2.0
> I have windows 10
> Ft8 not decode ft4 do decode 
> In still t8 2.2.0 
>  
> ___
> 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] Valid DXCC checking feature

[George J Molnar]

This strikes me best handled by astute operators rather than by software that 
will rapidly consume the efforts better spent on performance and capabilities.

George J Molnar
College Park, Maryland
KF2T | FM19ma___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.4.0-rc1 MacOS Possible Bug

[George J Molnar]

No, it exits without a crash report.

Sorry for the bad news!

> On Feb 3, 2021, at 2:00 PM, Bill Somerville  wrote:
> 
> On 03/02/2021 17:45, George J Molnar wrote:
>> 
>> 
>> Under macOS BigSur (11.2), ver 2.4rc1 loads normally, but closes without 
>> error message within a minute. If “monitor” is de-selected, the app does not 
>> crash. Behavior same across modes.
>> 
>> 
>> George J Molnar, KF2T
> Hi George,
> 
> is there a crash report generated?
> 
> 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] WSJT-X 2.4.0-rc1 MacOS Possible Bug

[George J Molnar]

Under macOS BigSur (11.2), ver 2.4rc1 loads normally, but closes without error 
message within a minute. If “monitor” is de-selected, the app does not crash. 
Behavior same across modes.


George J Molnar, KF2T
(202) 288-8000
FM19ma - Maryland, USA


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

Re: [wsjt-devel] WSJT-X 2.3.0rc1 Mac Bug?

[George J Molnar]

Sorry, Bill! Saw Gary’s message just after I sent mine.

73,

Geo/KF2T


> On Sep 27, 2020, at 5:55 PM, Bill Somerville  wrote:
> 
> On 27/09/2020 22:35, George J Molnar wrote:
>> 2.3.0rc1 fails with the dreaded “unable to create memory” error. Here is the 
>> result AFTER a reboot.
>> 
>> Running Catalina 10.15.7
>> 
>> 
>> georgemolnar@Georges-Mac-mini ~ % sysctl -a | grep sysv.shm
>> kern.sysv.shmmax: 14680064
>> kern.sysv.shmmin: 1
>> kern.sysv.shmmni: 128
>> kern.sysv.shmseg: 32
>> kern.sysv.shmall: 17920
>> 
>> 
>> 
>> 
>> George J Molnar
> Hi George,
> 
> apologies for this omission, the shared memory requirements have changed. See 
> this post to the WSJT-X Groups.io list for a fix:
> 
> https://wsjtx.groups.io/g/main/message/16844 
> <https://wsjtx.groups.io/g/main/message/16844>
> the sample sysctrl.conf file is updated for the next release.
> 
> 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] WSJT-X 2.3.0rc1 Mac Bug?

[George J Molnar]

2.3.0rc1 fails with the dreaded “unable to create memory” error. Here is the 
result AFTER a reboot.

Running Catalina 10.15.7


georgemolnar@Georges-Mac-mini ~ % sysctl -a | grep sysv.shm
kern.sysv.shmmax: 14680064
kern.sysv.shmmin: 1
kern.sysv.shmmni: 128
kern.sysv.shmseg: 32
kern.sysv.shmall: 17920




George J Molnar
Arlington, Virginia, USA
(702) 767-5420
KF2T   -   FM18lu
















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

Re: [wsjt-devel] r2.2.2 Minor Issue with "short" calls that use DX

[George J Molnar]

JN0 is not a valid grid (you should enter at least four characters). Even so, 
2.2.2 will allow you to enter both an “invalid” call and grid in the DX Call 
and DX Grid boxes, press Generate Std Msgs, and call the station. Yo may need 
to manually step through the QSO cycle, but it WILL work.

5CT is NOT a valid callsign format, but N7C is. It’s not the length, it’s the 
format that counts. Looking through DX spots lately, I don’t see a 5CT 
operation spotted anywhere. Is it possible you had a false decode?

George/KF2T



> On Aug 18, 2020, at 7:51 AM, Stephen VK3SIR  wrote:
> 
> Frode,
>  
> Thanks … By not “picking up” I was meaning you could not click, double-click 
> or even use a third-party product via the UDP interface to force WSJT-X to 
> place WSJT-X into a Tx2 mode that should have responded to the call. It’s a 
> damn shame that I could not catch the call quickly enough (again) to get a 
> recording of the stream. 
> 
> Recorders are on now … Hopefully someone else out there has seen this, has it 
> and can supply?
>  
> I had no problem sending any of the Tx1 - Tx5 messages with 5CT in the DX 
> Call field and JN0 in the DX Grid field.
>  
> The problem is not sending; it’s the program being able to RESPOND through 
> WSJT-X to 5CT sent as an attempted Tx1 ! It was not just me seeing this - 
> which is why I responded with a report here.
>  
> First of all 5CT is not a valid call sign.
>  
> It may or it may not be … It COULD have been allocated. But I have been 
> responding to a number of calls that now fit this template i.e. N7C ( 
> https://www.qrz.com/db/n7c  ) is a VERY valid and 
> sought after call. I was able to make contact with that station but not this 
> one !
>  
> 73
>  
> Steve I
> VK3VM / Vk3SIR
>  
>  
> From: Frode Igland mailto:frodeigla...@gmail.com>> 
> Sent: Tuesday, 18 August 2020 9:08 PM
> To: WSJT software development  >
> Subject: Re: [wsjt-devel] r2.2.2 Minor Issue with "short" calls that use DX
>  
> Steve, I guess that your statement "WSJT-X will not pick up this call" means 
> that WSJT-X will not automatically enter this call into the "DX Call" field, 
> nor the locator into the "DX Grid" field. That is true, but WSJT-X will 
> certainly pick up the call and grid as decoded if you enter it manually into 
> the two fields. WSJT-X does not care how the call and grid arrives in the two 
> fields, but once they are there they are used as entered.
> I had no problem sending any of the Tx1 - Tx5 messages with 5CT in the DX 
> Call field and JN0 in the DX Grid field.
>  
> Secondly, and all important here, it 5CT is not in accordance with the WSJT-X 
> defintions and algorithms for what constitutes a call sign as defined in 
> https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.2.2.html#PROTOCOL_OVERVIEW
>  
> 
>  . Consequently, all my messages were sent as free text messages truncated at 
> 13 characters, which is just right. 
>  
> 73 Frode LA6VQ
>  
> tir. 18. aug. 2020 kl. 08:11 skrev Stephen VK3SIR  >:
> Hi Folks,
> 
> I am unsure whether this has been reported:
> 
> 30m:
> 
> 055130 -11  0.2 1626 ~  CQ CO8LY FL20  Cuba
> 055130 -17  0.3 1342 ~  R3BV F1LYV RR73
> 055130 -19  0.3  618 ~  CQ DX 5CT JN0  Morocco  <-- Will not allow this 
> to be picked this up
> 055200 -12  0.2 1627 ~  CQ CO8LY FL20  Cuba
> 
> No matter what you do or how you try to pick up this calling station and pick 
> up its call (i.e. click on it, double click, even use JTAlert) WSJT-X will 
> not pick up this call !
> 
> I can see that this is being primarily interpreted as a text message (i.e. > 
> 13 chars) ... with the call framed in a " bad" format (missing the final char 
> of the maidenhead).
> 
> [ It is fully understandable and understood why the logic will not allow this 
> call to be picked up as the truncated maidenhead is confusing things ]
> 
> Unfortunately I do not have a recording of this to post back ...
> 
> The screen is going nuts here with PM's so it needs be reported.
> 
> 73
> 
> Steve I
> VK3VM / Vk3SIR
> 
> ___
> 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

[wsjt-devel] VHF Contest Observations

[George J Molnar]

Hi Dev Team,

A couple of possible bugs, and a couple of suggestions for WSJT-X after a 
contest weekend.

Split mode (CQ 260, etc) and Contest Mode don’t play well together. CQ TEST 260 
KF2T FM18 is impossible, of course. Possibility - drop the TEST tag and let the 
auto-exchange cadence provide for the hint? Some people don’t seem to have 
figured out what “CQ TEST” means and were publicly befuddled.

During multiple instances, I occasionally got lost with multiple wide graphs 
open. Could the graph corresponding to the active instance have the transmit 
“goalpost” highlighted (yellow background or something) to aid identification? 
Or perhaps a setting for the active instance to take focus?

In the interest of better rates, it sure would be handy if we could stack 
callers, so that when two people answer (or someone calls in at the last 
exchange) I could click on them without affecting the TX state of the existing 
QSO and allow for the next station to be worked straight away. Would limit ot 
to perhaps 3, so we don’t making QSO machines.

Finally, I noticed some stations I worked displayed 6-character grids in the 
received exchange box, despite the exchange (and transmission) being 
4-characters. My guess is that the longer form may have been populated by my 
wsjtx_log.adi file that I once appended an export of my full station log to. 
Not all callers got this result.

Overall, a very good shakeout for 2.2.1 this weekend. A pleasant weekend was 
had!

George J Molnar
Arlington, Virginia, USA
(702) 767-5420
KF2T   -   FM18lu














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

Re: [wsjt-devel] FT8 with click anomaly

[George J Molnar]

Sometimes hear that kind of effect showing up from an overtaxed computer. 
Over/under-runs and such.


George J Molnar, KF2T 
Arlington, Virginia, USA


> On May 28, 2020, at 6:00 PM, Gary McDuffie  wrote:
> 
> 
> 
>> On May 28, 2020, at 12:33, Andy Durbin  wrote:
>> 
>> The linked WAV file was captured by, and edited in, Audacity.  It does not 
>> replay in WSJT-X.
>> 
>> https://tinyurl.com/y8ehtrkd
> 
> I don’t have a definitive answer, Andy, but have heard that myself now and 
> then.  I sometimes chalk that sort of thing up to having the blanker turned 
> on.  Verify, of course, by turning it off.  That’s not always the case here 
> though.
> 
> Gary - AG0N
> 
> ___
> 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.2.0-rc1 Crash on Mac

[George J Molnar]

Unable to duplicate on 10.15.5 (beta). Fonts changed as expected.

George J Molnar, KF2T 
Arlington, Virginia, USA


> On May 11, 2020, at 5:08 PM, Chuck Reti WV8A via wsjt-devel 
>  wrote:
> 
> 
> Bill,
> 
> Deleted Font and DecodedTextFont lines from the .ini file for my “default” 
> FT8 Config, (though noticing that every one of the configs has its own Font 
> settings lines)
> Still crashing when ticking the font buttons in settings.
> 
> pasted below is additional info from Terminal. Sent this earlier but 
> Sourceforge bounced mail via my VPN’s IP.
> ——
> 
> /Applications/wsjtx.app/Contents/MacOS/wsjtx ; exit;
> qt.qpa.fonts: Populating font family aliases took 1142 ms. Replace uses of 
> missing font family "MS Shell Dlg 2" with one that exists to avoid this cost. 
> qt.qpa.fonts: QCoreTextFontDatabase: Found no matching fonts for family ""
> qt.qpa.fonts: QCoreTextFontDatabase: Found no matching fonts for family ""
> Segmentation fault: 11
> logout
> Saving session...
> ...copying shared history...
> ...saving history...truncating history files...
> ...completed.
> Deleting expired sessions...none found.
> 
> [Process completed]
> 
> — 
> 
> Chuck
> WV8A
> 
> 
> ___
> 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] Flex bug

[George J Molnar]

I do not experience this issue when switching profiles. Profile switches are 
also much quicker than the 3 seconds reported. Suggest that Mike’s case may 
include a user network issue.

Flex 6600, Mac OS Catalina. WSJT-X 2.1.2

George J Molnar
Arlington, Virginia, USA
(702) 767-5420
KF2T   -   FM18lu














> On Apr 23, 2020, at 2:08 PM, Bill Somerville  wrote:
> 
> Hi Mike,
> 
> so what's wrong with the WSJT-X user pressing Retry when changing a SmartSDR 
> profile breaks the CAT connection?
> 
> 73
> Bill
> G4WJS.
> 
> On 23/04/2020 18:20, Black Michael via wsjt-devel wrote:
>> Yes
>> 
>> 
>> 
>> 
>> On Thursday, April 23, 2020, 12:19:11 PM CDT, Bill Somerville 
>>  <mailto:g4...@classdesign.com> wrote:
>> 
>> 
>> Hi Mike,
>> 
>> Does this cause WSJT-X to offer a Retry/Reconfigure/Cancel message box?
>> 
>> 73
>> Bill
>> G4WJS.
>> 
>> On 23/04/2020 18:00, Black Michael via wsjt-devel wrote:
>>> The Flex takes almost 3 seconds to do a profile change and with a polling 
>>> rate of 1 second the code in PollingTransceiver.cpp times out and does a 
>>> shutdown so sends "q" to rigctld for example.  
>>> 
>>> Not talking about changing the polling_rateneed to add a counter to 
>>> only time out after 4 seconds instead of using the  
>>>  polling rate to determine the timeout.
>>> 
>>> Any rig should be able to poll at 1 second (or even faster for that matter) 
>>> but the timeout should not be 1 secondit needs to be the worst case 
>>> scenario to avoid WSJT-X from disconnecting unnecessarily.
>>> 
>>> Mike
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On Thursday, April 23, 2020, 11:49:27 AM CDT, Bill Somerville 
>>>  <mailto:g4...@classdesign.com> wrote:
>>> 
>>> 
>>> On 23/04/2020 17:34, Black Michael via wsjt-devel wrote:
>>>> Found a problem with Flex which is fixed by changing the rig polling rate 
>>>> to 3 seconds and adding some changes to hamlib.
>>>> Doing a profile change on Flex can take almost 3 seconds.
>>>> So if you have polling at 1 second WSJT-X times out waiting for the 
>>>> profile change and actually requests hamlib to disconnect *(i.e. shutdown).
>>>> This may explain random disconnects when any rig takes too long to respond 
>>>> on any command.
>>>> 
>>>> There are a few possible solutions which I'll rank in my preference 
>>>> order
>>>> 
>>>> #1 Fix the polling to provide a fixed timeout of 4 seconds.  Users won't 
>>>> have any idea what to set for this and I don't see any problem with 
>>>> waiting up to 4 seconds when things are getting delayed.  Normally we 
>>>> don't run into this timeout but we need to gracefully recover when we do.
>>>> #2 Provide a user-controllable setting which defaults to 4 seconds.  Just 
>>>> in case this longer timeout causes a different problem.  Maybe put it in 
>>>> the release candidate and then remove it when nobody complains.
>>>> 
>>>> So...for Flex userschange polling to 3 seconds and use this 
>>>> hamlib_settings.json file in the WSJT-X configuration directory
>>>> This changes will be in the next version of WSJT-X for the Flex6xxx entry.
>>>> 
>>>> {
>>>>  "config": {
>>>> "retry": "13",
>>>> "post_write_delay": "0",
>>>> "timeout": "300"
>>>>  }
>>>> }
>>>> 
>>>> 
>>>> de Mike W9MDB
>>>> 
>>> Hi Mike,
>>> please explain what you mean by requests Hamlib to disconnect? Are you 
>>> referring to a TCP/IP connection failure? Does this cause WSJT-X to offer a 
>>> Retry/Reconfigure/Cancel message box?
>>> 
>>> A 3 s polling interval being enforced is not acceptable for an issue that 
>>> only happens when a profile is changed on SmartSDR.
>>> 
>>> 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] FT8 F/H mode - am I out of step ?

[George J Molnar]

Looks absolutely fine

George J Molnar, KF2T 
Arlington, Virginia, USA


> On Feb 26, 2020, at 4:48 AM, runninge...@gmail.com wrote:
> 
> Hi,
> 
> This morning I was trying to contact the PY0FF expedition and observed a
> strange behaviour when attempting the QSO and sending my locator.
> My "PY0FF ON4PB JO20" message is sent every 30 secs whereas all other
> stations are sending their locator in group at a specific time (see
> screenshot at 091715).
> 
> I did not receive other stations sending their locator "out of step", so I
> thought something went amiss here ?
> From the screenshot, one can see that I am in hound mode and calling above
> 1000 Hz :
> 
> https://1drv.ms/u/s!AtBGol2-BnqRhflgvVRljaWMXxDnjg?e=T9rava
> 
> And for the record, I was eventually able to complete the QSO.
> Is this a correct behaviour or am I missing something here ?
> 
> 73's Erik
> ON4PB
> 
> 
> 
> 
> 
> ___
> 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] Sorry!

[George J Molnar]

Cockpit error here led me to believe I lost my first (draft) response, so I 
re-wrote it. My apologies for the wasted bandwidth. Admins, please feel free to 
strike the older of my two similar missives.

George J Molnar
Arlington, Virginia, USA___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 Fox and Hound Mode - FOX Mode Operator enhancement request

[George J Molnar]

A couple recent comments on Fox/Hound mode have me perplexed. 

Aren’t major efforts (those we expect to use F/H) frequencies pre-coordinated 
and published in advance of the trip? 

Do holiday-style trips really need F/H?

Major dxpeditions should never operate in the standard watering holes, right? 
Isn’t there advice about this in the manual?

So, why would operators looking to maximize QSO count need additional band 
monitoring displays? Shouldn’t they concentrate on answering the calls headed 
their way? Clearing contacts would seem to be the goal, not searching a pileup 
for a multiplier or rare one, right?

I grant you, DQRM or operator error can wreak havoc. Wouldn’t this show up in 
the fox’s completion rate and thus raise suspicion by an experienced operator?

For hounds not willing to set up a profile, why? It is extremely easy and 
affords you the ability to enter the Dxpeditions published frequencies, switch 
between them nearly instantly, and keep some semblance of order by not editing 
your normal frequency list. Is there an advantage I am missing?

Hound mode allows full passband monitoring capability, check-box on the main 
screen. Is this insufficient to check band activity before jumping in? I 
thought the receive side of hound mode looks and acts like “normal” FT8. 

In the event of multi-signal operation from non-WSJT-x operations (perhaps in 
the watering holes), why would there be interest in switching to hound mode? 
Standard FT8 works perfectly in this situation. Identifying the mode of 
operation takes little time - if you see someone above 1000 Hz complete a 
contact, it’s not F/H. Or am I confused?

I appreciate the group’s indulgence and patience.

George J Molnar, KF2T 
Arlington, Virginia, USA___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 Fox and Hound Mode - FOX Mode Operator enhancement request

[George J Molnar]

Please forgive what may be ridiculous questions. Some are for foxes, others 
for hounds.

Fox/Hound operation should only be carried out away from the main “watering 
holes,” right? For expeditions, isn’t it standard practice to coordinate with 
other expeditions before leaving home to ensure efficient spectrum use?

Why is looking for another station on the same DF and cycle helpful? Wouldn’t 
the sudden influx of calls for someone-not-you be a tipoff?

Is building a configuration for F/H so onerous, since it could even include the 
announced DXpedition frequencies in the drop down without messing with 
day-to-day use?

Isn’t there a “receive all frequencies” checkbox on the main screen during F/H 
operation? Is this not sufficient to monitor the pileup before jumping in?

Is there value to monitoring another frequency while operating F/H that can’t 
best be solved with a second instance?





George J Molnar, KF2T 
Arlington, Virginia, USA
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Mac OS Catalina

[George J Molnar]

Concur with Greg’s observations. 

George J Molnar, KF2T  
Virginia, USA




George J Molnar
Arlington, Virginia 


> On Oct 4, 2019, at 10:08 AM, Greg Vatt  wrote:
> 
> Bill,
> 
> Here is the crash report of WSJT-X v2.1 using the last developer beta before 
> MacOS Catalina is released today. Thread 12 Crashed: which shows it is still 
> a Qt issue.
> 
> This beta is supposed to be the same as the full release but I am waiting to 
> update later today with the public release of Catalina and see if this is 
> fixed. (Still using MacOS 10.14.6 on my other computer connected for Ham use 
> and WSJT-X v2.1 works fine here.)
> 
> Greg, NC7B
> 
> 
> Thread 12 Crashed:
> 0   org.qt-project.QtCore 0x0001088b4ce9 QLocale::QLocale() + 
> 25
> 1   org.qt-project.QtCore 0x000108909395 
> QDateTimeParser::parseSection(QDateTime const&, int, QString&, int&, int, 
> QDateTimeParser::State&, int*) const + 1237
> 2   org.qt-project.QtCore 0x00010890b340 
> QDateTimeParser::parse(QString&, int&, QDateTime const&, bool) const + 512
> 3   org.qt-project.QtCore 0x00010890de14 
> QDateTimeParser::fromString(QString const&, QDate*, QTime*) const + 148
> 4   org.qt-project.QtCore 0x0001088a10de 
> QDate::fromString(QString const&, QString const&) + 94
> 5   org.k1jt.wsjtx0x0001039156a6 
> LotWUsers::impl::load_dictionary(QString const&) + 230
> 6   org.k1jt.wsjtx0x00010391725c 
> std::__1::__async_assoc_state, 
> std::__1::__async_func (LotWUsers::impl::*)(QString 
> const&), LotWUsers::impl*, QString> >::__execute() + 60
> 7   org.k1jt.wsjtx0x00010391758e void* 
> std::__1::__thread_proxy  std::__1::default_delete >, void 
> (std::__1::__async_assoc_state, 
> std::__1::__async_func (LotWUsers::impl::*)(QString 
> const&), LotWUsers::impl*, QString> >::*)(), 
> std::__1::__async_assoc_state, 
> std::__1::__async_func (LotWUsers::impl::*)(QString 
> const&), LotWUsers::impl*, QString> >*> >(void*) + 62
> 8   libsystem_pthread.dylib   0x7fff69e65d76 _pthread_start + 125
> 9   libsystem_pthread.dylib   0x7fff69e625d7 thread_start + 15
> 
> 
> 
> Full Crash report:  
> 
> 
> 
> 
>  
>> On Oct 4, 2019, at 3:47 AM, Bill Somerville  wrote:
>> 
>>> On 04/10/2019 11:34, Gary Rogers wrote:
>>> Question for Bill: Mac OS Catalina will be released to the public today. 
>>> Will WSJT-X version 2.1.0 be impacted if Mac users upgrade to Catalina? 
>>> Thanks Gary KO3F
>> 
>> Hi Gary,
>> 
>> the only testing has been done with beta releases of macOS 10.15 (Catalina), 
>> there were problems that caused WSJT-X to fail but those problems appeared 
>> to be operating system issues rather than WSJT-X issues, so they may have 
>> been fixed for the public release of macOS 10.15.
>> 
>> As there are known issues with WSJT-X v2.1.0 on macOS that will not be fixed 
>> until the next release I would not recommend attempting to run WSJT-X v2.1.0 
>> on any macOS version at present. Anyone willing to try WSJT-X v2.0.1 on 
>> macOS 10.15 would be welcome, but no guarantees of success are offered just 
>> yet. I will try and get a VM updated to 10.15 once it is available and do 
>> some testing myself.
>> 
>> 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] Help! Ft857d, signalink, Windows 7 and ft8

[George J Molnar]

What are you using for CAT control? The Signalink only handles audio and PTT. 

George J Molnar
Arlington, Virginia USA
Office: ‪(202) 618-1077‬
Mobile: (702) 767-5420

> On Jul 21, 2019, at 1:34 PM, Robert Anthony  
> wrote:
> 
> 
> Anyone using the above and getting it to work? I can't get them to work in 
> the f/h mode. Get a error message. 
> 
> W8om Bob Anthony 
> 
> 
> 
> Sent from my Galaxy Tab® A
> ___
> 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] [HL2WA] Request of 80m band review for FT4 frequency

[George J. Molnar]

The bottom 25 kHz of each band generally are used pretty heavily for CW DX, 
with DXpeditions often in the xx30 to xx40 range. I would encourage keeping 
away from that space to avoid conflict.

Geo/KF2T



> On May 1, 2019, at 8:36 AM, 이동규  wrote:
> 
> Hi, Bill (G4WJS)
>  
> Thank you for your kind and quick email reply.
> 
> About 80m band FT4 frequency 3.523MHz and I think Korean DX members are very 
> positive.
> 
> We will respond to your opinions in a short period of time by collecting 
> opinions from Korean HAMs.
> In addition, we request a review to be able to assign the 60m Band to 1.822 
> KHz or another frequency( ex) 1819 , 1820)  from 1.800 to 1.825 MHz.
>  
> de HL2WA ( KYU )

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

[wsjt-devel] User Experience

[George J. Molnar]

Regarding the comments on button locations, etc., I am inclined to agree with 
W2SRH. The user experience should be consistent, standardized, and expected. 
Honestly, as my eyes age, it sometimes is hard to see a button’s text, so I 
rely on muscle memory and a good guess to press the right button.

Not being on the developer “inside,” I do have to respect their efforts to 
prevent various unsavory behaviors, be they adding “features” not abiding by 
the intent of the authors, or stealing code wholesale. The devs do a ton of 
work, for free, and do have the right to decide the best strategy for their 
app. If the reason for changing up the buttons is really worth affecting the 
user experience, then I can go along with that (and the devs are under no 
obligation to defend their choice here). If it isn’t, please don’t punish the 
many for the sins of a few.

As always, excited to be a small part of this amazing evolution!

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] Possible bug in WSJTX 2.1.0-RC5 Log-Qso

[George J. Molnar]

Would a bold box frame and text be easier to accommodate for both color blind 
and visually impaired users? Perhaps with the frame colored an agreeable shade 
for non-color-blind users?



George J Molnar
KF2T, Arlington, Virginia, USA


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

> On Apr 30, 2019, at 9:43 AM, Derek Turner via wsjt-devel 
>  wrote:
> 
> Dear Bill
> 
> That is better.
> 
> It will be quite easy to look for one rectangle filled with a dark colour and 
> then click on it.
> 
> 73 de G4SWY Derek +++
> 
> 
> 
> 
> On Tuesday, 30 April 2019, 14:33:34 BST, Bill Somerville 
>  wrote:
> 
> 
> On 30/04/2019 14:17, Bill Somerville wrote:
>> On 30/04/2019 14:09, Tom Ramberg via wsjt-devel wrote:
>>> As for colour blindness, red and green are the absolute worst alternatives 
>>> for us that are affected. (10% of male population).
>>> 
>>> 73 de Tom OH6VDA
>>> Sendt fra min iPad Air 2
>> Hi Tom,
>> 
>> I agree but I have not come across a pair of colours that widely imply 
>> stop/go, bad/good, reject/accept, ... conceptually and that are visible to 
>> those with red-green colour blindness.Any suggestions?
>> 
>> 73
>> Bill
>> G4WJS.
>> 
> Hi Tom,
> 
> here is a good summary from the UX perspective:
> 
> https://uxplanet.org/using-red-and-green-in-ui-design-66b39e13de91?gi=4879d577a25a
>  
> <https://uxplanet.org/using-red-and-green-in-ui-design-66b39e13de91?gi=4879d577a25a>
> perhaps the most useful information I can take from that is maybe using just 
> one colour for the OK button is a better approach and make that green. Then 
> at least those with red-green colour blindness can learn that the brown 
> looking button is the OK button. Like this:
> 
> 
> 
> 73
> Bill
> G4WJS.
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel 
> <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

[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] The FT4 Protocol for Digital Contesting - more on frequencies

[George J. Molnar]

A quick two cents…

Is there a good reason why FT4 could not use the existing JT65 and JT9 watering 
holes on all bands? They are quite clear most of the time, and considerate 
operators could certainly share, especially with JT9.

In areas where licenses don’t allow operation on the watering holes, it seems 
that we have (mostly) figured it out around the world.

Looking forward to testing out the new mode. Wonder if speed will trump 
sensitivity for general use?

Many thanks to the dev team for years of effort for the ham community.


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] Feature Request

[George J Molnar]

KF6E has spilled the beans! The secret “whine mode” feature in WSJT-X has been 
revealed. On April 1st, of all days.

Whine mode is exotic code that scans the operator’s brainwaves for signs of 
frustration, and just as he/she is about to give up (afterwards on slower 
computers) permits a DX decode. Otherwise, only calls from your ITU region are 
displayed. 

If you’re calling CQ DX, the software also generates multiple callers from your 
DXCC entity. Only when you give up and/or answer one will the application 
unlock DX decoding.

There are variants on this mode for VHF/UHF, described in the supplemental 
operators’ guide, chapter 42.

George J Molnar
KF2T - Virginia, USA




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

Re: [wsjt-devel] WSJT-X: macOS users - Important - please read

[George J Molnar]

Thanks, Bill!

George J Molnar
KF2T - Virginia, USA



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

Re: [wsjt-devel] What's causing this?

[George J. Molnar]

Do you have a notch filter turned on, or some receiver EQ dialed in?

Geo/KF2T



> On Mar 4, 2019, at 8:52 AM, Bill Mullin  wrote:
> 
> Like this:
> 
> http://aa4m.com/links/Flatten_Off.jpg 
> 
> That's definitely not the fix!
> 
> 73
> 
> On 2019-03-04 06:39:47, Black Michael via wsjt-devel wrote:
>> What does it look like with Flatten turned off?
>> 
>> de Mike W9MDB
>> 
>> 
>> 
>> 
>> On Monday, March 4, 2019, 7:36:18 AM CST, Bill Mullin  
>>  wrote:
>> 
>> 
>> I have "dead space" running from about 1300 - 1700 on all bands:
>> 
>> http://aa4m.com/links/Problem.jpg 
>> 
>> This screen capture shows that this dead space is in the same location on 
>> 80, 40, 30, and 20 meters.  I'm running WSJT-X 2.0.1 and have been since the 
>> day it came out.  This problem started yesterday, so I don't think it's a 
>> glitch in the program.  I've probably (accidentally) screwed up a parameter 
>> but I have no idea which one.  Can anyone help?
>> 
>> 73, Bill - AA4M
>> 
>> ___
>> 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

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

Re: [wsjt-devel] Power Changes and Tapering Decodes

[George J Molnar]

The power changes you are observing are functions of your rig’s audio passband. 
SSB microphone input circuits are typically equipped with a response curve to 
optimize voice. It is almost never “flat.” Some rigs do have a data mode with a 
flat response. Some do not. 

This is not a flaw in WSJT-X, although it can look like that. Check your rig’s 
manual for possible ways to flatten the audio response. If you can’t, and have 
CAT control, engage the “split” mode which attempts to keep your audio tones 
centered in the transmit bandpass by slightly adjusting your “carrier” (0 Hz) 
point.

As for decodes tapering off, this sounds a lot like clock drift with time. Have 
you confirmed the long-term accuracy of your PC clock? Could be it synchs on 
boot only, so as time goes on, you drift away from the necessary accuracy.

George J Molnar
KF2T - Virginia, USA

> 



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

Re: [wsjt-devel] WSJT-X RX Window not in chronological order

[George J Molnar]

I’ve noticed this in situations where there are more decodes than can be 
processed in between TX/RX cycles. Solution is to improve computer performance, 
change to a quieter frequency, or constrain your decode bandwidth a bit. 

George J Molnar
KF2T - Virginia, USA

> 



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

Re: [wsjt-devel] Microsoft Update Bug Has Bitten

[George J Molnar]

Flex software is at 2.4.9
WSJT-x is at 2.0.0

Too many numbers!

George J Molnar
KF2T - Virginia, USA

> On Jan 31, 2019, at 4:08 PM, Richard Solomon  wrote:
> 
> Let me try that.
> 
> Tnx, Dick, W1KSZ
> 
> Sent from Outlook
> From: Al Pawlowski 
> Sent: Thursday, January 31, 2019 10:15 AM
> To: WSJT software development
> Subject: Re: [wsjt-devel] Microsoft Update Bug Has Bitten
>  
> Try turning up the “sleep after” and “screen off after” controls so that your 
> computer does not go to sleep and screen does not power down.
> 
> The audio connection (via VAC) between WSJT-X and my SDR program goes out 
> after wakeup from sleep, and/or screen off, which is fixed only when WSJT-X 
> and the SDR program are restarted.
> 
> Running Win10 home. Problem showed up 3-4 weeks ago.
> 
> 
> Al Pawlowski, K6AVP
> Los Osos, CA USA
> 
> 
> 
>> On Jan 31, 2019, at 08:58, wsjt-devel-requ...@lists.sourceforge.net wrote:
>> 
>> Date: Thu, 31 Jan 2019 16:43:56 +
>> From: Richard Solomon 
>> To: "Dave  W1DWZ" , "Dave  W1DWZ"
>> , wsjt-devel 
>> Subject: [wsjt-devel] Microsoft Update Bug Has Bitten
>> 
>> ……..I now find that if I leave FT8 running for a time, I can no longer 
>> Transmit (Tune button
>> does not work).
>> If I am active on FT8 all is well, …...
>> 
>> Any ideas what I should look for ?
>> 
>> Tnx, Dick, W1KSZ
> 
> ___
> 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] [SPAM] Re: WSJT Reporting to PSK Reporter

[George J Molnar]

Phil,

May I recommend JT-Bridge by SM0THU as a replacement for JT-Alert on your Mac? 
It works well.

There have been several episodes of slow (or no) performance on PSKReporter 
lately. I understand the volume of traffic is extremely high and taxing Phil’s 
free service and volunteer time. 

George J Molnar
KF2T - Virginia, USA

> On Jan 31, 2019, at 10:15 AM, pc ccc  wrote:
> 
> Hi Paul, Laurie & Bill,
>  
> Thanks for the additional information you provided.
>  
> I cannot use JTAlert when I am abroad because a Mac version does not exist. I 
> currently use a MacBook Air wirh WSJT-X and RumLog.
>  
> If I remember well, JTAlert can report to Hamspots and WSJT-X reports to 
> PSKReporter.
>  
> I do not understand why there is such a delay between the time my QSOs or 
> calls are made and the moment they appear on Hamspots. It never happens so 
> when I make QSOs in Europe. I did not see a single report on Hamsports when I 
> was on air last time (about 1,5 h) but I could see many few hours later (the 
> same as the ones reported by Laurie).
>  
> 73
> Phil, F5FDV
>  
>  
> Envoyé: jeudi 31 janvier 2019 à 01:23
> De: "Paul Randall" 
> À: "WSJT software development" 
> Objet: Re: [wsjt-devel] WSJT Reporting to PSK Reporter
> Hi Phil F5FDV, Laurie VK3AMA and Bill G4WJS
> 
>  
> 
> Phil, do you have JTalert installed?
> 
> With WSJT v1.9, reports to PSK reporter worked because the full non-standard 
> callsign did not appear in the CQ call, allowing room for the QRA locator.
> 
>  
> 
> Laurie,  I just installed JTalert and part of the process is a dialogue box 
> asking if I want it to report to Hamspots. Maybe the Hamspots results for 
> Phil that you show in your screenshot come from JTalert as they now do for 
> VK2/G3NJV.
> 
>  
> 
> Bill, in one of your messages to Phil you wrote “...You can be spotted on PSK 
> Reporter using a non-standard callsign by using one of the mechanisms I 
> stated above” Where can I see those mechanisms please?
> 
>  
> 
> Best 73 Paul G3NJV (VK2/G3NJV)
> 
>  
> 
> Sent from Mail for Windows 10
> 
>  
> 
> From: Laurie, VK3AMA <_vk3a...@vkdxer.net>
> Sent: Wednesday, January 30, 2019 10:58:51 PM
> To: wsjt-devel@lists.sourceforge.net
> Subject: Re: [wsjt-devel] WSJT Reporting to PSK Reporter
>  
>  
> On 30/01/2019 7:00 pm, t...@gmx.fr wrote:
> On Tuesday, I made QSOs with Europe from South Africa using my long call with 
> WSJT-X in FT8 mode.
> 
> I had a look at Hamspots and PSKReporter to figure out where in the world my 
> call was spotted.
> 
> I saw no report except one report on PSKReporter from an Indonesian station 
> using ….   a Red Pitaya !!!
> 
> Phil, F5FDV
> 
> I see several spots on HamSpots for ZS1/F5FDV
> 
> 
> 
> de Laurie VK3AMA
>  
> ___ 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] Required duplication feature

[George J. Molnar]

What a great pleasure to work contest mode this time — kudos to the dev team 
for a HUGE improvement.

Tricky thing is that the “Contest Log” shows only contacts for that particular 
profile. So with one or more -rig setup, a unique log is generated. 
Understandable, but inconvenient. Probably best to export to N1MM (or 
equivalent) in real-time, and use that for all-circumstance logging/duping?

George J Molnar
KF2T, Arlington, Virginia, USA


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

> On Jan 20, 2019, at 7:10 PM, ComDaC  wrote:
> 
> Hello,
>  
> Although, there were multiple contacts in today’s, and yesterday’s event, to 
> be the primary mode – as it appears to be with no SSB posts – it needs a 
> duplicate noting feature.  I attempted a contact with K1JT with no success, 
> but that’s understandable.  I like the mode, and it brought me back to VHF 
> and HF with little use in the recent past.  Thank you for your efforts, and 
> it shows the move to the digital modes for efficiency.  Your efforts are 
> appreciated.
>  
> 73,
> Durf
> KX8D
> www.comdac.com <http://www.comdac.com/>
>  
> ___
> 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] TX function lost, then have Task Manager problem

[George J. Molnar]

FWIW, Using a Flex 6600 and MacOS Mojave, xDAX and xCAT - no problems like 
those reported below. CPU usage is in line with previous versions, CAT and DAX 
operation, even via SmartLink, work smoothly.

Geo/KF2T

> On Dec 13, 2018, at 10:27 AM, Al  wrote:
> 
> I also have seen the problem and have come to believe that it related the 
> CAT.. 
> If I use a traditional CAT ( comport) with Kenwood TS480, I do not have this 
> problem. If is use the Flex interface for CAT  this problem returns.. 
> You should also note that the CPU usage for the WSJT task is about 10 times 
> normal, which might indicate some kind of looping fault in the program.
> 
> AL, K0VM
> 
> On 12/12/2018 2:53 PM, bergeracb--- via wsjt-devel wrote:
>> Have not seen my problem listed yet, so I will try to explain what I see.
>> Every once in a while operating, the TX function stops working. The
>> Transmitter goes into transmit but there is no audio drive so no RF is
>> produced. WSJT-X thinks it is working. If I shut down WSJT-X and try
>> to restart the program I get the message that their is another instance
>> of WSJT-X running and the program won't start. Checking the task
>> manager under the Running APPS shows no WSJT-X app listed.
>> However if I look in the Running BACKGROUND tasks, WSJT-X
>> has been moved from the APPS to the BACKGROUND tasks.
>> using END TASK there and then I can restart the program and use
>> the transmitter again. Can't decide if it is a WSJT-X problem or a
>> FLEX 6700 and DAX problem. but I have tried shutting  down and
>> restarting DAX several times without any success. Of course shutting
>> down and restarting the 6700 (after the background WSJT-X task is
>> closed)  also fixes the problem.  I'm wondering if any of the other
>> Flex owner see this problem? I have the work around so right now
>> it is just a nuisance.
>> 73 Al Berger N4AB
>> 
>> 

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

Re: [wsjt-devel] Problem - WSJT-X decoding poorly.

[George J. Molnar]

Probably because you are using a beta release of software two versions back. 
The FT-8 and MSK144 protocols have changed in the last week, with the release 
of version 2.0.

You should update. It should clear your issues.

73,


George J Molnar
KF2T, Arlington, Virginia, USA


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

> On Dec 12, 2018, at 9:21 AM, Bob Seaboldt  wrote:
> 
> Program version - wsjt-x v1.9.0-rc4
> 
> Operating system - linux - Debian GNU/Linux 8 (jessie) 64-bit
> 
> System - 2G ram, 1.66GHz (dual), SSD HD 240G (acer aspire one)
> 
> Radio - TS2000 with SignaLink USB (Through ACC port)
> 
> Concise description of the problem - It seems that wsjt-x is unable to decode 
> FT8, especially signals with high amplitude.   When I first had the system 
> running, I was able to decode all signals (in fact I was very impressed).  
> Now, after about a week, it has stopped decoding properly.  I am using NTS 
> time utility and the clock seems to be spot on, certainly within 2 seconds.  
> I have changed the audio level out of the SignaLink from 10 to 80 (on wsjtx - 
> it was running well at about 30 to 50) with no change. I have also tried 
> adjusting the audio level out of the TS2000 (menu 50C) again with no change.
> 
> Exact sequence of steps required to reproduce the problem - Problem has been 
> persistent for 2 days now.  If I see a signal calling CQ (usually a weaker 
> signal), then I can work them.  If I call CQ and I see a station attempting 
> to reply, then I likely will not see the decode.  Just monitoring I will see 
> several signals on the waterfall (lets say 5), but only a few will decode 
> (lets say 1).  it seems to be louder signals that are affected.
> 
> - NS0V
> 
> ___
> 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] Average DT Time

[George J. Molnar]

Thanks John!

There is nothing to be gained by tweaking the last milliseconds out of timing. 
Sure, it looks pretty and appeals to the perfectionist in us, but as long as it 
-WORKS- call it good and have some fun.



George J Molnar
KF2T, Arlington, Virginia, USA


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

> On Dec 6, 2018, at 6:45 AM, John Kludt  wrote:
> 
> Al,
> 
> I think the key question is are you otherwise getting satisfactory 
> performance?  Are you making Q's?  This subject is starting to take on the 
> tenor of the never ending quest for a 1:1 SWR.  And as we used to like to 
> say, "If the SWR is less than 10:1, call 'CQ'!"
> 
> John
> 

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

Re: [wsjt-devel] WSJT-X 2.0 User Guide PDF

[George J. Molnar]

https://www.dropbox.com/s/ijtfbow5urghoi6/WSJT-X%202.0%20User%20Guide.pdf?dl=0 
<https://www.dropbox.com/s/ijtfbow5urghoi6/WSJT-X%202.0%20User%20Guide.pdf?dl=0>




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] RTTY RU Test Results

[George J Molnar]

Other than the contest log displaying in local time (with AM/PM!), everything 
seemed to work fine in the mock contest. No crashes, no unexpected operation.

MacOS Mojave, Flex6600.

George J Molnar
KF2T - Virginia, USA




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

Re: [wsjt-devel] RC 4 testa.

[George J. Molnar]

Check https://pskreporter.info/cgi-bin/pskstats.pl\ 


There are still 81 people currently using the venerable JT65-HF. Almost 4,000 
on MSHV and JTDX combined. Multiple users on WSJT-X 1.6, 1.7, 1.8, and a sea of 
old RC’s. 

I’m going to take a deep breath or six. Then maybe join in the Scotch Drinking 
Club.

“Friends don’t let friends use old betas!"

Geo/KF2T




> On Nov 19, 2018, at 9:16 AM, Ryan Tourge  wrote:
> 
> I suspect a large population is using one of the mutants (JTDX etc.) and 
> probably don't even know about any of this. That said... I have used both and 
> WSJT-X pretty much offers everything now that I looked for in JTDX.
> 
> On Mon, Nov 19, 2018 at 3:34 AM dgb  > wrote:
> Amen
> 
> I tried RC4 for the last hr. with CQ's on 160-30 and got many replies but not 
> one using RC4!!
> 
> Apparently a very small part of the population using RC4.
> 
> What's it going take to get them to change their ways? ;-)
> 
> 73 Dwight NS9I
> 
> 
> On 11/17/2018 4:01 AM, Krzysztof Krzemiński wrote:
>> Ladies and gentelmen, HAMs,
>> 
>> Where is the ham spirit?
>> 
>> Quite nobody WW is using RC4.
>> 
>> Let's start and run RC4, nobody will do it in your name.
>> 
>> Even if new, super contact "do not change colour on your log".
>> 
>> Help Joe and his team.
>> 
>> Kris, SP5NOH
>> 
>> 
>> Wysłano z TypeApp 
>> 
>> 
>> ___
>> 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

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

Re: [wsjt-devel] RC 4 testa.

[George J. Molnar]

Alas 1.9.1 has no “use or discard by” date. Going to be an uphill slog on HF 
FT8. Look how many comments have already been generated.

Geo/KF2T




> On Nov 19, 2018, at 8:58 AM, Neil Zampella  wrote:
> 
> November 30th, when it self-destructs.
> 
> Neil, KN3ILZ
> On 11/19/2018 3:04 AM, dgb wrote:
>> Amen
>> 
>> I tried RC4 for the last hr. with CQ's on 160-30 and got many replies but 
>> not one using RC4!!
>> 
>> Apparently a very small part of the population using RC4.
>> 
>> What's it going take to get them to change their ways? ;-)
>> 

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

Re: [wsjt-devel] So far, so good

[George J. Molnar]

Actually, I think that has happened to me a couple of times, too. Earlier RC’s 
have those checkboxes for RX/TX in old vs new formats. Am pretty sure some RC3 
guys decoded me and tried responding in the old format. 

Geo/KF2T


> On Nov 16, 2018, at 9:18 AM, Neil Zampella  wrote:
> 
> Gary,
> 
> I seriously doubt you were called by 75 bit users, as they can't decode 
> anything you're sending with RC4.  So there's really no need to include 
> anything about RC4 or 77BT in your CQ transmission.
> 



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

Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc4

[George J Molnar]

Maybe it would be okay if the 5-min no-mouse watchdog was active only for HF 
FT8? And it superseded any WD timer settings?

George J Molnar
KF2T - Virginia, USA

> On Nov 13, 2018, at 12:58 PM, Hasan al-Basri  
> wrote:
> 
> The five minute mouse timer business is going too far. Long MSK144 qsos over 
> difficult paths, should not require the OP to be chained to the desk.
> 
> Several ops are running (on a clear freq), for hours to complete. They aren't 
> sitting in front of the mouse. The developers may not approve of this 
> operational style. but it should NOT be hard coded. It is going to discourage 
> long standing efforts to see a contact to completion.
> 
> ...and who hasn't wandered around the shack, or even made a bathroom run, in 
> the course of an hour long attempt?
> 
> Please don't throw the baby out with the bathwater, unless there is a 
> compelling reason to do so.
> 
> Running smoothly on 260 MSK144, no problems noted, but it's early.  :-)
> 
> Thanks for all the hard work!
> 73, N0AN 
> Hasan
> 
> 
>> On Tue, Nov 13, 2018 at 10:37 AM George J. Molnar  wrote:
>> Congrats, dev team. Running smoothly so far (Mac OS 10.14).
>> 
>> Not sure I understand the intent of the five minute no-mouse timer. Isn’t 
>> this essentially competing with the watchdog? Not sure of a use case that 
>> requires this second timer.
>> 
>> Can you elaborate?
>> 
>> Thanks
>> 
>> 
>> 
>> 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
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc4

[George J. Molnar]

Congrats, dev team. Running smoothly so far (Mac OS 10.14).

Not sure I understand the intent of the five minute no-mouse timer. Isn’t this 
essentially competing with the watchdog? Not sure of a use case that requires 
this second timer.

Can you elaborate?

Thanks



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] Flex Split Operation Setup with WSJT-X

[George J Molnar]

Quick point. Slice refers to an discrete frequency setup. Panadapter is a band 
segment. You can have multiple slices per panadapter, each its own virtual VFO.

George J Molnar 
KF2T, Virginia, USA


> On Oct 27, 2018, at 10:55 AM, Black Michael via wsjt-devel 
>  wrote:
> 
> Ensure you don't have the other frequency on a separate slice.  That may be 
> confusing things.
> Just put on one slice and it should behave.  
> 
> de MIke W9MDB
> 
> 
> 
> 
> On Saturday, October 27, 2018, 2:05:02 AM CDT, Star Light 
>  wrote:
> 
> 
> Thanks for the response.
> 
> As I mentioned in my post, it doesn’t work just fine on one slice.  That’s 
> one of the reasons I posted the question.
> 
> Does anybody have any actual knowledge about this?
> 
> Thanks, Russ
> 
> 
> 
> Sent from my iPhone
> 
>> On Oct 25, 2018, at 9:16 PM, Black Michael via wsjt-devel 
>>  wrote:
>> 
>> I don't know why you would need separate slices to work split in WSJT-X.  
>> Aren't slices really for different frequency ranges?
>> Split in WSJT-X is all inside the audio band pass of one slice.  It just 
>> adjusts the frequency so that the audio is always in the 1500-2000Hz offset.
>> Split is really designed for rigs (or operators) that have harmonics on 
>> their signal (usually from incorrect audio settings).
>> As long as you aren't hitting the ALC on your Flex your signal would be 
>> clean and split is not needed.
>> But it should work just fine on one slice.
>> 
>> de Mike W9MDB
>> 
>> 
>> 
>> 
>> On Thursday, October 25, 2018, 5:55:03 PM CDT, Star Light 
>>  wrote:
>> 
>> 
>> 
>> Hello, I have WSJT-X (v1.9.1) set up with my Yaseu FTdx9000 to operate full 
>> (not “fake") split and it works great.  WSJT-X seems to always listen on the 
>> A side and set Tx on the B side (no matter how it’s set initially) and moves 
>> the B side Tx freq around in a logical way.
>> 
>> I’m not sure how to set up the corresponding configuration on my Flex.  At 
>> present I have it set to the A slice and listening through DAX 1 on the B 
>> slice (to be “split”).  It makes odd freq adjustments that don’t make sense 
>> on the A Tx slice, never changes Tx to the B slice and never moves the DAX 
>> slice choice no matter how I set it up.  I don’t know what it is assuming 
>> and can’t see any way to “tell it” it’s listening on the B slice.  I don’t 
>> know if it assumes that in setup or something else but seems to work best 
>> when set up this way from a simply making contacts point of view.
>> 
>> If I set Tx and DAX audio both on the A slice (always choosing split in 
>> config), it will actually activate the B slice from time to time but never 
>> set’s DAX audio output from it, or Tx to it.  So it can’t actually be using 
>> the B slice for anything.  Then shortly after it activates it, it 
>> deactivates it.
>> 
>> Flex is a drop-down option so I know WSTJ-X “knows” about it, I just know 
>> how it expects the physical radio to be set up to use it in split mode.  Any 
>> advice would be appreciated!  Thanks, Russ KR6W
>> 
>> ___
>> 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
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] VP6D on wrong time slot

[George J. Molnar]

Clicking on their (odd sequence) CQ does put my Hound into TX first, and seems 
to work okay. The checkbox IS greyed out, so I can’t manually change it.

Ver 1.9.1 running Mac OS.



George J Molnar
Arlington, Virginia, USA
KF2T   -   FM18lv












> On Oct 22, 2018, at 10:46 AM, WB5JJJ  wrote:
> 
> Those options should have been removed for the F/H mode.  Perhaps, they 
> triggered this by accident.  
> 
> On Mon, Oct 22, 2018 at 9:41 AM Sam W2JDB via wsjt-devel 
> mailto:wsjt-devel@lists.sourceforge.net>> 
> wrote:
> Ctrl-E - Turns on TX Even
> Shift-E - Turns off TX Even
>  
> good luck
>  
> Sam W2JDB
> 
>  
>  
> -Original Message-
> From: WB5JJJ mailto:wb5...@gmail.com>>
> To: wsjt-devel  <mailto:wsjt-devel@lists.sourceforge.net>>
> Sent: Mon, Oct 22, 2018 10:32 am
> Subject: Re: [wsjt-devel] VP6D on wrong time slot
> 
> Yes, you are correct.  
> 
> I think what we are seeing is a glitch in the software on their end, which 
> was an occurrence even I experienced where I was not able to UNCHECK the EVEN 
> box as it was grayed out.  Restarting WSJTx solved the problem and it's never 
> returned.  But how are so many guys transmitting on the EVEN time slot?  They 
> must be using v1.8.x which, if I remember, would allow choosing time slot.  
> What's funny, is all the guys transmitting on ODD with no chance of being 
> heard by VP6D.  
> 
> Time to move on to another frequency and let this run it's course.  
> 
> On Mon, Oct 22, 2018 at 9:22 AM Jay Hainline > wrote:
> I am seeing this too George as of 1415z on 14090. I remember where this could 
> happened in an earlier version but thought it had been fixed. 
> 
> Jay KA9CFD
> 
> 
> 
> Sent from my U.S.Cellular© Smartphone
> 
>  Original message 
> From: WB5JJJ >
> Date: 10/22/18 09:01 (GMT-06:00)
> To: wsjt-devel@lists.sourceforge.net <>
> Subject: [wsjt-devel] VP6D on wrong time slot
> 
> Right now on 20m (14.090) VP6D is transmitting on the ODD time slot.  About 
> half of the callers are on EVEN and the others on ODD.  How is the happening? 
>  He's using DX Fox according to what I'm seeing from him.  
> 
> -- 
> George Cotton, WB5JJJ
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net <>
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel <>
> 
> 
> -- 
> George Cotton, WB5JJJ
> PO Box 1025
> Russellville, AR  72811
> 
> 479.968.7737 Home
> 479.857.7737 Cell
> 
> DMR K5CS (Local Repeater) - 310515, CC1, TS2
> DMR Arkansas - 3105
> 
> 4
> ___
> 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 <mailto:wsjt-devel@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel 
> <https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
> 
> 
> -- 
> George Cotton, WB5JJJ
> PO Box 1025
> Russellville, AR  72811
> 
> 479.968.7737 Home
> 479.857.7737 Cell
> 
> DMR K5CS (Local Repeater) - 310515, CC1, TS2
> DMR Arkansas - 3105
> 
> 4
> ___
> 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] Improving S/N

[George J. Molnar]

If I recall correctly, the S/N calculation is made in WSJT-X based on a fixed 
value somewhere around 2.8 kHz. Applying a wider or narrower bandwidth to the 
decoder will provide numerically different values, but not affect decoding 
performance UNLESS the narrowed bandwidth had an incidental improvement in 
noise rejection, AGC capture, or some other condition.

It may look good on the screen. It may sound better to your ear, but the 
software doesn’t really care.



George J Molnar
Arlington, Virginia, USA
KF2T   -   FM18lv












> On Oct 19, 2018, at 11:14 AM, Black Michael via wsjt-devel 
>  wrote:
> 
>  A decrease of bandwidth by a factor of 6 will increase reported SNR by 
> approximately 16dB.
> But that's just a matter of what noise reference you use...not any real 
> change in the signal level.
> If you used signal peak instead of RMS the SNR reported would be really 
> lowit's all relative to the value chosen for N.
> 
> You could just as well divide the signal level by some really small number 
> and have 100's of dBs shownthe signal never changed though.
> 
> de Mike W9MDB
> 
> 
> 
> On Friday, October 19, 2018, 9:58:10 AM CDT, DG2YCB, Uwe  
> wrote:
> 
> 
> Frank, seems indeed to work! Just tested during RX of station KG4HF with 
> bandwidth of either 3 kHz or 500 Hz. See the following S/N comparison. 
> Astonishing!
> 
>  
> 
> 
>  
> 73 de Uwe, DG2YCB
> 
>  
> Von: Frank Kirschner [mailto:frank.kirsch...@gmail.com] 
> Gesendet: Freitag, 19. Oktober 2018 15:48
> An: WSJT software development
> Betreff: [wsjt-devel] Improving S/N
> 
>  
> One thing I haven't seen discussed on this reflector is improving the S/N by 
> narrowing the receiver bandwidth. It is no surprise that decreasing the 
> bandwidth received increases the S/N, by 10 to 15 dB, sometimes more. When I 
> see a station I want calling at -24 or so, I can narrow the BW and get solid 
> communications. This is very easy with the graphical presentation and digital 
> filtering of the Flex 6600, but with a little practice, could be done on any 
> modern receiver.
> 
>  
> This means that, if we knew where the stations were calling at -30 or so, we 
> could focus on them and bring them up to the point of making contact. Since 
> you can't decode stations at that S/N, it would have to be done "out of 
> band." Is there any thought being given to setting up an FT8-only DX cluster 
> with exact frequencies?
> 
>  
> What a fascinating hobby!
> 
>  
> 73,
> 
> Frank
> 
> KF6E
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel 
> <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] Decode Background Colors - Suggestions

[George J. Molnar]

Honestly, I think WSJT-x doing the highlighting and parsing is probably a bad 
idea. If we keep it simple, with just CQs and your QSO partner, it should be a 
better user experience and sturdier program. Helper apps like JT-Alert do the 
external heavy lifting for those that want it, so there’s no need to duplicate 
the functionality. 

Think that some of the well-intentioned added functionality is going to come 
back and bite us.



George J Molnar
Arlington, Virginia, USA
KF2T   -   FM18lv








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

Re: [wsjt-devel] WSJT-X 2.0 possible new mode/protocol

[George J Molnar]

While it probably is a remote possibility that the WSJT-X team is contemplating 
adding internet-based linkages, I want to agree with N2ADV and emphatically say 
“no!” to any ham radio communications protocol that relies on anything but ham 
radio to work effectively. 

Even in this day of skimmers and spotting networks, automatic rotators, and 
auto-sequenced contacts, the contact itself is still a radio contact, and 
should remain so in its entirety.


George J Molnar
Arlington, Virginia, USA
KF2T   -   FM18lv






> On Sep 8, 2018, at 6:38 PM, James Shaver  wrote:
> 
> Yes but my previous question about Internet usage still stands: When I am 
> sitting in a park or out on a snowmobile trail with my KX3 and my laptop 
> using a GPS for time sync since there’s no cell reception there, anything 
> that relies on the Internet will be basically useless to me.  Why would we 
> aim to exclude a growing number of such users like me?  Perhaps I’m 
> misunderstanding.  
>  
> Jim S. 
> N2ADV

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

Re: [wsjt-devel] WSJT-X 2.0 possible new mode/protocol

[George J Molnar]

I think he is lamenting the “loss of sensitivity” with FT8 compared to JT65 now 
that the former has come to dominate. Not sure his math works out, so will 
leave that to the dev team. Imagine they are keenly interested in performance, 
too.

George J Molnar 
Virginia, USA


> On Aug 8, 2018, at 8:04 AM, Neil Zampella  wrote:
> 
> Frankly,  I don't see where you're getting the idea that JT65 sensitivity is 
> missing?
> 
> It is still much more sensitive than FT8, and will be for the foreseeable 
> future, as are the other WSJT-X modes.JT9A is at -27, JT65A is at -25, 
> and QRA64A  is at -26.   FT8 is -21 .. all this is based on a average noise 
> floor.
> 
> I don't see what your 'new mode' is going to accomplish.
> 
> Neil, KN3ILZ
> 
> 
>> On 8/8/2018 2:29 AM, Игорь Ч wrote:
>> Hello Joe and all,
>> .
>> We all have been missing JT65 mode sensitivity and proposed WSJT-X 2.0 new 
>> FT8 approach with 0.2 dB sensitivity penalty can make things even worse.
>> .
>> I would like to ask you to consider a new protocol where callsign hash would 
>> be used instead of the real callsign in all messages but CQ and incoming 
>> call, this way we can get back to -25..26dB SNR sensitivity although will 
>> get more limited with the free message length.
>> .
>> CQ message: 28 bit callsign1  + i5bit + 12 bit CRC = 45 bit
>> incoming call: 10 bit call1 hash + 28 bit callsign2 + i5bit + 12bit CRC = 55 
>> bit
>> report message: 10 bit call2 hash + 10 bit call1 hash + i5bit + (10 bit 
>> call3 hash for DXpedition) + 6 bit report + 12 bit CRC = 43(53) bit
>> roger+report message: 10 bit call1 hash +  10 bit call2 hash + 6 bit report+ 
>> i5bit + 12bit CRC = 43 bit
>> 73 message: 10 bit call2 hash + 10 bit call1 hash  + 15 bit GRID + i5bit + 
>> 12bit CRC = 55 bit
>> RR73 message: 10 bit call1 hash + 10 bit call2 hash + 15 bit GRID + i5bit  + 
>> 12bit CRC= 52 bit
>> .
>> Spare bits can be used for nonstandard(special) callsign transmission in CQ 
>> message. call1 hash could be omitted in the incoming call message if this 
>> message is originated by the nonstandard(special) callsign.
>> .
>> Probably we can optimize protocol even better while a main idea is to 
>> transmit a full callsign only once per each QSO and to transmit not more 
>> than one full callsign in the message.
>> .
>> 73 Igor UA3DJY
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Please to send no Newsletter !!!!!

[George J Molnar]

Please note the unsubscribe link at the bottom of each message.

https://lists.sourceforge.net/lists/listinfo/wsjt-devel 
<https://lists.sourceforge.net/lists/listinfo/wsjt-devel>



George J Molnar
Arlington, Virginia, USA
KF2T   -   FM18lv












> On Jul 26, 2018, at 11:15 AM, Jan C. Robbins  wrote:
> 
> Amen to that!  What a waste.
> 
> On 7/26/2018 8:38 AM, Anton STEINWIDER wrote:
>> Hello WSJT-Team !
>> 
>> Please finish the sending of the infomails of WSJT
>> to a-steinwi...@aon.at <mailto:a-steinwi...@aon.at>.
>> 
>> Please do not send any further information to me.
>> Thank you
>> 
>> Best regards
>> 
>> Anton Steinwider
>> OE6ANG
>> 
>> 
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot 
>> <http://sdm.link/slashdot>
>> 
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel 
>> <https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! 
> http://sdm.link/slashdot___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Contest mode CQVHF

[George J Molnar]

Wouldn’t it be simpler to have the sequencer logic respond to R XX## without 
choking? If we can do away with antipodal grids, that should make both modes 
compatible. The sequences will continue and not be lengthened by either or both 
of the operators trying to switch.

George J Molnar 
Virginia, USA


> On Jul 24, 2018, at 12:51 PM, Mark Spencer  wrote:
> 
> I'd support using an extra FT8 bit to explicitly indicate contest mode (using 
> another extra bit to explicitly indicate a "/R" call would also be nice.)   I 
> realize there is a desire to keep FT8 and MSK144 functionality as similar as 
> possible (and that MSK144 doesn't have the "extra bits" that FT8 has) but in 
> practice I don't believe MSK144 has nearly as many contest mode / vs non 
> contest mode issues.
> 
> 73
> 
> Mark Spencer
> VE7AFZ
> netsyn...@gmail.com
> 
> 
> 
>> On Jul 24, 2018, at 9:38 AM,   wrote:
>> 
>> I also was more than a bit frustrated with the contest mode this past 
>> weekend. It's not a fault of the software, just that there's no way to know 
>> from someone's CQ whether they are in contest or QSO mode.
>> 
>> A suggestion that is hopefully easy to code that might fix the problem - add 
>> a CQ predefined message that includes a binary flag to the software with 
>> 0=QSO mode and 1=contest mode. Then, when someone double-clicks on the CQ to 
>> respond, WSJT-X can switch to the appropriate mode. That will also help 
>> those of us in a contest that want to work non-contesters for points, even 
>> though those folks don't want to use contest mode.
>> 
>> 73,
>> 
>> Eric NC6K
>> 
>> -Original Message-
>> From: W0MU Mike Fatchett  
>> Sent: Monday, July 23, 2018 4:37 PM
>> To: wsjt-devel@lists.sourceforge.net
>> Subject: [wsjt-devel] Contest mode CQVHF
>> 
>> First of all I want to thank everyone for this great advancement in the 
>> hobby!
>> 
>> 
>> The CQ WW VHF was my first exposure to contest mode and it was a very 
>> frustrating 27 hours.
>> 
>> If I am in contest mode and I call CQ and get an answer from someone who 
>> is not, there is essentially no way to complete a qso unless one side 
>> changes into or out of contest mode.  What happened to me is I would 
>> switch and then the other side would switch and we would be opposite.  
>> Frustrating!
>> 
>> The main issue is that we cannot expect those not in the contest to have 
>> to switch into a specific mode to work us.  This does not happen in any 
>> other contest.  We cannot expect this from casual ops.  I am glad they 
>> want to work me.  Being able to work them should be painless too!
>> 
>> Why is contest mode needed?  If a qso is good in contest mode with less 
>> sequences I suggest that all FT8 exchanges be the same. Is there a 
>> specific reason two have multiple sets of exchanges for in a contest and 
>> not in a contest?  I don't think so.
>> 
>> I understand that this was an issue for the June VHF contest too.
>> 
>> If you guys can move my xmit around in fox/hound mode, which worked out 
>> really well, there has to be a solution for this.  I believe that the 
>> fox was still able to work people not running hound?  We need the same 
>> ability in contest mode.
>> 
>> I believe that this is already being examined but I thought I would give 
>> my feedback.  I would be happy to provide more information if desired.
>> 
>> Thanks again for all the hard work in bringing us FT8!
>> 
>> W0MU
>> 
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>> 
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] File Lock is on Windows 10

[George J Molnar]

If you’re trying to run two instances, check the manual for the command line 
options you need to use. The two instances must be individually defined.

George J Molnar 
Virginia, USA


> On Jul 10, 2018, at 11:21 AM, Larry Nathanson  wrote:
> 
> I am having trouble with the file lock. I removed all temporary files and 
> reinstalled the program twice. I still get an error message. The message is 
> that 2 users can’t operate at one time. Please help. Larry N2CPA
>  
> Larry Nathanson
>  
> 
>  
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Tx/Rx

[George J Molnar]

Would changing the arrows to an equals sign solve the problem?

George J Molnar, KF2T 
Virginia, USA


> On Jul 3, 2018, at 4:38 PM, dgb  wrote:
> 
> Only to those that don't take the little time to see how they work!
> 
> 
>> On 7/3/2018 10:38 AM, Al Pawlowski wrote:
>> If a count was taken, I bet it would be 10 to 1 or more that think the 
>> button arrows are backwards. 
>> 
>> 
>>> Date: Tue, 03 Jul 2018 14:08:57 +0100 
>>> From: Barry Smith  
>>> To: wsjt-devel@lists.sourceforge.net 
>>> Subject: Re: [wsjt-devel] Tx/Rx 
>>> 
>>> ...There are as many people who think the sense is 
>>>> correct as there are that think it is reversed. 
>> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] How much operating time before rebooting your computer

[George J Molnar]

If by losing sensitivity you mean fewer signals are decided, are you sure it’s 
not just band conditions?

If you’re seeing signals on the waterfall that don’t decode after your computer 
has been on a long time, perhaps you need to re-sync your time more frequently?

George J Molnar
Washington, DC
@GJMolnar | KF2T 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] DXpedition mode: dissapointed somehow

[George J Molnar]

Andras,

Yes my family is from Hungary. I clearly remember my grandfather’s strong 
accent, expressions, and cooking! We have been in America only since WW1, and 
am sure there are many relatives in Europe. I understand your concern 
completely. Not sure there is much we can do about some operators who do not 
operate as good citizens. 

Rather than this group get embroiled in debates over what constitutes a worthy 
use of Fox/Hound mode, or what frequencies should or should not be used, let’s 
see what we can do to help the dev team with constructive ideas for appropriate 
use of Fox/Hound. It may well turn out that we all have to change our ways. 

Should we split our FT-8 operations into two sub-bands, with one being 
self-designated “foxes” and the other “hounds”? While we’d still want major 
pileups removed from the customary working frequencies, perhaps this will 
alleviate congestion and allow operators to become accustomed to this 
particular brand of split operating. That way, the confusion will be reduced 
(of course never eliminated) when the rare ones fire up. Train the way you 
fight, right?

Just an idea. Who has others?

George J Molnar
Washington, DC, USA
KF2T   -   @GJMolnar









> On Mar 14, 2018, at 8:48 AM, Andras Bato  wrote:
> 
> Hello Mr. Molnar,
> maybe our predecessors were fighting together for freedom here in Hungary.
> A large port of the problem is jamming by operators of certain countries, 
> mainly in South-Europe.
> Something has to be done against their bullying style.
> I'm sure it helps!
> GL de HA6NN
> Andras

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Fox mode suggestion

[George J Molnar]

Perhaps one of the Fox channels can include a randomized ID (even like CQ PH0X 
FM29), not to exceed 9 minutes? Might help pileup management.

George J Molnar
Washington, DC
@GJMolnar | KF2T 
> 
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] 1.9 RC2 - UI Suggestion

[George J Molnar]

Thanks for the clarification, Joe.

George J Molnar, CEM, CHPP
@GJMolnar | KF2T | AFA9GM

> On Feb 26, 2018, at 3:47 PM, Joe Taylor  wrote:
> 
>> On 2/26/2018 3:20 PM, George J Molnar wrote:
>> Any chance for 6-place grid squares at VHF & higher?
> 
> Of course you can send a 6-character locator as part of a free text message.
> 
> But as a JT-style structured message??
> 
> Think about it this way: A 4-character Maidenhead locator fits in a 15-bit 
> field.  A 6-character locator must allow for AA to RR as the final two 
> characters.  That's another 18 x 18 = 324 possibilities, or another 9 bits.  
> All 72 bits in the JT structured messages are "spoken for".  We don't have 9 
> unassigned and available bits.
> 
>-- Joe, K1JT
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] 1.9 RC2 - UI Suggestion

[George J Molnar]

Also suggest “NA VHF Contest” label be changed to simply “Grids."

Any chance for 6-place grid squares at VHF & higher?




George J Molnar
Washington, DC, USA
KF2T   -   @GJMolnar









--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] 1.9 RC2 - UI Suggestion

[George J Molnar]

Like ZL2IFB’s “arrowheads” idea. Yes, the existing model makes sense, but his 
idea makes (in my opinion) more sense.

Great work on rc2, guys!


 
George J Molnar
Washington, DC, USA
KF2T   -   @GJMolnar






> 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Updating the WSJT-X User Guide; OS X sample rate

[George J Molnar]

Joe, 

I have not experienced this issue using virtual audio cables (Flex 6000-series 
DAX support) running at 48k. However, using an external USB sound card, the 
problem does intermittently rear its head. Am not sure if the 44.1k “fix” is 
anecdotal or not, or if it covers all versions of MacOS. It does appear to have 
worked for several people.

Suggest recommending the 48k rate, while allowing that, “in the event of 
unexpected audio issues” a 44.1k rate may be helpful to try.



George J Molnar
Washington, DC, USA
KF2T   -   @GJMolnar









> On Feb 8, 2018, at 1:07 PM, Joe Taylor  wrote:
> 
> Hi all,
> 
> In preparation for an upcoming release candidate of WSJT-X v1.9.0, I am 
> updating the WSJT-X User Guide.  If you are aware of anything that needs work 
> in the User Guide, please post a message here or otherwise let me know.
> 
> Here's a specific question for Mac users.  In Section 3.3 we currently say 
> this:
> 
> "Use the Mac’s Audio MIDI Setup utility to configure your sound card for 
> 48000 Hz, two-channel, 16-bit format."
> 
> But several Mac users have reported losing audio unless they set the sample 
> rate to 44100 Hz.  Is this always the case with OS X?  Should this 
> instruction be changed?
> 
>   -- 73, Joe, K1JT
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] "Contest" to "Grids" Change?

[George J Molnar]

Just a “vote up” for changing the “NA Contest Mode” label to “Grids” for 
simplicity and continuity with older practice. 

Also, I seem to recall there were a couple of bits “left over” looking for a 
purpose some time ago. If those bits are still there, maybe they could be used 
to support 6-place grid locators? Maybe have 6-place grids available optionally 
on a per-band basis? In truth, though, it probably wouldn’t hurt to use them as 
our normal way of doing business, regardless of band. The software could use 6 
places if entered, otherwise four.

Happy New Year, everyone. 


George J Molnar
KF2T - Nevada, USA








--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Audio level to TS590SG USB card

[George J Molnar]

You can use the slider on the right side of the main screen to adjust your 
output level. It can also be set (in preferences) to remember settings by band.

Hope that helps!

George J Molnar, KF2T 
Nevada, USA


> On Dec 16, 2017, at 3:50 PM, Gilbert Baron  wrote:
> 
> I got all working but the Transmit Audio is MUCH too high and I get both a 
> full 100 watts and excessive ALC on my TS590SG. Is there a setting in the 
> program to control the audio level fed to the radio? If not, this is 
> something that is really needed. If not, I would have to change my radio or 
> Windows setting for every program that uses the sound card and I have 3. The 
> other 2 have a level setting and remember it. If I missed this could you 
> point me to the correct spot. Thanks.
>  
> I would like to get started with JT8. There are MANY more signals on than PSK 
> or RTTY and a lot of DX. I see why this is becoming popular.
>  
>  
> Outlook Desktop Gil W0MN
> Hierro Candente Batir de Repente
> 44.08226 N 92.51265 W EN34rb
>  
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] DXPedition System Clock Sync

[George J Molnar]

Sounds like a perfect idea for a stand-alone application. 

Not sure what it might take to support clock changes across various OS’s now 
using WSJT-X.



George J Molnar
KF2T, Nevada, USA







> On Nov 11, 2017, at 8:32 AM, Ria Jairam  wrote:
> 
> That is an excellent idea.
> 
> A clock sync feature using WWV, WWVB, JJY, YVTO, CHU, DCF etc would
> help those who don't have the ability to sync clock over the Internet.
> 
> 73
> Ria, N2RJ
> 
> On Sat, Nov 11, 2017 at 11:23 AM, Scott Bidstrup  wrote:
>> On 11/11/2017 09:26 a.m., Bill Shell N6WS wrote:
>>> 
>>> Hello,
>>> 
>>> While using FT8 in a DXPedition setting, there may be conditions where
>>> there is no reliable timing source for syncing of the system clock.
>> 
>> 
>> Bill,
>> 
>> When my Internet here in Costa Rica has been down, I've been able to sync my
>> system clock adequately closely by using WWV and using the Windows clock set
>> feature to set the clock, by simply setting to the next minute and then
>> clicking the Apply button as the time comes around to zero seconds.  After
>> doing it a few times, you can nearly always get the hang of it and get it
>> within a second or so.  Close enough that I've gotten by.  It's a nuisance
>> and takes a bit of practice, but it can be done in a pinch.  And it's gotten
>> me back on the air many times.
>> 
>> Per your request, though, I envision a clock set feature whereby you would
>> set the receiver to zero-beat WWV, and call a special clock set routine that
>> would look for the top-of-the-minute tone at the right audio frequency and
>> at approximately the top of the minute.  When it sees the tone appear at the
>> right frequency, and at about the right time, it sets the system clock
>> accordingly.  In my professional work, before the advent of the Internet, I
>> used hardware clocks based on such a system, and they seem to have worked
>> reasonably well most (though not all) of the time.
>> 
>> That would only work, however, in parts of the world where WWV is available.
>> When I lived in Africa many years ago, however, WWV was rarely audible, but
>> there was a different time signal that I could hear, a digital signal of
>> some sort, and I have no idea where it originated from (EU maybe?) or what
>> the protocol was.  Something that uses that or other protocols might be
>> useful in those regions.
>> 
>> Scott Bidstrup
>> TI3/W7RI
>> 
>> 
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Fast Graph Suggestion

[George J Molnar]

Suggestion - Fast Graph Auto Level should use only the lower (completed) period 
to base gain/zero vales. Pressing Auto Level with the current (top) period 
provides varying results depending on the progress of the period.

Doesn’t affect operation; just a suggested UI tweak.


George J Molnar
KF2T, Nevada, USA







--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT 1.8.0 RC3

[George J Molnar]

I’d like to briefly weigh in in support of default split mode. 

Trunked radio and cellular systems operate this way all the time - the actual 
operating frequency is unknown to the user, and changes depending on a variety 
of factors. This is advantageous.

In an FT8 environment, I suggest it is also advantageous. By responding to a 
station (DX or not) on a frequency that is clear at your location, you are 
actually minimizing QRM and improving circuit effectiveness. Other callers on 
other frequencies can be selected by the target station without having to worry 
(as much) about overlapping signals effectively destroying an otherwise working 
path. 

Being “zero beat” doesn’t improve anything, and, unless you’re looking at the 
waterfall, doesn’t mean anything in an FT8-like situation. Consider the whole 
passband (approx 3 kHz) as “on channel” and it’s all good.

Admittedly, it took some getting used to. Forty years of habits aren’t shed 
overnight. Now, I find my best results are had by finding a clear spot, locking 
(holding) my TX, and responding to stations in the passband. I never liked 
having the software move my TX based on the remote operator’s stability or 
preferences. I think QSO rates are better this way, and interference is reduced.

By the way, using split does not cut the number of contacts per kHz in half. 
The same number of signals can be sent during each cycle, either way. Once you 
don’t worry about the guy on “your” frequency during the opposite cycle not 
being your QSO partner, it’s no problem at all.

So, a vote for the rc3 method. 


George J Molnar, KF2T
Nevada, USA






--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] CQ after 73 possible regression?

[George J Molnar]

Noticed this morning that TX is disabled (Enable TX box is cleared) after 
logging, regardless of the setting of “Disable TX after 73.”  r8159, MacOS 
10.13, running FT8, with Hold TX Freq, Auto Seq, and Call 1st checked. 




George J Molnar, KF2T
Nevada, USA







--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Experimental changes in r8147

[George J Molnar]

Looks good and works well. Think the new logic is...logical.

George J Molnar, KF2T 
Nevada, USA


> On Sep 30, 2017, at 3:12 PM, DXer  wrote:
> 
> Jim, Joe,
> 
> Working fine answering a CQ in JTAlert in the format CQ NA EA3RT JN01.
> 
> 73 de Vince, VA3VF
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Experimental changes in r8125

[George J Molnar]

One point about using control-clicks that hasn’t been raised, but might affect 
usability is the growing number of tablet and other touch screens in use. 
Double clicking for setting both RX/TX, unless TX Lock is on, is the simplest, 
most natural gesture without a keyboard. At least on my end.

George J Molnar, KF2T 
Nevada, USA



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Experimental changes in r8125

[George J Molnar]

Suggested behavior for double click might be to set TX/RX to same tone, unless 
lock TX is set, in which case only RX moves.

Seems more intuitive and consistent.

George J Molnar, CEM, CHPP
KF2T - Nevada, USA

> On Sep 28, 2017, at 2:12 PM, Ron Gibson  wrote:
> 
> Hi Joe,
> I for one have adapted to the "Tx frequency is not changed unless Ctrl is 
> held down" just fine!
> 73 de Ron
> VE3CGR / CG3CGR
> 
>> On 9/27/2017 8:47 AM, Joe Taylor wrote:
>> Hi all,
>> 
>> If you are building WSJT-X from code in the development branch and
>> experimenting with it on the air, please pay attention to the commit message 
>> for r8125 and report your findings here.
>> 
>> For full and open disclosure I'll copy the commit message here:
>> 
>> ## 
>> Experimental new behavior for "Lock Tx=Rx" and for clicking on waterfall and 
>> decoded text.
>> 
>> 1. Checkbox "Lock Tx=Rx" is now labeled "Lock Tx Freq", and its meaning is 
>> quite different.  If checked, the audio Tx frequency cannot be changed. It's 
>> like the "Lock" function on some transceivers.
>> 
>> 2. Clicking on the Wide Graph waterfall and on lines of decoded text now 
>> behave as follows:
>> 
>> Click on   Action
>> -
>> Waterfall: Click to set Rx frequency
>>Shift-click to set Tx frequency
>>Ctrl-click to set Rx and Tx frequencies
>>If Lock Tx Freq is checked, Tx freq does not move
>>Double-click to set Rx frequency and decode there
>> 
>> Decoded Text:  Double-click to copy transmitting callsign to DX Call
>>and locator to DX Grid; change Rx frequency to decoded
>>signal's frequency; generate standard messages.
>>Tx frequency is not changed unless Ctrl is held down
>>and Lock Tx Freq not checked.
>> 
>> If this experimental behavior is adopted, some descriptions in the User 
>> Guide and Special Mouse Commands will need to be updated.
>> 
>> 3. Starting to implement a new function on the Tools menu, "Solve for 
>> calibration parameters".  This is not yet finished; DO NOT USE in its 
>> present form.
>> ## 
>> 
>> -- 73, Joe, K1JT
>> 
>> --
>>  
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>> 
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] NA VHF Contest Mode

[George J Molnar]

Same experience last night with N2ADV on FT8. I called him in contest mode, 
which did not seem to advance the sequence. When I switched back to “normal,” 
the sequence progressed.

My version 8101. Not sure about Jim (but know he is on this list).

George J Molnar, KF2T 
Nevada, USA


> On Sep 22, 2017, at 5:39 AM, Larry Davis  wrote:
> 
> yes we were using msk
> 
> 
> On Friday, September 22, 2017 7:23 AM, Jay Hainline  wrote:
> 
> 
> Yes we were both using 8101 and msk144 mode. We did not try ft8. Sorry I 
> forgot to mention it.
> 
> Jay KA9CFD
> 
> 
> 
> Sent from my U.S. Cellular® Smartphone
> 
>  Original message 
> From: Joe Taylor 
> Date: 9/22/17 07:16 (GMT-06:00)
> To: WSJT software development , Steven 
> Franke 
> Subject: Re: [wsjt-devel] NA VHF Contest Mode
> 
> Hi Steve,
> 
> On 9/22/2017 8:12 AM, Steven Franke wrote:
> > Hi Joe,
> > 
> > Recall that MSK144 is configured such that fix_contest_msg is *always* 
> > called, independent of whether or not the contest box is checked. Won’t 
> > this prevent the contest-mode prompt from being triggered in that mode?
> 
> Yes, it seems that must be so.  Maybe Jay and Larry were using MSK144?
> 
> -- Joe
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! 
> http://sdm.link/slashdot___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] NA VHF Contest Mode

[George J Molnar]

You bet, Joe.

George J Molnar, CEM, CHPP
KF2T - Nevada, USA

> On Sep 21, 2017, at 1:14 PM, James Shaver  wrote:
> 
> Drop me a note, George, we can find a semi-empty corner of a band :)
> 
> Jim S.
> 
> N2ADV
> 
> 
>> On 9/21/2017 4:05 PM, Joe Taylor wrote:
>> Hi George,
>> 
>>> On 9/21/2017 3:56 PM, George J Molnar wrote:
>>> Joe, would absolutely not remove sh - it’s incredibly useful. My intention 
>>> was to say the term should be written as a full word (e.g. “Shorthand”), 
>>> not deleted.
>> 
>> RR, understood.  Can you find someone with whom to do stress tests of 
>> contest mode?
>> 
>> -- Joe
>> 
>>>> On Sep 21, 2017, at 12:42 PM, Joe Taylor  wrote:
>>>> 
>>>> Hi George,
>>>> 
>>>>> On 9/21/2017 3:31 PM, George J Molnar wrote:
>>>>> Quick feedback on the repositioned contest mode checkbox. Bravo! Good 
>>>>> idea.
>>>>> Before GA release, it might be helpful to clean up the labels and 
>>>>> alignment, so everything flows smoothly. ”Sh” could be written out, and 
>>>>> maybe NA VHF Contest could distill down to just “Contest.” With 
>>>>> appropriate tooltips, think it should be okay.
>>>> 
>>>> Thanks for the feedback.  A little GUI cleanup is indeed desirable.
>>>> 
>>>> Why would you remove "Sh"?  In mSK144 mode it's widely used at 144 MHz and 
>>>> higher.
>>>> 
>>>> What would be *really* helpful is for you to work with someone else and 
>>>> thoroughly exercise the new capabilities.  Both MSK144 and FT8. The idea 
>>>> is that one of you would be trying to make contest QSOs; the QSO partnet 
>>>> might or might not be in the contest, or know anything about what "Contest 
>>>> Mode" means.  Test all possibilities, and report back.
>>>> 
>>>> -- Joe, K1JT
>> 
>> --
>>  
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 
> -- 
> 73,
> 
> Jim S.
> N2ADV
> www.qrz.com/db/N2ADV
> https://www.facebook.com/groups/FT8.Digital.Mode/
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] NA VHF Contest Mode

[George J Molnar]

Joe, would absolutely not remove sh - it’s incredibly useful. My intention was 
to say the term should be written as a full word (e.g. “Shorthand”), not 
deleted.

George J Molnar, CEM, CHPP
KF2T - Nevada, USA

> On Sep 21, 2017, at 12:42 PM, Joe Taylor  wrote:
> 
> Hi George,
> 
>> On 9/21/2017 3:31 PM, George J Molnar wrote:
>> Quick feedback on the repositioned contest mode checkbox. Bravo! Good idea.
>> Before GA release, it might be helpful to clean up the labels and alignment, 
>> so everything flows smoothly. ”Sh” could be written out, and maybe NA VHF 
>> Contest could distill down to just “Contest.” With appropriate tooltips, 
>> think it should be okay.
> 
> Thanks for the feedback.  A little GUI cleanup is indeed desirable.
> 
> Why would you remove "Sh"?  In mSK144 mode it's widely used at 144 MHz and 
> higher.
> 
> What would be *really* helpful is for you to work with someone else and 
> thoroughly exercise the new capabilities.  Both MSK144 and FT8. The idea is 
> that one of you would be trying to make contest QSOs; the QSO partnet might 
> or might not be in the contest, or know anything about what "Contest Mode" 
> means.  Test all possibilities, and report back.
> 
>-- Joe, K1JT
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] NA VHF Contest Mode

[George J Molnar]

Quick feedback on the repositioned contest mode checkbox. Bravo! Good idea. 

Before GA release, it might be helpful to clean up the labels and alignment, so 
everything flows smoothly. ”Sh” could be written out, and maybe NA VHF Contest 
could distill down to just “Contest.” With appropriate tooltips, think it 
should be okay.


George J Molnar
Nevada, USA




--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Found: Cause of MacOS Window Position Error

[George J Molnar]

Either, including switching Configuration. However I close/restart the common 
factor is the Menus checkbox in the main window.

I haven’t tried this on Windows, so can only report results on MacOS.


George J Molnar, KF2T
Nevada, USA







> On Sep 5, 2017, at 8:44 PM, Black Michael via wsjt-devel 
>  wrote:
> 
> Are you closing WSJT_X via the "X" icon or the File/Exit?
> 
> I found the "X" icon does not preserve window position on Windows 10.
> 
> de Mike W9MDB
> 
> From: George J Molnar 
> To: WSJT software development  
> Sent: Tuesday, September 5, 2017 6:29 PM
> Subject: [wsjt-devel] Found: Cause of MacOS Window Position Error
> 
> Gentlemen,
> 
> It seems that my problem with the main window not staying where I positioned 
> it has to do with the main window “menus” checkbox. Sizing and location are 
> not preserved unless that box is checked.  Subsequent launches will re-set to 
> the last “checked” state, which had been upper left (default), but can be 
> anywhere on screen.
> 
> 
> Test procedure:
> Open WSJT-X
> Ensure "Menus" is checked in the main window
> Reposition the window
> Relaunch WSJT-X (change configuration or Exit/Restart)
> Window stays in position 
> 
> Uncheck “Menus"
> Reposition the window
> Relaunch WSJT-X (change configuration or Exit/Restart)
> Window does NOT stay in position
> 
> 
> MacOS 10.13 beta, RC2 8069
> 
> I had thought it might be a bad .plist or .ini file, but deleting and 
> rebuilding those did not help.
> 
> 
> 
> 
> George J Molnar, KF2T
> Nevada, USA
> 
> 
> 
> 
> 
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot 
> <http://sdm.link/slashdot>___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel 
> <https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! 
> http://sdm.link/slashdot___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Found: Cause of MacOS Window Position Error

[George J Molnar]

Gentlemen,

It seems that my problem with the main window not staying where I positioned it 
has to do with the main window “menus” checkbox. Sizing and location are not 
preserved unless that box is checked.  Subsequent launches will re-set to the 
last “checked” state, which had been upper left (default), but can be anywhere 
on screen.


Test procedure:
Open WSJT-X
Ensure "Menus" is checked in the main window
Reposition the window
Relaunch WSJT-X (change configuration or Exit/Restart)
Window stays in position 

Uncheck “Menus"
Reposition the window
Relaunch WSJT-X (change configuration or Exit/Restart)
Window does NOT stay in position


MacOS 10.13 beta, RC2 8069

I had thought it might be a bad .plist or .ini file, but deleting and 
rebuilding those did not help.




George J Molnar, KF2T
Nevada, USA







--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Possible flaw - Window position not retained

[George J Molnar]

Thanks for checking, Bill - using the official build dmg.


George J Molnar
Nevada, USA







> On Sep 3, 2017, at 7:22 AM, Bill Somerville  wrote:
> 
> Hi George,
> 
> I am not able to reproduce that issue on my OS X 10.11.6 development system. 
> Are you using the officially release RC2 installer DMG or a self built 
> version?
> 
> Any other Mac users seeing this issue? If so please chip in with your o/s 
> version.
> 
> 73
> Bill
> G4WJS.
> 
> On 03/09/2017 14:54, George J Molnar wrote:
>> Right - that’s not happening with the main window. I can move it in one 
>> configuration, and upon return to that configuration, it its back at the 
>> default position. The fast graph “sticks” where I move it, though.
>> 
>> 
>> George J Molnar
>> Nevada, USA
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>> On Sep 3, 2017, at 6:51 AM, Bill Somerville >> <mailto:g4...@classdesign.com>> wrote:
>>> 
>>> On 03/09/2017 14:43, George J Molnar wrote:
>>>> The main window may be positioned anywhere on the screen, but returns to 
>>>> the top left when a different Configuration is changed. The waterfall/fast 
>>>> graph retains positioning, however.
>>> 
>>> Hi George,
>>> 
>>> the WSJT-X configurations each have a completely separate settings, 
>>> included in the saved settings are the window sizes and positions. This 
>>> means you can arrange things as you prefer for each configuration and 
>>> switching to that configuration will restore those last used settings.
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! 
> http://sdm.link/slashdot___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Possible flaw - Window position not retained

[George J Molnar]

Right - that’s not happening with the main window. I can move it in one 
configuration, and upon return to that configuration, it its back at the 
default position. The fast graph “sticks” where I move it, though.


George J Molnar
Nevada, USA







> On Sep 3, 2017, at 6:51 AM, Bill Somerville  wrote:
> 
> On 03/09/2017 14:43, George J Molnar wrote:
>> The main window may be positioned anywhere on the screen, but returns to the 
>> top left when a different Configuration is changed. The waterfall/fast graph 
>> retains positioning, however.
> 
> Hi George,
> 
> the WSJT-X configurations each have a completely separate settings, included 
> in the saved settings are the window sizes and positions. This means you can 
> arrange things as you prefer for each configuration and switching to that 
> configuration will restore those last used settings.
> 
> 73
> Bill
> G4WJS.
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Possible flaw - Window position not retained

[George J Molnar]

Running RC2 (8069) under MacOS 10.13 (beta).

The main window may be positioned anywhere on the screen, but returns to the 
top left when a different Configuration is changed. The waterfall/fast graph 
retains positioning, however.

Steps to Duplicate:
Launch WSJTX
Select a Configuration 
Move main window
Select a different Configuration
Return to original Configuration 

Tremendous work, guys. Easy to operate and GREAT performance. Sensitivity, CPU 
usage, and fun level ALL better!

73

George J Molnar
Nevada, USA







--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] GUI Suggestion

[George J Molnar]

Small suggested change in the GUI for the group’s consideration:

Move the WD Timer from the lower right corner to be in line with the spin boxes 
(RX, FTol, Report, T/R, etc as appropriate for mode) and make it into a spin 
box. The progress bar can remain as is.

This will allow operators to select how long they’re going to keep trying “on 
the fly” with greater accuracy.

Optionally, delete the “click anywhere to reset” function for the WD Timer.

Second option, which could be included in the main Preferences, is to make the 
WD either minutes OR sequences, depending on operator preference.


Opinions?


George J Molnar
Nevada, USA
KF2T  @GJMolnar





--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT on DXpedition

[George J Molnar]

Agree 100% with Ria.

FT8 in Contest Mode would be ideal for DXPeditions. Running split - of course! 
Nice thing is that a custom "CQ UP VQ9TC” meets the mode specification.


George J Molnar
Nevada, USA
KF2T  @GJMolnar





> On Aug 8, 2017, at 9:53 AM, Ria Jairam  wrote:
> 
> I think that the real appeal of FT8, apart from the weak signal
> capability is that it is a capable replacement for RTTY.
> 
> RTTY is a pain in the neck to use and provides increasingly
> diminishing returns. You can use less power on FT8 and get out better
> plus auto SEQ and prem. JT65 had the problem of 6 minutes per QSO
> which will only make angry ops worldwide if used on a DXpedition for
> anything except EME. Meanwhile 30 seconds for a QSO isn't too bad for
> FT8.
> 
> I'd probably suggest that major DXpeditions would be better off using
> a separate window instead of the regular window. This would help keep
> the QRM down.
> 
> Watching this with keen interest.
> 
> 73
> Ria, N2RJ
> 
> On Tue, Aug 8, 2017 at 12:44 PM, Bill Somerville  
> wrote:
>> On 08/08/2017 17:19, John Zantek wrote:
>>> 
>>> Rate is the number #1 concern as well as a few other issues.  A WSJT
>>> exchange from an expedition perspective is a fast exchange which hams are
>>> typically familiar with, such as CW and or RTTY modes.
>> 
>> 
>> Hi John,
>> 
>> just a quick initial reply, I will think more about this requirement and
>> reply more fully later.
>> 
>> My first comment is that perhaps rate expectations should be moderate and
>> the real benefit of weak signal modes like JT65/JT9/FT8 is their potential
>> to exploit band conditions unable to support CW/RTTY/Phone QSOs. Given that
>> then dedicating a position to weak signal modes when QSOs may be logged far
>> faster with CW/RTTY/Phone will not be popular. OTOH if a position is idle
>> due to no open band to run then that should be the cue to open up on the
>> weak signal modes on the least marginal available band.
>> 
>> It may be worth considering operating on a non-conventional frequency
>> (assuming one can be found) to try and avoid hoards of stations calling on
>> frequency, although stations calling on frequency can be easily ignored
>> (unlike on CW/RTTY/Phone) so maybe it's not a huge issue.
>> 
>> 73
>> Bill
>> G4WJS.
>> 
>> 
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Ver 1.8 RC1 audio in slider problem

[George J Molnar]

Mike, you're right. Previous experiences with “Flatten” had led me to not use 
it for a long time. Just tested using it, and it is much better than I recall, 
and quite satisfactory!

I respectfully withdraw my support for slider retention. 

PS - I do use the fast graph frequently, but can adjust without difficulty.

George J Molnar, KF2T 
Nevada, USA


> On Jul 19, 2017, at 10:20 AM, Black Michael via wsjt-devel 
>  wrote:
> 
> The "Flatten" option on the waterfall solves that problem too.
> But not for the fast graph.
> Are you using the fast graph or is there some reason not to use Flatten for 
> you?
> 
> de Mike W9MDB
>  
> 
> From: George J Molnar 
> To: WSJT software development  
> Sent: Wednesday, July 19, 2017 10:15 AM
> Subject: Re: [wsjt-devel] Ver 1.8 RC1 audio in slider problem
> 
> Vote for retention of the slider. Switching bands often calls for readjusting 
> the waterfall, and the slider is a convenient, easy to understand tool. 
> 
> I wouldn't mind moving it away from the thermometer, to clarify the proper 
> function. It isn't really difficult to grasp, though!
> 
> George J Molnar, KF2T 
> Nevada, USA
> 
> 
>> On Jul 19, 2017, at 8:49 AM, Dan Malcolm  wrote:
>> 
> 
> Mike, Bill,
> FWIW I’d like to keep the slider.  I like the idea of encouraging users to 
> read the manual.
>  
> From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
> Sent: Tuesday, July 18, 2017 10:37 PM
> To: WSJT software development 
> Cc: Black Michael 
> Subject: Re: [wsjt-devel] Ver 1.8 RC1 audio in slider problem
>  
> There were those that still wanted the waterfall adjustment for the fast 
> graph handy so leaving it as an option would be the only solution.
>  
> I submitted some tooltip changes a while ago to make it pretty much 
> in-your-face on the meter tooltip.
> Then we need to spice up the documentation so be more in-your-face too.  
> "Transceiver setup" as an index title is not intuitive but hopefully most 
> know how to use search for keywords.  I tried to see if you could put a 
> hyperlink in a tool tip but appears not.  Though about doing a ctrl-click on 
> the meter or such to bring up the relevant section in the manual then put the 
> ctrl-click info in the tooltip.
>  
> de Mike W9MDB
>  
> From: Bill Somerville 
> To: wsjt-devel@lists.sourceforge.net 
> Sent: Tuesday, July 18, 2017 5:54 PM
> Subject: Re: [wsjt-devel] Ver 1.8 RC1 audio in slider problem
>  
> On 18/07/2017 23:32, Black Michael via wsjt-devel wrote:
> I'd say the vast majority have no use for the slider anymore.
> So let's hide it by default and have an enable checkbox in the config.
>  
> I'll do that patch if you think that's acceptable...we'll still end up with 
> "what happened to..." but se la vie... 
> Hi Mike,
> if you are going to do a patch then remove the slider altogether, that is 
> probably the best option. It is of limited value and will always be 
> misunderstood by many who don't understand the underlying realities of 
> digital samples. Unfortunately the result may well be that those who miss the 
> slider will revert to using the operating system sliders which are 
> effectively the same thing and equally pointless (even harmful at extreme 
> settings) as the WSJT-X slider.
>  
> 73
> Bill
> G4WJS.
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>  
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 
> 
> --
> Check out the vibrant tech community on one of the