Digitizing makes the clips start @ 00:00:00:00

[Mark Maness]

I will have to say that I have bee seeing this bug myself. I had it to happen a few times last week and its really bugging me.

I have FCS (FCP 5.1.2), MacOS 10.4.8, and Mac Intel dual 3.0, 2 gig of RAM, AJA Kona 3, ATTO Celerity FC card.

_______________________________

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

[Jeremy Garchow]

Is this only happening on recapturing multi-clips?

Jeremy

[Mark Maness]

[JeremyG] “Is this only happening on recapturing multi-clips?”

No. Its happening for me in the Log & Capture. I log all of my footage and then capture. Sometimes with some clips it looses the metadata and resets the timecode and reel names. I’m puzzled by this myself.

What version of Mac OS is everybody running?

_______________________________

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

[Jeff Coleman]

same problem here. FCP 5.1.1, OS X.4.7, QT 7.1.3.
Digitized HDCam 1080, 29.97 at DV then rezzed up to 1080 10bit Uncompressed. The batch capture worked fine until it was done capturing the clips. When all (almost all, it didn’t ask for all the reels for some odd reason) the clips were recaptured, the reel numbers went blank and the timecode started at zero. Trashing prefs, restarting has no effect. I logged a clip and then batch captured that clip and it did the same thing. THIS IS USELESS!
What version of QT is everybody using?

Love,
Jeff

Final Cut Studio 5.1, G5 2GHz Dual Processr, 2.5Gb RAM, AJA IO

[Jeremy Garchow]

I am beginning to think this is a humongous bug and I don’t know what to do or how to fix it.

FCP 5.1.2 QT 7.1.3. It has to do with drop/non drop. This latest version of quicktime has really messed a lot of things up.

Jeremy

[Jeff Coleman]

Please explain
[JeremyG] “It has to do with drop/non drop.”

I’m also starting to believe QT 7.1.3 may be the culprit, but I’m wondering if media manager has anything to do with it. If you create a new project and log a few clips into your browser, then batch capture them, does the timecode reset to zero?

I’ve been experimenting and I couldn’t get it to happen in that scenario. Did you by chance “make sequence clips independent” before you media managed?

I discovered I actually have two projects now that have been recaptured with no timecode and no reel numbers. The quicktime capture files themselves (viewed outside of FCP) have no tc and no reel numbers. Its not just a disconnect, but as if FCP never handed QT the info when it captured the clips or QT didn’t receive the info properly from FCP. But I’m guessing…

[Jeremy Garchow]

[Countdown] “Please explain [JeremyG] “It has to do with drop/non drop.””

Well, i wish I could get the problem to be consistent but I can’t. I am finding I have the most issues when combining drop/non drop material. This latest project I am doing I have client supplied tapes from an old library. Some were shot drop, some non drop. FCP gives me warning about coming in drop/non drop even though each tape has it’s own format of tc. It gives the waring, but captures the material correctly and keeps the metadata. Before when I have seen that warning, it loses the metadata. I can’t tell when it’s going to work or not. If I get the warning before capture, I immediately stop and make a BU copy of the project so I won’t have to relog if FCP loses the metadata after capture. Major pain in the butt. This is all coming through an AJA io.

A few weeks ago I had a firewire DV project that was even more disastrous where the tapes had mixed formats of tc on the same tape (again it was client supplied f’ed up tapes) and they also had multiple timecode restarts (timecode going back to 00 on the tape, sometimes 5 times per tape). FCP could not discern which clips were drop and non drop. Once I told FCP which clips were and changed the capture setup to reflect drop/non drop, the clips came in and had their metadata. This should not matter with RS-422 deck control and FCP should just pick up whatever tc it has and capture, but with DV I had to tell FCP which clips were drop/non drop. That was terrible. I had never seen nay warnings or problems like this in my FCP days at all and it all started happening after the qt update. It has to be something with 7.1.3.

Jeremy

