Capture Now = Create Problems Now

[Shane Ross]

What version of QT are you running? 7.3?

Shane

Littlefrog Post

GETTING ORGANIZED WITH FINAL CUT PRO DVD now for sale!
http://www.lfhd.net

[David Roth weiss]

I’m running all the latest updates now Shane. But, I think this problem may have been around for a while, possibly through several different updates. I’ve just now identified the source as Capture Now however, earlier I had no idea why the problems were happening.

David Roth Weiss
Director/Editor
David Weiss Productions, Inc.
Los Angeles

POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

A forum host of Creative COW’s Business & Marketing, and Indie Film & Documentary forums.

[Shane Ross]

Hmmmm…I’ll have to try to CAPTURE NOW soon. I just did on FCP 5.1.4 and QT 7.1.6 and didn’t notice any issues. But that is what my laptop was running before I went Leopard..

Shane

Littlefrog Post

GETTING ORGANIZED WITH FINAL CUT PRO DVD now for sale!
http://www.lfhd.net

[Kevin Hamm]

I use capture now all the time and don’t have any issues with it. I’m going to be using it later today as I do a show for this evening, and I will let you know if anything goes awry.

Just to ask, tho, do you have any funky settings such as unchecking the default “Abort capture on dropped frames” or anything? Since you’re using a Sony deck, is there any chance you’re using a Panasonic or Canon camera with the tape recording speed set to LP or whatever they name it? I mean the setting that changes a tape from 60 minutes to 90 minutes. I know that my Panasonic deck won’t read tapes from a Canon using that setting – which I found out when my sister borrowed the camera and taped her daughter’s concert. Had to use the cam to import that footage…

[Uli Plank]

I’ve observed one problem with “Capture Now” from the beginning (long before FCP 6, QT 7.3 or Leopard): If you grab a whole tape or large parts of it, capture now tends to loose audio sync where a batch capture doesn’t. My assumption is that FCP compares the number of audio samples with the TC after a batch capture and fixes it somehow, while capture now doesn’t.

Regards,

Uli

[David Roth weiss]

[Uli Plank] “My assumption is that FCP compares the number of audio samples with the TC after a batch capture and fixes it somehow, while capture now doesn’t.”

I think you’ve got it Uli. Its why capturing as a clip or even recapturing the bad file produces a proper capture.

David Roth Weiss
Director/Editor
David Weiss Productions, Inc.
Los Angeles

POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

A forum host of Creative COW’s Business & Marketing, and Indie Film & Documentary forums.

[David Roth weiss]

[Kevin Hamm] “Just to ask, tho, do you have any funky settings such as unchecking the default “Abort capture on dropped frames” or anything?”

Nothing funky Kevin, just default settings across the board. And, its reproducable using two cameras and a DSR-11.

David Roth Weiss
Director/Editor
David Weiss Productions, Inc.
Los Angeles

POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

A forum host of Creative COW’s Business & Marketing, and Indie Film & Documentary forums.

[Kevin Hamm]

Well, I’m currently typing this post and importing video using capture now on the same machine, and it’s working just fine so far… but I did try something to see what would happen, and it might be of interest to you:

I disconnected a network drive by turning it off – this caused the finder to alert me that a device had been removed and even tho that device had absolutely nothing to do with the importing of the footage, because it was attached to the same bus as the deck (firewire bus) it caused the import to fail, hard.

I don’t have any drives on USB, which is a separate bus but a similar protocol, but I wonder if having someone remove a USB jumpdrive during an import without ejecting it might be causing your problem. Is that a possibility?

[David Roth weiss]

Kevin,

The problem stems from the capture of a full tape, so just doing any old Capture Now probably won’t initiate the problem. You have to start the capture and let the tape run until the timecode runs out. I’m doing a multicam edit, that’s why I was doing this in the first place. The bottom
line is that all one needs to do to avoid the prolem is to mark an In at the head and an Out at the tail, then capture the clip, but it used to be that you could just hit capture now at the head and walk away.

David

David Roth Weiss
Director/Editor
David Weiss Productions, Inc.
Los Angeles

POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

A forum host of Creative COW’s Business & Marketing, and Indie Film & Documentary forums.

[Kevin Hamm]

Well, I’m using new tape and capturing from the head to the end of the timecode, which is, today, 42 minutes give or take, and I’m not having the problem that you are experiencing. I’m also doing a multi-cam edit (although not using multi-cam clips because it’s actually faster without for this) so we’re having analogous needs, just not analogous issues. I thought I’d try the drive pull trick and let you know that it might be the source of your problems – the Finder can mess with anything, and usually does at the wrong time. I wasn’t disregarding your thoughts, just offering another possibility.