Spent some time over at theora. If you're running that stuff voluntarily,, you should be able to figure it out. I can't make heads or tails out of the descriptions because they seem to indicate you must have not only the components to handle comrpession, you must also have a playback component. That cannot possibly be correct but that's what they say about QT7. Insane.
*Xiph QuickTime Components (XiphQT) is, in short, the solution for Mac and Windows users who want to use Xiph formats in any QuickTime-based application, e.g. playing Ogg Vorbis in iTunes or producing Ogg Theora with iMovie.*
*Learn more about XiphQT...*
*14.06.2009 - XiphQT 0.1.9 released*
*We're happy to announce XiphQT release 0.1.9!*
*This is another bugfix release, where fixes are few but significant: reduced memory usage, fixed playback of HD content and fixed compatibility with iMovie '08. As always, release notes have a bit more details.*
*Also, the official 0.1.9 builds have been linked against recent versions of codec libraries. Most notably, that means Theora release 1.0, bringing performance improvements, especially in encoding.*
Thanks for looking into that David. Yeah, html5 doesn't really play anything. It all depends on the browser. Safari plays anything your quicktime plays, but ff, google chrome, and opera don't use anything with the h.264 codec. ie, firefox, chrome, opera, and android are all going to the webm codec. So apparently when you encode video for html5, you need 3 different files. One in an mp4 wrapper with a h.264 video file for safari, iphone, and ipad, one in an ogg wrapper with a a theora and vorbis codec, and one with a webm codec. My problem is actually getting my source footage compressed correctly into those codecs so they play on everything other than safari since i seem to be able to make nearly any codec play on safari. It might just be easier to convert the world to safari. who knows?
Looking for a solution for converting OGG/Theora & WEBM with Apple Compressor4. Miro only has one compression setting and doesn't intergrate with the FinalCut / Compressor workflow. This is a major oversight on Apple's part.
Any info would be helpful. OGG & WEBM are needed for HTML5 video, this is not the some wacky edge case.
I agree that it's a major oversight. Everything I've tried to do with HTML5 ends up being a huge workaround.
I'm curious as to what you are trying to accomplish. I take the final version of the video out of Compressor as an H264 and feed that through Miro to output the OGG and WEBM. I don't think I've ever tried to put an OGG back through Final Cut. If further edits are required I'm forced to edit the original Final Cut doc and output it again and convert it again. A huge pain, but that's the only way I've found to do it ...
Been playing with OGG and WebM recently and my workflow has been as follows:
FCP > Quicktime Conversion > H.264
Using the Firefox plugin Firefogg to then convert that to OGG or WebM. Easy setup, few clicks and you are on your way. Or you can tweak some advanced options.
Using Export > Quicktime Movie does NOT work (at least with a ProRes timeline). You get an audio file without video for both WebM and OGG conversions.
Hope this helps!
Just wanted to throw out an overview of the landscape of delivering video to a browser.
The HTML5 way:
- H.264 in mpeg 4 for Internet Explorer, Safari, iOS, and Android (although I think H.264's days in Android are numbered, like they were for Chrome)
- WebM or Theora for Firefox, Chrome, Opera, and Android
- Flash backup needed for people with older browsers
- Conditionals you have to code to serve the right video to the right browser.
The Flash way:
- It quite simply works for everyone except iOS clients. You can add on Adobe Flash Media Server to send flash video to the crippled iOS devices.
You can **** around with this fantasy world, but today HTML5 video is as much bag of hurt as HD-DVD
HTML5 video a "bag of hurt"? What is Adobe Flash Media Server? A Matrix of Hurt? Everything in digital video has a bloody learning curve.
My issue is batching my encoding of H.264, WebM & OGG. If my current project could justify Sorensen Squeeze I'd buy it and be done. (Thanks @Shawn Birmingham) I know Sorensen makes great stuff... but that doesn't let Apple & Compressor off the hook. IMO, Apple needs to support HTML5 video workflows.
Thanks for the tip on converting H.264 to OGG/Theora !!!!! I thought that transcoding from H.264 to OGG would kill the quality, but it looks fine for my use. Export > Quicktime Movie >> Miro/ffmpeg > WebM works for me with DV NTSC 48kHz (obviously not using ProRes)
My current workflow
1) Export > Quicktime Movie
#Then I use a bash script to trigger the final conversions with ffmpeg (using Miro settings) and go to bed while my Mac churns away.
2) Quicktime Movie > Miro/ ffmpeg > WebM
3) Quicktime Movie > Miro/ ffmpeg > H.264 (iPad setting)
4) H.264 > Miro/ ffmpeg > OGG/Theora
#My Step 4 starts with the H.264 file because Miro/ ffmpeg OGG doesn't convert my NTSC DV QT to square pixels like it's WebM & H.264 conversions do successfully. (???)
This is far from ideal... but it gets the job done for the moment.
Whilst I can't help with a Mac solution to creating WebM and OGV, I use http://www.xmedia-recode.de/ on Windows. Hope this is useful to some of you.
HTML5 Resources (many include HTML5 video help)
- http://webexpedition18.com/articles/brilliant-and-useful-html5-tutorials-you-mus t-see/
HTML5 Video Resources
I've found the QT components to install that will let you easily render out of QT7. After installing the components, and running a couple of tests, the ogg option in QT seems a bit better quality. You can simply open the vid in QT7 and go to export and find an ogg option or webM option. Simple. I haven't created the Compressor preset yet. I'll play with that later this week. Again, these are third party components that can fit with QT; but not official/approved.