Higher channel density
Keep the selected platform and use measured efficiency for more network-audio channels or product features.
OEM LICENSING + INTEGRATION
Measured receiver scale.
Your Linux platform.
Evaluate and license a measured AES67 receiver architecture for higher multichannel density, lower configured receiver targets and more CPU and memory headroom—without maintaining a custom kernel media 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
1 ms TARGET64 channels8 streams × 8 channels
2 ms TARGET128 channels16 streams × 8 channels
3 ms TARGET256 channels32 streams × 8 channels
Reference evidence: quad-core Cortex-A72 and verified logical ALSA outputs. Commercial scope: Linux-capable receiver 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.
Create system headroom
Lower receiver pressure leaves more of the platform available for control, mixing and product features.
Portable Linux userspace
Target Arm Cortex, NXP i.MX, x86 or another Linux-capable platform without a custom kernel module.
BENCHMARK ADAPTER AVAILABLEA familiar route to
A familiar route to
target-platform proof.
OEM teams can use the open-source linux-aes67-daemon REST/SDP control plane to configure the Bama Box receiver during evaluation. The commercial question stays simple: what capacity, latency profile and system headroom does the receiver deliver on your product hardware?
The adapter supports evaluation without forcing a production control-plane decision. See the detailed userspace and kernel-boundary explanation on the technology page.
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