HT202204: Compressor 4.1.3: Release notes

Learn about Compressor 4.1.3: Release notes
Dave123456789101112
Level 1 (0 points)

Q: Compressor 4.1 Crashing

Hey there!  Love the new Compressor 4.1.  It's so simplified!  All you do is import your FCPX file, choose an output or two, hit submit, and voila! It freezes and crashes!

 

"That's weird," you might be thinking.  "Must have been a fluke," you tell yourself.  "After all, there's no way Apple would take a perfectly fine, working program and replace it with some piece of crap so buggy it can't even export a single file."  So you reopen it.  Ah!  Your FCPX project is still there.  That's nice, all you have to do is rechoose those outputs.  So you click on the "add outputs" button and WHAT THE **** IT JUST CRASHED AGAIN.  DIDN'T EVEN FREEZE TO THINK ABOUT IT, JUST POOF IT'S GONE.

 

Ok, your flash of fury has passed.  You calm down.  You take a deep breath, pondering your options.  I mean, it must be something wrong on your end, right?  Compressor 4.1 not only works, it's way better than 4.0.7, that's why they released it!  So, you restart your computer, and open compressor.  Look at that!  Your FCP project is still there.  "But wait!" you say.  "That would be too easy!"  So you deftly click on the project to delete it, so that you can reopen FCP and reimport a fresh version.  Just waiting for the spinning ball to register your click.  Silly Compressor, it's probably trying to load that old project.  Doesn't it know I'm just gonna delete OH MY GOD WHERE'D COMPRESSOR GO.  ARE YOU KIDDING ME, IT CRASHED AGAIN.  I HADN'T EVEN TRIED TO START A BATCH.  I LITERALLY JUST CLICKED THE FILE TO DELETE IT AND IT CRASHED.  WHAT THE **** IS THIS CRAP.

 

Ok, ok, ok.  You're better than this.  Don't let this thing beat you.  You've got it.  Instead of clicking the project, you'll RIGHT click it, and "cut" the project.  It works!!  It's all clear.  You, good sir, are a genius.  You reopen FCPX, resend to compressor, and rechoose your outputs.  Only, this time, you choose just one output, and a preset one at that.  You click ok and the "Start Batch" button lights up!  It's working!!  You click start batch and hear your external drive start to spool!  The ball starts to spin, but worry not!  That's just because it's trying to add it to the "active" menu.  Although, it is taking quite a while... A very long while... No... This can't be hapenning... No. no, no no no nononononono nonn nono no no nonn on non nono!!!! IT FROZE AGAIN.  IT EFFING FROZE AGAIN. IT IS LITERALLY INCAPABLE OF DOING AAAAAANNNNNNYYYYYYTTTTTHHHHHIIIIIIINNNNNNGGGGGG.  Sick update guys!

 

You know what would be cool?  Some kind of explanation as to why this crap replaced my perfectly fine 4.0.7 version.  You know what would be even better?  To be able to export my film.

 

kthxbai.

MacBook Pro with Retina display, OS X Mavericks (10.9)

Posted on Dec 24, 2013 1:15 AM

Close
Dave123456789101112

Q: Compressor 4.1 Crashing

  • All replies
  • Helpful answers

