Post by Promwad Engineering

5,511 followers

๐—ฃ๐—ผ๐—ฟ๐˜๐—ถ๐—ป๐—ด ๐—ฎ๐—ป ๐—ฆ๐——๐—œ-๐—ฎ๐—ป๐—ฐ๐—ต๐—ผ๐—ฟ๐—ฒ๐—ฑ ๐˜ƒ๐—ถ๐˜€๐—ถ๐—ผ๐—ป ๐—บ๐—ถ๐˜…๐—ฒ๐—ฟ ๐˜๐—ผ ๐— ๐—ซ๐—Ÿ-๐—ป๐—ฎ๐˜๐—ถ๐˜ƒ๐—ฒ ๐˜€๐—ผ๐—ณ๐˜๐˜„๐—ฎ๐—ฟ๐—ฒ ย  A tier-one vision mixer vendor was losing points on broadcaster RFPs. The product was strong, but its media engine was welded to an FPGA pipeline and a proprietary chassis, with no credible answer to the software-defined production that customers are now buying. ย  We led the MXL SDK integration: decoupling the media engine from the FPGA, re-homing it in MXL-native C++20, and keeping SDI and ST 2110 I/O as edge adapters so existing deployments kept running. The outcome was sub-frame latency on commodity hardware, a Kubernetes-ready container image on x86_64 and aarch64, and two broadcaster pilots signed within one quarter of the first public demo. ย  At Promwad we port shipping broadcast products into MXL-native software: protocol-to-protocol porting, multi-arch container builds, and interop validation, with your existing codebase treated as IP to preserve rather than rewrite. ย  ๐Ÿงท If your broadcast product is still anchored to dedicated hardware while your customers move to shared COTS hosts, this is the kind of port we scope and deliver. See how our MXL SDK integration works: https://lnkd.in/d6WV8dut ย  #Broadcasting #MXL #ST2110 #PromwadCase

Post content