June 2024 Summaries

Content piracy remains a significant issue in today's digital age, with estimates suggesting it costs between $25 and $70 billion annually. The problem affects all parties involved in video streaming, from creators to infrastructure service providers. Piracy can harm the reputation of companies hosting content, leading to potential blacklisting by vendors or loss of business from legitimate customers. Content owners are also affected as pirated streams can damage their brand and discourage new partnerships. To combat piracy, a balance must be struck between the effort put into protecting content and the willingness of pirates to circumvent these measures.

Mux Player now supports chapters, allowing users to split videos into titled sections for easy navigation. To create chapters without manual input of timestamps, a Node.js script can be used in conjunction with OpenAI's AI LLM (large language model). The process involves uploading a video to Mux and enabling auto-generated captions, then using the captions as input for the AI LLM to generate chapter titles and timestamps. This automation simplifies the process of creating chapters for videos and enhances user experience by allowing them to quickly access content they are most interested in.

At Mux, the company's mission is to democratize video on the internet so customers can build amazing experiences around it without worrying about the hard things that go into engineering video at scale. Velocity is key to achieving this mission, as it allows the company to ship products quickly and innovate. However, managing cost, scope, and speed has proven challenging when engineering video at scale. The company realized that its 6-month planning cycles were causing inconsistent focus and slowing down velocity. To address this, Mux implemented a new 6-week planning and execution cycle, closely aligning planning and execution to match the natural cadence of the business. This change allowed for increased feature velocity, complexity, and innovation, while maintaining focus and adaptability. By striking the balance between speed, scope, and cost, Mux aims to be at the center of the Iron Triangle, enabling customers to build amazing video experiences with ease.

Video encoding always involves some quality loss due to compression processes. The goal is to achieve the best possible compression for a specific use case while considering factors like compatibility with players, deliverability over the internet, time to encode, cost to store, and perceptual quality (PQ). PQ measures how close an encoded video looks compared to the original source video. Lossy compression is often used in video encoding as it allows for significant reduction in file size but results in imperfect reproduction of the original content. Popular algorithms for estimating PQ include PSNR, SSIM, and VMAF. Achieving a high-quality video involves balancing factors like bitrate, cost, and usability to ensure optimal viewing experience for end users.

Digital Rights Management (DRM) is a set of technologies used to provide an extra layer of content security for video content through encryption and licensing. It helps protect copyrighted content against piracy by blocking or limiting the impact of screen recording, screen sharing, downloading tools, and other content security concerns that can't be completely addressed with traditional security tools like signed URLs, referrer, or user agent restrictions. DRM is commonly used in streaming video services to protect high-value content from unauthorized access and distribution. However, implementing DRM can increase costs and may also introduce friction for viewers, potentially pushing them towards piracy. Therefore, it's essential to find the right balance of security and viewability when using DRM in a video service.

A recent bug at Mux involved daily disconnections of live streams using Secure Reliable Transport (SRT) but not RTMP, all occurring at the same time each day. The problem was traced to a timestamp issue where PES timestamps wrapped around roughly every 26.5 hours due to their limited range in MPEG-TS format. This caused Mux's timestamp rewriter to interpret the timestamps as going backwards, leading to disconnections or slate insertions. The fix involved handling wraparound in the PES timestamps by treating it as a normal monotonically-increasing timestamp. Lessons learned include considering all permutations of data types, leveraging monitoring tools for problem diagnosis, and staying prepared for unforeseen edge cases.