What are they, and what do they do?
These jobs differ from the standard SimpleCmd cmdline- and cmdrange-based jobs in that they will "find" a particular version of a 3rd-party application on the worker when the job runs. This has several benefits:
...
| Warning |
|---|
The appFinder jobs do not perform a "best match" for version number; if AfterEffects CS5.5 is specified, it will not use CS6 if CS5.5 is not installed. A warning message will appear in the job logs, and the job instance will be restarted on another worker. |
Applications currently supported as AppFinder jobs in WranglerView:
- AfterEffects (all versions)
- Cinema4D (R14 and later)
How do they work? (internal details for developers)
When the job is submitted, the command line contains a "application template" that looks like __XYZ__ The XYZ portion between the double-underscores specifies which application to run. Currently,the following application templates are supported, being specified in the API library file $QBDIR/api/python/qb/backend/appDefaultPaths.py
...
INFO:CmdRangeBackEnd: attempting auto-pathingINFO:CmdRangeBackEnd: Paths in the command have been translated as per this worker's worker_path_mapINFO:CmdRangeBackEnd: __C4D__ -nogui -frame 3 3 1 -oimage "/Users/jburk/Documents/C4D/renders/test" -render "/Users/jburk/Documents/C4D/test_R14.c4d"INFO:CmdRangeBackEnd: -> "C:\Program Files\MAXON\CINEMA 4D R14\CINEMA 4D 64 Bit.exe" -nogui -frame 3 3 1 -oimage "Z:/Documents/C4D/renders/test" -render "Z:/Documents/C4D/test_R14.c4d"
| Anchor | ||||
|---|---|---|---|---|
|
If your studio does not install 3rd-party applications into standard locations, there are 2 approaches you can take:
...