Quote from a white paper Transitions just completed on fragmented MP4 (fMP4) and MPEG-DASH:
Proponents say that the Common File Format (CFF) and Common Encryption (CENC) scheme will represent two important steps toward large-scale online video distribution via adaptive delivery of fragmented elementary streams.
Since CFF can also be used outside of the bounds of UltraViolet, significant interoperability may also exist between UltraViolet disc-based playback and online video platforms, in much the same way that the DVD Forum’s published specifications for DVD playback guaranteed interoperability between DVD players. It’s not out of bounds to think of CFF as the DVD standard for the web.
To get a better understanding of the power of fragmented MP4, first look at the sidebar in the white paper on "combinatorial complexity" for which Netflix contributed a real-world example. Even without CFF and CENC, Netflix is proving the case that fMP4 scales much better than the HLS approach (with a far lower asset management impact).
The white paper has been several months in the making, starting first as separate concepts by two key companies in the streaming space: Adobe Systems and Microsoft Corporation. Each has their proprietary solutions, but both are committed to seeing fragmented MP4 (fMP4) offer a potentially viable alternative to legacy streaming solutions.
After several meetings, both companies chose to jointly work with Transitions to create a white paper noting the benefits of fMP4 and, to a slightly lesser extent, the potential benefits of MPEG-DASH (a proposed standardization of dynamic streaming over HTTP that I mentioned in a prior blog post).
Special thanks to Microsoft and Adobe for providing financial resources and access to subject-matter experts, who spent time expanding on key concepts and the ever-changing nature of fragmented MP4 and the MPEG-DASH ratification process.
The full white paper can be found here.
[Addition: Adobe and Microsoft have both published blog posts, outlining their support for fMP4 and mentioning reasons for working together: Adobe's Kevin Towes blog post Microsoft's Chris Knowlton blog post]
Proponents say that the Common File Format (CFF) and Common Encryption (CENC) scheme will represent two important steps toward large-scale online video distribution via adaptive delivery of fragmented elementary streams.
Since CFF can also be used outside of the bounds of UltraViolet, significant interoperability may also exist between UltraViolet disc-based playback and online video platforms, in much the same way that the DVD Forum’s published specifications for DVD playback guaranteed interoperability between DVD players. It’s not out of bounds to think of CFF as the DVD standard for the web.
To get a better understanding of the power of fragmented MP4, first look at the sidebar in the white paper on "combinatorial complexity" for which Netflix contributed a real-world example. Even without CFF and CENC, Netflix is proving the case that fMP4 scales much better than the HLS approach (with a far lower asset management impact).
The white paper has been several months in the making, starting first as separate concepts by two key companies in the streaming space: Adobe Systems and Microsoft Corporation. Each has their proprietary solutions, but both are committed to seeing fragmented MP4 (fMP4) offer a potentially viable alternative to legacy streaming solutions.
After several meetings, both companies chose to jointly work with Transitions to create a white paper noting the benefits of fMP4 and, to a slightly lesser extent, the potential benefits of MPEG-DASH (a proposed standardization of dynamic streaming over HTTP that I mentioned in a prior blog post).
Special thanks to Microsoft and Adobe for providing financial resources and access to subject-matter experts, who spent time expanding on key concepts and the ever-changing nature of fragmented MP4 and the MPEG-DASH ratification process.
The full white paper can be found here.
[Addition: Adobe and Microsoft have both published blog posts, outlining their support for fMP4 and mentioning reasons for working together: Adobe's Kevin Towes blog post Microsoft's Chris Knowlton blog post]
Posts
