Q: Compressor 4.2.1 not processing FCPx  10.2.2 projects

Same Problem here. OS X 10.10.5 - FCPX 10.2.2 - Compressor 4.2.1

Also I tried to send a project from Motion 5.2.1

That also didn't work.

I got the same message from Compressor and also some random crashes.

No, I'm still at Yosemite. Rendering in FCPX works fine. Also when I compress a video file that's already exported, Compressor does the job as expected. I reinstalled Compressor two times, deleting all the Library stuff, but no luck. Whenever I try to send a Project to Compressor it just says "Loading Project", but that never finishes.

Are you completely up to date? Is Pro Video Format 2.0.3 installed?

Actually, the majority of cases I've seen where Send to Compressor doesn't work, the problem was the sending app – not Compressor.

Russ

edot: cleaned up second sentence.

I have the same issue, just started today (10/17). 10.10.5 on Mac Pro 2013, FCPX 10.2.2, Compressor 4.2.1, Pro Video Formats 2.0.3. It worked last week before I travelled, does now results in this same error.

FCPX is able to export the video from within the app. Send to Compressor... results in the error.

The changes I've made to the machine since last week were the software updates available when I booted it yesterday (10/16)- iMovie 10.1 update, iWork updates, Pixelmator 3.4, and 1Password 5.4. I'm guessing (just a hunch) it being something related to iMovie, though I've not run it since the update, and I don't believe I've ever run it on this computer.

I have tried "Reset Queue..." in Compressor's Preferences>Advanced, and ran the Digital Rebellion Preference Manager and deleted Compressor's prefs, but these steps did not change the outcome.

I hope we can get to the bottom of this.

thx!

I also updated iMovie (though I hardly use it) to 10.1 and did open it, have all the updates (FCP X 10.2.2, Motion 5.2.2, Compressor 4.2.1 and Pro Video Formats 2.0.3), running on El Capitan 10.11. I am NOT seeing the issue.

Yes, this issue started for me, completely out of nowhere, about two weeks ago.

I see "Loading project..." instead a preview of the video with the A | B split screen after clicking anywhere on the Compressor screen. Then the preset is lost and I can only see one second of bars.

If I submit batch, after usually six minutes, I get the red "Failed 3x server" message.

And when I say "out of nowhere" that's what I mean. Compressor worked in the morning, it was broken a few hours later with no modifications to the machine at all.

I trashed Compressor and reinstalled form the App Store -- no change in this behavior. I will be looking at other scorched earth solutions like hunting down and trashing every one of Compressor's files.

Frustrating.

Well, the usual scorched earth approach is to pull the settings sub folder out of the Compressor folder (in ~Library/Applications Support). Then trash the Compressor folder. You could also  run Digital Rebellion Compressor Repair.

But as I suggested earlier in the thread, it seems to me that this is at least just as likely to be one of the FCP X glitches, rather than Compressor.

Russ

Putting the error message in to google revealed the same and similar issues have been happening with Compressor since early 2009.

Here are some of the suggestions:

http://jonnyelwyn.co.uk/film-and-video-editing/compressor-3x-crash-service-down- error/

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

my testing was consistent in that with the best s

settings- Resize Filter, Deinterlace, Adaptive Details checked and combination whatsoever of any value above 0 on the sliders for Anti-alias and Details Level gave me the 3x crash. if one of them was 0 then I had no issue. Curtis

When I wanted to share from within Final Cut Pro and either do the preset renders (like Apple Devices) it would give me that 3x crash service down error. Same if I export to compressor - compressor would fail.

Now if I just share, sent to compressor then it would work and compressor would be fine.

But to fix the problem, I uninstalled Perian (like a previous poster suggested) and that solved the issue - no more errors.

For what it's worth, I found that creating a droplet from within Compressor and using that, as opposed to opening the Compressor, have been the solution for some people, myself included.

• First, make sure that you're only logged in to one local account.  A Mac OS feature called Fast User Switching allows you to be running as multiple users at the same time.  This can be convenient, but it also interferes with Compressor's encoding engine.  Often, our students can resolve the 3X Crash Service Down error by logging out of all other users and resubmitting their Compressor jobs.
• If that isn't enough to solve the problem, reset Compressor's encoding services.  From the Compressor menu, choose "Reset

The other thing to try, if that doesn't work, is to go to the finder, hit "go to folder" (apple shift g), and type "var/spool/qmaster", and move the contents in it into the trash. Then reset background encoding and try again.Background Processing."

I have found discussions about the 3x crash problem on the Apple support site as well as other FCP discussion groups but no clear solution seemed to be posted except a suggestion to use Digital Rebellion's Preference Manager. While at the Digital Rebellion site I found "Compressor Repair" which I ran as it also can remove Compressor's preferences.

Russ H wrote:

Well, the usual scorched earth approach is to pull the settings sub folder out of the Compressor folder (in ~Library/Applications Support). Then trash the Compressor folder. You could also  run Digital Rebellion Compressor Repair.But as I suggested earlier in the thread, it seems to me that this is at least just as likely to be one of the FCP X glitches, rather than Compressor.

Russ

Possible.

The historical (totally anecdotal and therefore unreliable) evidence implies it is a much weirder issue than just a sub-folder contents. But, yeah, I'll try that, too!

See me (possibly pointless) research below (and that was just the first page of google hits!).

Rats.

The Settings folder in the Libray…Compressor holds all of my carefully parsed custom settings.

I've trashed them in the name of science and for the good of the community!

Sorry. Guess I wasn't clear. Should have appended to my "pull the settings folder out" something like "and set them aside to preserve them".

Of course you can restore the sub folder  from a back up.

Russ

Trashed the Settings Folder (sigh). Restarted machine, just to make sure. Have even tried a new user account. No chancge in Compressor's behavior.

I can Share from FCPX but Send to Compressor give me "Loading Project…" without any ability to preview anything. Submit Batch shows "Processing" but no progress is ever displayed in the progress bar and eventually Compressor will return the red Failed 3x error.