Hamlib (windows) jump to VFO-B after VFO-A

[PY2AD]

For information, since I don't even know if there's a way to fix it:

I use QLog on Windows with Hamlib and FT950. If I'm on the radio at 10m, and an interesting station appears on the cluster at 20m, if I click to change bands, the radio quickly jumps to VFO-B and only then goes to VFO-A at 20m.

I tested it on Ubuntu 24.04.2 and this doesn't happen.

[foldynl]

This needs to be solved with Hamlib.Of cource it is necessary to test it with rigctl itself first but QLog uses standard functions for radio control and QLog does not request to switch VFO before changing the band.

[PY2AD]

Stranger, because this happen only in windows, not in linux.

[aa5sh]

What version of Hamlib are you using in each?

…

On Sat, Oct 18, 2025 at 3:55 PM PY2AD ***@***.***> wrote: Stranger, because this happen only in windows, not in linux. — Reply to this email directly, view it on GitHub <#792 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUEEMXSOMPHRATASAMTNSBT3YKSMJAVCNFSM6AAAAACJQ6W5A2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINZRHA4DEMQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[PY2AD]

I am using default from QLog.... just select in radio setup.
I have Ubuntu 24.04.2 and W10.

On linux changes normal, only VFO-A, in W10 jump first to VFO-B, then goes to select frquency on cluster (VFO-A).
Only happen when changes band.

I am not using split on radio.

[foldynl]

The difference between Windows and Linux is significant when it is related to Hamlib. If you’re not using the Flatpak installation package, QLog uses the Hamlib version from the distribution. Unlike Windows, which uses the latest Hamlib version. This can cause major differences, especially with Hamlib. Ubuntu 24.04 has Hamlib 4.5.5, Window has hamlib 4.6.5.

Hamlib is an actively developed project, and things sometimes work differently from one version to another.

[PY2AD]

Is there any way to change version on windows?

[foldynl]

You can try downloading hamlib from Hamlib Releases and replace all DLL files from hamlib tarball (bin/libgcc_s_seg-1, bin/hamlib-4.dll, bin/libusb-1.0.dll, lib/libwinpthread-1.sll) in the directory where you have installed QLog. But the functionality is not guaranteed. QLog for windows is compiled for a specific version and there can be some version-by-version limitations.