Waybeam v0.24 — mDNS, 144 fps and new sensor modes
Development did not stop after the June update: on July 4 the OpenIPC/waybeam_venc repository was synced with the developer's fork, and the current version is v0.24.1. Below are the key changes since v0.17 and what to watch out for when upgrading.
🔹 mDNS — the camera announces itself on the network
Waybeam now announces itself on the local network via mDNS (v0.18):
- the
_waybeam-venc._tcp.localservice + the short namewaybeam.local - a unique name
waybeam-<suffix>.local, where the suffix is the tail of the SigmaStar chip die ID - a new
discoveryconfig section (enabled,serviceType,name,bareAlias) — also exposed via the HTTP API and WebUI - the full 12-hex serial is readable from
GET /api/v1/config→data.device.serial
No more hunting for the camera's IP with a scanner — just open http://waybeam.local.
🔹 The frameLost field is gone BREAKING
In v0.19 the SDK frame-lost strategy was removed entirely: the video0.frameLost field no longer exists in the config or the API. If it is still in your /etc/waybeam.json, simply delete that line. In its place there is now a 1000 kbps bitrate floor.
🔹 Maruko: new auto-exposure — a quarter less CPU
Since v0.22 Maruko has a single AE mode: the vendor's native AE+AWB converge first, then a dedicated thread periodically re-runs CUS3A_RunOnce at fps/3 (30 Hz minimum). The result is ~24% CPU savings at 1080p100.
The isp.aeEngine field has been removed on Maruko (it still works on Star6E as before). Live isp.gainMax changes via the API have been fixed.
🔹 New sensor modes BREAKING
A major mode rework on Maruko (v0.20–v0.23):
- IMX415 — new non-binned 16:9 modes at 1485 Mbps:
2952×1656@50,2952×1368@60,2112×1184@90,1920×1080@100 - IMX335 — a new best-per-fps lineup: 30 / 50 / 60 / 90 / 100 fps
video0.sizewidth alignment relaxed from /16 to /8isp.keepAspectis now honest: on an aspect-ratio mismatch the frame is anamorphically squeezed instead of silently cropped
sensor.mode indices renumbered
Mode indices changed on both sensors. After upgrading, check sensor.mode in your config or leave it at -1 (auto-detect). The current mode list for your camera is available at GET /api/v1/modes.
🔹 144 fps for minimal latency
In v0.24 the IMX335 gained an ultra-low-latency 1536×864@144 mode (16:9), and the live video0.fps limit was raised to 144. The frame rate is bounded by ISP bandwidth, so it is only available in this dedicated mode.
🔹 Other changes
- apfpv (WiFi mode): boots with unconnected UDP output and clamps the RTP payload to 1400 bytes — less fragmentation on the WiFi link
- Record-only audio: a negative
audioPortvalue writes sound to the recording without transmitting it over the air - Dual-record fixed (v0.17.1): the second record channel is created right away with
record.mode: dual, and the SD-card recording bitrate is independent of the live stream - WebUI: a custom dashboard can be dropped into
/usr/share/www— it overrides the built-in one without rebuilding - Maruko: stabilization controls in the WebUI are now greyed out — this chip lacks the IVE block; stabilization remains Star6E-only
🔹 Documentation
The Waybeam pages have been brought up to date with v0.24.1 (settings for older versions are tucked into collapsible blocks):
- Waybeam overview — features and comparison with Majestic
- Install on the camera — tarball,
/etc/waybeam.jsonconfig, first run - WFB-ng integration — replacing Majestic, ground station
- Web panel and HTTP API — framing, resilience, all endpoints
Repository: github.com/OpenIPC/waybeam_venc — MIT license, open source.