Drop-Frame vs. Non-Drop-Frame Capture question

Hi,

I'm using Final Cut Pro 5 capturing 16:9 anamorphic video and removing an advanced 24 frame pulldown from my Canon XL-2. This is for a documentary for which I have captured over 30 full tapes of footage. I've been logging in the clips FIRST, then going back and batch capturing everything afterwards.

My question is this: I have logged everything the same way with seemingly all the same settings. However, when I capture some tapes I get the warning that I'm capturing Non-Drop frame media to a Drop-Frame clip and it could cause problems in the future with relinking. Then some tapes don't give me that message at all. Is there something I'm not noticing about how I log some tapes but not others? Would it have to do with the presets I have Final Cut set to when I'm capturing a tape? I'm fairly positive I've always setup FCP to the proper capture settings before logging anything...but could something else be causing this? Thanks for your help.

-JD

iMac G5, Mac OS X (10.4.11), Using FCP 5, Capturing on Canon XL-2, 24p Adv. pulldown removal, 16:9 anamorphic

Posted on Jan 9, 2008 7:08 PM

Reply
12 replies

Jan 10, 2008 7:26 AM in response to JD Marlow

check your tape by turning on visible timecode in your lcd on camera. if there are semi colons or commas separating the pairs of numbers on screen you have recorded drop frame, if there are colons in the display you have recorded non drop. I usually roll tape a little before I log so the tc mode is noticed by FCP. other than that if you log a bunch of tapes and don't track the reel numbers properly you can get messed up by feeding the monkey the wrong tape.
you can choose to ignore the warning and proceed with capture anyway

Jan 10, 2008 7:36 AM in response to tallguy

Hi tallguy,

Thanks for responding. I have been pretty dilligent about labeling my reels. Everything is setup properly with regard to that. I have been ignoring the error -- it's just irritating because I get time codes captured that are slightly off from what I logged. Why would I be recording drop-frame sometimes and non-drop frame others? I haven't changed any frame settings on my camera -- it's almost always set to 24P advanced.

-JD

Jan 10, 2008 11:03 AM in response to JD Marlow

timecode and canon cameras are notorious. I think the default tc is df I'm trying to remember the options on the tc section of the camera but the picture in my mind is somewhat fuzzy. there can be an issue with the battery that remembers the cmos settings on board the camera. I would log then capture that tape and put it up. the tc on dv can slip and slide as it is parsed to simulate SMPTE and is actually called dv

Jan 10, 2008 12:57 PM in response to JD Marlow

Hi JD Marlow
I hope I am in the proper place. I was referred to this forum & find that your problem relating to capture is similar to my problem relating to preview of sequence: When the playhead reaches a certain location on a clip in timeline, it stops with a report on dropframe. This happens before even adding any effects or filter to the timeline.
I have recorded drop frame (semi colon between zeros) as tallguy says. He also says, "you can choose to ignore the warning and proceed with capture anyway" which seems consistent with what the manual says, "if you're bothered by the reports of dropped frames, during playback, not by dropped frames themselves, you can keep using Unlimited RT and just turn off the reports" from User Preference.
In your case, the two good sources for trouble shooting are: Optimizing your FCP System and the article http://www.csif.org/html/dropframe.html. I hope this help.
However, in my case of previewing sequence can I would like to know how the decision to turn off reports would affect the clips. Would this mean the clips be dropped altogether during outputting? In other words, by keeping to use Unlimited RT how my documentary movie will be affected. I hope you, tallguy or anyone else provide me with some answer. Thank you. golab.

Jan 10, 2008 1:05 PM in response to golab

Dropped frames are different from drop-frames. Dropped frames refer to frames that have not been captured due to a lag in the capturing system whereas *drop-frame timecode* refers to a type of timecode that drops the first two frames of every minute, with the exception of every tenth minute. This is to correct for 30 fps video being broadcast at 29.97 fps when color TV was invented.

