Vimeo settings?
- Thread starter Gladiator
- Start date
sublimesnfu
Well-known member
Are you using FCP - if so open Cinema Tools and select Conform you clip to 30p. It will play back super smooth and you can upload it for the world to enjoy.
So sorry, Premiere Pro CS4. And thank you for your reply! They seem to be few and far between around here.
Have you tried exporting a test clip at 30p?
Doesn't the Adobe Media Encoder have some presets that might assist?
Doesn't the Adobe Media Encoder have some presets that might assist?
I guess I am worried that shooting 720 60p can't be encoded to 720 30p and run smoothly on Vimeo. I downloaded the Vimeo/You Tube compression settings file and they seemed to help. I also uploaded the video to Vimeo and that helped even more, but it is still choppy. It's also not nearly as crisp as in Premiere, it doesn't run smooth in Premiere either.
I transcoded it with Cineform Neoscene to help it run smoother and it helped, but it is still so choppy I can't tell if I have camera shake or not.
My computer is i7 820 with 8gb RAM, GTX260 (1.8 gb), and a seperate drive for my NLE (300gb 10,000 RPM Velociraptor) so I expected it to run pretty smooth, but it doesn't.
I transcoded it with Cineform Neoscene to help it run smoother and it helped, but it is still so choppy I can't tell if I have camera shake or not.
My computer is i7 820 with 8gb RAM, GTX260 (1.8 gb), and a seperate drive for my NLE (300gb 10,000 RPM Velociraptor) so I expected it to run pretty smooth, but it doesn't.
After years of messing with Vimeo I can tell you that the bitrate of your video is going to effect the smoothness of playback more than anything you do with frame rates.
For example, an H.264 at 6Mbps will result in perfectly smooth Vimeo display, yet a 12Mbps or above stream will create a stutter with Vimeo encoding/playback.
For the best results in Premiere -- use the default H.264 HDTV 720/24p export preset -- set it to the frame rate of your project -- and let Vimeo worry about encoding it to whatever frame rate their algorithm prefers this month.
I'm not a Vimeo guy so I can't explain the technicals -- just do the above -- and you'll see it works.
For example, an H.264 at 6Mbps will result in perfectly smooth Vimeo display, yet a 12Mbps or above stream will create a stutter with Vimeo encoding/playback.
For the best results in Premiere -- use the default H.264 HDTV 720/24p export preset -- set it to the frame rate of your project -- and let Vimeo worry about encoding it to whatever frame rate their algorithm prefers this month.
I'm not a Vimeo guy so I can't explain the technicals -- just do the above -- and you'll see it works.
Yes please do send the links. Thanks.
GrahamH
Well-known member
If you are on a PC and have access to AviSynth or Virtualdub, doing the following produces clean 30P from 60P:
Avisource("Cineform720p60.avi")
SelectEvery(2,1)
And if you want to resize, say to SD, add:
LanczosResize(720,480)
I do this because I found Premiere and AME, both of which I use for other things, do a spectacularly bad job of these kinds of conversions.
Avisource("Cineform720p60.avi")
SelectEvery(2,1)
And if you want to resize, say to SD, add:
LanczosResize(720,480)
I do this because I found Premiere and AME, both of which I use for other things, do a spectacularly bad job of these kinds of conversions.
Just wondering if you have tried the new Adobe Media Encoder 4.2.0 and whether Adobe have lifted their game with this version?
GrahamH
Well-known member
To be fair, I should say that I've been using AME4.x regularly to output files at the same resolution and framerate as the source footage, and I have no problem with it for that purpose (but see my last comment). My griping in the previous post was regarding its poor performance when asked to resize and/or change framerate to something other than the source material. For example, try using AME to produce SD Mpeg2 (either progressive or interlaced) from 720p60 material for DVD authoring ... and see if you are happy with the result. I don't think 4.2 has improved on that task, at least.
One thing I saw over the weekend was a post (somewhere? - can't find it now) where a guy was unhappy with a change from AME4.1 to 4.2 in field blending behavior - but I don't recall exactly what the issue was, other than that fields were being blended when the guy didn't want them to be.
One problem I've just ran into is that when I ask AME to render edited 720p59.94 Cineform footage out to a new Cineform 720p59.94 clip, the result is 60.00 with the audio out of sync! If I render out to any other codec I get 59.94 as expected, so it seems somehow related to how AME handles Cineform, but I haven't found anyone else yet who can confirm this problem, so perhaps it's just a quirk of my machine?
Edit: oh I forgot to mention ... here's another reason - the interlaced chroma bug - to be wary of AME (the example clip in that thread was encoded using 4.2.0): http://www.dvxuser.com/V6/showthread.php?t=200584
One thing I saw over the weekend was a post (somewhere? - can't find it now) where a guy was unhappy with a change from AME4.1 to 4.2 in field blending behavior - but I don't recall exactly what the issue was, other than that fields were being blended when the guy didn't want them to be.
One problem I've just ran into is that when I ask AME to render edited 720p59.94 Cineform footage out to a new Cineform 720p59.94 clip, the result is 60.00 with the audio out of sync! If I render out to any other codec I get 59.94 as expected, so it seems somehow related to how AME handles Cineform, but I haven't found anyone else yet who can confirm this problem, so perhaps it's just a quirk of my machine?
Edit: oh I forgot to mention ... here's another reason - the interlaced chroma bug - to be wary of AME (the example clip in that thread was encoded using 4.2.0): http://www.dvxuser.com/V6/showthread.php?t=200584
Last edited:
andythefilmer
Veteran
Nice machine!
Thanks, but I it's actually an i7 860 not 820. Maybe I was wishing for an i7 920 :happy: