Mozilla Skin*/?>

CL2 Project

From ConduitWiki

Back to User's Guide contents

Setting up the project

The project in Conduit Live 2 is built from node widgets that determine what gets rendered. This offers a great deal of flexibility because node widgets can be added, deleted, reconfigured and interconnected. Very little in Conduit Live 2 is fixed in such a way that it couldn't be customized to suit the user's needs.

There are a handful of fundamental settings and modes that affect the entire project, rather than individual nodes. This section of the User's Guide explains these important concepts.

Project settings

These settings are located in the Project window under the Project settings tab.

Default render resolution determines the resolution at which effects are rendered. You can freely mix video clips and live sources regardless of size and depth in Conduit Live. Only when compositing the application needs to make a decision about the output resolution. If you don’t have any effects, the video streams will be processed at their original resolution -- hence this setting currently only affects Conduit Effect node widgets.

Render quality contains two settings that affect the quality vs. speed of accelerated rendering.

By default, Conduit always renders at floating-point quality, so you never need to worry about artifacts introduced by insufficient color depth (such as clipping and banding). Sometimes the effects being applied are so simple that you don't need full precision, and it's acceptable to render using regular 8 bits per channel precision. This would be the case if you're only doing crossfades and simple color corrections, for example. If you know that you don't need full precision, enable Prefer speed over color precision.

Conduit Live will synchronize its output to the display to avoid artifacts like tearing. However, this synchronization may cause delays, as the system must sometimes wait until a display cycle is complete. If you want always the fastest rendering and lowest latency without care about artifacts, enable Prefer speed over display integrity.

Interface timebase determines the frame rate used by the Conduit Live interface. Conduit Live allows mixing video clips with different frame rates in the same project. This setting is thus necessary to control how time codes are presented in the user interface. It also affects other user interface functionality that requuch as “Frame forward” and “Frame backward” buttons.

There is an “Auto” mode: when it is enabled, the interface timebase will be set automatically when a movie is loaded using the Movie Source node widget. (E.g. if the loaded movie has a frame rate of 24 fps, the interface timebase will be set accordingly.)

Auto mode is on by default. Unless you work with mixed frame rates, you’ll generally want to leave it this way.

The Project settings tab also contains Capture session settings. These determine the folder where Conduit Live will store video recordings. For more information, see Recording video to disk.

Free Run and Timeline modes

Conduit Live 2 has two clock modes, Free Run and Timeline. They are quite different, and the choice between the two modes depends on your use case.

In Free Run mode, there's no fixed duration to the project. When you press "Play", the clock starts running and the node widgets will keep producing output until "Stop" is pressed. This mode is ideal for dynamic situations where you don't know the exact length of the "show": live video capture, performance, installations...

In Timeline mode, the application behaves like a traditional video compositor. The project has a specific duration, and play controls become available in the user interface for moving to a specific time within the timeline. You should use this mode if you're working with on-disk video or image files, rather than live sources.


Screenshot of the project in Timeline mode.

Back to User's Guide contents