Clayton Smith
Clayton Smith
The build steps I linked to above are used to produce automated builds, so I expect they will work if you use them on your machine.
> Apparently, it is to be run on Docker. Actually, it's a workflow configuration for GitHub Actions: https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions > Is there another way to run the yml script? It can't...
Are you able to grab a stack trace in a debugger?
Oh wait, I thought it was a crash but I guess it's just misbehaving.
I don't immediately see what connection that commit could have to the remote control, so some investigation will be needed.
I believe graphics and networking are both processed on the UI thread (in an event loop) so changes to the plotter could affect timing of remote control commands. Expecting a...
That said, I would expect the performance improvements in #1383 to result in the UI thread spending less time on drawing, not more.
If you run in a debugger and press Ctrl+C during a stall, the backtrace should reveal the culprit.
To help with measurement, I put together this Python script, which hammers Gqrx with remote commands and measures the worst latency over one-second intervals: ```python #!/usr/bin/env python3 import socket import...
On my system (Ubuntu 24.04, Qt 6.4.2), latency numbers are actually improved on the master branch (v2.17.5-13-g0218221): ``` [ Fill off ] Worst latency: 5.49 ms Worst latency: 5.26 ms...