The meeting focused on discussing the scope and potential work of the SVTA group regarding encoding and packaging technologies, with particular attention to automation APIs. Yuriy shared information about existing proprietary APIs used by Online Video Platform (OVP) vendors and cloud services like AWS, explaining how these systems handle content delivery and encoding workflows. The group debated whether to standardize existing APIs or focus on defining recommended parameter sets for encoding and packaging functions. Alex raised concerns about potentially endorsing specific vendors through API standardization, suggesting a safer approach would be to create generic parameter recommendations and safeguard ranges rather than defining specific API implementations. The discussion concluded with plans to develop a document listing recommended parameters for encoding and packaging, with Yasser and Alex volunteering to help compile this information.
- Yasser: Start compiling a list of encoding and packaging parameters from previous presentations (e.g. from document 277) for the new reference document
- Alex: Help with 264 parameters for the new reference document
- Yuriy: Share the latest version of the OVP API document with Yasser
- Team: Solicit a presentation about Quick as a contribution protocol, specifically from Wendell
- Alex: Investigate possibility of showing GAI and LCD implementations at NAB booth with DevGIS
- Antitrust Statement & Media Encoding Automation Protocols
- Yuriy and Yasser discussed contribution protocols and automation in media encoding workflows.
- Yasser explained the concept of using signaling and control plane information to automate encoding processes, particularly regarding audio and video formats.
- Yuriy interpreted this as similar to proprietary APIs used in cloud environments like AWS, where developers can access and integrate with underlying media tools and frameworks through API calls.
Online Media Platform APIs Discussion
- Yuriy and Yasser discussed online media platform APIs and workflows, focusing on how content is processed and delivered.
- Yuriy explained that OVPs (Online Video Platforms) use standardized APIs for tasks like content ingestion, transcoding, and playback, though these APIs vary in syntax between vendors.
- He shared details about a document outlining key APIs used in media processing systems, including CMS APIs, ingest APIs, and playback APIs, noting that major OVPs and cloud services like AWS offer similar functionality through their media services.
Online Video Platforms Discussion
- Yuriy and Yasser discussed the role of Online Video Platforms (OVPs) in the media industry, explaining that OVPs act as middleware between content providers and distributors, offering services like registration systems and API management.
- Yuriy described the business model of OVPs, which typically charge based on data delivery and resell CDN services to smaller media publishers, offering control over the viewing experience that native services like YouTube and social networks do not provide.
- The conversation touched on how OVPs cater to different market segments and price tiers, with Yasser inquiring about the relationship between SVTA’s encoding and packaging work and the broader OVP ecosystem.
API Automation and Documentation Planning
- Yuriy and Yasser discussed creating clarification documents and exploring automation APIs for the industry.
- Yuriy proposed creating an extended list of APIs from different vendors, including AWS Elemental and Media Convert, which Yasser expressed interest in reviewing.
- They also touched on the trend of cloud-based processing and edge-level APIs, with Yuriy mentioning that Cloudflare offers transcoding services.
- The discussion included a brief overview of existing standards, such as MTEG’s network-based media processing and 3GPP-based ecosystem, though these standards appear limited in use.
API Implementation and Vendor Concerns
- The team discussed API implementation approaches for encoding and delivery settings.
- Yuriy and Yasser explored examining existing APIs to identify commonly used parameters, while Alex raised concerns about potentially endorsing proprietary vendors through this approach.
- Alex suggested focusing on open-source solutions like FFmpeg, X264, X.265, and SVT-AV1, while creating generic parameter recommendations rather than supporting specific proprietary APIs.
- The discussion remained open about how to balance practical implementation with avoiding vendor endorsement issues.
Content Profile Generation Parameters Discussion
- The team discussed defining parameters for content adaptive profile generation, with Yasser offering to start compiling a list of parameters based on previous work.
- They agreed to seek a presentation on Qlik from Gwendal, who is working on contribution protocols.
- The group also discussed the upcoming NAB booth where they could showcase their work, including GAI and LCD implementations, with Alex taking the lead on exploring options for displaying these technologies.
Next Meeting: Wednesday, April 8, 2026 9am PDT