Compressor 3's QAdministrator hogging cluster

Hi Folks,
I'm on latest version of Lion, FCX, Compressor 4 and latest for Compressor 3 from FCS3.
I can create a cluster just fine through system preferences, but Compressor 3 " hogs " it and won't let Compressor 4 see it.
By that, I mean, I can go into QAdministrator from within my Final Cut Studio folder and it sees the cluster. Then I can adjust and create my cluster, go into Compressor 3 and after clicking Submit, I see it as an option.
If I bypass Qadmin from FCS and go into FCX and choose share - send to compressor, version 4 launches, but if I go to Apple QMaster on the menu bar, it will not see the cluster. Therefore, I can't use it upon submitting.
I tried trashing QAdmin from FCS, but that did nothing.
Any thoughts? very frustrating b/c I used to export a self-contained QT from FCP7 and used BitVice to compress m2vs for DVDs as it automatically recognizes all cores.
Unfortunately with Compressor 4, i still have to tweak settings so it will use all cores - but that doesn't seem to be working either!
I'd use Compressor 3, but of course, when you share - compressor from within FCX, it goes to the new version.
Any ideas?
Cheers,
Keebler

Hi Kleeber, quiet an interesting problem. I dont have the same environment as you do so I'm going to suggest that these might be places you could look.
it seems compressor.app V4 administers all Apple Qmaster itself via the Compressor.app | application menu Apple Qmaster and maintains this state information in ~/Library/Application Support/Apple Qmaster. (getting tired oft yping this in .. ). This is unlike Qmaster V3 that was managed autonamously via the system preferences/Qmaster and maintained it goodies elsewhere... you know all this..
so back in July 2011 this made me think that the two compressors (V3 and V4) were not meant to chat to each other.. any ideas?
further the CLI interfaces for qmasterprefs, qmaster and compressor are now buried in the content of the new FCPX apps.. yep fine with that but they had Links (ln / alias) in the V3 and FCP 7 days where one could simply invoke these form the cli via terminal.app ... all this you probably know too. Interestingly Apple have documented very well in detail the use of the compressor cli command in the Apple Compressor Users Guide V4.. yes all this is known.
what appears to be missing is the use of the qmasterprefs and qmaster cli commands in the documentation of Apple Qmaster V4 (see the pdf). this strikes me as that this is no longer a supported interface for qmaster and tha one MUST USE the Compressor.app | application menu Apple Qmaster UI.. any clues on this welcomed!
so?? well this strikes me as a bit odd. I would think a CLUSTER is a CLUSTER... I too use Apple Qadministrator and make use of managed clusters.. seems more stabel that the Quickcluster in FCPX/Com.app V4).. for me any way.
Thus, I would think that in a rendering sense (Nuke etc) you could submit a render to a Qmaster cluster regardless of it origin (Compressor V4 + Qmaster V4 or Qmaster V3 and Compressor V3.5)... just a thought. Same with the transcoder.
I can try and account (guess?) for why Compressor V4 cant see the Cluster you created via Apple Qadminstrtor V3.. Maybe because the state information for the cluster(s) is now maintained in ~/Library/Application Support/Apple Qmaster (user directory btw!)... So Id imagine that FCPX / Compressor V4 are expecting goodies in here. I just checked and its seems not. Instead Apple Qadminitrator is using many ports to see whats aorund. Theres loads of undescribed file handles opened as well.. Thus unless the application has radically changed from qmaster 3 and Qmaster 4, then I'd imagine that Apple Qmaster4 and V4 should be able to see the clusters! Someone reading this may enlighten us.. please do.
In short its most possible that FCPX + compressor V4 + apple qmaster v4 are tied together more that I have tried to describe above. Its very strange that the cluster you created under Apple Qadministrator cannot be found when using the workflow:
FCPX:send to compressor ; compressor V4:submit to cluster: cluster not in the list.
In the Compressor V4.app are you able to Mount the Cluster Storage? (+shift+m)? If so then thats a good sign because it uses ports to find these it seems.
do you have any further developments?
warwick
Hong Kong

