preserve network time
AES67 RECEIVER TECHNOLOGY
Network time in.
Controlled audio out.
Bama Box turns timestamped AES67 packets into controlled device delivery in one Linux userspace architecture. OEMs can keep their chosen Linux platform while adding lower-latency profiles, higher receiver density and predictable timing control.
USERSPACE RECEIVE CONTROLLER PTP MAPPED
NO CUSTOM KERNEL MODULEDRIFT CONTROLHW TIMESTAMPS VIA API
Keep the platformIntegrate on the OEM's selected Linux hardware
Control the deadlineConnect RTP time directly to device delivery
Scale the productUse recovered headroom for channels or features
WHAT THE ANIMATION SHOWS
Timing decisions stay connected.
Packet intake, buffering and physical-device delivery remain tied to one presentation timeline. That integrated control is the product advantage—not any single isolated optimization.
Deadline scheduler
Maps RTP presentation times to controlled delivery deadlines as stream count rises.
Time-drift control
Tracks the difference between the PTP timeline and the physical device clock.
Jitter buffering
Absorbs packet-arrival variation while protecting the configured receiver target.
PTP time mapping
Consumes platform timestamps through an OEM-facing software API.
ALSA mmap delivery
Moves PCM into the physical audio path with bounded runtime queue depth.
Userspace portability
Runs without a custom kernel module and is not tied to one CPU core, SoC family or board.
CONTROL-PLANE INDEPENDENTKeep your control plane.
Keep your control plane.
Change the media engine.
The Bama Box receiver accepts normalized stream configuration through a defined adapter. OEM discovery, routing and product-control software can stay in place while the receiver handles the time-critical media path.
DEFINED BOUNDARYStream adapterconfiguration · status · lifecycle
PATENT-PENDING USERSPACEBama Box receiverPTP timing · jitter control · deadline scheduling · ALSA mmap
Working reference: the unchanged linux-aes67-daemon REST/SDP control plane can configure the Bama Box receiver as an alternative media backend. The adapter supports receiver benchmarking across stream configurations and ALSA outputs; any control plane that supplies the required stream description can integrate at the same defined boundary.
ILLUSTRATIVE MIXPhysical and null sinks can run together.Counts are configured for the test plan.
hw:0hw:1
Hardware-ring clock-drift control
null:0null:1null:2null:3
Receiver capacity and resource load
CLOCK CONTROL IN PRACTICEDrift is measured.
Drift is measured.
Correction is declared.
In the measured PCM5122 run, the device consumed roughly one extra 48 kHz frame—20.83 µs—about every ten seconds. The controller tracked the difference and made six declared single-frame repeats during 60 seconds.
That is a frame-level clock-control observation, not a claim of analog end-to-end latency.
PTPCONTROLDAC
0 s6 declared one-frame repeats60 s
OEM-SUPPLIED BOUNDARY
Your hardware. A defined software adapter.
The remaining OEM integration is the platform boundary: timestamps, clocks, NIC capabilities and audio interfaces are exposed through a defined software API. The receiver is portable across Linux-capable processors; performance is established on the OEM target.
Arm Cortex Linux SoCsNXP i.MX familiesx86 systemsOther Linux platforms
BENCHMARK IT ON YOUR SOC
Benchmark your target platform Bring your timing and audio interfaces.
We can define the adapter boundary and run a confidential receiver comparison on the target hardware.