Higher channel density
Keep the selected platform and use measured efficiency for more network-audio channels or product features.
OEM LICENSING + INTEGRATION
One AES67 RX/TX engine.
Integrated or modular.
Use Bama Box inside a product that already has Linux compute—or as the media engine in a dedicated AoIP module. Unified 256×256-channel AES67 full duplex is measured on the quad-core Arm reference platform.
YOUR PRODUCT ARCHITECTUREIntegrated Linux productDedicated AoIP moduleEmbedded or x86 systemNXP i.MX and other Linux families
DEFINED SOFTWARE APIOEM adapter
PATENT-PENDING USERSPACEBama Box RX/TX engineReceive measured · transmit measured
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: integrated products and dedicated module platforms, benchmarked on the OEM target.
COMMERCIAL LEVERAGE
Efficiency becomes a product decision.
The media engine fits products with existing Linux compute and dedicated modules serving analog equipment, stageboxes, consoles, amplifiers and broadcast systems.
Lower-latency profiles
Reach a strict 1 ms receiver target through an off-the-shelf physical PCM5122 path.
Create system headroom
Lower media-path 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.
DEPLOYMENT CHOICE
Build it into the product—or into your next AoIP module.
Bama Box provides the patent-pending RX/TX media engine beneath the architecture that fits the OEM product. Unified 256×256-channel full duplex is measured on the reference platform, with physical audio interfaces qualified on the OEM target hardware.
256 logical outputs
32 eight-channel streams sustained at a 3 ms configured receiver target on the quad-core Cortex-A72 reference platform.
Physical audio I/O
SAI/TDM interfaces, lane mapping, codecs, DSPs and board routing remain properties of the OEM hardware.
256 network channels
32 eight-channel streams sustained from ALSA to AES67 on the quad-core Cortex-A72 reference platform.
Two deployment models: integrate Bama Box into an existing Linux product, or use it as the media engine inside a vendor-branded AoIP module. Module partners retain their control plane, timing, physical I/O, routing and customer-facing product identity. Efficient software can free FPGA and SoC resources, creating a path to a simpler module architecture and lower BOM after target-platform qualification. The unified media engine sustained 256 receive and 256 transmit channels simultaneously; physical I/O capacity is established on the target platform. See the technical integration path.
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?
This working adapter provides the receive-evaluation path. Full media-engine evaluation also measures transmit and simultaneous RX/TX operation without forcing a production control-plane decision. See the technology integration path.
JOINT EVALUATION
A clear path from target SoC to production.
The RX and TX paths are implemented. OEM work focuses on proving the business case, measuring each direction and connecting the platform-specific timestamp, clock, networking and audio-interface boundaries.
- 01
Target SoC
Define the Linux build, NIC, timing source, audio interface and required profiles.
- 02
Benchmark
Measure receive, transmit, physical audio 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
Commercial terms matched to the product.
Exact pricing stays private and is matched to product scope, volume, platform and strategic rights.
At shipment
The production royalty is paid when the OEM product ships.
Aligned to the product
Enabled network-audio capacity defines the appropriate commercial tier.
Scaled for production
Production scope and shipment volume are reflected in the OEM agreement.
CONFIDENTIAL OEM DISCUSSION