Seth Bloombaum
September 14th, 2009, 04:14 PM
I've been avoiding shooting in 24p - prefer better temporal resolution and such.
However, I was shooting for a friend's project at a bicycle race, and he's all about 24p for this stuff.
Shot with my Sony HVR-V1u, set to HDV-24pa (the mode that starts each clip with a fresh pulldown cadence). (Sony's approach is to add pulldown and record in a 1080-60i stream)
Ingested using Vegas Pro 8.0c, using Vegas' internal HDV capture app, with "enable hdv scene detection" checked.
Most of the clips are fine, and play perfectly from the timeline at full framerate best/full in a 24p project. about 7 of them don't. These play at about 8fps, and show motion ghosts.
After some tracking through clip properties & such, I realized that Vegas is identifying these clips as 29.97 interlaced. Resetting them to progressive-none in properties helps some with playback rate, but still have motion ghosting & excessive judder & such. The "good" clips are all correctly identified as 24p, and play beautifully.
I'm about to try some recaptures, but was wondering if anyone else had run into this, and what their solution was? Is there a way to rewrite the framerate in the m2t header?
To forestall questions - yes, the cam was set up properly for 24pa. No, the camera settings for these clips didn't change at all. The "problem" clips are scattered through the tape...
However, I was shooting for a friend's project at a bicycle race, and he's all about 24p for this stuff.
Shot with my Sony HVR-V1u, set to HDV-24pa (the mode that starts each clip with a fresh pulldown cadence). (Sony's approach is to add pulldown and record in a 1080-60i stream)
Ingested using Vegas Pro 8.0c, using Vegas' internal HDV capture app, with "enable hdv scene detection" checked.
Most of the clips are fine, and play perfectly from the timeline at full framerate best/full in a 24p project. about 7 of them don't. These play at about 8fps, and show motion ghosts.
After some tracking through clip properties & such, I realized that Vegas is identifying these clips as 29.97 interlaced. Resetting them to progressive-none in properties helps some with playback rate, but still have motion ghosting & excessive judder & such. The "good" clips are all correctly identified as 24p, and play beautifully.
I'm about to try some recaptures, but was wondering if anyone else had run into this, and what their solution was? Is there a way to rewrite the framerate in the m2t header?
To forestall questions - yes, the cam was set up properly for 24pa. No, the camera settings for these clips didn't change at all. The "problem" clips are scattered through the tape...