Hello everyone. I just joined this group today and have a question that hopefully can be answered. Please forgive me if this has already been covered; I tried to find documentation on this issue without any success. The download and install of the program went just fine. However when I try to launch the program I get 2 error messages about shared memory. I have attached screenshots below. Does anyone know why this is happening and a possible remedy for it? Thanks, Michael Rieger KJ7BRM

Hello, My first attempt at a build from source. I have done my best to search for an answer but no luck. My system is Xubuntu 20.04.1 Thank you for any help, My problem: -- Building for for: Linux-x86_64 -- ****************************************************** -- Checking for module 'hamlib' -- Package 'libusb-1.0', required by 'hamlib', not found -- Found hamlib CMake Error at /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:146 (message): Could NOT find hamlib (missing: hamlib_LIBRARY_DIRS) (Required is at least version "3") Call Stack (most recent call first): /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:393 (_FPHSA_FAILURE_MESSAGE) CMake/Modules/Findhamlib.cmake:88 (find_package_handle_standard_args) CMakeLists.txt:875 (find_package) -- Configuring incomplete, errors occurred! See also "/home/zx20/build/build/wsjtx-prefix/src/wsjtx-build/CMakeFiles/CMakeOutput.log". make[2]: *** [CMakeFiles/wsjtx-build.dir/build.make:68: wsjtx-prefix/src/wsjtx-stamp/wsjtx-configure] Error 1 make[1]: *** [CMakeFiles/Makefile2:442: CMakeFiles/wsjtx-build.dir/all] Error 2 make: *** [Makefile:84: all] Error 2 This looks like I need to find libusb-1.0 Thank you , Stan, KA1ZE

When my PC turns the screen off (not sleep mode), and then wakes up again, WSJT receives OK. But when I try to transmit, the CAT/PTT stuff works OK, but no audio is sent to the rig. I have to restart WSJT to actually transmit a signal. I just changes PCs, and this didn't happen with my previous PC. Both were running Win10 through a microKeyerIII to a Yaesu FTDX101. This may be more of a PC question... I just don't know where to look... Thanks, Frank W2YK

Hi - been away from WSJT-X for a while. Just installed v2.2.2 on my MacBook Pro, running OSX Catalina 10.15.6. I’m using an Elecraft KX2. I am seeing something very different on the decode process than what I had seen on previous versions - several months ago. When on FT8, the progress bar goes across almost to completion, and a bunch of decoded signals display in the left panel. Then, the decode button turns off, then back on and several (usually 2-3) more signals are shown in the last panel. The older version didn’t do that - when it was done decoding, it was done, period. Where this causes an issue is when that left panel is almost full at decode time. Just as I’m about to double click on a station to call, those last few lines pop up on the screen, moving the one I was going to call up a few lines. Do I have something set incorrectly in the preferences that causes this? Jim Bennett / W6JHB Folsom, CA

This document was originally posted by Bill, G4WJS as part of a long thread. Assuming you are running on MS Windows and have installed WSJT-X, this explains how to set Tx audio levels correctly: The issue you may have with Windows WSJT-X Tx audio levels is due to the "Pwr" slider in WSJT-X no longer being linked to the Windows mixer control for the Tx audio device. This means that you must set the mixer slider manually, this should be a one-time operation. Setting the mixer control is a two step operation. Firstly you must set the mixer control to maximum. The mixer control is only visible when transmitting so use the "Tune" button in WSJT-X. It is advisable to reduce the "Pwr" slider in WSJT-X to minimum while doing this to limit the output power, or do this part with the rig switched off. The mixer slider will look something like this: Once the mixer is set to maximum the second step is very important. You must now adjust the master level for your Tx audio device to 0dB. The level control for that is in the audio playback device properties for the Tx audio device which looks like this: If your slider scale is not in decibels then right-click the slider and select decibels. Your audio device may not have gain, in which case 0 dB will be fully to the right. Some devices do have gain, *in those cases it is critical that the gain be reduced to 0 dB* otherwise a severely distorted transmit signal will be produced. Once you have completed this one time setup you can increase the "Pwr" slider back to maximum for full level audio output from WSJT-X. I recommend rechecking your Tx levels elsewhere, e.g. data modulation level adjustments on your rig, audio interface level controls etc. to ensure that you are not over-driving the audio input of your rig. A good method is to use a 1,500 Hz Tx audio offset "Tune" tone with the " ;Pwr" slider at maximum and your rig at maximum power into a good dummy load. With that arrangement reducing the interface or rig's data modulation input level until little or no ALC is indicated on the rig is about right and should give around 90% of the maximum output of your rig. If your interface and rig do not have any Tx audio level controls then it is OK to use the operating system audio device master level control as shown above to reduce the audio level to a correct amount *so long as the critical 0 dB level is never exceeded*. Once this setup is complete you can make routine Tx power adjustments using power control on the rig or the "Pwr" slider in WSJT-X. Bill G4WJS.

I noticed two problems with FT4 sequencing: 1. Double-clicking on a station to can set the "Tx even/1st" incorrectly. It was supposed to be checked, it was not. This led me to make 3-4 calls with the wrong sequencing before I stopped and realized what was wrong when I heard the DX on the same sequence as my transmitter. 2. Receiving RR73 from the other station toggled (or cleared) "Tx even/1st" so my 73 was sent on top of his NEXT transmission. Both of these happened when I tried to work EA8AQV on 20m this afternoon (14080). -- Jim Reisert AD1C, <jjreisert@...>, https://www.ad1c.us