Proper workflow for dealing with 30P footage...

TheDeanster wrote on 10/25/2008, 9:12 PM

Any of you guys working with 30P footage? And then rendering out to 30P?

I sent a still from from a rendered out video to a friend and he said that my workflow isn't set up correctly because the still picture has a blur to it. Part of the picture is crystal clear but in areas where there is movement, there is some blur. He is saying that had I followed the correct workflow, this picture would and should have no blur.

So, when dealing with 30P footage, what is the "proper" workflow and how should I have things setup? I'm bringing in 30P footage shot with my Sony Z7U. I want to edit it and render it out at 30P as an M2T file.

Thanks in advance for your time!

Comments

TheHappyFriar wrote on 10/25/2008, 9:29 PM
30p is 30p, even if you render it out to interlaced, it's 30p footage with an attribute saying it's 60i. Just like if you took 4:3 footage & put a 16:9 tag on it, it's 4:3 but will play stretched.

Make sure Vegas it setup for 30 fps progressive. *IF* he's seeing interlace blur he can just change the properties to progressive (and his project) and it should work. But if it's not interlace blur, all images (still from a still camera or video from a motion camera) have blur if the shutter isn't fast enough. Doesn't matter if it's 1000000fps or 5fps.

EDIT: this guy using vegas too?
ScorpioProd wrote on 10/25/2008, 11:27 PM
Should one always use Vegas for encoding for DVD or Blu-ray with 30p footage? I notice that DVD Architect 5 doesn't have any templates for 30p.
TheDeanster wrote on 10/26/2008, 2:16 AM
I figured out the issue. My footage was 29.97 but when I rendered it out ...I had it set to render out at 30. What happened was I was getting a ghosting effect. When I switched the render back to 29.97, the effect was gone and the footage is much sharper and more clear.

So this bring up a question....I thought 29.97 was 30P. Apparently there is a difference. My Sony Z7U is setup to shoot 30P but when I right click on the footage it says 29.97. What's the deal with that? I thought my footage was 30P and so I had it set to render out at 30P. My footage is actually 29.97 and setting it up to render out at 30P is what gave me trouble :/

Heeeeeeelp!!!
John_Cline wrote on 10/26/2008, 3:29 AM
No, 30P is really 29.97. Calling it "30" is just technically inaccurate shorthand. Just like "60i" is actually 59.94.
TimTyler wrote on 10/26/2008, 9:03 AM
Frame Rate: 29.97
Field Order: None (Progressive)
johnmeyer wrote on 10/26/2008, 9:37 PM
John,

I am confused. I thought 29.97 was the same as 59.94i which is usually referred to as 60i. I thought 30p really was 30 frames per second, progressive, which is a completely different thing from 29.97.

Am I wrong? (Probably ...)
John_Cline wrote on 10/26/2008, 9:59 PM
In my experience, 30P has always been 29.97 progressive frames per second.
johnmeyer wrote on 10/27/2008, 10:44 AM
In my experience, 30P has always been 29.97 progressive frames per second. OK, that's what I thought too. We're on the same page after all.
TheHappyFriar wrote on 10/27/2008, 11:01 AM
we should probably say "30 NTSC" as that's what Vegas uses. 29.97= NTSC fps. If you talked to someone who wasn't in NTSC land (aka anyone who ISN'T in video but still uses frames) 30p = 30 frames per second, not 29.97.