marcspag
Level 1 (0 points)

Q: Can't submit batch after 4.1 update...

After updating to 4.1, I receive the following error when submitting a batch:

 

Unable to submit to queue. Please restart your computer or verify your Compressor installation is correct.

 

I removed and re-installed Compressor several times, rebooted numerous times, and repaired permissions. No luck.

 

If anyone has any suggestions, I'd love some advice.

Final Cut Pro X, Mac OS X (10.7)

Posted on Dec 19, 2013 9:45 AM

by Russ H,Solvedanswer
Russ H Russ H
Level 7 (21,780 points)
Quicktime
A:

FWIW, I got the same message. After trashing prefs I ran FCS Remover, emptied the trash and reinstalled. That seemed to cure it.

 

Good luck.

 

Russ

Posted on Dec 19, 2013 2:13 PM

Close
marcspag

Q: Can't submit batch after 4.1 update...

  • All replies
  • Helpful answers

Page 1 Next

  • by Russ H,Solvedanswer

    Russ H Russ H Dec 19, 2013 2:13 PM in response to marcspag
    Level 7 (21,780 points)
    Quicktime
    Dec 19, 2013 2:13 PM in response to marcspag

    FWIW, I got the same message. After trashing prefs I ran FCS Remover, emptied the trash and reinstalled. That seemed to cure it.

     

    Good luck.

     

    Russ

  • by marcspag,

    marcspag marcspag Dec 19, 2013 2:52 PM in response to Russ H
    Level 1 (0 points)
    Dec 19, 2013 2:52 PM in response to Russ H

    Thanks Russ. I actually did that process before but after reading your advice, tried it again. I noticed that on the previous run, I didn't check QMaster in addition to Compressor. I figured since qmaster is frequently at the heart of Compressor issues, I checked that box as well.

     

    After the reinstall, that seemed to do the trick. Much appreciated!

  • by hbuelta,

    hbuelta hbuelta Dec 19, 2013 3:16 PM in response to marcspag
    Level 1 (0 points)
    Dec 19, 2013 3:16 PM in response to marcspag

    Same problem here...

    did as you recommend but still the same... ( used FCS Remover to remove Compressor AND QMaster)

    Before compressor 4.1 upgrade everything worked fine (well.... 'fine' in a 'compressor sense'...... )

     

    Any help will be greatly appreciated..

     

    Thx

     

    Hector

  • by halemmerich,

    halemmerich halemmerich Dec 19, 2013 3:36 PM in response to hbuelta
    Level 1 (0 points)
    Dec 19, 2013 3:36 PM in response to hbuelta

    I too am having the same issue, after following the instructions (deleting Compressor, trashing prefs, using FCS remover on Compressor AND Qmaster), still the same issue:

     

    Screen Shot 2013-12-19 at 6.35.39 PM.png

     

    Please halp.

  • by halemmerich,

    halemmerich halemmerich Dec 20, 2013 11:03 AM in response to halemmerich
    Level 1 (0 points)
    Dec 20, 2013 11:03 AM in response to halemmerich

    Just wanted to reply here, in case anyone else had this issue:

     

    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.

     

    This fixed it ^^.

  • by hbuelta,

    hbuelta hbuelta Dec 20, 2013 1:00 PM in response to halemmerich
    Level 1 (0 points)
    Dec 20, 2013 1:00 PM in response to halemmerich

    Just did as you said and now everything is working fine.

    I also trashed Apple QMaster Folder.

    Even distributed enconding is back to work !!

     

    Greets

  • by Richard van der Laan,

    Richard van der Laan Richard van der Laan Dec 22, 2013 3:36 AM in response to hbuelta
    Level 1 (0 points)
    Dec 22, 2013 3:36 AM in response to hbuelta

    I followed all the steps and additionally removed all old Final Cut Studio files with FCS Remover.

    This without any success. I still get the error 'Unable to submit to queue'.

     

    Any other suggestions to solve this problem?

  • by Cojcolds,

    Cojcolds Cojcolds Dec 22, 2013 7:55 AM in response to Richard van der Laan
    Level 1 (0 points)
    Dec 22, 2013 7:55 AM in response to Richard van der Laan

    I'm like Richard - tried everything mentioned above with no success!!!!!

     

    I removed Compressor v3 and v4 as well as Qmaster with FCS Remover.

    Manually removed personal Library/App Supp/Apple Qmaster & Compressor folders as well as com.apple.Compressor... prefs all to no avail!

     

    The only thing left to do is remove everything FCP (v6 & v10) and try again but I'm suspecting something else is getting in my way.

     

    This is SOOOOOOO TIME WASTING, it's now 3am and I'm now well over it... at this rate I'll miss my Christmas day deadline!

     

    All suggestions are most welcome!

     

    Chz,

     

    Brett

  • by bholtzkener,

    bholtzkener bholtzkener Dec 22, 2013 12:07 PM in response to marcspag
    Level 1 (5 points)
    Photos for Mac
    Dec 22, 2013 12:07 PM in response to marcspag

    Same with me.

    I received the very nice easter egg fixes to FCP and the new Compressor 4.1.

    But I cannot make it start a batch.

    One more thing..

    When I hit start Batch on the main window, nothing appears to happen.

    When I hit start batch on the fole drop down, i get a message that it canot be added to the queue because hte target is not specified.

    I have scanned the Compressor 4.1 docs (more or less) and ther term target does not appear. My destination does seem to set up.

    Thanks

    Barry

  • by Cojcolds,

    Cojcolds Cojcolds Dec 22, 2013 4:37 PM in response to bholtzkener
    Level 1 (0 points)
    Dec 22, 2013 4:37 PM in response to bholtzkener

    Sorry to hear you're in the same boat Bholtzkener (and the others on this thread).

     

    My last efforts were to remove everything FCP (v6 & vX) then re-install them. I'm still getting the EXACT same issue as before. It's relentless and I have absolutely nowhere to turn now apart from rebuilding an entire OS and trying that...

     

    Brett

  • by Richard van der Laan,

    Richard van der Laan Richard van der Laan Dec 23, 2013 1:16 AM in response to Cojcolds
    Level 1 (0 points)
    Dec 23, 2013 1:16 AM in response to Cojcolds

    Still no success in submitting files to Compressor's queue. So no batch processing.

    But what works is sharing a fcpx project straight to a Compressor configured destination.

     

    Maybe this is a workaround if you need to render only one project.

  • by Russ H,

    Russ H Russ H Dec 23, 2013 4:40 AM in response to Richard van der Laan
    Level 7 (21,780 points)
    Quicktime
    Dec 23, 2013 4:40 AM in response to Richard van der Laan

    Have you tried a new user account?

     

    Russ

  • by Richard van der Laan,

    Richard van der Laan Richard van der Laan Dec 23, 2013 11:44 AM in response to Russ H
    Level 1 (0 points)
    Dec 23, 2013 11:44 AM in response to Russ H

    I tried, but without any success. Still the same problem.

  • by Cojcolds,

    Cojcolds Cojcolds Dec 23, 2013 7:48 PM in response to Richard van der Laan
    Level 1 (0 points)
    Dec 23, 2013 7:48 PM in response to Richard van der Laan

    Great suggestion Russ.

     

    I did finally have some success last night though. I formatted an external hard drive and installed Mavericks on it. I then copied FCPX and Compressor onto it and booted off the drive. I had no troubles launching FCPX & Compressor, then encoding my files overnight (though my Mac did seem to fall asleep half way through it and, when I woke it in the morning, the rest of it finished).

     

    As a quick test, I just tried a new account, logged into it and opened FCP but when I tried to open the fcpbundle file to load all of my projects it told me it couldn't work with the file due to permission restrictions. I set the fcpbundle file to read/write for staff & everyone but the file still errored on opening. I even went inside the package to see if I could set permissions for the sub-folders also but some items would allow me and others wouldn't. It's strange that I didn't get the same problem when I booted off the external drive (even with a different account name & all).

     

    Anyway, too many damned hurdles to get this to work!!!!!!!!!!!

     

    Merry Christmas,

     

    Brett

Page 1 Next