Re: Compressor Settings
Re: Compressor Settings
- Subject: Re: Compressor Settings
- From: Darrin Cardani <email@hidden>
- Date: Thu, 15 May 2014 09:57:21 -0700
Robert,
Here’s some more info from the Compressor team:
1) There is a little more documentation in the Compressor Help files. From the Help menu, choose “Compressor Help”.
2) From the contents on the left side of the window, open “Work Smarter,” then “Use Distributed Processing,” then “Use the Command Line”.
There are some examples in that section of the docs.
Also, I asked them about the XML format for settings files and they had this to say:
> There is no other way to easily create them other than using Compressor. That being said, they are XML, and once created in Compressor, an application can modify them in mostly obvious ways (width, height, frame-rate, etc…), however this is undocumented, and not guaranteed to be “future proof”. The best approach is for said 3rd party app to make a variety of settings in Compressor covering their needs, and then offer them in a menu to their users. If the setting is made in Compressor, then it is future-proof.
Darrin
On May 14, 2014, at 4:54 PM, Darrin Cardani <email@hidden> wrote:
> Robert,
>
> I’m no expert on Compressor, but from the response they gave me, it looks like the only way to supply detailed settings is via the command line interface, and specifying the path to a settings file.
>
> I’ll have to ask about for more details on the -info flag and the XML settings documentation.
>
> Darrin
>
> On May 14, 2014, at 11:13 AM, Robert Monaghan <email@hidden> wrote:
>
>> Hi Darrin!
>>
>> I looked at the output, myself. A touch sparse .. :)
>> I take it that there is no way to provide detailed settings, like crop, scale, interlace modes, etc. via command line then?
>> The -info flag looks interesting, could this be a potential way to push settings into a job?
>> I also looked at the settings file, which is a fair bit of XML soup. Is there any docs on it?
>> If I were to only provide some of the tags in the settings XML, will the rest be populated by defaults, internally?
>> Older FCS3 packages tended to do that...
>>
>> I really hope to pass stuff using a command line. Sandbox is a pretty significant sink-hole, as development time goes.
>>
>> Thanks again!
>>
>> bob.
>>
>>
>> On May 14, 2014, at 10:50, Darrin Cardani <email@hidden> wrote:
>>
>>> According to the Compressor team, the command line tool’s interface is documented via the -help option:
>>>
>>>> cd /Applications/Compressor.app/Contents/MacOSUsage: Compressor [Cluster Info] [Batch Specific Info] [Optional Info] [Other Options]
>>>>
>>>> ./Compressor -help
>>>>
>>>> -computergroup <name> -- name of the Computer Group to use.
>>>> --Batch Specific Info:--
>>>> -batchname <name> -- name to be given to the batch.
>>>> -priority <value> -- priority to be given to the batch. Possible values are: low, medium or high
>>>> Job Info: Used when submitting individual source files. Following parameters are repeated to enter multiple job targets in a batch
>>>> -jobpath <url> -- 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).
>>>> -settingpath <url> -- url to settings file.
>>>> -locationpath <url> -- url to location file.
>>>> -info <xml> -- xml for job info.
>>>> -scc <url> -- url to scc file for source
>>>> -startoffset <hh:mm:ss;ff> -- time offset from beginning
>>>> -in <hh:mm:ss;ff> -- in time
>>>> -out <hh:mm:ss;ff> -- out time
>>>> -annotations <path> -- path to file to import annotations from; a plist file or a Quicktime movie
>>>> -chapters <path> -- path to file to import chapters from
>>>>
>>>
>>>
>>> So I think you can add “-settingpath <url>” to the command and get it to use any settings file you want. (You could put it in the /tmp directory, or have some presets in your app bundle, or whatever.)
>>>
>>> Darrin
>>>
>>> On May 14, 2014, at 4:19 AM, Robert Monaghan <email@hidden> wrote:
>>>
>>>> Hi Everyone,
>>>>
>>>> I am adding the ability to send a job to Compressor 4, from within my application.
>>>> One of the abilities I am working through, is to allow the user to select range of options for export.
>>>> For instance, the user may want to export a scaled movie, rather than the actual size.
>>>>
>>>> I see that I would need to provide a settings file, in order to render a job. This is a “.cmprstring” file located somewhere in the users’s home directory.
>>>> Can I provide this string dynamically via command line? Or, do I have to pre-generate a library of “.cmprstring” files, to include along with my application?
>>>>
>>>> Thanks!
>>>>
>>>> bob.
>>>>
>>>>
>>>> Robert Monaghan
>>>> Glue Tools LLC
>>>>
>>>> P.O.Box 24124
>>>> Santa Barbara, CA, 93121
>>>> United States
>>>>
>>>> tel: +1 805 456 7997
>>>> fax: +1 805 456 7998
>>>>
>>>> www.gluetools.com
>>>>
>>>>
>>>> _______________________________________________
>>>> Do not post admin requests to the list. They will be ignored.
>>>> Pro-apps-dev mailing list (email@hidden)
>>>> Help/Unsubscribe/Update your Subscription:
>>>>
>>>> This email sent to email@hidden
>>>
>>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden