F35: Tutorial - How to Record & Extract VFR and Ramp Footage from F23/F35 with Odyssey 7Q

I'm not sure that what's being proposed here is post ramping. The camera is ramping, producing correct motion blur for the effective frame rate. It's just padding the output with duplicate frames so that the recording is always at (almost ) 60p. The postprocessing is intended to remove the duplicate frames, as the Sony recorder would have done automatically based on SDI metadata.

It would probably not be that difficult to write code to allow a recorder to read and act on this Sony-proprietary metadata, but I can understand why the likes of Convergent Design and Atomos probably don't think it's a particularly worthwhile way to spend their time, given the tiny audience. Shame.

I would reiterate the idea that recording ProRes and doing dupe frame removal with something like ffmpeg would probably be less fiddly, and I don't think it would necessarily be that much more or less of a time sink simply because the files would be so much smaller.

P
 
I'm not sure that what's being proposed here is post ramping. The camera is ramping, producing correct motion blur for the effective frame rate. It's just padding the output with duplicate frames so that the recording is always at (almost ) 60p. The postprocessing is intended to remove the duplicate frames, as the Sony recorder would have done automatically based on SDI metadata.

It would probably not be that difficult to write code to allow a recorder to read and act on this Sony-proprietary metadata, but I can understand why the likes of Convergent Design and Atomos probably don't think it's a particularly worthwhile way to spend their time, given the tiny audience. Shame.

I would reiterate the idea that recording ProRes and doing dupe frame removal with something like ffmpeg would probably be less fiddly, and I don't think it would necessarily be that much more or less of a time sink simply because the files would be so much smaller.

P

Takes a different set of programming skill to use ffmpeg and to write alogrithms to compare images that are not binary byte-for-byte matches. I agree it is sound in theory, and would likely work well in practice, but its not code that I know how to write.
 
So I understand, you're manually triggering when and at what rate the ramp takes place, yes? That was all I meant- that it's a deliberate action based on what you're seeing in frame and not a reflexive editing cliche done in post.
 
So I understand, you're manually triggering when and at what rate the ramp takes place, yes? That was all I meant- that it's a deliberate action based on what you're seeing in frame and not a reflexive editing cliche done in post.

Yes, manually and intentionally triggered. Although, I do have some interest in trying to link the ramp timing to motorized pan/tilt/slide moves with Kessler Second Shooter or Cinedrive systems.
 
I wonder if the KiProMini could deal with F23/35 Ramps the same way it deals with ramps from my HDC27 Varicam? If so, it would be a much simplier process but given the KiPro only gets 4:2:2 i guess the quality would not be as good
 
I wonder if the KiProMini could deal with F23/35 Ramps the same way it deals with ramps from my HDC27 Varicam? If so, it would be a much simplier process but given the KiPro only gets 4:2:2 i guess the quality would not be as good

I have the Ki Pro Mini and an F35, I could try out.
 
Back
Top