Variable Framerate Capture Problems (Varicam / HD1400VTR / FCP)

[Walter Biscardi]

[TimSnider] “The problem is encountered when capturing the 60fps footage. I get similar results to Athen Ross in that I don’t get all of the clip. Only about a third of it. For example if I mark my in/out points to show a duration of 00:47:15, upon capture I only get 00:18:22. I’ve tried changing the device control preset to have it look at VITC instead of LTC, but that doesn’t work. Also using Firewire deck control doesn’t work either.”

This is absolutely correct. You need to switch over to 720/59.94 in order to capture the entire clip if it’s truly shot at 60fps. Otherwise you’re capturing it at slow motion and what you’re seeing is normal behavior.

If you want slow mo, capture at 59.94 then use the Frame Rate Converter to convert.

Walter Biscardi, Jr.
https://www.biscardicreative.com
HD Editorial & Animation for Food Network’s “Good Eats”
HD Editorial for “Assignment Earth”

“I reject your reality and substitute my own!” – Adam Savage, Mythbusters

[Tim Snider]

Thanks, Walter. I have found that when capturing 60fps material via the Kona 2 using a capture preset of “AJA Kona 2: 720p 23.98…”, the clips are set to the desired 23.98 frame rate so I can immediately see the slow-mo effect of overcranking. Is there no way to get around the timecode issue? Using the Frame Rate Converter is ok, but certainly slows down the workflow to have to address individual clips. Any ideas?

Thanks again.
Tim
Deja View Media, Inc.
http://www.dejaviewmedia.com

[Walter Biscardi]

[TimSnider] “Is there no way to get around the timecode issue? Using the Frame Rate Converter is ok, but certainly slows down the workflow to have to address individual clips. Any ideas?”

No. FCP is actually capturing the expected amount of footage. That is, it is truly capturing for 47 seconds as you set. BUT, when you’re done, you end up with a slo mo shot or only 18 seconds or so of final footage. So Final Cut Pro is doing what it’s supposed to do, it starts at the In Point and ends at hte Out Point of your capture, but since you’re capturing in slow mo, you end up with a much shorter clip.

the only workaround is to set your Out Point much further down the road than you think you need.

Walter Biscardi, Jr.
https://www.biscardicreative.com
HD Editorial & Animation for Food Network’s “Good Eats”
HD Editorial for “Assignment Earth”

“I reject your reality and substitute my own!” – Adam Savage, Mythbusters

[Gary Adcock]

[walter biscardi] “This is absolutely correct. You need to switch over to 720/59.94 in order to capture the entire clip if it’s truly shot at 60fps. Otherwise you’re capturing it at slow motion and what you’re seeing is normal behavior.”

That behavior depends on which build of the K2 Driver.
( Tim– send your driver and bit file info from the kona control panel)

In the 2.x version what you are getting could be correct, as FCP would have captured the 60FPS content as 23.98 (still the same amount of time- but less frames) – but in the 3.x driver versions it should have accommodated the flags on the 60FPS content and captured it accordingly (i.e.: making it 2.5x slower )

But if the content is NOT originally shot at 60FPS it would capture as indicated.

What does the Kona Control panel tell you the frame rate of the shot is? ( Timecode + show user bit box checked)

However
Tim is working with a non standard-config of FCP 5.04 along with 10.4.8 and QT 7.1.3 that is NOT recommended so his functionality may vary.

gary adcock
Studio37
HD & Film Consultation
Post and Production Workflows