Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Pink and green hash on capture…

  • Pink and green hash on capture…

    Posted by Ron Dylewski on February 28, 2006 at 6:05 pm

    Hi –

    Am I losing my mind? (okay, that’s a separate question!)

    I am capturing a bunch of very short clips. All seemed to be
    going well. However, apparently about half way through the process
    something WENT HORRIBLE WRONG!

    The ends of most of these clips turn from normal video to a sort of
    alternating green and pink video hash. I am using a CineWave card
    and importing from Beta as YUV. I tried deleting the clips and trying
    again, and the same thing happened. I am capturing to an external drive,
    but it has tons of space on it. Is it possible that it can’t keep up
    with the capture, for some reason?

    Any help would be great.

    Thanks

    Ron

    Photos, news, memories and musings on the great American Roadside experience
    https://www.theamericanroadside.com

    Are you a collector? Put your collection online for free at What A Collection.com!
    https://www.whatacollection.com

    Ron Dylewski replied 20 years, 2 months ago 3 Members · 6 Replies
  • 6 Replies
  • Jeremy Garchow

    February 28, 2006 at 6:22 pm

    What OS/QT versions are you running? Have you updated or upgraded any software recently?

  • Rob Sankey

    February 28, 2006 at 6:23 pm

    I am getting that also. Are you using OS 10.4.5? This may be the problem.

  • Ron Dylewski

    February 28, 2006 at 6:37 pm

    Haven’t changed anything recently. Still on FCP 4.5 running OS X 10.3.4 and QT 6.5.1

    This just happened halfway through my capture session this morning. Clips I did up until a certain point we fine, then this bizarre problem cropped up.

    I did have a crash in between, so perhaps I should trash my preferences and see if that fixes things… Other than that, I’m baffled.

    Ron

    Photos, news, memories and musings on the great American Roadside experience
    https://www.theamericanroadside.com

    Are you a collector? Put your collection online for free at What A Collection.com!
    https://www.whatacollection.com

  • Ron Dylewski

    February 28, 2006 at 8:58 pm

    This is apparently a drive-related issue. Someone had hung a new Maxtor drive on the system and it, for whatever reason, was unable to capture correctly. In the meantime I’ve gone back to my HUGE raid and all is well.

    Thanks for the ideas…

    Ron

    Photos, news, memories and musings on the great American Roadside experience
    https://www.theamericanroadside.com

    Are you a collector? Put your collection online for free at What A Collection.com!
    https://www.whatacollection.com

  • Jeremy Garchow

    February 28, 2006 at 9:13 pm

    Sweet! Was this an internal drive or a firewire drive?

  • Ron Dylewski

    February 28, 2006 at 9:47 pm

    It was an external Maxtor firewire job. It is new and is the first thing on the chain of a couple of drives. There is a chance that this is related to whether it’s set for RAID 0 or RAID 1 – something I have yet to check.

    Ron

    Photos, news, memories and musings on the great American Roadside experience
    https://www.theamericanroadside.com

    Are you a collector? Put your collection online for free at What A Collection.com!
    https://www.whatacollection.com

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