Motion Media

Overview
The PipelineFX Qube!TM Jumpstart provides you with a quick and immediate way to get up and rendering with Qube!. Designed for deployments on a tight schedule and for companies with limited available technical resources, Qube! Jumpstart will insure basic render management functionality in the shortest possible timeframe.

Benefits

• Accelerate your Qube! Render management deployment
• Reduce risk by leveraging experienced consultants and proven best practices
• Easy to schedule and delivered remotely

Deliverables
Installation of Qube! Supervisor
Installation of 2 Qube! Workers
Installation of 1 Qube! Client
Validation
Training

Scope
4 hours via telephone and GotoMeetingAssist
Maximum of two end user contacts
One Supervisor, two Workers and one Client
PipelineFX Qube! Jumpstart delivered by a Qube!
Requirements

• All computers with OS installed and networked
• Hostname resolution working properly on all computers
• Network filesystem reachable by Client and Worker machines
• All applications already installed and licensed
• Ability to remote login to all machines

Architecture:
Qube!'s client-server architecture reduces network traffic by limiting the communication between machines to the Supervisor and its workers.

API Support:
- C++
- Perl
- Python

Platform Support:
Qube! runs on Linux, Windows and Macintosh OS X.
System Requirements for the Supervisor, Worker, and Client:
- Red Hat Linux 9.0
- Red Hat Enterprise Linux 3.0, 4.0, 4.0 x64, 5.1 x64, 5.2 x64, 5.3 x64
- Fedora Core 3.0, 5.0, 5.0 x64
- Fedora 8 x64
- SuSE 9.3, 10.0, 10.1, 10.1 x64, 11.1 x64
- Windows XP Pro, Vista Business/Ultimate, Windows7 Pro/Ultimate
- Windows XP Pro x64, Vista x64, Windows 7 64-bit
- Windows Server 2003, 2008
- Mac OS X 10.4 (Tiger), 10.5 (Leopard) Universal Binary, 10.6 (Snow Leopard)

Application (Name)	GUI Submit	In-App Submit	Type	Notes
3Delight			SimpleCmd	3Delight standalone renderer
3dsMax			Perl, Plugin	Dynamic Allocation. Verified Renders: scanline, mentalray, vray. Installation: Front-end and Back-end
3dsMax (3dsmaxbatch)			SimpleCmd	Verified Renders: scanline, mentalray, vray
AfterEffects (aerender)			SimpleCmd	Uses "aerender" command for distributed rendering. Works with CS3 and CS4.  In-app interface behaves like "render" for RenderQueue.  Will now show % complete.
Aqsis			SimpleCmd
Blender			SimpleCmd
Cinema4D			SimpleCmd	OSX only
Combustion			SimpleCmd
Fusion (ConsoleSlave)			SimpleCmd	Uses Fusion ConsoleSlave.exe introduced in Fusion 5.1.
Houdini hscript hscriptRender hython hythonRender hrender mantra			SimpleCmd
Lightwave			Perl	For Windows only
Lightwave (screamernet)			SimpleCmd	Uses Lightwave Screamernet For all Lightwave platforms
Maxwell Render			SimpleCmd	For Maxwell Render 2.0.2 and above.
Maya			Perl, Plugin	Dynamic allocation, Works with all renderers using Maya's Universal Renderer framework Installation: Front-end and Back-end Versions: Through Maya 2011
Maya (Mayabatch) software hardware lightmap mi export mentalray vector render 3delight vray rib gen renderman turtle			SimpleCmd	exposes all commandline options for standard and many optional renderers
Maya (maya_melCmds)			SimpleCmd	exposes ability to run general mel commands
Maya/MentalRay (MiGen)			Perl	Two-stage process to generate and render .mi files. Requires Maya jobtype Installation: Front-end and Back-end
Maya/Renderman (Mtor)			Perl	Two-stage process to generate and render .rib files. Requires Maya jobtype Installation: Front-end and Back-end
Mayaman (batch)			SimpleCmd
Nuke			Perl	Dynamic Allocation. Nuke 4.x. Installation: Back-end
Nuke (cmdline)			SimpleCmd	Tested with Nuke 5.0
Mentalray Standalone			Perl	Render .mi files Installation: Back-end
RED (redline)			SimpleCmd	For RED camera transcoding
RealFlow4			SimpleCmd	Allows the offloading of a simulation from the artist's machine to a machine on the renderfarm.
Rhino			SimpleCmd
Renderman Standalone			Perl	Render .rib files Installation: Back-end
Sequence Publisher			SimpleCmd
Shake			Perl	Installation: Back-end
Vue			SimpleCmd	Submits to the e-on Vue RenderBull framework
Softimage XSI			Python	Dynamic allocation Installation: Front-end and Back-end Versions: Through Softimage 2011
XSI (xsibatch)			SimpleCmd	exposes all commandline options for xsi renderer

Terms:

• GUI Submit -- Submission dialog present for this application through the QubeGUI.
• In-App Submit -- Submission dialog present directly inside the Application to provide convenience so the artist does not have to switch away from their 2D/3D content creation application.
• Dynamic Allocation -- Supervisor-Worker communication provides per-frame distribution of work with application and scene already loaded for maximum throughput. Dynamic allocation maximizes render throughput by loading the application and scene file only once, and then sending single frames to each render host until the job is complete. Faster hosts finish first and are dispatched another frame. All without having to re-load the application and the scene file. Using dynamic allocation also allows users to scale up or down the number of render hosts allocated to a job on the fly.
• SimpleCmd -- Framework that leverages the power and flexibility of the commandline backend with a friendly submission dialog. Installation only needed on client/artist machines. Many SimpleCmds now standard as of Qube 5.4. See the SimpleCmds Forum for downloading additional SimpleCmds.