Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy capture errors, fcp 6.0.3

  • capture errors, fcp 6.0.3

    Posted by Chris Gorman on May 17, 2008 at 8:41 am

    I’ve tried 3x capturing 45 mins. of hdv from a tape. Whether batch or capture now, I get an error message before it completes, so the capture fails. I want to figure this out before the tape gets too much wear and tear from re-tries.

    The error message says something like “streaming error”. I’ve never seen that before, and never had capture problems before. This started after I upgraded from fcp studio and fcp 5.0.4, to fcp studio 2 and fcp 6.0.3, QT 7.4.5, OSX.4.11

    When I check the hard drive with Disk Warrior, it tells me it’s at least 50% out of order. This is with hardly any activity on a new 500 GB SATA II hard drive. Even after using disk warrior,there’s only a small improvement – not like the results I used to get before these upgrade/updates.

    I’m using Disk Warrior v.3.0.3. I’ve ordered the disk warrior upgrade and it’s in the mail. With everything else recently upgraded and a new hard drive, I’m not sure what’s the most likely problem.

    Help! I’m starting to run way behind on this project.

    Dominique Piollet replied 17 years, 11 months ago 7 Members · 11 Replies
  • 11 Replies
  • David Roth weiss

    May 17, 2008 at 9:20 am

    Did you format that new drive as Mac Extended before trying to capture to it?

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

    POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

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

  • Chris Gorman

    May 17, 2008 at 3:26 pm

    Yes.

  • Jeremy Garchow

    May 17, 2008 at 3:31 pm

    Log and capture. Don’t try to capture 45 minutes of HDV in one go. Break it up in to smaller chunks (like 5 minutes) if you MUST do long captures, but if you log and capture into clips of video, your system will like it much more.

    Jeremy

  • Chris Gorman

    May 17, 2008 at 5:41 pm

    I cleared off (erased) a different hd and now I captured it ok. I’ll try to figure out later when I have time if something is wrong with the first HD.

    Another thing I changed, don’t know if it matters in this case . . .is that I unchecked “abort capture on dropped frames”.

    BTW, I can’t batch cap small segments because this is concert footage where I need to be able to sync all 3 cameras.

  • Jeremy Garchow

    May 17, 2008 at 6:21 pm

    [chris gorman] “Another thing I changed, don’t know if it matters in this case . . .is that I unchecked “abort capture on dropped frames”. “

    Yes, that will matter as you won’t see if the computer is dropping frames, it will capture regardless if it’s coming in or not. You should leave it on.

    [chris gorman] “BTW, I can’t batch cap small segments because this is concert footage where I need to be able to sync all 3 cameras. “

    So capture it every 10 minutes and stitch it back together with timecode.

    Jeremy

  • Paolo Ciccone

    May 17, 2008 at 10:16 pm

    FCP is known to be unable to handle long takes of HDV material. With the JVC HD100, for example, you cannot ingest a full tape of *uninterrupted* footage. You simply can’t, FCP will break it at arbitrary spots and create a new clip.
    I personally got fed up with that as I was synching 3 cameras for interviews, a similar scenario, and switched to Premiere with does the job just fine, same tapes and camera, no breaks. If you want to use FCP you can work around the problem by using DVHSCap, an Apple program part of the FireWire SDK, capture your footage as .m2t files, then convert them to QT by using MPEG Streanclip, another free program. Bring the footage in FCP now and you’ll be able to use Multiclips. If you shot your footage in 24p you will need to specify the frame rate in MPSC as 23.976.

    Good luck


    Paolo Ciccone https://www.paolociccone.com
    Hellriser Digital
    Santa Cruz, CA

  • Chris Gorman

    May 18, 2008 at 12:28 am

    It’s working now, so could be the steps i took to clear things up. Hopefully it keeps working.

    I’m also preparing to set up a RAID 0, so this should help more I would think. The error message did say something about “streaming”, so it did not seem to be a timecode or dropped frame issue. I wonder if capture now is safer than batch?

  • Rich Rubasch

    May 18, 2008 at 12:36 am

    We just saw the same error with 6.0.3 for the first time ever. On the intel Macpro with a Kona 3 the error was “Tape Error” etc. We were uploading 50 minutes off a DVCAM via SDI to DVCPro50. NEVER happened before.

    Then on another machine (G5 dual 2.7 with an Aurora Pipe) it was a new error, perhaps the streaming error. A third attempt on the Pipe system and it came in. Does seem to be a 6.0.3 issue. The Intel is Leopard, the G5 is tiger. both are QT 7.4.5.

    Rich Rubasch
    Tilt Media

  • Simon Webb

    May 18, 2008 at 2:36 am

    It’s interesting to read this. I was having terrible problems last week while trying to capture HDV through FireWire to my dual 2.7 G5 running 6.0.3. All of the clips were logged, but when capturing perfectly good footage (with no in-camera cuts), FCP would capture in small sections – breaking up, say, a 1 minute clip into a number of shorter clips (with the usual missing frames in between).

    Originally, I thought it might be some wacky problem with the G5 so I tried capturing the stuff using my MacBook Pro running 6.0.3 but the problem was the same on that machine.

    So… Then I gave it a shot on my clunky old G4 running 5.1.something, and lo and behold, everything captured perfectly.

    Hmmmmmm…

  • Chris Gorman

    May 18, 2008 at 3:13 am

    What you describe was a separate little problem I had (not the stream error) which was easily solved when i noticed i had overlooked unchecking that pesky little setting unexpectedly in the clip setting in the log and capture window. when i corrected that, my 45 min. hdv tape captured with no breaks.

    BTW, my footage definitely did not have any record stops on the footage, so don’t know why it breaks it up when the box is inadvertantly left checked (it’s checked by default).

Page 1 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy