Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Spinning Beachball Digitizing DVCPRO HD

  • Spinning Beachball Digitizing DVCPRO HD

    Posted by Jeff Gural on February 10, 2010 at 9:39 pm

    I’m having a frustrating time trying to digitize DVCPRO HD ever since we upgraded to Snow Leopard.

    When logging we get a random beachball. The only way to end it is to force quite. I lose all the clips I logged even if I’ve recently saved.

    Or if I bring a batch in to digitize, it will get through a few clips and then beachball requiring a force quit.

    We have the latest Final Cut and latest OS updates. We are diging from an AJ-HD1400 deck using firewire. This used to work fine before we upgraded and it’s happening on multiple computers all with the same updates.

    Any ideas?

    Thanks,

    Jeff

    John Pale replied 16 years, 4 months ago 5 Members · 9 Replies
  • 9 Replies
  • Michael Sacci

    February 11, 2010 at 1:38 am

    Did you do a clean install or just upgrade the OS. There was a major QT upgrade with SL so if you didn’t do a clean install of the OS and the apps that maybe the problem.

    FCP installs the DVCPro codecs and they maybe be getting corrupted.

  • Jeff Gural

    February 11, 2010 at 1:44 am

    The problem is that one computer we have issue with is a brand new iMac. So it came with snow leopard installed and then we installed a clean version of fcp. I’m completely at a loss.

  • David Roth weiss

    February 11, 2010 at 1:48 am

    Did you run Apple>>Software Update several times until it sent the message that all your software was up to date?

    David Roth Weiss
    Director/Editor/Colorist
    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, Indie Film & Documentary, and Film History & Appreciations forums.

  • Jeff Gural

    February 11, 2010 at 1:52 am

    Yeah, I tried that and using a fcp utility to trash all the usual fcp prefs and caches. And fixed permissions. I’m starting to wonder if it’s the deck. But then it seems fine on a computer we have with leopard. Very bewildering.

  • Michael Sacci

    February 11, 2010 at 2:13 am

    What Firewire settings do you have selected for the Device control, try the other.

    Can you capture from another deck or camera via FW?

    Have you tried another cable?

    Just throwing out things to try.

  • Jeff Gural

    February 11, 2010 at 2:18 am

    I have tried multiple cables and the alternate FireWire control settings. But I haven’t tried capturing from the camera. That would be a good way of eliminating the deck. It seems lime a control issue as it happens when I’m logging which seems like the codec would not be an issue.

  • Brynn Sankey

    February 11, 2010 at 6:13 am

    May seem like a very elementary question, but have you checked your Capture Scratch folder? If a clip was captured in its entirety before FCP crashed, it should be there, despite its absence from the FCP browser.

  • Jeff Gural

    February 11, 2010 at 1:35 pm

    Yes, the files that FCP has digitized are in the capture folder. But it requires a force quit and then a reconnect media to get moving again. And it usually crashes within the first five clips of a batch. My batches tend to be sixty to seventy clips so it’s really slowing me down.

    And then my other crash which happens in logging is where all my logged clips vanish from the project. Those haven’t been captured yet so there is no media to be reconnected. The frustrating thing is that I can save the project and then a second later have it crash and force quit and lose every clip I had just logged in my batch. The only way I’ve found around that is to close the digitizing window and save or to save and quit and start up again.

    It doesn’t sound like anyone else is having any similar issues so I’m going to assume this is some sort of weird mystery spot where I’m editing. I’m going to guess that it has something to do with a combination of firewire and Snow Leopard. I’ll try using another form of deck control and see if that solves it.

    Jeff

  • John Pale

    February 12, 2010 at 6:51 am

    Export a batch list of your capture bin before you attempt to capture, this way you wont lose your logged clips if it continues to happen.

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