Tnx for the new Build 137.
I have a Glitch, it's not really a Bug. And this exists since some Time. Not sure, if it is cqrlog, wsjtx, hamlib or the remote Mode.

My Setup:
Linux Mint 21.3 Cinnemon
CQRLog 137 Alpha
WSJTX 2.7.0 - Split Setting: Fake it. None or RIG didn't make a Difference.
Hamlib 4.6.2
WSJTX, build from Source, uses Hamlib 4.6.1 internal. Using 4.6.1 System wide makes no Difference.
RIG - Yaesu FT-DX10

I use the Remote Connection for WSJTX via Hamlib NET rigctl as RIG in WSJTX.
This Combination did work very well with a little Glitch, that appears only in this Configuration and not, if WSJTX is connected direct to the RIG without CQRLog.
It's with the RX and TX Audio Settings in the WSJTX Main Window and Band or Mode Switching (with a Frequency Change).
Example:
In WSJTX, RX and TX Audio are set to 800 Hz.
Now switching to another Band. TX and RX Audio Settings should not change, only the Band Frequency.
But always on Band Switching, the RX Audio Settings jumps to 5000 Hz. But only in Remote Mode with CQRLog, not with direct Connection to the RIG.
Same happens on Mode Switching in the same Band, if a Frequency change for the Mode happens.
FT8 to FT4 - RX jumps to 5000 Hz.
Set RX back to 800 Hz and switching back to FT8 - no RX Audio change.
Now back to FT4 - RX jumps again to 5000 Hz.
In Short: Band change - RX Audio switches always to 5000 Hz. Mode change FT8/FT4 - one change for Free :-)
RIG and WSJTX direct Connection - no RX Audio changes.

It's not a Bug, a little (Cosmetic) Glitch and a interesting Behavior. It's not a big Deal and only one more Click to equalize TX and RX Audio in WSJTX. And it's only needed if you want to Monitor your TX Audio for other Users on the same TX Audio.

Heinz-Juergen DO1YHJ