I believe the setting are saved in WSJT-X.ini in the same directory as the .log & .adi files AL, K0VM On 1/22/2020 10:21 AM, Gilbert Baron wrote:

If you monitor total CPU load in windows Resource monitor, you may notice that there is a peak in CPU loading at the end of each decode cycle in which decodes did not fail. If the cppu

This is bad advice, based on wandering around in the dark. See http://k9yc.com/KillingReceiveNoise.pdf and http://k9yc.com/RFI-Ham.pdf which are based on extensive, peer-reviewed research. 73, Jim

I have messed up SO MANY times with configurations. After spending hours getting it the way I want IU try to make a backup of current settings. All my other windows programs work by Select a

GM I find I need all of the vertical space for stations calling me. Having the waterfall on a second monitor frees up space for the WSJT-X and JTAlert windows. Once the windows are arranged to your

I have the same problem with occasionally dropped decode cycles. I'm use the internal audio drivers in my Icom ic-7300, and the receive level is always on abt 60 db. I have no problem with non-synced

I am using some #31 material doughnuts which are 1.25"D x 0.25" H  with an ID of 0.625".  That 5/8" ID is just large enough for a USB connector to pass through allowing me to make a couple of turns

No Bill. That is the start up message. I will let it run and when it next crashes, I will look and see what comes up at the end of the terminal window. If that doesn't present any directions of

Hi Bill, RFI may be a common cause, but not the only cause... Recently, I had the waterfall freezing just 45 seconds after starting WSJT-X. Clicking the "Monitor" button once or twice showed the

Hi Tony, those messages are benign. Did the output you showed include a crash of WSJT-X? 73 Bill G4WJS.

OK Bill - I started wsjtx in a terminal and this is the output. THE PROGRAM starts up and runs fine (apparently anyway) in spite of the warnings. It typicaly runs for about 12 or 20 hours before

Thanks Bill. That sounds like a productive route to follow. I will have to do some digging to find out about this 'gdb' thing. Never heard of it, so this will provide a new interest to get me through

Hi John, I log my QSOs in a logging program (RumLogNG on macOS), then regularly export the whole log as a .adif file. In the 'Colors' tab of the WSJT-X settings dialog, there's a

How about swapping the callbacks for setting the RX and TX frequencies in the waterfall? ! Setting the TX frequency is very clumsy if you're runnong remote desktop on a tablet or a phone. Al

Thanks, Bill. I thought that WAV file should cover the time from 211745 to 2113030. It decoded at 213030 for me also. It skipped decodes at 211830, 211845, 212115, 212145, 212345, 212415 and

Thanx 4 the hint, Neil. I'll do my home work 👍

OK ... the first request can be accomplished by a third-party utility, JT-Alert or similar. The worked B4 request is already in the program, and is covered in the User Guide:

I don't know if any of that functionality already exists as I am a new user, but nice ideas. I'd like to know if it's possible to show a user you've worked before in a different colour or something so

Hi Dave, Thanks for this information, it is very helpfull. During my investigation I found that ptt keying with one comport to the ts2k did work but it was not possible to use the acc2 audio

Would be very handy to have a "lookup feature" where callsigns and locators could be easily accessible. Right clicking on a call sign under the DX Call label or a locator under DX Grid label cound