Stopping and starting the engine within a second or so ends in the Error state even though the engine and audio capture come up fine. Stop queues the rig teardown on the TX handler, and with a rig attached the shutdown PTT release can hang for hamlib's full timeout, so the old session still holds the USB device when the new start opens the rig. That open times out, and the error broadcast flips the whole UI to Error while audio keeps flowing.
The TruSDX and QMX paths already have a "cleanup still active" guard for this. Hamlib, network, and RTS don't.
Filing so it doesn't get lost. I plan to fix it.
Stopping and starting the engine within a second or so ends in the Error state even though the engine and audio capture come up fine. Stop queues the rig teardown on the TX handler, and with a rig attached the shutdown PTT release can hang for hamlib's full timeout, so the old session still holds the USB device when the new start opens the rig. That open times out, and the error broadcast flips the whole UI to Error while audio keeps flowing.
The TruSDX and QMX paths already have a "cleanup still active" guard for this. Hamlib, network, and RTS don't.
Filing so it doesn't get lost. I plan to fix it.