Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy FCS 2 + Leopard not getting along

  • FCS 2 + Leopard not getting along

    Posted by Shawn Gaiero on August 2, 2008 at 5:11 pm

    Hey guys, big problems over here with FCS 2 & Leopard:

    I got my new 8-core (dual 3.2) with Leopard pre-installed.
    I did a clean install of FCS 2.
    I begin editing an HD project in 720p @ 23.98 fps; the footage is from
    a P2 card in the .MXF format.

    After about 10-20 minutes while working within the timeline, the
    spinning beach ball appears. I force quit out of FCS 2, however it
    remains active in the finder. It won’t FORCE QUIT so I have to do
    a hard re-boot.

    I’ve ditched FCP preferences, run disk permissions, clean install
    of FCS 2 and nothing’s working. I’ve hard re-booted several times already.

    Any Suggestions? Anyone else running Leopard having difficulty using FCP 6?

    Thanks in advance for any help whatsoever.

    G5 Mac Pro Quad-Core Intel Xeon dual 3.2 ghz, 6 gigs of Ram.
    Leopard 10.5.4
    Quicktime 7.5
    FCP 6.0.4 – No Plug-ins

    Edo Medicks replied 17 years, 4 months ago 6 Members · 7 Replies
  • 7 Replies
  • David Roth weiss

    August 2, 2008 at 6:16 pm

    Did you run every single Leopard update until you got the message, “all software is up to date.”

    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.

  • Walter Biscardi

    August 2, 2008 at 7:01 pm

    [Shawn Gaiero] “Any Suggestions? Anyone else running Leopard having difficulty using FCP 6? “

    Did you run every single Leopard update BEFORE installing Studio 2?

    Did you then run every single update for Studio 2 BEFORE staring to work?

    Walter Biscardi, Jr.
    Biscardi Creative Media
    HD and SD Production for Broadcast and Independent Productions.

    STOP STARING AND START GRADING WITH APPLE COLOR Apple Color Training DVD available now!
    Read my Blog!
    View Walter Biscardi's profile on LinkedIn

  • David Roth weiss

    August 2, 2008 at 7:12 pm

    [walter biscardi] “Did you run every single Leopard update BEFORE installing Studio 2?

    Did you then run every single update for Studio 2 BEFORE staring to work?”

    Right! The only time I’ve ever seen similar problems was from failing to run all the updates.

    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.

  • Daniel Haworth

    September 1, 2008 at 6:57 pm

    did you ever get this worked out? obviously the spinning beach ball can come form hundreds of different issues, but i had the exact situation as you seem to: just purchased new machine (8 core 2.8), with leopard, ran all system updates, installed FCS 2, updated that completely, started using FCP, runs great, then 10-20 minutes in, spinning beach ball, and i can’t force quit ANYTHING, have to hard reboot the machine, lose all my work. i had previously been using a powerpc g5, and have been told renders made on a G5 are not compatible with intels…so i deleted all my renders, started fresh…same issue. it’s happening right now! system functions, until i try to force quit whatever app i’m in..firefox, itunes, finder…then that particular service is dead until a hard reboot. this is complete list of things i have tried to isolate the problem:

    -copy all used media off network drives (NAS/SAN) to local drive
    -delete FCP prefs
    -delete all old renders
    -repaired permission on all drives
    -ran disk warrior on all droves
    -removed all firewire drives

    this really seems like a file access problem…it’s as if a drive that FCP was accessing suddenly went offline…but none did, they are all (at this point) hardwired into my box.

    i’ve also been told this may be a graphics card problem (mine is a NVIDIA GeForce 8800 GT).

    is there some sort of crash log where a layman can see what caused FCP to crash?

    thanks everyone.

  • Oded Farber

    December 25, 2008 at 10:09 am

    Same problem here.

    Dual 3GHz 10.5.6 updated to the max
    permission repaired (although it found nothing)

    more details about the problem here is that waveform display slows down before crashing. seems like RAM problem but we work on 2 suites here on the same sequences but only one of them suffers from the crashes.
    The network is connected but all media is local.

    Another thing is that from time to time, the render manager looses all connections to the renders (have do delete them manually)

    The FCP won’t Force quit on the Finder level.

    any more suggestions?

  • David Roth weiss

    December 25, 2008 at 6:13 pm

    Tell us about your media drives oded… And, how are you monitoring? Do you have a I/O card installed? It would help greatly if you would spell out your hardware configuration in your profile so we can help you.

    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.

  • Edo Medicks

    January 4, 2009 at 10:46 am

    Hi, I have similar problem, which i suspect are related to the x.5.6 update. since the update, i have the mouse issue (https://discussions.apple.com/thread.jspa?messageID=8739409#8739409 )
    and FCP hangs during launch. other FCS2 apps are not effected.
    tried removing FCS2, re-install did not solve this.

    can anyone else correlate x.5.6 and FCP issues?

    MacPro 8×3.0 GT8800 16gb LHe3 LSI SAS 8tb Infortrend raid osX.5.6

    The cup is half full and my shirt is half wet

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