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