After install 10.5.7 update QMaster/Compressor hangs/not responding??

Question

I find it funny that the 10.5.7 update was supposed to "improve OS stability". Well it looks like all it has done is made my Mac a worthless pile of pooh.
I have an older MacPro (2007) with two dual core processors (4 CPUs). I setup QMaster as QuickCluster with services (this is the only way Compressor will see it when I submit a batch). I selected 2 CPU instances. Hit "Submit" in Compressor and open the batch window, I see it "try" to parse out the video segments to 2 CPU instances, but get Audio successful and Video "Unknown" with a Service controller "error" and a progress bar for the main batch at 50% with time duration increasing (never decreases).
So I bring up Activity Monitor and find that coreaudio is "not responding" compressor is "not responding" and final cut pro is "not responding" ... oh joy!!
All this "used" to work before the 10.5.7 update, so what gives???
How to reproduce on my hardware:
1. Open FCP
2. Create a Sequence
3. Send Sequence to Compressor
4. In Compress I have a predefined H.264 setting and destination with "Job segmenting" checked, hit submit
5. Open batch window, look at 50% mark with errors mentioned above
NOT very happy.
Rob

Answer 1

Compressor repair? Can you give me more details on what this is?
I had FCP to Compressor using QMaster (2 CPU instances) working in 10.5.6. It created some bizarre project name under FCP (i.e. 13DAA64E-8A34-4476-A12B-86) but would work. With 10.5.7 the same steps just hang/fail -- fail as in they Submitted batch never completes (I can leave it for 10 hours on a H.264 small duration clip of 30 seconds).
So now (with 10.5.7) the only way I can get Compressor and Qmaster to work is if I export sequence to QuickTime movie, close FCP, open Compressor create a new batch using the exported QT movie, set my settings/destination then submit. Which defeats the purpose of using a 2 Instance QMaster in the first place since I've had to introduce a Export to Quicktime in FCP. So essentially any benefit using 2 CPUs has been negated by the extra export step.
Sorry for the frustration/tone, but if I wanted this much hassle with Mac software/OS, I would have just stayed exclusively on a Windows based platform -- as of right now I see very little difference between the two companies, both are not responsive to correct obvious problems and both create more work than solutions. I gotta wonder why I even selected to use a Mac and why I successfully converted at 11 friends over from Windows to Mac - SSDD.
Frustrated.
Rob