Research and publish the best content.
Get Started for FREE
Sign up with Facebook Sign up with X
I don't have a Facebook or a X account
Already have an account: Login
Video Breakthroughs
242.6K views |
+1 today
Monitoring innovations in post-production, head-end, streaming, OTT, second-screen, UHDTV, multiscreen strategies & tools
Curated by
Nicolas Weil
 Your new post is loading...
Your new post is loading...
Scoop.it!
WebM is surely one of the hotest streaming topics right now, because WebM is one of the two final HTML5 video standards with H.264. When Google bought On2 in 2009 and open-sourced its latest VP8 codec one year later, two promises were made : providing a codec which quality can compete with H.264 , and providing it in a royalty-free way. On the quality point, the general opinion is that the VP8 codec is slightly less performing than H.264– but it can be an acceptable trade-off regarding the royalties point.
Precisely, the royalty-free point is the one which raises the more questions now, as MPEG-LA is said to have a lineup of 12 patent owners ready to claim their rights on intellectual property, as VP8 would use compression techniques taken from H.264. Seeing their fight against Google being a success would cause a major setback in HTML5 standardization efforts around open source solutions – WebM then being another coding technology subject to royalties after H.264. Nevertheless, the patent war has not started yet and WebM is still a good alternative to H.264, on the paper. And that’s why we are curious to know how we can implement it in our existing or upcoming workflows.
So let’s walk through the different steps of the WebM streaming workflow ! 
Scoop.it!
Maybe some of you remember the Tarari Encoder Accelerator for Windows Media which came on market in 2005 as a FPGA loaded PCI board. It was a 10K$ investment but it could seriously boost your encoder performances and it was a transparent solution for all encoders integrating Windows Media SDK. That was maybe the only real reliable option to do HD encoding decently at that time. More confidential were the Ambric cards for accelerating MainConcept H.264 and MPEG-2 SDK, which were found to be working with Inlet Armada transcoding farm.
|
Scoop.it!
NAB 2012 closed its doors two weeks ago, so it’s a good time to draw an appraisal on various themes concerning OTT issues, and especially premium OTT issues, that have been handled through industry technology offer during the tradeshow. Here we’ll go from production to distribution and examine the salient NAB facts and products, at least the ones which have a potential influence on OTT workflows evolution in the coming months (or years ?).
Tom George's comment,
May 16, 2012 11:04 PM
Great Scoop.it topic. Question. Would you like to share your scoops on http://www.internetbillboards.net? We are building a community of curators who all use Scoop.it and you would really be great. I think I could create a new category in video for you.
Scoop.it!
There are basically two ways to sustain the extensive growth of video formats that you must, as a media distributor, serve to your different clients’ target devices : the most common answer is to choose the best in breed most-powerful encoders to prepare all the target formats during the content preparation time (see Panorama article N°1 on this topic), but you can adopt a different approach saying that you want to prepare your contents once and have the distribution part of the overall workflow take care of the repackaging and protection of the contents on the fly.
Server-side repackaging of the streams consists eventually in : - choosing languages in audio and subtitle tracks available in the original mux (optional) - transcoding/transrating the video content in different sizes/bitrates from a high quality video file (optional) - applying a DRM compatible with the output format (optional) - generating the manifest file corresponding to the target adaptive streaming technology (mandatory) - remuxing and chunking the video data according to the output protocol requirements (mandatory) Historically, repackaging was pushed as a quick solution for broadcasters to add iOS streams on top of existing Smooth or Flash streams. In a wider OTT/Adaptive Bitrate perspective, this alternative approach means : less files to manage in the main production workflow, less storage, less bandwidth to populate the origin servers, smaller time to contents’ online availability and easier support for new formats – shortly said, an agile path. Potentially a risky one, but quite attractive… Let's examine the available options on the market, to do it on your own platform or in the cloud !
|
Le replay du webinar est visible en ligne :
http://web.dbee.com/dbee/20121218/index.php