×
Mbl4 Broadcast V1.12 -
MBL4 Broadcast likely serves as a broadcast management and distribution solution for audio/video content — for example, live streaming, scheduled playout, multicast distribution, or hybrid OTT/broadcast workflows. Version 1.12 indicates an incremental, stability-and-feature update after initial 1.0 stabilization; such releases typically focus on bug fixes, performance tuning, minor feature enhancements, and improved interoperability rather than major architectural changes.
Primary goals of v1.12 would include:
Now assign granular permissions:
No more shared passwords or accidental config changes during live shows.
| Metric | MBL4 v1.11 | MBL4 v1.12 | Improvement | | :--- | :--- | :--- | :--- | | ST 2110-20 Latency (4Kp60) | 420 µs | 390 µs | -7.1% | | Failover Time (Primary switch loss) | 1.2 sec | 0.4 sec | -66% | | Concurrent Flows (per 10G port) | 32 | 48 | +50% | | CPU Idle % (under 4K load) | 38% | 54% | +42% | | NMOS Registration Time | 6.2 sec | 1.9 sec | -69% |
Source: Internal lab tests (Fuji Reference Architecture, Cisco Nexus 9K).
The most striking gain is the 48 concurrent flows per 10G port. This allows a single MBL4 card to handle four independent UHD sources plus 44 ancillary data streams (closed captions, OP-47, timecode, etc.) without resorting to link aggregation.
Perhaps the most requested feature: SDI-IP stream corruption healing. If the MBL4 detects a corrupt SDP (Session Description Protocol) file or a malformed RTP header, v1.12 will roll back to the last known good configuration stored in an encrypted flash partition. The rollback takes 1.8 seconds – down from 12 seconds in v1.11 – making it virtually unnoticeable during live talk shows.
If you use your MBL4 in a managed environment, install v1.12 immediately. The update closes a medium-severity vulnerability (CVSS 6.8) discovered in the historical SNMP v2c implementation. An attacker on the same local network could theoretically query device routes. Version 1.12 deprecates SNMP v2c in favor of SNMP v3 with AES-256 encryption.
Additionally, the default "admin" password is now required to be changed before the first stream is configured on a fresh factory reset.
