Icon

This is the documentation for an older version of Qube. The latest version of the documentation can be found here: Qube

Versions Compared

Old Version 8

changes.mady.by.user John Burk

Saved on

compared with

New Version Current

changes.mady.by.user John Burk

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3
Note

This jobtype was added in Qube v6.4-2.

This jobtype requires Python to be installed on the executing worker.

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:

  1. AfterEffects (all versions)
  2. Cinema4D (R14 and later)
  3. Maya BatchRender

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

...

The jobtype backend code on the worker will examine the job's command-line and appVersion values, and check and see if a suitable application can be found on the worker.  Only the 3rd-party software developer's default installation paths for a given application are scanned.  See the section Supporting non-default installation paths with AppFinder if your studio installs applications in non-standard locations.

...

INFO:CmdRangeBackEnd: attempting auto-pathing
INFO:CmdRangeBackEnd: Paths in the command have been translated as per this worker's worker_path_map
INFO: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
Non_Default_Install_Paths
Non_Default_Install_Paths
Supporting non-default installation paths with AppFinder

If your studio does not install 3rd-party applications into standard locations, there are 2 approaches you can take:

...