To answer your question, you can ignore the dialog box and it will not cause any issues, but you may not be able to play back the clip in real-time. It might judder and skip. To fix this, render the clip.

Jan 10, 2008 8:16 PM in response to Jon Chappell

Hi Jon Chappell
Thank you so much for such clear explanation of the way the two behave. I fully now understand what is what. However, "somenoe said that "by matching the video to my sequent setting I don't have to render the video in the timeline. The only time I have to render is when there a filter/transition applied to the video. (small price to pay)." My question is how to match the video to sequence and how to set the sequence. I would be gratefull if you could kindly tell me how or refer me to an article. Thank you so much. golab

Jan 17, 2008 2:55 PM in response to Jon Chappell

The same thing is happening to me while trying to capture DV Cam tapes using a DSR-11. My main problem with this is that I have a few hundred clips to capture and after every clip during batch capture I get this error message:

"WARNING: A change in the timecode format (Non-Drop Frame to Drop Frame) was detected while capturing clip"

I have to click OK to go to the next clip. This sort of defeats the purpose of batch capturing.

I have a few tapes and they all appear to be recorded in non-drop frame (I have the colon between seconds and frames on my deck's TC display) but one of the tapes captured without any error messages. I used the standard DV NTSC preset.

I've tried playing around with Capture and User settings but nothing seems to work. Is there a way to capture to non-drop frame?

Feb 20, 2008 5:33 PM in response to Jonathan Shearburn1

First of all do the obvious: make sure that in your audio/video settings, under DEVICE CONTROL PRESET (which you'll find on the Summary tab) you've chosen Firewire NTSC NDF (I'm assuming you are capturing NTSC video).

Then you should not have a problem. But you might: I did. The problem, so far as I can tell, came down to dirty heads on my deck, a Sony DSR-11. Somehow, since the deck was not finding time code, Final Cut assumed that the problem was in the time code itself. So it gave me the non-drop/drop error message. The DSR-11 is prone to all sorts of misbehavior. Sometimes, for example, I can't preview video when I am in log and capture. It's not a great deck. You get what you pay for.

Feb 20, 2008 6:09 PM in response to lvgnyc

The thing to watch out for, both in logging and in capturing, is when you log or capture multiple tapes with mixed NDF & DF timecode.

There are three or four things that can affect this:

FCP5 and later allow you to set the TC format of the capture preset, such that the Log & Capture window would default to NDF if you are working with NDF tapes.

Otherwise, Log & Capture will still auto-detect during playback when logging, but you have to be sure to play the tape some before logging the clip. If you capture multiple tapes using capture now, You could easily start recording before the time code format updates. This kind of error results in a clip whose in point is the correct "number", but the format is wrong.

During Batch Capture, the device control is not always able to change the time code format. I'm not sure about FCP6, but I am in the habit of grouping my clips in batches according to the TC format. You ma be seeing this alert because you are switching the TC format of the tapes in the batch capture, but device control is "stuck" in DF mode, for instance. This is not an issue during logging, only capture.

I think it may also be possible to override the clip's logged TC format at capture by unchecking "use logged clip settings".

Capturing clips with the wrong TC format can really mess up recapture later. The offset that happens as the format gets converted back increases as the starting hour of the timecode gets bigger.

So basically you can have clips that get logged wrong, and clips that were logged correctly, but captured with the wrong TC. It's easier to miss it when logging, since there's no alert message to pop up. But the other alert is there to tell you there is a mismatch somewhere, preventing you from making the second kind of error. Your only error may only be that you had both DF and NDF clips in the same batch.

There is a trick to get the TC format to switch to the non-default for batch capture - Open Log & Capture and play the tape until you see the TC format update. Now start the batch capture with Log & Capture still open - device control will stay in that TC format now. Otherwise, I think device control switches to the format of the first clip in the batch, but stays there until you cancel and start a new batch.

Hope this helps -


Max Average User uploaded file

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Drop-Frame vs. Non-Drop-Frame Capture question

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.