For giggles I tried again. I'm on 13.0.1 too. Uninstalled everything. Used CleanMyMacX to do so. Reinstalled 2.6.0 rc5. Redid special file. Rebooted. After cycles the waterfall stopped moving and

Dave, are you saying that he is not a Fox nor Hound? When I am in the Hound mode, then my transmitter starts at 15/45. I never read the original message carefully, sri. So it is unclear whether Lars

Reino, if he is in F/H should he not be transmitting at 15/45, and listening at 00/30.. sounds like it is not actually in f/h mode Dave Garber VE3WEJ / VE3IE wrote:

Every three or so calls, I cease transmissions, take a look for open spaces, then change transmit frequency to an open location, and begin the call cycle again. 73, and thanks, Dave

Lars, If you are not transmitting and activate selection "Rx All Freqs" at the lower middle, then you will see other hounds. 73, Reino OH3mA

The update is available in System Preferences/General/Software Update I have 13.0.1 and my applications will not recognize any ports except the /dev/bluetooth Not sure yet on where the issue is. --

I agree with Reino and Gilbert. What about this logic for an enhancement: After I send a Tx 4 "RR73", I receive the "Prompt me to log QSO" (current state). IF I receive a repeat Tx 3 "R-xx" reply

I saw and reported this behavior when I updated to 13.0.0, and there was no solution or recommendation. I did several complete removals of the software and auxiliary files and reinstalled both 2.5.4

You cannot see the other hounds as they are transmitting at the same time as you are. 73 -- Larry -- W1DYJ

Yes, a bunch of people are after the update to macOS 13.0 Ventura. It;s happening on all versions of WSJT-X including 2.6.0 rc5. -- Thanks & 73. Jeff K3JRZ ● Email ( K3JRZ.Jeff@... )

Rick, I’m using Ventura on my intel based MacBook Pro with WSJT-X 2.6.0 rc5 without issues. Maybe upgrade to 2.6.0? Radio is FTDX10 though. Also using JT Bridge and Rumlog.

My WSJT-X is v2.6.0-rc5. In FT8 Hound mode, I listen to the Fox, set my TX frequency, and press "Activate TX". WSJT-X then transmits to the Fox at 00 and 30. But during the RX periodes (15/45), I

I think it’s important to remember — for any mode (not just FT8) — that there is always the possibility that you thought you were in the other station’s log when in fact you ultimately

Snip>>I will use the OFTEN SEEN example below that was recorded in VK3 on 6m FT8 "segment" 2022-12-03. The actual op call has been obscured as identifying the op would be bad practise. 230345 -15

I had similar issues and it was because I had another instance of WSJT-X running on the PC.

Is anyone else seeing this problem on Mac? Since the Mac OS to 13.x update, WSJT-X locks up when it transmits in FT8. Until the update, it received and decoded normally. Now, transmitting usually

Hi Rafal, I like to provide some feedback on this list about FT8 so that all interested parties have a hint what is fed back. First of all the guide is an excellent and very useful source of radio

The ft8 section is at p 167 (according to my PDF viewer), although I'd recommend that people read more of the guide, which I find very good. I will probably read the whole thing as there is still too

Yep confirmed baud rate matches (but thanks for the idea!). Using DX Labs in between works OK but not the preferred solution since I have some macros that execute on QSYs that do things like setting

Most, if not all amateur software has an 'update' software command. Both for the application itself, and sub associated applications. AKA cty.dat etc. I don't think this is the case for