4 ms·
I'm impressed you guys encode that much. I don't think you're the common case. The case where WebM dies is that everyone continues to encode with H264 (which
by kenjackson 16y ago
I'm impressed you guys encode that much. I don't think you're the common case.
The case where WebM dies is that everyone continues to encode with H264 (which is what they're doing now). If you're IE or an iOS device you get raw H264. If you're Chrome or Firefox you get H264 in Flash.
You just encode H264 and that's it. Now dual encoding, and you work everywhere.
Whereas with WebM there is NO delivery mechanism to iOS devices (iOS won't play WebM and won't play Flash). You have to dual encode to get those devices. Just seems like a less likely scenario.
- rbanffy 16y ago> I'm impressed you guys encode that much. I don't think you're the common case. Compared to the effort it takes to produce the content, encoding is negligible. We have a complete studio and a dedicated team producing a couple hours of original material every week. Originals are kept as uncompressed as possible storage-wise and are captured at the highest quality the equipment allows. Encoding happens in a server that's nowhere near capacity. I proposed a presentation on it at the last FISL but it didn't make the cut (for which I am glad - two others did and it was quite enough work preparing them).