Mbl4 | Broadcast V112 Better

One of the standout improvements in v112 is the optimization of the internal database engine. In previous versions, stations with libraries exceeding hundreds of thousands of tracks occasionally experienced latency during intensive searches or auto-generation of playlists. v112 introduces faster indexing and querying algorithms. The result is near-instantaneous search results and smoother navigation through the media library, allowing DJs and program directors to find content faster without breaking the flow of their show.

MBL4 broadcast v112 is a non-rollback upgrade for the base station (but clients can roll back). Follow this safe migration path:

Do not attempt a "downgrade" of the base station after upgrading to v112—the broadcast queue format is incompatible with v109.

MBL4 Broadcast Firmware v1.12 – Changelog mbl4 broadcast v112 better

Improvements:

Fixes:

Note:
To get “better” performance, ensure all units in your broadcast group are updated to v1.12 or later. One of the standout improvements in v112 is

Debugging broadcast systems just got easier. You can now enable JSON-formatted logs with:

MBL4_LOG_FORMAT=json ./your_app

Logs include msg_id, topic, node_id, and latency metrics — ready for ingestion into tools like Loki or Splunk.

For video or telemetry, set FEC Redundancy to 15-20%. For control data, set to 30%. The Bloom filter works best with higher redundancy. Do not attempt a "downgrade" of the base

In Policy > Broadcast, set Unicast Retransmission to "FEC-Only". This forces the system to rely on forward error correction, eliminating the "weakest link" drag.

Default is 512 bytes. For mixed traffic, increase to 1024 bytes to reduce overhead. Do not exceed 1500 unless all clients support jumbo frames.