RapidWeaver Forums

yes .movs do work .

And I also have a copy DV kitchen in my toolbox. Although not being a ‘video pro’ I use another way (without these expensive apps) that will be cooked into a special supportcasts classroom for working with video for web

NodeProductions - 01 July 2010 11:08 PM

Regardless, hopefully you find DV Kitchen helpful in other ways for your workflow.

As Kevin corrects, the .mov extension DOES work in the symfoni stack, just not with the x.264 codec that dvKitchen is using.

Jeff, I’ll keep to my workflow of exporting out of FCP. I was just using Visual Hub to convert all my flash videos into HTML 5 compliant files.

Kevin of course told me months ago that html 5 would eventually replace flash. He was, and usually is right. I like his html 5 video stack.

vtbobo,
can you export the settings that you used for sorenson as a “preset” and PM me with a location where I can grab them? Would help me to know the exact settings that you used and were successful with, other than me trying to recreate it. That way I can use it in my tests this weekend.

Kevin,

Good to hear that .mov will work. I had used DV Kitchen successfully with your flowbox stack, but hadn’t tried it yet with the html5 stack.

Jeff / Jamie you both have email

Kevin and I did some testing over the weekend using a motion graphic that I had created for a recent project, and we have arrived at what we believe is a good solution, or at least a solid starting point for anyone using Final Cut Studio and wanting to encode with Compressor, with an output that is compatible with HTML5, iPad/iPhone and has the proper fallback to flash, when used in the SymVideo5 stack.

I started out originally with the article from the Ken Stone site referenced in the earlier post, but found that the apple device starting point in Compressor actually limits your ability to modify a number of the parameters to my liking, so I then moved to a starting point in compressor of the H.264 for Streaming presets. I then modified a number of settings from there, so that my output would be 640X360 (same as the original poster), but modified some of the video bitrates, audio settings, and a couple of other minor tweaks to try and optimize file size for streaming across the web, yet maintaining the compatibility as described above.

Source file was a 1440X1080 ProRes422 file

You can see the resulting video here: SymVideo5 Stack Sample

All of the gory detail of the settings are below the video. I have also attached a droplet to this post that I have created form the Compressor preset, and hopefully this will be a helpful starting point for anyone looking to encode and then use this great stack from SymfoniP. I have also added a screen grab of the original posters video details as currently displayed on their site, along with the same view of the file created with the attached droplet (although it appears to be reading the audio settings a little incorrectly).

Kevin and I tested on Mac (Safari and Firefox), PC (IE7 & Firefox), and on iPhone and iPad. All appeared to work properly across these devices and applications (noting proper fallback to flash where needed, perfectly managed by the SymVideo5 stack).

BTW, I also tried some outputs from DV Kitchen that I referenced earlier, and noted that there is a problem with the X.264 preset recipes from DV Kitchen, in that they will play okay in desktop browsers using the stack, with fallback, but do not play on iPhone or iPad. I haven’t tried to dig into that problem at this point, but wanted to note it here for others to reference.

Hopefully this post & Compressor Droplet are useful starting points. I found that you can play with the frame rates, the bit rates, and the audio settings, and still produce a compatible output, so people should be able to adjust as needed (staying within documented parameters for iDevices) and produce a desired output quality.

Thanks to Kevin for all of his help and assistance during this process as well as producing these great plugins and stacks for us to use. (note that I am not affiliated with SymfoniP in anyway, but their products and customer support has won me over time and again).

Hopefully this information is useful, I know it will help me as I get ready for my site redesign and hosting move.

NodeProductions - 04 July 2010 05:24 PM

Hopefully this information is useful, I know it will help me as I get ready for my site redesign and hosting move.

Extremely useful, thanks Jeff for all the hard work. I will definitely use your compressor droplet and launch for my html5 video stack compressions. Generous of you to include this. And thanks for confirming that DV Kitchen’s recipe is lacking. Hopefully, they will update soon in the future.

I thoroughly endorse your recommendation of Kevin’s work. I too am enjoying this html5 video stack.

Thanks Jeff and Jamie for the kind words and support

Spoke with Jamie earlier today, and we discovered that the droplet I created for Compressor will only work on the new version, 3.5 or greater. If you are working on an earlier version, then if you start out with the presets that are located under: Apple- Other Workflows - Web - Streaming - QuickTime 7 Compatible - H.264 800Kbps Streaming (wow, if you can find that starting point, then you should consider yourself lucky) you can modify the preset to something along the lines of the below settings (or modify to taste), and then either save as a preset or export as a droplet. Files created based on this template should work as stated in my earlier post.

My initial settings preset (yours can vary for video size, video Kbps, Audio settings, etc. but keep within published settings for iDevices and your desired bandwidth targets):

Name: SymVideo5Stack
Description: H.264 video with stereo AAC audio. Settings based off the source resolution and frame-rate.
File Extension: mov
Estimated size: 276.48 MB/hour of source
Audio Encoder
AAC, Stereo (L R), 22.050 kHz
Video Encoder
Format: QT
Width: 640
Height: 360
Pixel aspect ratio: Square
Crop: None
Padding: None
Frame rate: (100% of source)
Frame Controls On:
Retiming: (Fast) Nearest Frame
Resize Filter: Linear Filter
Deinterlace Filter: Fast (Line Averaging)
Adaptive Details: On
Antialias: 0
Detail Level: 0
Field Output: Same as Source
Codec Type: H.264
Multi-pass: On, frame reorder: On
Pixel depth: 24
Spatial quality: 75
Min. Spatial quality: 25
Temporal quality: 50
Min. temporal quality: 25
Average data rate: 0.614 (Mbps)
Maximum data rate: 0.614 (Mbps)
Hinted for QuickTime
streaming server

Hopefully that will help people from earlier 3.X versions. Not sure if these presets existed in the 2.x version of compressor or not. I am no Compressor guru (I am no Brian Gary), but hope this tip helps those wishing to create content for this stack from within FCS.

Excellent Jeff

Jeff’s compression setting works beautifully but beware of updating FCS2 and/or Compressor into a SL environment.

I was getting batch errors and phoned Apple Care who directed me to a six-page re-install that has taken me into Applehell where I have been unsuccessfully trying to reinstall FCS2, Compressor and Qmaster. From the Apple forums, I read that there is a Qmaster daemon that doesn’t allow the installer to finish. My thinking now is that Apple had no intention of supporting Compressor in SL and I may have to spring for the upgrade to get out of this mess.

And yes, I repaired permissions, Disk Warrior, Clean Your Mac and have tried re-installing three times, force quitting the installer each time. Compressor now runs fine; FCP doesn’t run at all.

I am wondering why you set the audio to 22.050 kHz? Just curious as I have spent a lot of time fiddling with settings as well.

GuillermoA - 10 August 2010 04:14 AM

I am wondering why you set the audio to 22.050 kHz? Just curious as I have spent a lot of time fiddling with settings as well.

Can’t tell the difference online so why not save the bandwidth?

Jamie is right. I didn’t hear much if any difference either, so I figured I would save the bandwidth. I also typically up the video bandwidth to 0.8 (Mbps) rather than the 0.614 (Mbps) referenced in my original reply. I did see a difference from most of my content, which is primarily fast motion, and the higher video bit rate helped.