Similar Messages

  • Compressor 3.5 'my computer' cluster option missing

    Hello
    I'm hoping someone can help me. I am using Compressor 3.5 and it's been working absolutely fine until today when I sent a project for FCP to compressor, added all my settings and destination, clicked submit but when the drop down box appears, the submit button is greyed out. For the 'cluster' option where it used to say 'my computer' now says 'none' and I can't seem to add anything here. I've tried the troubleshoot options of deleting caches for qmaster and compressed, deleting the 'com.apple.Compressor.CompressorSharedService.plist' and 'com.apple.compressor.Compressor.plist' etc but nothing seems to be working. I've tried googling this problem but I can't find a solution. I'm using a Mac OS X 10.9.4 (3.5 GHz intel Core i7)
    Any help would be much appreciated
    Many thanks
    Kaylee

    Oops! Forgot that Mavericks broke the Qmaster Preference Pane. You can still access it through the CLI (Command Line Interface), using Terminal. See this doc.
    Alternatively, download and run the free and safe Compressor Repair form Digital Rebellion.
    Let us know how you make out.
    Russ

  • Compressor post-processing applescript and cluster

    I'm having a lot of trouble using a post-processing applescript. I have a preset that pumps out an mp3 from an hdv .mov. the post-processing script does some funky stuff and should pump out an xvid .avi. when submit the job to "This Computer" it works fine, I get the .mp3 and the script gets kicked off and generates .avi's. When the job is submitted to our cluster, however, the job fails immediately, doesn't generate either mp3s or .avi's. the log has the following:
    <----snip---->
    pid="250" msg="Hard-linked source file to cluster storage."/>
    <log tms="226012897.974" tmt="02/29/2008 13:21:37.974" pid="250" msg="Job resource error: System Error = 1 {Operation not permitted}Failed to read filethread terminated due to exception (remote exception). This is likely caused by missing or renamed watermark filter file."/>
    <mrk tms="226012897.975" tmt="02/29/2008 13:21:37.975" pid="250" kind="end" what="service-request" req-id="D729F684-764C-439E-9A06-888BB4C9405C:1" msg="Preprocessing job request error (exception=Job resource: System Error = 1 {Operation not permitted}Failed to read filethread terminated due to exception (remote exception))."></mrk>
    </logs>
    </service>
    </services>
    <----snip---->
    all requisite files have been placed on either a global filesystem (OD home directory for the post-processing script itself) or copies have been distributed to all nodes (a requisite to the applescript). The submitting user has full read/write permissions to the working dir and any subfolder.
    Any ideas?

    In case anyone runs up against this one, I found a solution/workaround. It turns out that when submitting the job to the queue, qadmin would copy the applescript over to the shared folder. During this copy, it would change attributes of the file such that the OS thought the .app was a classic application and would refuse to run it.
    Workaround: in compressor preferences, set "Cluster Options:" to "Never copy source to cluster"
    Luckily this worked for our setup as we assume all source media and scripts are already on a global filesystem.

  • INTEGO NET BARRIER CRASHES COMPRESSOR/QM, and says Virtual Cluster not seen

    I just discovered via process of elimination that Intego Net Barrier 10.4.5 was crashing compressor. While Compressor was hung ("waiting" in Batch Monitor, would not allow cancel), I tried de-selecting different settings in NB, to no avail... BUT... when I disabled NB completely, compressor un-hung immediately and began processing my submission without a glitch, seeing even my virtual cluster.
    Bye Bye Net Barrier.

    I installed the Update Rollup 4 to my SCVMM 2012 SP1 installation, and this is ok now.
    Mark

  • Compressor jobs fail when using a 6 instance cluster

    Hello all,
    The last week or so, any file I send to Compressor and use my quick cluster with 6 instances fail. Not only does it fail it locks up my entire system!
    Does anybody know what's going on?
    Thanks

    This works great when bringing files into compressor to be converted to other formats, such as a QuickTime Movie... but, I have not had any luck trying to export this way directly from FCP. I've tried on multiple machines and I always get the error "Failed - HOST ["Machine Name".local] Final Cut Pro.app generated an error or unexpectedly quitUser aborted Media Server. Then it tries to cancel the export but just sits there until I either Force Quit FCP, stop sharing in Apple Qmaster or restart the machine. Should this be working as far as sending FCP projects to compressor for export, or will it only work by bringing in an already exported file? Anyone have any ides or suggestions?

  • Compressor 4.1 shared cluster computer not appearing - but slave can see master

    On my main "master" machine, I cannot see one of my shared cluster machines. However, on the particular shared cluster machine (slave) that my "master" cannot see, the slave can see the master in the list of shared computers. So, in other words, I suppose I could launch the Compressor job from the "slave" machine [since the source file is on a network drive that all machines can access], but it doesn't make any sense.
    Why can't the "master" see the "slave".
    I've tried restarting the master computer, tried turning off wifi and ethernet on the master computer, tried manually inputting the IP address and host name on the master computer in the list of shared computers by hitting the "plus" button. Also tried setting the "Use network interfaces" option to either both, ethernet only, or wi-fi only, also tried resetting the compressor queue, and trashing the Compressor preferences.
    Nothing works. What's strange is that this master computer was able to see the slave computer two weeks ago, using Compressor 4.1. Nothing has changed. They are both on the same 10.0.0.x network and subnet. The master machine can ping the slave machine.
    Any ideas?

    Just posted this in this discussion forum. Might be helpful even though its specifically for Compressor V4.0.
    Run through some of the the procedure if you are on Compressor V4.0 earlier.
    https://discussions.apple.com/thread/5781288?tstart=0
    As you're using Compressor V4.1, check the cluster and compressor logs for errors and network and file system permission errors:
    ~/Library/Logs/Compressor (new in V4.1) to see what he jobcontroller and services node are doing
    check /var/logs (system log)
    else for compressor V4.1 it seem sensitive to hardware configurations now.
    might be of some help.
    w

  • Compressor not seeing cluster

    Hello, i set up a real cluster, not a quick cluster like everyone else seems to be doing...and when i open compressor to submit a job to the cluster...it does not see the cluster. the weird thing is that batch monitor on that same computer can see the cluster.
    any ideas?

    Ron,
    I don't know if this is a little late, but I have been experiencing the same problem lately - and noticed something odd:
    I have a 'part-time' qmaster cluster of intel iMacs to aid web and DVD video compression. They're setup as a managed cluster, and I sometimes experience the same problem you do. The cluster appears in the batch monitor, but not in Compressor. After much head scratching, I noticed two things:
    1) Compressor doesn't seem to list a cluster if none of the nodes are offering compressor services.
    2) Even if you have setup a node to offer compressor services, those services will not appear until that Mac is logged in. (i.e. If you boot up to the login screen, only the 'Rendering' services will appear. You need to log into an account to enable the 'Compressor' services.
    This was a problem for me, as the 'part time' cluster of iMacs were not set to automatically log into an account.
    So - The macs need to be logged into an account to enable the compressor services ... and Compressor will not list a cluster that has zero compressor services available. I suppose in some ways it's a good thing that Compressor checks the available services before offering it as an option.
    The way I see it: QMaster looks like a great solution if you have dedicated machines. But as a part-time render farm, it can be troublesome to setup.
    Good luck!
    Oli Trenouth
    Media Developer
    National Museum of Photography, Film & Television, UK.

  • CLI framerate and serial jobs on a cluster

    Hello,
    I have couple of questions for compressor (ver 4 )
    1) Is there a way to specify framerate for image sequence using command line interface.
    The compressor help lists the following but does not provide a way how such an option work. I tried few different ways in vain
    -jobpath  -- url to source file.                        -- In case of Image Sequence, URL should be a file URL pointing to directory with image sequence.
    -- Additional parameters may be specified to set frameRate (e.g. frameRate=29.97) and audio file (e.g. audio=/usr/me/myaudiofile.mov).
    2) I have a managed cluster with 8 nodes each running 4 instances. For some reason compressor only uses 6 instances spread across many nodes and not all 32.
    3) Is there a way to specify and process just one job for a given cluster? This is equivalent of serialize option but it does not seem to be available.
    Currently when I submit multiple jobs few of them run at once and create a havok on NFS mounts and fail. I can limit the job queue to one but that is not ideal.
    I would appreciate any pointers.
    Thanks
    --Amit

    Hi Amit, just saw your post. I assume you are passing the settings via the "-settingspath" <my_specific_job_settings_in_a_file_path_somwhere.settings" on the compressor command?
    If so, it's a very simple matter to specify the frame rate etc etc on the VIDEO setting itself, save it and use it.
    I don't recall that such "atomic settings" we're actually available in the v3 of compressor.app. I'll check later for v4. I'd be surprised  if they are. :)
    What I've done in the past is to simply make my own personalised settings (and destinations) up using  the Compressor.app V4 UI (save as ... my name .. i.e.  prores_noaudio_PAL" and path these file paths on the -settingspath" parm on the compressor cli. In your case I'd imagine a simple VIDEO setting for your frame rate and you're set!
    Compressor.app v4 makes any of your own R.Y.O settings on your ~/library/application support/compressor/settings folder. You can copy or move or link these anywhere you like and pass these customised Parms to compressor cli as above.
    I doubt also if these atomic settings are available as AppleScript properties, there's likely no vars like that there me thinks. . I recall the same ones exist as they do for the cli and now in compressor.app 4 they probably support Qmaster .. Yeah.. Compressor.app is apple scriptable.. It's not in the default list library so just add it...
    Lastly as a guess these compressor ".setting" files are probably XML base.. So you might consider to tinker with one with an editor.
    Anyway.. Try then"-settingspath" operand and see how u go.
    2) the way Qmaster schedules across unmanaged transcode nodes is likely based on how busy each node is. You should be able to see if there is a pattern simply by looking on the Qmaster job controller.log .. See share monitor.app info or use console.app look on
    your ~/library/application support/apple Qmaster/logs directory. There will be something in there.
    Also have a look for any errors on the cluster services logs in case the services you expects to be there are actually not.
    Are you using a managed cluster? Personally I have found this quite stable. Make sure u insure that those services are for managed climates only..
    3) yes you can specify a specific cluster on the using the "-clusterid" operand. Should you have more than one managed cluster in the farm, this is a cool way to go. Also considering the "-priority" operand usage as well for hot jobs. Make sure all submissions are low priority... It's batch.. Works great!!
    4) NDS mounts.. Well the simple rule is to keep them mounted on their own subnet, maker sure all destinations and sources are available to all hosts, set compressor options to copy to cluster only when ya must, and make sure the service time for NDS io READ Request is as fast as u can make it. ( jumbo frames, dedicated NICs and sinners and optimum fast read file systems... Keep other traffic away for it.. Works a treat!
    Should you turn something up pleased at it here for others to see. I'm certainly interested.
    Sorry for typos.. Just on MTR with iPhone on way home. :)
    Hth
    Warwick
    Hong Kong

  • Basic Questions (Compressor/Qmaster)

    I can't find answers to some really basic questions:
    1. To distribute Compressor tasks, is Qmaster and Compressor required on all participating Macs?
    2. Are they required to be exactly the same version across the participating Macs?
    3. Are they required to have unique serial numbers? (I tried to start Compressor on a second Mac that had been installed from FCS 5.1 Crossgrade package that resides on original Mac - all that was on the second Mac was Compressor and Qmaster - Qmaster didn't seem to mind, but Compressor gave me a warning message and terminated....)
    4. Assuming the above issues have been resolved as required, does Compressor have to be started on the "Services Only" Mac in order to assist in the processing?
    Again, my apologies for the level of these questions....
    Stan

    1. No - just use the Qmaster node installer (In the extras folder of Final Cut Studio install disc).
    2. Yes - same versions of Qmaster
    3. The nodes don't require a serial number.
    4. No - just turn on Services in the Apple Qmaster panel of System Prefs. On the nodes, check Share and Managed and click the "Start Services" button. Set up the Nodes as Services only and your Controller (the machine with Compressor installed) as Services and cluster controller. Then use Qadmin to set up the cluster.

  • Trouble with Qmaster, Compressor

    Hello all!
    I am trying to compress a 48 Minute long HDV sequence to HD-DVD using the H.264 60 Min encode settings, and I am having problems.
    I have read how to setup Qmaster to run multiple cores, so I have made a 4 core quick cluster on Qmaster with the following settings
    "Quick Cluster with Services" - Checked
    Under the services box, I have "Share" checked for Compressor
    I have 4 instances selected (out of 16 possible)
    "Include unmanaged services from other computers" - Checked.
    All other options unchecked.
    On Advanced menu, only "Log service activity to file" was checked.
    What happens is that when I submit the job in compressor (I select the 4 cluster when I submit), I see all the instances in Activity monitor, but one of them is red and non-responding. I can't get all the instances to do work at the same time, as the cpu utilization is only indicating one instance doing work at a time. I thought they were all supposed to be utilized.
    In the end, I waited 36 hours, and the encode still wasn't finished.
    Any ideas what could be going on? Am I set up correctly? Let me know any thoughts!
    Thanks,
    Ken

    Hi Ken here's some ideas. I use compressor/Qmaster all the time. I too have a brand new Nehalem MACPRO 2.93 @ 12GB.
    Firstly for distribution, *compressor is your best friend*... see why...
    Some diagnostics tips first:
    • go check out /var/logs or the utilities/console.app (leave the late in the dock). Look under the various directories for QMASTER. There is usually a wealth of information in there.
    • COMPRESSOR.app/prefs: not always but worth it to (a) MOUNT the shared cluster storage you used in /system prefs/qmaster/advanced: shared cluster storage
    • COMPRESSOR.app/: look at HISTORY
    • Batch MOnitor.app : check on the "i" status for each node running a segment in the multi pass segmented transcode (segment=TICKED in inspector video for compressor). Look at the "status" and "logs" in the pane.
    • turn off ALL network devices (airport, EN & FW) until you get it working QMASTER seems to go looking everywhere for other nodes.. so dont let it.
    • COMPRESSOR.app/prefs: set "NEVER COPY SOURCE TO CLUSTER" - we'll work about his when yu start to use other nodes outside your MACPRO.
    • COMPRESSOR.app/reset background processes - to start
    OK when you have all tjis done... let look at some ways to commence to fire up Compressor using Qmaster cluster.
    • assume QUICKCLUSTER ste up: click "managed services=ticke" if you like
    • *systems prefs/qmaster:* set SERVICES: for number of instances I am using 14! (*yes 14 instances*) on this MACPRO and it rides all the 16 cores and I can edit fine on FCP at the same time..PLenty of head room in these new MACPROS 2009 models (+doubters go buy a dell p.o.s+ ). *CAVEAT= YOU HAVE ENOUGH RAM* - not sure if 6GB will cut it so trial and error.. works great for me thou and I have 8GB not used from 12GB!. NOte in the non Nehalem MACPRO era the R.O.T. was one instance of compressor per core... however since I have bene usingthis baby on the last few days I have cranked it to 14 instances and it runs fine and all cpres are nearly 100% usage with a very responsive machine. THe transcodes are at least 3-4 times faster than my 8*core 2007 MACPRO!.
    •  *systems prefs/qmaster:* / advanced: tick the port ranges =on.
    OK .. now you're ready to rock!
    1) *systems prefs/qmaster:*: setup: clock OPTION=CLICK over the start button to RESET any transcodes that were going.
    2) Set up a job in compressor.app making sure "job segmenting" is ticked in the ENCODER inspector.
    3) submit and select your cluster in the list box.
    4) sit back while your new MCPRO 2009 earns its money! - watch all the cores light up GREEN in the activity monitor!
    5) watch teh console.app "all messages for errors" form QMaster.
    OK.. this is only a summary.
    POst your results of PM me if you need help.
    I love compressor and Qm especially on this NEW MAC PRO.. it just smokes anything else I've used for transcoding.
    Oh: *and one other tip for your workflow* which you can take or leave regarding HDV. Yep its not on may favourite codec list but here's some good tips for getting your compsition ready for distribution as you are trying to do from when I owned a SONY-Z1P HDV some years back.
    This will cut 10's of hours of what you are seeing. (well maybe not that magnitude).
    With the edit prepared and not rendered:
    • take ALL the footage fomr the HDV that you ingested form the tape in the CAPTURE folder and use COMPRESSOR.app and transcode it to PRORES422 only. (Same resolution etc etc).... Simply try this out please. USe "copy and BLOCK SELECT + paste all the codec+targets information in the COMPRESSOR window.. its simple... submit it to your QMASTER and come back in say 10 minutes .. it shoud all be done. (what you have done is to make a mezzanine instance of LGOP HDV footage into iFRAME PRORES422 - no quality has been lost nor gained.
    • in your FCP project DISCONNECT all the media from your Sequences and then RECONNECT the media to the same file names that are the new PRORES 422 - (conforming) in FCP.
    • now your edit sequqnces are pointing to the PRORES versions of your clips. edit at will here and watch the play head and edits slice through prores422 like the proverbial +hot knife through butter+ (assume you have a fast disk system underneath.. my MACBOOKPRO does this in its sleep).
    *when your ready to make a distribution*, try this from within FCP timeline/sequence:
    • export QUICKTIME MOVE" as a reference movie (untick "self contained") and call the movie client_ref.mov (etc) . *This step is very important*. And +DONT EXPORT TO COMPRESSOR+. this is nuts at the moment. wait for FCS V3 soon I hope.
    • last step: make this distribution using COMPRESSOR by using the reference clip client_ref.mov as input to compressor.
    And as they say .. thats it!
    Ph one more cool thing.. while it is transcoding and all your cores are ringing out at 99% each, try setting up a COMPRESSOR DROPLET. Set this on your desktop and drag and drop client_ref.mov onto it.. and watch compressor and master do their work.
    Yes.. compressor is your best mate when you set him up properly.
    HTH
    w
    sorry for the typos, I'm in a hurry...

  • FCP export using compressor

    does anybody know where the jobs compressor submits get stored?
    I can't export via compressor out of FCP 6.1, (FCP quits responding) but if I export a quicktime then get that in compressor using a quemaster quick cluster, it rocks along fine until I forget I can't export out of FCP, or a freelancer does it and resources get stupid until the job finally finishes. cancelling won't fix it, quitting, shutting down none of it stops the job. If I could find where the job is stored I could trash it and work could renew. Thankyou

    duh
    users/library/aapplication support/compressor/history
    fixed it. now if only I didn't have to worry about export using compressor from FCP 6.1 Studio2. wouldn't that be something? if it really worked? wow that'd be cool

  • Compressor 4.05: submit-button greyed out

    When I want to submit a job in Compressor 4.05 the name/cluster/priority-window pops up but the 'submit' button there is greyed out.
    I tried to run a small programm called Compressor_Repair but of no avail. Effectively Compressor 4.05 is useless now.
    Until the last upgrade to 4.05 Compressor has always functioned.
    Now what? Please don't tell me I have to uninstall Compressor and delete files from over 10 different folders before reinstalling again.

    Called Applecare today. There was no quick solution and I'll receive an email with follow-up steps to make another user account and see if it happens again. Hopefully I can resolve the problem myself, otherwise I have to go back to Applecare and pay €90 for further support since it's been over 90 days that I purchased the "professional software".
    In fact it's cheaper to purchase again
    This is the full mail I received from Applecare, except signature:
    Hi Jerome,
    http://forums.creativecow.net/thread/20/857850
    http://support.apple.com/kb/TS1888

  • Qmaster and compressor - the forever copying file

    I have witnessed this phenomenon numerous times now and am ready to throw my computer through the wall. I have created a quick cluster - 2 Dual 2.5 G5's connected via Ethernet (direct, no switch). I have exported my FCP doc as a self-contained QT movie (30GB file), made a single batch in compressor and sent it to my cluster. In the batch window, I see it says "status: Preparing: Copying source file" After 2 hours (yes, that's right. 2 hours to transfer 30gb file via 1000 BaseT - a whole other bag of worms you can try to clarify to me if you'd like), but after 2 hours, it completes the copy and begins to copy it again. Just starts over for no reason. I am now 6 hours into the batch and it still has not finished copying the file. WHat is going on?!!!!!!!! There is plenty of room on the other computer.
    Please, someone help me out.

    You may have figured this out by now, but in Compressor/Preferrences there is a Cluster Option "Copy source as needed". Changing this to Never will stop the copy.
    This may or may not help, but make sure that all drives are mounted for all comps are mounted on ALL comps, to make sure each comp has access to any resources needed on the other comp. i.e. Make sure all drives on Comp A are mounted on Comp B, as well as all Drives on Comp B are mounted on Comp A.
    This should prevent any errors due to missing resources.
    Ta
    Gary

  • 4 Node Q-Master Cluster issue with Nodes stuck at "Waiting"

    I have a 4 node QMaster cluster configured no problem, One Cluster Controller and 3 Service nodes. When i export a project from FCP to compressor i can assign the cluster no problem. Then the only node that starts to process is the cluster controller, The service nodes stay at Waiting.... I f i make any other service node the Cluster controller then THAT node starts to process and the 3 Service nodes are stuck at waiting.
    I can mount the cluster storage on all nodes and i am able to read/write to that volume.
    The source material (Firewire drive) is also mounted on all nodes.
    The setup is a new MB-PRO running FCP 5.0 and Compressor 2.0, QMaster 2.0 , the cluster nodes are all 1ghz G4's
    Any ideas?
    Many thanks
    MACBOOK PRO 2.1 Mac OS X (10.4.6) Multiple G4's
    MACBOOK PRO 2.1   Mac OS X (10.4.6)   Multiple G4's

    I don't recommend submitting to a cluster directly from the timeline. Instead, export a QT referance movie, and submit that to the cluster via compressor using a setting that has 'allow job segmenting' checked. If that is not checked, then you are telling Qmaster to only let one machine work on that file - this is recommended for high quality, multi-pass VBR Mpeg2 jobs because of how multi-pass and VBR work...
    If you submit from outside FCP, but you are doing multi-pass VBR, you can send your cluster 4 jobs that will all happen at the same time tho.
    Basically, to use all the nodes, it needs to have the whole file and be allowed to break it into segments, and send thos segments to the nodes. when you export off the time line, fcp sends the data to compressor frame at a time, not as a whole file, thus, no segmenting.

  • Service nodes are greyed out

    I am trying to create a cluster between my i5 iMac and my MBP.
    I am following the instructions in the manual but when i get the the last part, after creating a cluster where I am supposed to drag service nodes in from the bottom of the Apple Qadministrator panel I can't do it because the services nodes are greyed out (see image).  Any thoughts?  Thanks all!

    Hi - I eventually figured this one out.  Took a while! 
    In the dialog where you set up the original 'service nodes' on the client machines (where you go Apple QMaster > Share this computer) there is a checkbox 'Require this service to only be used in Managed Clusters'.  It seemed bad to be so I didn't check it.  Nothing in the instructions says to.  But you must.
    Once you do this, the service lines all magically go black, and you can drag them by their header up to the box.
    It then all worked fine for me, but only for jobs loaded via compressor.
    So far no-one has confirmed the bug I noted that jobs I enter into compressor and send to a cluster work reliably, but this does not happen when from within FCPX I try to do the Export > Send to Compressor and choose a cluster.
    If you could let me know how this goes I'd be grateful.
    Chris.
    PS - I think at this stage that just about no-one in the whole world is actually trying to do any of this.  Must just be us two.  :-)

Maybe you are looking for