Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Compressor interface SLOW

  • Compressor interface SLOW

    Posted by Lars Fuchs on August 23, 2010 at 9:50 pm

    I have been happily using compressor for some time now. However today its excruciatingly slow. Every single mouse click prompts a spinning beach ball sometimes lasting over 30 seconds.

    I’m running Compressor 3.5 on OS X 10.6.2 on an 8-Core mac pro with 6Gb of RAM.

    Im trying to convert quicktimes approx. 45-55 min. long, in mp4 720×480, to uncompressed 8 bit sd or Apple ProRes. It gets bad after I apply a setting (preset or custom, same difference). I’ve restarted Compressor, but haven’t yet tried a reboot. I’ll try that next after the current batch is done. In the meantime, anyone ever experience anything similar?

    thanks in advance

    Tad Newberry replied 15 years, 5 months ago 5 Members · 6 Replies
  • 6 Replies
  • John Fishback

    August 23, 2010 at 10:16 pm

    Try Trashing prefs and Repairing Permissions if you haven’t already tried that.

    John

    MacPro 8-core 2.8GHz 8 GB RAM OS 10.5.8 QT7.6.4 Kona 3 Dual Cinema 23 ATI Radeon HD 3870, 24″ TV-Logic Monitor, ATTO ExpressSAS R380 RAID Adapter, PDE enclosure with 8-drive 6TB RAID 5
    FCS 3 (FCP 7.0.2, Motion 4.0.2, Comp 3.5.2, DVDSP 4.2.2, Color 1.5.2)

    Pro Tools HD w SYNC IO & 192 Digital I/O, Yamaha DM1000, Millennia Media HV-3C, Neumann U87, Schoeps Mk41 mics, Genelec Monitors, PrimaLT ISDN

  • Keith Pratt

    August 27, 2010 at 11:19 pm

    When the beachball appears, open the Activity Monitor. Is Compressor saturating your processors?

  • Sasha Marvin

    October 12, 2010 at 4:57 pm

    I have the same problem. No it is not saturating the processor.

  • Lars Fuchs

    October 12, 2010 at 5:59 pm

    Its been a while since I had the problem, but trashing pref’s did the trick. I also recreated the custom Matrox settings I had; I suspected them of fouling things up. Perhaps they got corrupted? Anyway, its working now.

  • Tad Newberry

    November 12, 2010 at 7:49 pm

    ah yes…ye olde trashing the prefs trick…i don’t think i have ever done it with Compressor. my render has been terribly slow, says it’s 3 hours and 21 minutes into it and only half way done! would the vote here be to dump out of the render, trash prefs, and begin the render again? i wonder if the new render would be quicker than another 3 hours from this point???

    thanks for helping out a bonehead!
    __________________________

    FCS3
    2.66 GHz Quad-Core Mac Pro
    6GB RAM
    NVIDIA GeForce GT 120
    …and a few TeraBytes o’ storage
    (then it’s on to PetaBytes, ExaBytes and MosquitoBytes!)

  • Tad Newberry

    November 12, 2010 at 7:57 pm

    i bit the bullet and stopped it. trashed only the “compressor” pref, not the “CompressorSharedService” one, and so far it looks like this total render will be about 45 minutes, barely 1.5 times real time.

    : )

    thanks for helping out a bonehead!
    __________________________

    FCS3
    2.66 GHz Quad-Core Mac Pro
    6GB RAM
    NVIDIA GeForce GT 120
    …and a few TeraBytes o’ storage
    (then it’s on to PetaBytes, ExaBytes and MosquitoBytes!)

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