Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Creative Community Conversations Compressor 4.1 – Failed: 3x HOST [computer name] Error: className is null!

  • Compressor 4.1 – Failed: 3x HOST [computer name] Error: className is null!

    Posted by Max Tannone on December 19, 2013 at 4:43 pm

    Receiving this message when I try to transcode using the new Compressor 4.1:

    Failed: 3x HOST [computer name] Error: className is null!

    It happens whether I try to transcode on only my local computer, or on a cluster I have setup.

    I’m going directly into Compressor (i.e. not via Final Cut) with a 1080 ProRes MOV. Tried to convert that file to two different specs. All resulting in same error. Other users are having a similar issue (I discovered via Twitter.)

    Any ideas?

    Max Tannone replied 12 years, 4 months ago 3 Members · 14 Replies
  • 14 Replies
  • Martyn Greswolde

    December 19, 2013 at 5:26 pm

    I have almost exactly the same issue but I do not have any host listed in my error report-

    I had been having issues with Qmaster before the new FCPx suite so I uninstalled both Qmaster and its pref pane (I have no idea if this is related to the issue or not)

    Greswolde Photography
    http://www.greswolde.com

    I know little but I learn quickly!

  • Max Tannone

    December 19, 2013 at 5:29 pm

    Thanks Martyn. I do not, nor ever had, Qmaster and its preferences pane installed. (I briefly tried experimenting with Qmaster using the old compressor, but don’t remember having a preferences pane in system prefs or anything like that.) I may have just contradicted myself – but I definitely didn’t separately install Qmaster with the old Compressor.

    Regardless, it may be totally unrelated.

  • James Cude

    December 19, 2013 at 7:38 pm

    That’s strange. Which setting presets are you using? If you are modifying them, how?

  • Max Tannone

    December 19, 2013 at 7:47 pm

    The two different encodes I’ve tried were using the following settings:

    1280×720 h264 MOV, 3000kbps, 128kbps AAC

    and

    960×540 h264 mp4, 750lbps, 128kbps AAC

    Both are custom settings that I made.

  • James Cude

    December 19, 2013 at 10:39 pm

    Could you possibly still have remnants of the old Compressor and Qmaster somewhere causing problems? If these files still exist, try trashing them:

    /Library/Frameworks/Compressor.framework
    /Library/Frameworks/QMaseter.framework
    /Library/Frameworks/AECore.framework
    /Library/Application Support/Apple Qmaster/

  • Max Tannone

    December 19, 2013 at 11:07 pm

    Thanks James.

    I did find: /Library/Application Support/Apple Qmaster/

    I deleted the folder.

    However, before I did that, I tried running Compressor again, and got this message:

    I got the same message after deleting that Qmaster folder as well.

    Then, I deleted Compressor.app and re-downloaded from the App Store. Same message. Very confused.

  • Martyn Greswolde

    December 19, 2013 at 11:38 pm

    I found all of the files you listed and deleted them and I get the same error message as the OP.

    I have tried my own compressor settings as well as the apple shipped presets and all return the same error (although slightly different to the OP’s)

    Fresh Mint Films

    I know little but I learn quickly!

  • James Cude

    December 20, 2013 at 12:29 am

    Do you have the same problem with completely different clips and one of the built-in transcode presets?

  • Martyn Greswolde

    December 20, 2013 at 12:58 am

    Yep, different clips, as many presets as I can through at it, same result (apart from now I just get the above error.

    Fresh Mint Films

    I know little but I learn quickly!

  • James Cude

    December 20, 2013 at 3:09 am

    When I couldn’t submit in pervious versions, I’d remove ~/Library/Application Support/Apple Qmaster, then restart. This would fix most things. In 4.1, it looks like they are using ~/Library/Application Support/Compressor, so try removing that and restarting. Just be aware that your custom settings are stored there as well, so be sure to copy them before you delete the folder if you want to keep them.

Page 1 of 2

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