Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy trashing preferences unsuccessful: next?

  • trashing preferences unsuccessful: next?

    Posted by Jimi Lund on November 11, 2009 at 6:20 pm

    Hi all,

    I am working with Final Cut Studio 6.0.6.

    Initially some HDV files I was editing kept going out of sync every time I tried to put a dissolve between a cut, even though I unlinked the audio and only had the dissolve on the video. Then the audio started playing at differing rates on each channel – 1 slower than the other. But it was inconsistent – sometimes it randomly rectified itself & that i’ve never seen before.

    To cut a long story short, I went back to a DV Pal edit i’ve been doing without problems but now the audio wouldn’t play at all. No levels. Occasionally no image either. The raw footage plays fine from the hard drive though. The issue is only within FCP.

    I trashed preferences using Digital Rebellion’s tool. No success. Now there’s no audio within FCP but I also get the message that i’m dropping frames constantly, despite lowering the data rate to the least quality & frame rate & having 1 sequence open.

    FCP seems to be deteriorating. My media comes off a 2TB G-raid, firewire 800. I did wonder if the drive was dying (it’s a month old) but disk utility says it’s ok.

    So what now? A full install of FCS? Operating system?

    1 last thing that may be related, last night I had to do a reinstall of Compressor. Could this be linked?

    Many thanks.

    Mac OS X 10.5.8
    24″ I-Mac 2.8 GHz Intel Core 2 Duo
    2 GB Ram
    Quicktime 7.6.4

    Jimi Lund replied 16 years, 5 months ago 3 Members · 8 Replies
  • 8 Replies
  • Jerry Hofmann

    November 11, 2009 at 6:22 pm

    Do you have more than one firewire device connected to the computer? if so, disconnect it and see if the behavior goes away. FW drive setups work OK but don’t like sharing busses with cameras or decks for example.

    Jerry

    Apple Certified Trainer

    Author: “Jerry Hofmann on Final Cut Pro 4” Click here

    8-Core 3.0 Intel Mac Pro, Dual 2 gig G5, AJA Kona SD, AJA Kona 2, Huge Systems Array UL3D, AJA Io HD, 17″ MBP, Matrox MXO, CD’s

  • Jimi Lund

    November 11, 2009 at 6:42 pm

    Thanks for the swift reply.

    I know what you mean about the firewire conflict – i’ve experienced that before too. But not this time.

    I haven’t got any firewire device connected. My external hard drive is the only attached device.

    Any other ideas?

  • Brendan Maghran

    November 11, 2009 at 7:17 pm

    Have you recently updated your operating system? Snow Leopard? I recently updated mine and my Avid went all out of whack. Perhaps a similar problem.

  • Jerry Hofmann

    November 11, 2009 at 7:27 pm

    Bummer… I actually don’t believe in editing HDV natively at all. Things like this crop up because it’s a consumer format and just doesn’t play nice, which is what I believe is happening here. (Sony said exactly this when they announced it, but Canon decided to make “prosumer” cameras with it because it was inexpensive, and pro’s run into it because of that…) There isn’t a quick fix don’t think, but you could recapture to ProRes, and I’ll wager the problem disappears.

    Jerry

    Apple Certified Trainer

    Author: “Jerry Hofmann on Final Cut Pro 4” Click here

    8-Core 3.0 Intel Mac Pro, Dual 2 gig G5, AJA Kona SD, AJA Kona 2, Huge Systems Array UL3D, AJA Io HD, 17″ MBP, Matrox MXO, CD’s

  • Jimi Lund

    November 11, 2009 at 7:48 pm

    I’m not on Snow Leopard yet.

    I did think it was something to do with the HDV format, so i took the HDV clips into Compressor and exported them as DV Pal to see if I had any more stability. Alas no.

    But I don’t think it’s to do with HDV as other projects i’ve tested, with other formats (DV Pal, DV Cam) are all responding the same: absolutely no audio levels or output in FCP but fine in QT. And still every few seconds I get the droppped frames message.

    Incidentally I checked the Master audio control button in the audio mixer window. It’s not that either.

    Is it time for a reinstall of FCP?

    Are there any other tests I can do?

  • Jimi Lund

    November 12, 2009 at 2:02 pm

    Quick update – I resolved this issue. I think:

    I found another thread with the same issues and was worried that nobody had fixed the problem:

    https://forums.creativecow.net/thread/8/1005429

    So I phoned Apple. After the problems with my HDV going manic (still not sure why) and it affecting all my other formats. I took out the aforementioned measures to fix it but my DV clips would not play sound in either the viewer or timeline.

    I reimported one of my raw media files and it played fine. What I had to do, but wasn’t, once all my easy set-up settings were correct, was duplicate my sequence. Then everything played fine.

    It’s a bit of a gotcha that the amended settings aren’t immediate.

  • Jimi Lund

    November 12, 2009 at 3:53 pm

    False alarm. Still not working.

    Back on the phone to Apple. Problem unknown. When Mr Apple is exasperated you know something’s wrong.

    What i’ve tried so far (and having no success): Creating a new user account.
    Creating a new project and importing the footage. (this brought a File Error message before importing them).

    My next move is to uninstall my recent plug-ins.

    If unsuccessful, re-install FCP.

    If unsucessful, full wipe and install.

  • Jimi Lund

    November 13, 2009 at 12:51 pm

    Ok, i’m sure nobody’s listening anymore but I don’t want anyone else to have to go through this.

    After removing and reinstalling Final Cut Suite – then doing a full erase and install of everything (which to my dismay and horror didn’t solve the problem), and after much troubleshooting, it turns out that my project has become corrupt.

    After going back through my time-machine back-ups and trashing preferences at every step, i’ve established where it went wrong.

    My other projects were not working because I was opening them whilst my corrupt project was open and my preferences were bad.

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