fatal error

Arrrrrrgh nearly a year later, new Mac Pro, new OS, and this problem is still going on!!! Anybody have any solutions?

Did this issue get resolved without my knowledge? Our facility is being killed by this issue, so if there was a solution, please let me know what it was.

Thank you

Hello all, I too am having this problem. So there are definitely some truisms to this problem:
*It's happening with Leopard, FCP 6, MacPros and multi-cores*
*If you export a QT movie and then process it in compressor with the cluster, there's no problem*
*If you send to compressor from FCP 6 and use "this computer" you won't have any problems*
*If you send to compressor from FCP 6 and try to use your personalized cluster (taking advantage of those expensive cores!) it won't work.*
AND AS SOME OF YOU HAVE SAID...and this is a huge flaw for me!
*It won't work AND it won't go away, you can't stop it nor cancel it and when you close compressor and re-open, it's still there, this goes for both "this computer" batches and otherwise, if there's an error in one of your submissions, it won't go away, there's no way to delete it*
Now, I really hope some kind Apple FCP guru sees this and helps us all out because we're trying to find a solution and these discussions are one of our only resources and judging from these posts...THIS IS DEFINITELY UNRESOLVED and extremely FRUSTRATING

One other important thing I'd like to tell you all.
I've tried using less "instances" or cores than I really have, 1, 2, 4, and then the obvious 8 and none of this solves the problem for me.
So I imagine it must be a problem with FCPs communication with a personalized cluster in general, because it's not my configuration of QMaster and if it works importing a QT then something must be wrong in the path from FCP to Compressor

I am NOT having the "won't quit" problem if I jump on the circle x button (stop) as soon as the error appears. If I wait, it acts like it is doing something and does nothing until I reboot! The only workaround STILL TO THIS DATE is to export the movie and compress it. Going direct from FCP to Compressor and using a cluster (internal or networked) doesn't work as of this posting.

Wow... this has been happening for awhile apparently. The whole reason I got this machine was to batch process jobs sent to compressor directly from FCP. I find it more than annoying it hasn't been addressed on a supposedly "pro" rig.

By the way using reference movies causes issues as well. Using self-contained works, but by having to export to.mov's first I'm basically robbing Peter to pay Paul in terms of time savings.

Yo Apple.. pick up the ball!

Just getting into Qmaster myself, so I spent a few hours feeling my way around and eventually got it set up, only for it to error out on all machines in the cluster with ""FinalCutPro generated an error or unexpected quit." My immediate thought was that an upgrade from FCS to to FCS2 would fix the problem. Luckily I came here and so I could save myself hours of frustration (and the cash), until they find a fix. Very sad as I have numerous computers just waiting to join in the fun!!

I have exactly the same problems as described above running FCP 6 and compressor 3 on a 8 core mac pro.
Exporting the movie first to quicktime and then process it seems to be the workaround. Apple please fix this problem, this is supposed to be a "PRO" solution!

TRY THIS:

Hey guys I think that after 10 hours of battling this thing I might have just figured out.

May not be the answer for all, but here goes nothing: (This in fact fixed my issue)

I realized after hours of battling this that it was hit or miss if I disabled or enabled the network on both my macbook and my macpro, so immediately I realized it had to do with networking.

So what had I changed recently that would cause this problem ........ MobileMe/.Mac settings.

A while back I had disabled "Back to my Mac" as it was causing some other unrelated problem and I had forgotten about it, so now that the mobile me update came out I decided to turn it back on on both devices and forgot about it.

Check your .Mac/MobileMe settings under the preference panels and Turn Off “Back to my Mac” (Last tab)
Reboot your systems and give it a try.

Please do post back, I want to know if it was pure luck on my part.

Thanks.

I HAVE THIS PROBLEM TOO, GUYS BEFORE ANYTHING CHECK THAT WHEREEVER YOU ARE SENDING THE COMPRESSED FILES TO HAS ENOUGH SPACE, I KNOW IT SOUNDS OBVIOUS BUT BELIEVE ME IT WONT HURT TO CHECK, IT WORKED FOR ME, LET ME KNOW IF IT WORKS

PS. The problem basically means that compressor cant read o write to or from the target

hope it helps

As of the last ProTools update (003?) with 10.5.5 this is still a problem. I set Qmaster up on my MBP and on a G5 both with FCP and I get the same error. It's really sad because I'd like to be able to render my files, not just compress them, with Qmaster. Oh well, guess I just joined the club and get to sit and wait for HOURS while my HD footage processes. Thanks Apple.

I just bought a mac pro so I could compress quicker and i find myself with the same speeds i used to have with my imac..... I don't understand how this problem could be around for over a year without fixing. I mean, really??? I have searched and searched and read and read and i keep getting this error when i send a job to compressor and try to use a quick cluster:
Final Cut Pro generated an error or unexpectedly quitUser aborted Media Server

I then have to reboot my computer, and then just compress normally. I can export to quicktime and then give to compressor and it will work but that is a silly workaround that takes a lot of time. I'm not even sure it would save any time really.

Anybody know if there is a fix???

I'm just curious, how do others do it? I mean, are we the only ones who are having these problems? My project takes 6h of rendering (for a 40min clip), and it only utilizes one processor core.

... seriously considering an alternative (unfortunately a windows one) which worked fine, before I switched to FCS2.

ps: is there a Sony Vegas port for OS X?

This definitely did the trick where all else had failed:
http://www.digitalrebellion.com/blog/posts/howto_reinstall_compressor_andqmaster.html

To work around this, I simply export the desired timeline to Quicktime but DO NOT make the movies self contained. Usually, a 10 minute sequence will export in less than 15-30 seconds. Then I drop the timeline reference Quicktime into Compressor and everything works as expected.

Re-installing, clearing prefs, exporting from the browser, chanting, etc., did nothing to solve the problem of exporting from the timeline using FCP 6.0.5 and QMaster 3.0.5.