3 ms·
Publishing is part of the problem. We need to be able to go from Final Cut Pro to web. It has the capability to deliver HTTP Live Streaming, but that's not supp
by mozumder 8y ago
Publishing is part of the problem. We need to be able to go from Final Cut Pro to web. It has the capability to deliver HTTP Live Streaming, but that's not supported in all browsers.
Everything from between "Final Cut Pro" and "Web Browser" needs to be standardized with easy-to-use self-publishing capabilities.
(The CDN can take care of the bandwidth)
- doh 8y agoAll browsers (but Opera mini) support video [0]. There are standards all around video. The challenge is not in getting video from Final Cut Pro to a web browser, the challenge is to do it efficiently, economically with a good user experience. CDN is the tiniest part of the whole process. Each video has to be re-encoded based on the device and network capabilities. CDN can the deliver anything anywhere. Also good video player is needed. Even with HLJ.js and Video.js it's a lot of work to put all of this together in a very user friendly way. And then you want to have cross device support and more. Video is just hard. [0] https://caniuse.com/#feat=video https://caniuse.com/#feat=video
- mozumder 8y agoRight, but the whole process has to be optimized. I mean, Final Cut pro can export videos to Facebook and YouTube, but to export on your own media site is where everything starts to fall apart in terms of user experience.