Higher channel density
Keep the selected platform and use measured efficiency for more network-audio channels or product features.
OEM LICENSING + INTEGRATION
More product value.
Less platform overhead.
Keep your chosen Linux hardware and license a measured AES67 receiver architecture for higher channel density, lower-latency product profiles and more CPU and memory headroom—without maintaining a custom kernel module.
YOUR LINUX PLATFORMArm Cortex SoCx86 systemOther Linux CPUNXP i.MX and other families
DEFINED SOFTWARE APIOEM adapter
PATENT-PENDING USERSPACEBama Box receiverConnect timestamps · clocks · network · audio interface
MORE CHANNELS · LOWER-LATENCY PROFILES · MORE HEADROOM
MEASURED REFERENCE1 msstrict receiver target through physical PCM5122 output
COMMON 3 MS PROFILE+65%receiver density versus tested stock RAVENNA/Linux
COMMON 5 MS PROFILE+67%receiver density versus tested stock RAVENNA/Linux
Reference evidence: quad-core Cortex-A72. Commercial scope: Linux-capable platforms, benchmarked on the OEM target.
COMMERCIAL LEVERAGE
Efficiency becomes a product decision.
The receiver is relevant anywhere a Linux product must turn AES67 streams into scheduled audio—from compact stage endpoints to console engines and backstage servers.
Lower-latency profiles
Reach a strict 1 ms receiver target through an off-the-shelf physical PCM5122 path.
Protect the hardware plan
Lower CPU and memory pressure can support BOM, thermal, supply and platform-life decisions.
Portable Linux userspace
Target Arm Cortex, NXP i.MX, x86 or another Linux-capable platform without a custom kernel module.
BENCHMARK ADAPTER AVAILABLEKeep the test interface.
Keep the test interface.
Swap the media backend.
OEMs can evaluate Bama Box through a familiar open-source control surface. The tested adapter keeps the linux-aes67-daemon REST/SDP control plane unchanged and replaces its stock RAVENNA kernel media backend with the Bama Box userspace receiver.
USER SPACE · UNCHANGED REST + SDP CONTROL PLANElinux-aes67-daemonadd · status · rename · remove
USER SPACEControl-plane bridgeDaemon-managed configuration
KERNEL BOUNDARY
KERNEL SPACERAVENNA media moduleCustom kernel media backend
USER SPACEBama Box receiverPTP · jitter · deadlines · ALSA mmap
KERNEL BOUNDARY
KERNEL SPACEStandard Linux interfacesNetworking + ALSA · no custom media module
EXAMPLE MIXED BENCHMARKHardware + null sinksRun concurrently under one control plane
hw:0hw:1
Ring-aware drift control
null:0null:1null:2null:3
Capacity and resource load
Same userspace control plane, different media placement: the stock path runs the RAVENNA media backend as a custom kernel module; Bama Box runs the receiver in userspace and uses standard Linux networking and ALSA interfaces across the kernel boundary. Mixed physical and null sinks can then be configured for the test plan. The 2 + 4 graphic is illustrative, not a benchmark limit.
JOINT EVALUATION
A clear path from target SoC to production.
The core receiver is ready. OEM work focuses on proving the business case, confirming feasibility and connecting the platform-specific timestamp, clock, networking and audio-interface boundary.
- 01
Target SoC
Define the Linux build, NIC, timing source, audio interface and required profiles.
- 02
Benchmark
Measure physical output, receiver density and system resources at clear boundaries.
- 03
Feasibility
Confirm the achievable profile, integration scope and commercial value.
- 04
Integration
Expose hardware timestamps and platform interfaces through the software API.
- 05
Production license
Match licensing, support and enabled channel class to the OEM product.
LICENSING STRUCTURE
Predictable economics.
Exact pricing stays private and is matched to product scope, volume, platform and strategic rights.
At shipment
No recurring software subscription.
Aligned to capacity
Lower-channel products remain economical.
Predictable maximum
A negotiated ceiling controls the per-device royalty.
CONFIDENTIAL OEM DISCUSSION