FCP 5.1.2 capture drop-frame media to a non-drop frame clip BUG?

[Mark Maness]

I have seen this one many times myself.

The only solution I have used was to restart the computer and try it again. Most of the time it works, other times, I have to create a new clip and capture that clip instead.

Have you seen the changing timecodes, yet? Sometimes when I redigitize a clip, the timecode gets shortened by some various length. This happens alot too.

_______________________________

Wayne Carey
Schazam Productions
http://www.schazamproductions.com

[Peter]

It just cropped up this morning so I haven’t gone any further with the project on that computer….Huh, from your expereince and what a lot of other are saying the most up-to-date combo is really problematic with digitzing and time code. Someone mentioned QT 7.1.3 being the issue. Do you have any idea if Apple is aware of this and/or how to submit a bug report to them?

thanks in advance.

[Mark Maness]

[Peter] “Do you have any idea if Apple is aware of this and/or how to submit a bug report to them?”

Well, Peter, everytime is happens, I submit a feedback form and hopefully everyone else is doing the same. As for this issue, its been happening ever since upgrading to version 5.1.2. But we use the XDCM HD system and this update was necessary to us.

_______________________________

Wayne Carey
Schazam Productions
http://www.schazamproductions.com

[Peter]

I think it can be traced to 5.1.2 too. I have OS 10.4.8 and QT 7.1.3 on another computer with FCP 5.0.4 and everything is fine. I’ll submit a form as well – thanks for your input.

[Jeremy Garchow]

To complicate matters, this started for me after updating to 7.1.3 (when the the latest version of iTunes came out). This was before I even had 5.1.2.

Jeremy

[Peter]

I just made a report to apple – not easy to find this page on their site, https://www.apple.com/feedback/finalcutpro.html

Hopefully it’ll be addressed in the update…

[Gary Adcock]

I saw the later stages of these posts and want to ask a dumb question.

Are you trying to capture to 24p ( 23.98) from the 29.97 SD stream?

if so this warning is correct (but annoying)

gary adcock
Studio37
HD & Film Consultation
Post and Production Workflows

[Peter]

I am trying to capture 24p panasonic material when this happens. I’ve done it many many times though via the DV-NTSC 29.97 easy setup on other computers pre FCP 5.1.2 and never had a problem. It’s the old standard way of capturing 24p normal mode into FCP.

[Gary Adcock]

[Peter] “I am trying to capture 24p panasonic material when this happens. I’ve done it many many times though via the DV-NTSC 29.97 easy setup on other computers pre FCP 5.1.2 and never had a problem. It’s the old standard way of capturing 24p normal mode into FCP”

I guessed that.
It’s that FCP has gotten smarter in the latest builds.
24p (23.98) content is Non Drop and 29.97 is Drop Frame.

So the dialog is actually correct, even if you have never seen it before, it is just that with al of the changes in FCP to capture 24p materials Apple has added the dialog to make sure that users understand that they are changing the timebase of the content they are capturing.

gary adcock
Studio37
HD & Film Consultation
Post and Production Workflows

[Jeremy Garchow]

[gary adcock] “It’s that FCP has gotten smarter in the latest builds”

FOr every reaction, there is an equal but opposite reaction. This happened to me recently (I know there’s a thread on it somewhere) where I captured regular DV-NTSC over firewire for the first time in a really long time. The footage was regular ole dv, not 24p, and I’d get that message. After capturing, the timecode and other metadata would disappear from the browser. It was frustrating to say the least. My hunch was that the latest version of Quicktime has busted it because it started happening after that update. I have not seen this error in a while, but it’s been a pretty HD filled fall and winter and I capture that w/ the Kona and it’s been no worries there except for some weird 10 bit scaling, but that’s another matter.

Jeremy