Previous Page 2

  • by Jason5750,

    Jason5750 Jason5750 Jan 14, 2014 6:48 PM in response to PaloDave
    Level 1 (0 points)
    Jan 14, 2014 6:48 PM in response to PaloDave

    PaloDave-

     

    I'm having a similar exprience to, well, everyone here. If it helps to know, I'm recording church services at 720P, using ProRes 422HQ, and end up with about 150GB of file for 90 minutes of "film." Capturing the footage with a Blackmagic Thunderbolt Shuttle, recording to a striped-raid external Thunderbolt LaCie. I'm doing this with a 2012 mini with 2.6Ghz quad-core i7.

     

    Until a few weeks ago, processing a batch (which consists of a 150GB MOV parent to 10mbps mp4, mp3 for audio, MPEG2 for DVD, and Dolby digital audio...so 5 targets) took between 40-50 hours to complete. I eventually smelled something nasty, and figured out how to "enable" the 3 other cores (what an idiot, right?), and cut my encode time down to 3.5 hours. Boy was I smiling!

     

    That was all until this Saturday, when I upgraded the OS to Mavericks. At this point, I'm basically in a panic. Initially, 4.1 was crashing as soon as I added a source file. I soon figured out, oddly, that if I drug the file into Compressor, as opposed to "adding a file" manually, it wouldn't crash. So, that was solved, I thought. I ran a few tests, but stopped them all after a few minutes in. I'd always tried to share the resources of two adjacent iMac's, but never could figure out how to make QM work correctly across the LAN, and I'd heard that the new interface would be much eaiser...so I wanted to try. Who wouldn't? Anyway, I went into the other two computers, enabled file sharing, etc, set up the group on my i7 mini, selected the group, and hit "go." In just a few minutes I checked the logs on the two "remote" systems, and quite to my surprise, they were friggin' working. Holy Craphole! It worked!

     

    For about 10 minutes...

     

    Then, to my great sadness, I noticed that the QM service and transcoders on the i7 mini had stopped responding. To be quite honest, I think those other two iMac's completed the rest of the segmented jobs by themselves, w/o the "admin" doing anything. Lazy POS;-)

     

    So, a few things are keeping me awake.

    • Why would it take 4.5 hours to process, on 12 cores (all three computers), what I was doing in 3.5, on a single CPU, prior to Mavericks/4.1? If it helps, the two iMac's were showing @ 125% CPU usage, and the mini was showing like 260% over 2 "instances"/cores/whatever.
    • Will Handbrake process a 150GB MOV encoded with ProRes 422HQ? I have GOT to get a solution figured out, hence the question, although it makes me sick to my stomach.
    • What Matrox equipment are these guys discussing? I know they make video splitters, docks...capture devices too? How does that affect Compressor?
    • Would the fact that I added a USB3 to DVI "dongle" or "adapter", at the same time I installed Mavericks, make a difference? (that's the only port I could use for a badly needed second display)

     

    In closing, please forgive any community transgressions. I'm very new to the video capture/processing world, and anyone reading this knows how it's quite the rabbit trail...my point being I've not been taught by anyone, nor am I privy to any standard means and methods for any of this stuff...just kinda put the pieces together until it worked, and I'm sucking it up like a sponge every day, but, for now, I'm stuck, and unfortunately being held hostage by a bug-plagued app. Any thoughts, advice, suggestions are welcome.

     

    JasonO

  • by Warwick Teale,

    Warwick Teale Warwick Teale Jan 15, 2014 1:54 AM in response to Dave123456789101112
    Level 3 (588 points)
    Jan 15, 2014 1:54 AM in response to Dave123456789101112

    Hi, do you have any logs from the new compressor.app V4.1 that might show what happened? you can find these in ~/Library/Logs/Compressor now (Compressor.app V4.1)

     

    IF you have these,

    • have a look through and see what ERRORS you had and REPORT them here (if you like) with out dumping Km's and reams of lines. just the bits that failed.
    • Also have a look in the /applications/utilities/console.app to Logs/crashreporter to see if any Compressor.app component (theres a few) failed and issues a symptom dump. these are mostly caused by a "can't handle your data' reason... not a logic error.

     

    Certainly there may be some programme errors caused by specific environments peculiar to your workflow that the application does process correctly and YES these may not have been encountered nor tested in the application development or Beta testers.. so be it.

     

    However as a reasonable user of Compressor.app (a bit of a compressor.app fan too), me thinks this current flavour (release) of V4.1 is certainly a dramatic improvement over V4.0 and the previous V3 flavours.

     

    If you have some info, feel free to share it here. Usually the people on these forums are pretty slick resolving the issue.

     

    Avoid just blindly removing the application preferences, or state information or using a sledge hammer , resorting to 3rd party fix 'em applications, and blindly reinstalling from Apps store..

     

    Its likley something to do with the stuff from FCPX thats fed into Compressor.app V4.1 .. It can usually be resolved

     

    Post your results for others to see.

     

    Warwick

    Hong Kong

     Certified Apple ACTC

  • by remoran,

    remoran remoran Jan 15, 2014 6:27 AM in response to Warwick Teale
    Level 1 (0 points)
    Jan 15, 2014 6:27 AM in response to Warwick Teale

    Thanks to Palodave, I found out that Matrox reloaded into Compressor 4.1, thus causing it to crash but in using 4.1, I have not seen the speed boost Apple has been bragging about making it as fast as the Matrox system that worked wonderfully well in 4.07. Is there a way to duplicate this feat as I know some people are getting the speed hit without question. Any help on this would be terrific. The machine it runs on is a 2011 17" Mac Book Pro with 16gbs of memory.

     

    Best

  • by PaloDave,

    PaloDave PaloDave Jan 15, 2014 6:45 AM in response to remoran
    Level 1 (5 points)
    Jan 15, 2014 6:45 AM in response to remoran

    I'm using a mid 2012 MBP Retina. 2.6 GHz i7 with 16 GB of memory. Going from about an hour (75 GB) of ProRes to about 3.5 GB 1080p at 10 Mbps is taking 20 minutes. Using Matrox Mini Max it was taking about an hour.

     

    More information about hardware compression and 4.1 can be found here - http://www.larryjordan.biz/compressor-4-1-hardware-acceleration/

  • by Chris Torella,

    Chris Torella Chris Torella Jan 22, 2014 11:12 AM in response to remoran
    Level 1 (25 points)
    Jan 22, 2014 11:12 AM in response to remoran

    if you have matrox presets - delte those and uninstall the software - that worked for me..- you might also have to trash the layout folder if you get a grey screen on launch

  • by nokey&mousembp,

    nokey&mousembp nokey&mousembp Jan 22, 2014 3:02 PM in response to Dave123456789101112
    Level 1 (0 points)
    Jan 22, 2014 3:02 PM in response to Dave123456789101112

    I am getting a lot of screen artifacts when I use Compressor 4.1. This program definately has some memory leaks and bugs that need to be fixed and updated.

Previous Page 2