Re: [wsjt-devel] Unable to find how to reset Q65A default Tx duration (defaults to 30 sec and my operating requires 60 seconds)
Rex and everyone: My apologies for the extra email bandwidth. I just (re-) joined the WSJT-X Development list today. I’m aware (now) it’s previously reported and being handled.. Thank you everyone! 73, Dave From: Rex Moncur via wsjt-devel Reply-To: WSJT software development Date: Sunday, January 8, 2023 at 3:00 PM To: 'WSJT software development' Cc: Rex Moncur Subject: Re: [wsjt-devel] Unable to find how to reset Q65A default Tx duration (defaults to 30 sec and my operating requires 60 seconds) Hi Dave The answer to your first question is in a number of emails from Joe to the group and copied below: 73 Rex VK7MO Hi Bill, Barry, and others, On 1/7/2023 9:36 PM, Kurious George KB2SA via Moon-net wrote: > I see folks reporting that 2.6.0 no longer supports Q65-30B? Sorry about the missing T/R period control in WSJT-X 2.6.0. This was completely unintentional. The problem had been recognized and corrected, but the corrected code was inadvertently not moved into the master code branch. A bug-fix release will be made very soon. In the meantime, a simple workaround is to open the file WSJT-X.ini with a text editor (such as Notepad) search for any lines that contain "TRPeriod_Q65", and change the number to whatever you need. For example, for one-minute T/R sequences you will want the line TRPeriod_Q65=60 You may find more than one instance of TRPeriod_Q65. Change them all! File WSJT-X.ini is in the Log directory, which can be accessed directly from the WSJT-X File menu. -- 73, Joe, K1JT From: David Schmocker via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: Monday, 9 January 2023 7:46 AM To: WSJT software development Cc: David Schmocker Subject: Re: [wsjt-devel] Unable to find how to reset Q65A default Tx duration (defaults to 30 sec and my operating requires 60 seconds) 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 From: David Schmocker via wsjt-devel Reply-To: WSJT software development Date: Sunday, January 8, 2023 at 2:33 PM To: Cc: David Schmocker Subject: [wsjt-devel] Unable to find how to reset Q65A default Tx duration (defaults to 30 sec and my operating requires 60 seconds) Hello, Please advise where/how specifically do I change the Tx interval (duration) for Q65A. The default is currently 30 second period and my requirement needs 60 second default (Q65-60A for 6m EME) (in past versions this was settable from main screen and held there despite WSJT-X program restart). Operating platform: Mac OS Mojave v10.14.6, Mac mini, 16GB 1600 MHz DDR3 RAM Installed software version: WSJT-X v2.6.0 b7a9ef Improved (Previously tried the regular version (not Improved), and the AL_Improved with all three of these versions testing the same in this regard (unable to move away from 30 second period for Q65). Very grateful for all the team is doing and has done. Thank you, very 73, Dave KJ9I ___ 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] Unable to find how to reset Q65A default Tx duration (defaults to 30 sec and my operating requires 60 seconds)
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 From: David Schmocker via wsjt-devel Reply-To: WSJT software development Date: Sunday, January 8, 2023 at 2:33 PM To: Cc: David Schmocker Subject: [wsjt-devel] Unable to find how to reset Q65A default Tx duration (defaults to 30 sec and my operating requires 60 seconds) Hello, Please advise where/how specifically do I change the Tx interval (duration) for Q65A. The default is currently 30 second period and my requirement needs 60 second default (Q65-60A for 6m EME) (in past versions this was settable from main screen and held there despite WSJT-X program restart). Operating platform: Mac OS Mojave v10.14.6, Mac mini, 16GB 1600 MHz DDR3 RAM Installed software version: WSJT-X v2.6.0 b7a9ef Improved (Previously tried the regular version (not Improved), and the AL_Improved with all three of these versions testing the same in this regard (unable to move away from 30 second period for Q65). Very grateful for all the team is doing and has done. Thank you, very 73, Dave KJ9I ___ 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] Unable to find how to reset Q65A default Tx duration (defaults to 30 sec and my operating requires 60 seconds)
Hello, Please advise where/how specifically do I change the Tx interval (duration) for Q65A. The default is currently 30 second period and my requirement needs 60 second default (Q65-60A for 6m EME) (in past versions this was settable from main screen and held there despite WSJT-X program restart). Operating platform: Mac OS Mojave v10.14.6, Mac mini, 16GB 1600 MHz DDR3 RAM Installed software version: WSJT-X v2.6.0 b7a9ef Improved (Previously tried the regular version (not Improved), and the AL_Improved with all three of these versions testing the same in this regard (unable to move away from 30 second period for Q65). Very grateful for all the team is doing and has done. Thank you, very 73, Dave KJ9I ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Q65_Sync only goes to 1kHz on Mac OS 10.14.6
GE Gents: WSJT-X v2.4.0 rc4, Mac OS 10.14.6. Q65_Sync still only displays orange ‘grass’ from 0 Hz up to 1000Hz (not full 3500Hz bandwidth of radio and display). Thank you for all you’re doing. Very 73, Dave KJ9I ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Elecraft K3
GM Mike: I can test K3S if helpful. Please provide the specific use-case/instructions for Mac OS 10.14.6 If it’s any mode other than Q65 or JT-65, I’ll need the settings used also Very 73 Dave KJ9I Just a question: Why select “Fake-It” with K3S? I was advised to use “Rig” and it works well. From: Black Michael via wsjt-devel Reply-To: Black Michael , WSJT software development Date: Monday, March 22, 2021 at 2:25 PM To: WSJT Software Development Cc: Black Michael Subject: [wsjt-devel] Elecraft K3 Anybody out there with an Elecraft K3 or K3S willing do some testing for hamlib? I have a report that Fake It does not work correctly on the K3/K3S so would like to see some debug from other users to determine if this is a rig problem or an Elecraft problem. The behavior in Fake It is that the VFO will start walking up or down if the transmit offset frequency is different. Rig Split seems to work OK. Mike W9MDB ___ 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] Q65_Sync truncates at 1,000Hz
Joe: OK thank you so much; I appreciate that. Very 73, Dave On 3/20/21, 1:45 PM, "Joe Taylor" wrote: Hi Dave, On 3/20/2021 2:01 PM, David Schmocker KJ9I wrote: > This seems maybe a bug?On my WSJT-X, the Q65_Sync only gets up to > 1,000 Hz. Unable to attach screenshot (even compressed) due to > email reflector attachment size limits; could email to anyone directly > off-list.. > > Changing Bins/Pixel does not fix this (it stays capped at 1,000Hz). > > This is on Mac OS 10.14.6 Mojave. WSJT-X v2.4.0rc3 computer is Intel > 3GHz Intel Core i7, 16GB of 1600 MHz DDR3 RAM. Graphics Intel Iris > 1536 MB (Mac Mini). > > I am running this from a mode-specific WSJT-X Config named Q65 EME K3S > > Thank you for any help/ideas on how to resolve this. We believe this problem has already been fixed in WSJT-X 2.4.0-rc4, which will be released soon. Please upgrade to RC4 when it's made available, and report back if you still have a problem. -- 73, Joe, K1JT ___ 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] Q65_Sync truncates at 1,000Hz
Hello, This seems maybe a bug?On my WSJT-X, the Q65_Sync only gets up to 1,000 Hz. Unable to attach screenshot (even compressed) due to email reflector attachment size limits; could email to anyone directly off-list.. Changing Bins/Pixel does not fix this (it stays capped at 1,000Hz). This is on Mac OS 10.14.6 Mojave. WSJT-X v2.4.0rc3 computer is Intel 3GHz Intel Core i7, 16GB of 1600 MHz DDR3 RAM. Graphics Intel Iris 1536 MB (Mac Mini). I am running this from a mode-specific WSJT-X Config named Q65 EME K3S Thank you for any help/ideas on how to resolve this. Very 73, Dave KJ9I ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Feature request: Rx level input slider
Mike: Thank you for settings cross-check (current settings): Others have proposed reducing RF level (need to adjust AF level to preserve EME system noise figure) K3S entryValuecomments AF GAINLOreduces output level by about 10dB vs. HI setting AF LIMNOR 030don’t want AGC limiting levels for optimal EME decoding LIN OUT=PHONESNOR 000 gives 0dB while NOR 001 saturates WSJT-X at +78dB With LIN OUT set to =PHONES, I can use the radio K3S AF control to somewhat control the audio out level via the USB port, but it’s super sensitive. A 10-Turn trimmer AF control would be required to set it properly. The audio output abruptly jumps from zero to too hot when using the radio’s AF (volume) control. Also I’ve checked the computer MIDI settings (already at minimum). I have searched for WSJT-X audio settings and K3S on internet (N5XLHamRadio.blogspot.com has one good post but it must have referenced an older WSJT-X version that had Rx input slider). I’ll keep researching settings and welcome an email off-list from anyone who finds alternate solution on this to kj9idave (at) charter ( d ot) net Absent an Rx input level slider-control, I believe I just need to live with/accept the the 57dB level currently showing (no signals) on WSJT-X with Ref Spectrum measured viewing Cold Sky North. thank you Very 73, Dave KJ9I From: Black Michael via wsjt-devel Reply-To: Black Michael , WSJT software development Date: Monday, March 15, 2021 at 12:01 AM To: WSJT software development Cc: Black Michael Subject: Re: [wsjt-devel] Feature request: Rx level input slider Have you tried this setting? Seesms reducing this should work. LIN OUT NOR 010 Sets the LINE OUT level. LINE OUT connections go to PC soundcard inputs. Settings above 10 may result in overdrive of the soundcard or saturation of the KIO3’s isolation transformers; monitor signals using the PC to avoid this. Note: Normally, LIN OUT sets a fixed-level receive-only output for main/sub (L/R), compatible with digitalmodes. Tapping 1 switches LINOUT to =PHONES, where the line outputs match headphone audio, audio level is controlled by AF/SUB gain controls, and both RX andTX audio are available. Mike W9MDB On Sunday, March 14, 2021, 11:31:56 AM CDT, David Schmocker wrote: Dear WSJT-X development team: Feature request: Could we eliminate the Tx Power slider (lower right of main screen) and replace it with an Rx input level slider (far lower left of screen immediately adjacent to the Rx dB level) to allow attenuation of input Rx signal please? More detail/context: Elecraft K3S radio with WSJT-X users who use the USB-to-K3S radio interface can only reduce the input volume so far (typically maintains 60dB WSJT-X level on the Rx dB level indicator). Further reducing the audio output of the K3S drops the Signal to the point we see ‘jail bars’ (internal noise). To enable setting K3S output to WSJT-X recommended 30dB, the above Rx level slider would help. Tx slider seems unnecessary because every radio (correct me if wrong) allows a Tx or drive level reduction on the radio itself). Very 73, Dave KJ9I ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X feature request: JT-65A (1270Hz) and Q65 (1500Hz) defaults
Bill: OK.. will do this (I already have a unique config for some modes). Thank you! 73, Dave From: Bill Somerville Reply-To: WSJT software development Date: Sunday, March 14, 2021 at 11:37 AM To: Subject: Re: [wsjt-devel] WSJT-X feature request: JT-65A (1270Hz) and Q65 (1500Hz) defaults On 14/03/2021 16:30, David Schmocker wrote: Dear WSJT development team: Would it be possible (easy) to establish default Tx and Rx frequencies per mode: JT-65A (Tx 1270 Hz and Rx 1270Hz) any time JT-65 mode is selected and Q65 (Tx 1,500 Hz and Rx 1500 Hz)? I realize these can be manually changed (what I do currently), but when I am coaching a new user in another country who has limited time also, having the mode-specific frequency defaults would be one less problem to overcome across language barriers and time constraints. Just a friendly suggestion.. thank you.. Very 73, Dave KJ9I Hi Dave, both of those modes have multi-signal decoders in WSJT-X and are likely to be used when more than one signal is in the rig's passband. Given that default audio offsets do not have much meaning. I would recommend setting up separate configurations for each mode used, that will recall the last used Tx and Rx offsets when switching to each configuration. 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 feature request: JT-65A (1270Hz) and Q65 (1500Hz) defaults
Dear WSJT development team: Would it be possible (easy) to establish default Tx and Rx frequencies per mode: JT-65A (Tx 1270 Hz and Rx 1270Hz) any time JT-65 mode is selected and Q65 (Tx 1,500 Hz and Rx 1500 Hz)? I realize these can be manually changed (what I do currently), but when I am coaching a new user in another country who has limited time also, having the mode-specific frequency defaults would be one less problem to overcome across language barriers and time constraints. Just a friendly suggestion.. thank you.. Very 73, Dave KJ9I ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Feature request: Rx level input slider
Dear WSJT-X development team: Feature request: Could we eliminate the Tx Power slider (lower right of main screen) and replace it with an Rx input level slider (far lower left of screen immediately adjacent to the Rx dB level) to allow attenuation of input Rx signal please? More detail/context: Elecraft K3S radio with WSJT-X users who use the USB-to-K3S radio interface can only reduce the input volume so far (typically maintains 60dB WSJT-X level on the Rx dB level indicator). Further reducing the audio output of the K3S drops the Signal to the point we see ‘jail bars’ (internal noise). To enable setting K3S output to WSJT-X recommended 30dB, the above Rx level slider would help. Tx slider seems unnecessary because every radio (correct me if wrong) allows a Tx or drive level reduction on the radio itself). Very 73, Dave KJ9I ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] RC2 Report on MacOS 10.14.6 Mojave - Q65_Sync
John: Please send your telephone number to me at kj9idave. (at). Charter. [dot]. Net. . Let’s try a phone call. Very 73, Dave From: John Stengrevics Reply-To: WSJT software development Date: Saturday, March 6, 2021 at 10:24 AM To: WSJT software development Subject: Re: [wsjt-devel] RC2 Report on MacOS 10.14.6 Mojave - Q65_Sync Hi Dave, I followed your instructions, but ~/Library/Preferences/ is not there. Neither is there a folder for WSJT. And if I search “Library” for ~/Library/Preferences/, nothing comes up. John WA1EAZ On Mar 6, 2021, at 11:10 AM, David Schmocker wrote: Hi John: In order to show that folder, Open Mac finder Hold down the “Alt (Option)” key (lower left of keyboard). Navigate with mouse to the Go pull-down menu Select (left-click) library from that list.. Think now you can see those previously hidden files. ? 73 Dave KJ9I From: John Stengrevics Reply-To: WSJT software development Date: Saturday, March 6, 2021 at 10:05 AM To: Steven Franke Cc: WSJT software development Subject: Re: [wsjt-devel] RC2 Report on MacOS 10.14.6 Mojave - Q65_Sync Steve, I understand, but I can’t find the ~/Library/Preferences/ folder. If I search my Mac for it, nothing comes up but “WSJT User Guide.” I don’t see it anywhere. Sorry to be so clueless here. John WA1EAZ On Mar 6, 2021, at 10:54 AM, Steven Franke wrote: John, The file that Bill sent to you should be placed in the ~/Library/Preferences folder. This is the folder that your existing WSJT-X.ini file is located in. You should be able to open the ~/Library/Preferences folder and simply grab the attachment that Bill sent and drag it into that folder. When you are done you should see both WSJT-X.ini and wsjtx_log_config.ini next to (or near) each other in the list of files in that folder. ut User Guide.73 Steve k9an On Mar 6, 2021, at 9:43 AM, John Stengrevics wrote: Hi Steve, Thanks for that. I have followed your suggestions. However, I don’t see ~/Library/Preferences/ under WSJT. (Bill had asked me to move a file that he sent (wsjt_log_config.ini) there for debugging purposes.) Maybe move it to WSJT INI? 73, John WA1EAZ On Mar 6, 2021, at 10:27 AM, Steven Franke via wsjt-devel wrote: John, You can make the ~/Library folder visible in Finder with the following steps: 1. Open a Finder window. 2. Select your home directory in the left panel of the Finder window. 3. Select Show View Options under the “View” menu. 4. Check the “Show Library Folder” box. Thereafter, your Library folder will always be visible. 73 Steve k9an On Mar 6, 2021, at 8:36 AM, John Stengrevics wrote: Hi Bill, I can’t find the ~/Library/Preferences/ directory in which to put the file. Can you provide a bit more detail on how I can locate it? Sorry. John WA1EAZ On Mar 6, 2021, at 9:20 AM, Bill Somerville wrote: Hi John, so I can see what is happening put the attached file into the WSJT-X configuration files directory (~/Library/Preferences/ on macOS), restart WSJT-X, run a minimal test to demonstrate the issue, then quit WSJT-X (do not turn off the rig until WSJT-X has exited). There will be a new file on your Desktop called WSJT-X_RigControl.log, send me that file for analysis please (g4wjs classdesign com)? Once you have sent me the log file delete the wsjtx_log_config.ini and WSJT-X_RigControl.log files to resume normal operation. 73 Bill G4WJS. On 06/03/2021 14:13, John Stengrevics wrote: Bill, I have CAT selected and it does connect when I click on Test. John (G4KLA) had asked what driver I was using. I replied that the driver had not changed. It has always been /dev/cu.usbserial-A503XYAO. John WA1EAZ On Mar 6, 2021, at 9:07 AM, Bill Somerville wrote: Hi John, which option do you have checked for "Preferences->Radio->PTT Method"? 73 Bill G4WJS. On 06/03/2021 14:03, John Stengrevics wrote: Hi Bill, I just tried to use Q65 with “Cumulative" selected as you suggested. However, the problem is still there as described below. I have to shut down my transceiver (Elecraft K3S) to get it to stop transmitting. Thanks, John WA1EAZ On Mar 6, 2021, at 8:44 AM, Bill Somerville wrote: Hi John, I am not sure as I have not investigated this issue yet. It is easy enough to check, select "Cumulative" for the 2D spectrum display, restart WSJT-X, and see if the iusse goes away. 73 Bill G4WJS. On 06/03/2021 13:25, John Stengrevics wrote: Hi Bill, Will this fix solve the problem I reported yesterday with OS Big Sur? I’ll repost below in case you didn’t see it. Thanks, John WA1EAZ Repost - some additions in red: John & Joe, I had been using the previous version successfully on a MacBook Pro (Intel not M1) OS Big Sur 11.2.2. Today, I downlo
[wsjt-devel] "PTT hangs" on Mac OS 10.14.6
Everyone I just tested mode JT65 and the “PTT hang” issue (new to 2.4.0rc2) affects JT65 also. My test data shows this issue is not Q65-specific. Very 73, if there’s testing helpful to isolate root cause, I volunteer. Dave KJ9I ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] RC2 Report on MacOS 10.14.6 Mojave - Q65_Sync
On Mar 6, 2021, at 5:55 AM, Bill Somerville wrote: Hi Dave and Kevin, we have finally tracked down the cause of this crash, thanks for your patience it was not so easy to track down. It is repaired for the next release, for now if you do not use of the Q65_Sync Wide Graph synchronization plot the crash will be avoided. Note this is not a Mac specific issue although it does seem to have the most severe effects on that platform. 73 Bill G4WJS. On 06/03/2021 03:59, David Schmocker wrote: Hello all, A second report that mirrors this one:WSJT-X 2.4.0rc2 OS 10.14.6, Mac Mini Mode Q65,Waterfall Q65_ Sync selected and slow to let go of PTT line to K3S radio (even after Tx period). (when I go into Radio Panel, the Test PTT Red bar stays on, won't easily release). Then when a decode should take place, I get a crash exactly as Kevin reported with the same exact message as reported below. Thank you, 73, Dave KJ9I On 3/5/21, 8:47 PM, "Kevin McQuiggin" wrote: Hi All: I tried submitting this earlier today, but it didn’t seem to make to the list. Hence, a re-submission: Just trying out RC2 on an iMac, MacOS version 10.14.6 Mojave. Selection of “Q65_Sync” from dropdown box on the wide graph causes a crash as soon as the application starts to TX. Selection of “Cumulative” (the default) and TX/RX are normal. Specific exception was "EXC_BAD_ACCESS (SIGSEGV)”. I have saved the crash dump and can provide as necessary. 73, Kevin VE7ZD ___ 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 ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] RC2 Report on MacOS 10.14.6 Mojave - Q65_Sync
Good morning everyone OS 10.14.6 here (Intel ).. I saw in 2.4.0rc2 installation instructions we must uninstall then reinstall the drivers to the radio. For my application, this is the USB-CODEC inside the K3S radio.. I am currently trying to figure out how to uninstall then reinstall this driver Hoping it fixes the (hang-on PTT) issue I also have 73, Dave From: John Stengrevics Reply-To: WSJT software development Date: Saturday, March 6, 2021 at 8:15 AM To: WSJT software development Subject: Re: [wsjt-devel] RC2 Report on MacOS 10.14.6 Mojave - Q65_Sync Bill, I have CAT selected and it does connect when I click on Test. John (G4KLA) had asked what driver I was using. I replied that the driver had not changed. It has always been /dev/cu.usbserial-A503XYAO. John WA1EAZ On Mar 6, 2021, at 9:07 AM, Bill Somerville wrote: Hi John, which option do you have checked for "Preferences->Radio->PTT Method"? 73 Bill G4WJS. On 06/03/2021 14:03, John Stengrevics wrote: Hi Bill, I just tried to use Q65 with “Cumulative" selected as you suggested. However, the problem is still there as described below. I have to shut down my transceiver (Elecraft K3S) to get it to stop transmitting. Thanks, John WA1EAZ On Mar 6, 2021, at 8:44 AM, Bill Somerville wrote: Hi John, I am not sure as I have not investigated this issue yet. It is easy enough to check, select "Cumulative" for the 2D spectrum display, restart WSJT-X, and see if the iusse goes away. 73 Bill G4WJS. On 06/03/2021 13:25, John Stengrevics wrote: Hi Bill, Will this fix solve the problem I reported yesterday with OS Big Sur? I’ll repost below in case you didn’t see it. Thanks, John WA1EAZ Repost - some additions in red: John & Joe, I had been using the previous version successfully on a MacBook Pro (Intel not M1) OS Big Sur 11.2.2. Today, I downloaded Mac version 2.4.0-rc2. When running Q65, T/R = 30 seconds, Submode A, the program continues to transmit after the 30 second period is complete for 60 seconds total. However, it does not seem to drive my amplifier after 30 seconds. [PTT is activated for the second 30 seconds, but no audio to drive the amp.] I have since tried FT8 on WSJT-X and can confirm that it works as usual. Thus, the problem seems to be isolated to Q65. I did follow the instructions in the Readme file. If there is a file I can send you, please let me know. I would appreciate any suggestions you can provide. Best 73, John WA1EAZ On Mar 6, 2021, at 5:55 AM, Bill Somerville wrote: Hi Dave and Kevin, we have finally tracked down the cause of this crash, thanks for your patience it was not so easy to track down. It is repaired for the next release, for now if you do not use of the Q65_Sync Wide Graph synchronization plot the crash will be avoided. Note this is not a Mac specific issue although it does seem to have the most severe effects on that platform. 73 Bill G4WJS. On 06/03/2021 03:59, David Schmocker wrote: Hello all, A second report that mirrors this one:WSJT-X 2.4.0rc2 OS 10.14.6, Mac Mini Mode Q65,Waterfall Q65_ Sync selected and slow to let go of PTT line to K3S radio (even after Tx period). (when I go into Radio Panel, the Test PTT Red bar stays on, won't easily release). Then when a decode should take place, I get a crash exactly as Kevin reported with the same exact message as reported below. Thank you, 73, Dave KJ9I On 3/5/21, 8:47 PM, "Kevin McQuiggin" wrote: Hi All: I tried submitting this earlier today, but it didn’t seem to make to the list. Hence, a re-submission: Just trying out RC2 on an iMac, MacOS version 10.14.6 Mojave. Selection of “Q65_Sync” from dropdown box on the wide graph causes a crash as soon as the application starts to TX. Selection of “Cumulative” (the default) and TX/RX are normal. Specific exception was "EXC_BAD_ACCESS (SIGSEGV)”. I have saved the crash dump and can provide as necessary. 73, Kevin VE7ZD ___ 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] RC2 Report on MacOS 10.14.6 Mojave - Q65_Sync
Hello all, A second report that mirrors this one:WSJT-X 2.4.0rc2 OS 10.14.6, Mac Mini Mode Q65,Waterfall Q65_ Sync selected and slow to let go of PTT line to K3S radio (even after Tx period). (when I go into Radio Panel, the Test PTT Red bar stays on, won't easily release). Then when a decode should take place, I get a crash exactly as Kevin reported with the same exact message as reported below. Thank you, 73, Dave KJ9I On 3/5/21, 8:47 PM, "Kevin McQuiggin" wrote: Hi All: I tried submitting this earlier today, but it didn’t seem to make to the list. Hence, a re-submission: Just trying out RC2 on an iMac, MacOS version 10.14.6 Mojave. Selection of “Q65_Sync” from dropdown box on the wide graph causes a crash as soon as the application starts to TX. Selection of “Cumulative” (the default) and TX/RX are normal. Specific exception was "EXC_BAD_ACCESS (SIGSEGV)”. I have saved the crash dump and can provide as necessary. 73, Kevin VE7ZD ___ 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] Possibly another clue (terminal window text leading up to Segmentation fault: 11)
George: Thank you; Sometimes (after only step 1) it runs fine for a while. But I have let it in “monitor” mode and it sometimes keeps running. However to use the program requires changing settings (the Decode pull-down menu defaults arrive unoptimized) and so it’s not as simple as start it and let it run. Also in order to get maximum sensitivity (I am an EME user), this requires adding the callsign of Target station into “To Radio” field. Sometimes these above routine operational actions result in crash. Dave From: George J Molnar Reply-To: WSJT software development Date: Sunday, February 28, 2021 at 10:35 AM To: WSJT software development Cc: John Nelson Subject: Re: [wsjt-devel] Possibly another clue (terminal window text leading up to Segmentation fault: 11) 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 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] Possibly another clue (terminal window text leading up to Segmentation fault: 11)
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 https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Possible clues to OS 10.14.6. crash?
When trying to retrieve Log File, I first opened WSJT-X using Terminal window. /Applications/wsjtx.app/Contents/MacOS/wsjtx Next I did File-Open from pulldown menu.. this succeeds but yields some interesting interim messages (maybe clues to why I am crashing often)? Then this in the terminal window which was used to launch WSJT-X. 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. Hoping maybe somewhere in here is something useful? Very 73, thank you for all of your work and help. Dave KJ9I ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Crash during QSO
Hi Neil Sure.. What do you prefer Word.doc or .txt file or ?? From: Neil Zampella Reply-To: WSJT software development Date: Sunday, February 28, 2021 at 7:41 AM To: Subject: Re: [wsjt-devel] Crash during QSO David, is it possible to send this as an attachment, rather than a 'cut and paste' into an email? Thanks, Neil, KN3ILZ On 2/28/2021 7:23 AM, David Schmocker wrote: Sending JA7QVI KJ9I R-24. Awaiting RRRSH message (crash at start of Tx minute).. ___ 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] What is path of Refspec.dat on Mac OS 10.14.6 please?
Everyone: Where is the Refspec.dat stored on Mac OS Mojave please ? Please advise: thank you ! Very 73, Dave KJ9I ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X v2.4.0rc1 crashes on OS 10.14.6
John: Great; thank you: Today the action that caused crash was (in Q65-60A mode), EME Configuration, changed radio freq. from 50.188 to 50.190 with radio connected to computer (WSJT-X Unexpected close details attached). Please advise if other detail is helpful. Process: wsjtx [2348] Path: /Applications/wsjtx.app/Contents/MacOS/wsjtx Identifier:org.k1jt.wsjtx Version: v2.4.0 (2.4.0) Code Type: X86-64 (Native) Parent Process:bash [610] Responsible: wsjtx [2348] User ID: 501 Date/Time: 2021-02-28 05:39:31.910 -0600 OS Version:Mac OS X 10.14.6 (18G8022) Report Version:12 Anonymous UUID:1E2D07E1-9532-235B-3F34-D0F5B383F64D Time Awake Since Boot: 41000 seconds System Integrity Protection: enabled Crashed Thread:0 Dispatch queue: com.apple.main-thread Exception Type:EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00720232 Exception Note:EXC_CORPSE_NOTIFY Termination Signal:Segmentation fault: 11 Termination Reason:Namespace SIGNAL, Code 0xb Terminating Process: exc handler [2348] VM Regions Near 0x720232: MALLOC_LARGE 00014860c000-00014868c000 [ 512K] rw-/rwx SM=PRV --> STACK GUARD76aea000-76aeb000 [4K] ---/rwx SM=NUL stack guard for thread 8 Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 org.qt-project.QtCore 0x00012bb8b3ee QMutex::lock() + 14 1 org.qt-project.QtCore 0x00012bc452fe QRegularExpressionPrivate::compilePattern() + 30 2 org.qt-project.QtCore 0x00012bc46a49 QRegularExpression::match(QString const&, int, QRegularExpression::MatchType, QFlags) const + 41 3 org.k1jt.wsjtx 0x00010f1c0536 MainWindow::stdCall(QString const&) + 54 4 org.k1jt.wsjtx 0x00010f20964b MainWindow::genCQMsg() + 619 5 org.k1jt.wsjtx 0x00010f1b81bd MainWindow::handle_transceiver_update(Transceiver::TransceiverState const&) + 445 6 org.qt-project.QtCore 0x00012bd93f95 void doActivate(QObject*, int, void**) + 1157 7 org.k1jt.wsjtx 0x00010f228df5 Configuration::impl::handle_transceiver_update(Transceiver::TransceiverState const&, unsigned int) + 1157 8 org.qt-project.QtCore 0x00012bd8bb9f QObject::event(QEvent*) + 943 9 org.qt-project.QtWidgets0x00012ac25e9a QWidget::event(QEvent*) + 4698 10 org.qt-project.QtWidgets0x00012abea9ea QApplicationPrivate::notify_helper(QObject*, QEvent*) + 266 11 org.qt-project.QtWidgets0x00012abebe11 QApplication::notify(QObject*, QEvent*) + 497 12 org.k1jt.wsjtx 0x00010f268226 ExceptionCatchingApplication::notify(QObject*, QEvent*) + 22 13 org.qt-project.QtCore 0x00012bd60a34 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 212 14 org.qt-project.QtCore 0x00012bd61d79 QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 809 15 libqcocoa.dylib 0x00012e820259 QCocoaEventDispatcherPrivate::processPostedEvents() + 313 16 libqcocoa.dylib 0x00012e8209c8 QCocoaEventDispatcherPrivate::postedEventsSourceCallback(void*) + 40 17 com.apple.CoreFoundation0x7fff484ccd13 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17 18 com.apple.CoreFoundation0x7fff484cccb9 __CFRunLoopDoSource0 + 108 19 com.apple.CoreFoundation0x7fff484b05af __CFRunLoopDoSources0 + 195 20 com.apple.CoreFoundation0x7fff484afb79 __CFRunLoopRun + 1189 21 com.apple.CoreFoundation0x7fff484af482 CFRunLoopRunSpecific + 455 22 com.apple.HIToolbox 0x7fff4770e1ab RunCurrentEventLoopInMode + 292 23 com.apple.HIToolbox 0x7fff4770dee5 ReceiveNextEventCommon + 603 24 com.apple.HIToolbox 0x7fff4770dc76 _BlockUntilNextEventMatchingListInModeWithFilter + 64 25 com.apple.AppKit0x7fff45aa577d _DPSNextEvent + 1135 26 com.apple.AppKit0x7fff45aa446b -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361 27 com.apple.AppKit0x7fff45a9e588 -[NSApplication run] + 699 28 libqcocoa.dylib 0x00012e81f62f QCocoaEventDispatcher::processEvents(QFlags) + 2495 29 org.qt-project.QtCore 0x00012bd5cacf QEventLoop::exec(QFlags) + 431 30 org.qt-project.QtCore 0x00012bd61042 QCoreApplication::exec() + 130 31 org.k1jt.wsjtx 0x00010f264ec7 main + 10551 32 libdyld.dylib 0x7fff744943d5
[wsjt-devel] WSJT-X v2.4.0rc1 crashes on OS 10.14.6
Hi Bill: Have you been able to find root cause of the crashes of WSJT-X in rc1 please? Just about any operation I do, crashes about 50% of the time with same result: Last login: Sat Feb 27 13:22:02 on ttys000 Davids-Mac-mini:~ davidschmocker$ /Applications/wsjtx.app/Contents/MacOS/wsjtx Segmentation fault: 11 Davids-Mac-mini:~ davidschmocker$ /Applications/wsjtx.app/Contents/MacOS/wsjtx Segmentation fault: 11 Davids-Mac-mini:~ davidschmocker$ /Applications/wsjtx.app/Contents/MacOS/wsjtx Segmentation fault: 11 Davids-Mac-mini:~ davidschmocker$ /Applications/wsjtx.app/Contents/MacOS/wsjtx Segmentation fault: 11 Davids-Mac-mini:~ davidschmocker$ /Applications/wsjtx.app/Contents/MacOS/wsjtx Segmentation fault: 11 Davids-Mac-mini:~ davidschmocker$ /Applications/wsjtx.app/Contents/MacOS/wsjtx Segmentation fault: 11 Davids-Mac-mini:~ davidschmocker$ /Applications/wsjtx.app/Contents/MacOS/wsjtx Segmentation fault: 11 Davids-Mac-mini:~ davidschmocker$ /Applications/wsjtx.app/Contents/MacOS/wsjtx Operations that cause WSJT-X to crash: Turn the VFO knob on my connected Elecraft K3S, or Go into Preferences, Audio tab, change one setting.. the moment I hit “OK”. (crash). If you need more data, I can supply it. Please advise (maybe this issue has already been fixed for rc2 ? I saw someone else report they had crashes of their WSJT-X in Windows.. don’t know if cause is the same?? Thank you. 73, please let me know if more data would help! Dave KJ9I ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Waterfall WSJT v10 vs. WSJT-X
Everyone Waterfall bake-off: WSJT v10 vs. WSJT-X : WSJT v10. Nice waterfall with great detail. Six months ago, I would have joined the suggestion to “keep the old WSJT v10 waterfall” Why I currently favor WSJT-X waterfall: The precise frequency (DF) of target weak EME signal is usually not known until 1st visible waterfall trace appears. WSJT-X sometimes (with aggressive settings) decodes JT-65A and/or Q65-60A signals that are barely or invisible on the waterfall. (WSJT v10 would only decode when I could detect some faint paint-splashes on the waterfall). I realize the Waterfall gain, sensitivity, zero, etc. settings have everything to do with when signal is visible vs. when it decodes. WSJT-X has the new Q65_Sync (fish-finder) (bottom of waterfall) that helps locate signals barely visible to the eye. This is incredibly valuable because oft-times when running a sked with a new DX station, his DF (radio frequency) remains unknown relative to mine (Doppler shift and all else factored in). Scratching, scraping, digging for every 0.1dB more to bring that SNR to something usable is primary goal on 6m EME. I still use my old legacy JT-65A receive computers (one on Windows XP, another on Fedora core 30, and a third on Debian 10) but soon (with Q65), the XP PC will become officially obsolete (the hardware is insufficient to support current software) and the others will be changed from WSJT v11 to WSJT-X v2.4.0. Also, WSJT-X decodes multiple signals within the passband so WSJT-X replaces both WSJT v10 and MAP65 in a single software package. 73, Dave KJ9I ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X self-closing on OS 10.14.6 (v2.4.0 RC1)
Bill, Thank you so much. You guys are great.. and WE REALLY appreciate all the hard work going on by you and all of the development team! Very 73, Dave KJ9I From: Bill Somerville Reply-To: WSJT software development Date: Thursday, February 18, 2021 at 7:35 AM To: Subject: Re: [wsjt-devel] WSJT-X self-closing on OS 10.14.6 (v2.4.0 RC1) On 17/02/2021 20:12, David Schmocker wrote: Everyone: Running WSJT-X from the terminal window, it runs fine in Q65 mode, however I set mode to Q65-60A, and then I clear TO RADIO field (by putting mouse in this field then hitting delete to erase JA station in there from before”. Next I type in ‘N0TB’ (who was calling CQ but not decoding at the time). As soon as I type N0TB into TO RADIO then tab out of the field, the program closes. Here are details: Hi Dave, thanks for the issue report, I am investigating. 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] Running WSJT-X v2.4.0rc1 from terminal window on OS 10.14.6 Mojave Mac mini
Hi Bill: It seems you are always working (never sleeping)! Thank you for your help. Here’s permissions view you requested: From: Bill Somerville Reply-To: WSJT software development Date: Wednesday, February 17, 2021 at 4:17 AM To: Subject: Re: [wsjt-devel] Running WSJT-X v2.4.0rc1 from terminal window on OS 10.14.6 Mojave Mac mini On 17/02/2021 01:57, David Schmocker wrote: Hi Bill, 1) uninstalled all WSJT-X prior instances (v2.2.2, v2.3.0, and v2.4.0rc1) by dragging icon from Applications folder into trash can 2) re-down loaded WSJT-X .dmg file 3) launched .dmg installer 4) carefully followed the G4KLA Readme.txt instructions for my Intel processor (installation succeeded) 5) re-tried to run WSJT-X (from shortcut). Realizing in the past it auto-closed itself, I only kept it open for 15 seconds then closed it with pull-down menu: File-Quit (WSJTX). 6) opened terminal window and tried again to run WSJT-X (no success) Screenshots attached. Thank you 73, Dave Hi Dave, did you follow the graphical instructions in the installer to drag and drop the WSJT-X application bundle into the /Applications folder? Assuming you did, what does the following command print when run from a terminal: ls -lR /Applications/wsjtx* 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] Is there any forecast for WSJT-X v2.4.0rc2 please
Bill, Thank you so much for your patience. Here's bottom section of my finder in which I have left just single instance of WSJTX v2.4.0rc1 (named wsjtx). And what I get when I try to run it in terminal window with or without "Untitled" up front.I appreciate any inputs/suggestions. Thank you very 73, Dave On 2/16/21, 5:05 PM, "Bill Somerville" wrote: Hi David, to uninstall an application bundle like WSJT-X simply drag and drop it into the trash can. 73 Bill G4WJS. On 16/02/2021 22:39, David Schmocker wrote: > Gents > Thank you; I believe I foolishly (and contrary to User-Guide instruction) installed WSJTX v2.4.0rc1 and v2.3.0 over the top of formerly working v2.2.2 because I don't understand how you create a separate install folder in OS. > After doing the terminal window set-up commands for Mac, I dragged all (2.3.0 and 2.4.0rc1) installer shortcuts into the same Mac Applications folder). > > Next thinking I could somehow get the computer to separate these three WSJT shortcuts all same name in Applications folder (viewed in Finder), I went into finder and renamed two of the three instances with the version number. > > Now I think I need to learn how to uninstall all of the parts in OS 10.14.6, I think I need to start over with a clean install of just 2.4.0rc1. > > I would highly prefer to read or go off-line with this; your developer time is way too valuable! > > Very 73, > Dave KJ9I > > > On 2/16/21, 4:28 PM, "Joe Taylor" wrote: > > Dave -- > > There is no problem using WSJT-X v2.4.0-rc1 under macOS. Many are doing > so; all needed instructions have been posted on this reflector. If you > need help, just ask. > > Release candidates are published and updated when they are ready. At > this stage of development we can't predict exactly when that will be. > > -- Joe, K1JT > > On 2/16/2021 5:03 PM, David Schmocker wrote: > > Good afternoon/good evening gents: > > Is there any estimate when WSJT-X v2.4.0rc2 might be on the WSJT-X home > > page please? > > > > More detail: > > > > Joe K1JT mentioned it would help if I could provide 6m EME .wav files. > > I am currently unable to run WSJT-X v2.4.0rc1 because my OS 10.14.6 > > Mojave shuts down WSJTX with a Memory Allocation MALLOC error. > > > > Bill kindly provided the terminal-window work-around which doesn’t work > > (blocked due to permissions) so I am unable to do much yet.I tried > > sudo su (then my password) and then the path to launch WSJTX but it > > fails out every time. > > > > I don’t wish to consume precious developers’ time on tech support here. > > Just wondering when we may expect to see 2.4.0rc2. > > > > We REALLY appreciate all you’re doing! Thank you so much, very 73, > > > > > > Dave KJ9I ___ 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] Is there any forecast for WSJT-X v2.4.0rc2 please
Gents Thank you; I believe I foolishly (and contrary to User-Guide instruction) installed WSJTX v2.4.0rc1 and v2.3.0 over the top of formerly working v2.2.2 because I don't understand how you create a separate install folder in OS. After doing the terminal window set-up commands for Mac, I dragged all (2.3.0 and 2.4.0rc1) installer shortcuts into the same Mac Applications folder). Next thinking I could somehow get the computer to separate these three WSJT shortcuts all same name in Applications folder (viewed in Finder), I went into finder and renamed two of the three instances with the version number. Now I think I need to learn how to uninstall all of the parts in OS 10.14.6, I think I need to start over with a clean install of just 2.4.0rc1. I would highly prefer to read or go off-line with this; your developer time is way too valuable! Very 73, Dave KJ9I On 2/16/21, 4:28 PM, "Joe Taylor" wrote: Dave -- There is no problem using WSJT-X v2.4.0-rc1 under macOS. Many are doing so; all needed instructions have been posted on this reflector. If you need help, just ask. Release candidates are published and updated when they are ready. At this stage of development we can't predict exactly when that will be. -- Joe, K1JT On 2/16/2021 5:03 PM, David Schmocker wrote: > Good afternoon/good evening gents: > Is there any estimate when WSJT-X v2.4.0rc2 might be on the WSJT-X home > page please? > > More detail: > > Joe K1JT mentioned it would help if I could provide 6m EME .wav files. > I am currently unable to run WSJT-X v2.4.0rc1 because my OS 10.14.6 > Mojave shuts down WSJTX with a Memory Allocation MALLOC error. > > Bill kindly provided the terminal-window work-around which doesn’t work > (blocked due to permissions) so I am unable to do much yet.I tried > sudo su (then my password) and then the path to launch WSJTX but it > fails out every time. > > I don’t wish to consume precious developers’ time on tech support here. > Just wondering when we may expect to see 2.4.0rc2. > > We REALLY appreciate all you’re doing! Thank you so much, very 73, > > > Dave KJ9I > > > > ___ > 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] Is there any forecast for WSJT-X v2.4.0rc2 please
Hi Bill: Screenshot attached: (note my application is named ‘WSJTX_2.4.0rc1’). Thank you From: Bill Somerville Reply-To: WSJT software development Date: Tuesday, February 16, 2021 at 4:08 PM To: Subject: Re: [wsjt-devel] Is there any forecast for WSJT-X v2.4.0rc2 please On 16/02/2021 22:03, David Schmocker wrote: Good afternoon/good evening gents: Is there any estimate when WSJT-X v2.4.0rc2 might be on the WSJT-X home page please? More detail: Joe K1JT mentioned it would help if I could provide 6m EME .wav files.I am currently unable to run WSJT-X v2.4.0rc1 because my OS 10.14.6 Mojave shuts down WSJTX with a Memory Allocation MALLOC error. Bill kindly provided the terminal-window work-around which doesn’t work (blocked due to permissions) so I am unable to do much yet.I tried sudo su (then my password) and then the path to launch WSJTX but it fails out every time. I don’t wish to consume precious developers’ time on tech support here. Just wondering when we may expect to see 2.4.0rc2. We REALLY appreciate all you’re doing! Thank you so much, very 73, Dave KJ9I Hi Dave, please explain what "blocked due to permissions" consists of? You don't need to use root privileges to run WSJT-X, in fact it strongly recommended not to. 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] Is there any forecast for WSJT-X v2.4.0rc2 please
Good afternoon/good evening gents: Is there any estimate when WSJT-X v2.4.0rc2 might be on the WSJT-X home page please? More detail: Joe K1JT mentioned it would help if I could provide 6m EME .wav files. I am currently unable to run WSJT-X v2.4.0rc1 because my OS 10.14.6 Mojave shuts down WSJTX with a Memory Allocation MALLOC error. Bill kindly provided the terminal-window work-around which doesn’t work (blocked due to permissions) so I am unable to do much yet. I tried sudo su (then my password) and then the path to launch WSJTX but it fails out every time. I don’t wish to consume precious developers’ time on tech support here. Just wondering when we may expect to see 2.4.0rc2. We REALLY appreciate all you’re doing! Thank you so much, very 73, Dave KJ9I ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] #Feature request. 2.4.0
GA/GM Bill and all of the developers, Thank you so much for all the team is doing. Can Short-Hand messages be added for Q65A (used at 6m) also please? It’s helpful to have those single-tone messages Q65A at 6m EME because I have had at least one 6m EME JT65A weak signal QSO where the decoder didn’t decode the SH message, yet I was able to visibly see a ‘paint splash’ (partial trace) at the right frequencies knowing that SH message that was being sent so I could visually decode this. Also, if I go on a DXpedition (which I plan to), [my apologies in advance this is going to open a hornet’s nest], I am interested in working more stations, not spending time distinguishing between level-based reports. Perhaps my HF background where contesters give “599” no matter what colors this request. With EME, SH messages help. Having the choice of SH or not gives the level-sensitive or SH option. I appreciate your consideration. Thank you! Very 73, Dave KJ9I (flames if any to be sent to me directly not to the list please) From: Bill Somerville Reply-To: WSJT software development Date: Tuesday, February 9, 2021 at 5:00 AM To: Subject: Re: [wsjt-devel] #Feature request. 2.4.0 On 09/02/2021 03:54, Hattori, Yoshihisa wrote: Hi all. I am testing Q65 and realized that we are missing Short hand indicator on waterfall display, which is provided for JT65. (three yellow lines suggesting the RO/RRR/73 tones.) While less Q65/QRA64 users are using shorthand, it is good to have those since Sh will not be decoded and users need to visually identify the signal. Can you please implement it? De JO1LVZ/Hatt Hi Hatt-san, the single tone short code markers are shown for sub-modes C or wider. 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