[Ted Coakley]

Sooo, it’s been almost 2 years since the last post on this thread, and I’m a wonderin – any solution yet?!?

I’m having the same problem:
I opened up an FCP4.5 project into 5.1.4, batch captured some clips, and it changed the Media Start times to 00:00:00;00, AND the Reel field changes to either 001 or just goes blank/empty.

I’ve spent some hours today researching this online, reading through forums (cow and otherwise), and so far, no solutions.

I don’t know if this is relevant, maybe gives some indicator as to the problem, but when I do a Batch Capture of a clip, it is playing it TWICE in the capture process. No dropped frames along the way, it just plays through it in normal stuttery capture mode, rewinds, plays through again, leaving successful Capture (though with aforementioned Media times problem AND with occasional audio/video out of sync).

And, I don’t know if this is related or not either, but these clips sometimes capture with audio a bit out of sync (not drifting, but out of sync from beginning of captured clip). I also view these clips in QT and in the Finder, and they’re out of Sync, so it isn’t a FCP playback issue, but rather a FCP Capture issue. And, again, sometimes the clips ARE in sync.

Anybody know how to prevent any of these problems?

I’m running FCP 5.1.4, w/QT 7.4.1, OS 10.4.11.
I’m capturing from miniDV on Sony DSR-11.

[Mark Maness]

Let me ask you this…

How long have you seen this problem? What camera or cameras do you use? Have you set the cameras to record time code?

Without knowing too many details yet, I’ve seen this with my experience some time ago when I had your setup. It seems that it is caused by the cameras not recording time code properly. We use the Sony Z1U camcorders on a regular basis and by default the time code is set to Auto. That means time code could be drop frame or non-drop, it could start at zero at any time the tape had been searched or the camera had been shut off. Basically, it caused all sorts of problems without us knowing what was going on.

After setting the cameras to record time code and setting them to drop frame time code, all of our time code issues such as the one you are seeing stopped.

One more thing, check your User Preferences and see if you are setup to “Make New Clip” on time code break.

Oh yeah… it wouldn’t hurt to join the bandwagon and update your computer to the latest software either. If this is your bread and butter, you need to be up to date.

_______________________________

Wayne Carey
Schazam Productions
https://web.mac.com/schazamproductions
schazamproductions@mac.com

[Ted Coakley]

Hi Wayne, thanks for your reply.

The Media Time Start/End resetting problem and the Reel field changing problem both just started yesterday, lasted through about 8 captures, then the next six captures did not have the problem.

The audio/video out of sync was on about 5 of those first 8 captures, then on none of the last 6 captures.

The Capture process playing through the segment twice problem has been on all 14 of those captures, though on some of them, the first and/or 2nd pass wasn’t on the entire duration of the segment.

This is all from VX-1000 footage (minidv, 32kHz audio, DropFrame), and it is default & permanently set to record time code – you can’t change it to NOT record timecode.

The timecode IS recorded properly on the footage I’m digitizing, as it reads fine from my deck’s Display function, it shows on my studio monitor, and FCP 4.5 and QT both show the timecode as fine. It is just FCP 5.1.4 that is having this problem.

I AM set up to Make New Clip at Time Code Break, but none of the footage I’m digitizing has any Time Code Breaks.

Editing is part of my bread and butter, but if running correctly FCP 5.1.4 SHOULD be good enough.
On that note, I have friend working in Hollywood, working on A-list shows shot on film, cutting with FCP 2 or 3 on some old mac from that era, and using his old box tv that you have to bang the side to get it to warm up as a “studio monitor”. Of course, he is an exception, and I’d prefer to have the newest of new (if I had an I.T. person to work through all the kinks and roadblocks that come with each new update), but the point is, that if working right, nobody usually has the NEED to update/upgrade/BUY each new version (a.k.a. eat everything fed to them). He just has his old setup dialed in right, and flys on it all the time….

Thanks for your reply. Any more thoughts?