The waterfall runs at the rate it says it does.
A server could be asked for 20 frames a second and quietly send 7.8 — the same 7.8 whatever
you asked for, on every 32-bit machine (a Pi 2, an Android TV, any VibeServer Lite host).
It was never the hardware being slow: the frames were computed and then thrown away, half of
them, every single block. The boxes doing it were 50% idle at the time.
Fixed, and measured on real hardware — asked → delivered, before and after:
| asked | before | after |
|---|---|---|
| 20 | 7.8 | 19.8 |
| 15 | 7.8 | 15.0 |
| 10 | 7.8 | 10.0 |
| 5 | 4.9 | 5.0 |
If you run a VibeServer on a Raspberry Pi 2, an Android TV box, or anything 32-bit, your
waterfall has been running at less than half speed. Update the server too — sudo apt update && sudo apt upgrade vibeserver (5.6.45), or the VibeServer Lite APK.
Also in this build
- NR / NB / AN indicators. Noise reduction, noise blanker and auto-notch now show a lit
badge while they are on. They persist between sessions, and an effect you have forgotten
about is the one that makes a receiver sound broken — so now it tells you. - The connection meter stops crying wolf. A server that is simply slower than you asked
is no longer read as a failing link and throttled down for it. - Restarting a Linux server brings its radios back. Stopping and starting the service
left the front door running with every radio dead — which looked exactly like an update
breaking your dongle.
Android 7.0+. Sideload: allow install from unknown sources, then open the APK.