I cannot figure out what is going wrong with this, i’d have thought it would be simple…
I have 2 macs on a network, both have been blessed with compressor and Qmaster. One is set as a “services only” the other is the “services and cluster controller.” I installed DVD studio Pro on the services machine also.
No joy in harnessing the second machine’s processing power? Don’t tell me that the second station needs it’s own unique license for DVD studio pro / FCP Suite?
The master machine (my workstation) is a G5 dual 2.7, with FCP 5.1.4. The other machine is a newer G5 quad processor, but stands idle most of the day as it’s a under-utilised ProTools machine.
Sorry to butt in without anythign constructive to add:
There is a Qmaster forum at apple.com.
The traffic is low and the consensus seems to be that Apple’s implementation of mutli-machine rendering remains, after 4 years, an unnecessarily cruel joke.
Cool, thanks for the response…I’ll have a look at that guide and see if i can get it to wok. Did you have two separate licenses for each machine? I’m suspecting that my cluster is not working as a result of both being with same serial. Anyone able to shed light on this factor?
And, i think you nailed with the file transfer thing. Network rendering is best suited for framestack type rendering, where each computer gets a set of instructions, and creates a frame from those instructions. 3d rendering is the best example of this. But when you render to a QT movie, you can’t have one machine render the 1st half, and the 2nd render the 2nd half at the same time. one machine, one movie render, thus the limitation. So, encoding works the same way, especially with mpeg encoding. We had a combustion artist at my last compnay I worked for secretly install the combustion render utility on about 20 business computers that stayed on all night, and he worked 2nd shift. i saw him rendering a very complex 60 second spot for the station, and it was done in about 3 minutes, whereas his single machine would have taken over 2 hours. But, he would render to a framestack, so each machine only had to worry about its little bit of the pie, and his machine would divvy out the instructions and the neccesary frames to each computer, then recieve those frames back and place them in order.
might not be the most technical explanation, but that’s how i understand it, and therefore spend my time bugging my boss for a faster machine and more ram, and I leave Qmaster alone to weep for itself.
With FCS2, I’ve pretty much given up on Compressor let alone Qmaster. Just goes haywire for no reason after working for a week or two, and deleting prefs, even complete reinstalls doesn’t help. Sometimes completely crashes FCP, sometimes does nothing when I hit Submit, even the app itself won’t start up separately from FCP. Grrrr.
My experience with Compressor has been different. Different in a GOOD way.
We’ve been able to harness distributed rendering (on 50+ computers) to create our h.264 movies for web based review and approval. The timesavings from this are truly incredible.
I’ll admit that setting this up was not entirely smooth sailing, but once we got it right, we created “droplets” to automate the process. Now, all our assistants have to do is drag a QT movie onto a droplet and the process proceeds automatically.
We have observed some random quits and failures, but that has always been fixed by restarting the system in question.
Keep in mind this does NOTHING for FCP based FX rendering or QT creation. It only works for H.264 movies. But… that step alone is worth it.
I would be most interested in hearing your story in how you were able to do all this, and what issues you encountered along the way, Could you post a short tutorial in how you accomplished it? I would LOVE to take advantage of this, even with just he 5 office computers we have, as you know, any time savings is GOOD time savings.