Composition Contents¶
Compositions are made up of Tracks, Stages, And Intervals.
Pictured here is a Composition including three Tracks (“Ewan”, “Example_Clip”, and “Ewan”), with each Track containing one or more “Stages” (The rows labeled “Load:” or “Clean Mesh”), plus one interval per Stage (the long grey blocks of time to the right of the stage name ).
Tracks¶
Tracks are the basic building blocks of volumetric Compositions, representing individual clips of volumetric video and any editing applied within HoloEdit.
Each Track is made up of one or more Stages, which contain individual operations for adding or transforming data in the Track, such as loading data from a Clip, adding rigging data, or performing compression.
In the HoloEdit UI, tracks are displayed along with their individual stages in the Track View (see Track View on the left side of the Composition Panel. Tracks are aligned to the leftmost side, and the individual stages making up those tracks are nested downwards and to the right.
Tracks are displayed in the the order that they were added to the Composition, but the order doesn’t affect any HoloEdit processing or export.
Stages¶
Stages are procedural processes applied to Tracks to load or manipulate volumetric video. Stages take in data streams from earlier in the Track, and replace or alter those data streams going forward down the Track. Each kind of Stage performs a specific operation on one or more of their Track’s data streams, then outputs one or more new or modified streams.
The most fundamental Stage is the “Load Asset” Stage, which loads new samples into the Track from a Clip in your HoloEdit Workspace.
Stages are applied in order from top to bottom, with each Stage taking in the closest preceding Stage with appropriate data as its input for processing. Each Stage is applied to the Track through Intervals , which are spans of time in the Timeline with individual Stage settings configured for their specified portion of the Clip. For details on using Stages and Intervals, For details on the Stages and Intervals UI, see the Track View section. See the Stage Types section for more information on the function and settings of individual Stages.
Intervals¶
Processing from Stages is applied through Intervals. An arbitrary number of Intervals can be created per Stage, each representing a contiguous stretch of time containing one or more frames for processing. Where Stages represent the kind of work that will be done, and to what data streams, intervals represent what portion of the Clip’s samples will be processed, and with what settings.
With multiple intervals, a single process that occurs at a specific point in the Track (such as stabilization) can have varying settings throughout the Clip, to best suit the samples throughout the stream.
Three stages, with different intervals. The first stage has one long interval, while the subsequent two each have three smaller intervals. The second interval in the third stage is selected.¶
Loading Clips¶
Clips are added to a HoloEdit Composition using a special stage, called Load Asset. Load asset intervals directly apply the samples from your clip to your track.
For most data types, this means overwriting any existing data of the same type supplied by stages earlier in the track. Ie, if you use a Load Asset interval to add new mesh data to a HoloEdit track with existing meshes, the meshes from the new Load Asset stage will replace any existing meshes in the Track Result.
Audio streams behave differently. Audio is additive, so subsequent load asset stages containing audio will layer multiple audio streams over eachother.
To control this behavior, you can use the Excluded Streams setting on any Load Asset interval to exclude streams that you may not wish to apply.
Segments and Stabilization¶
Temporal Stabilization, or Stabilization, is a special form that Mesh streams can take which empowers compression and editing of volumetric video.
In Stabilized data, a mesh stream is broken up into one or more segments. Each mesh sample within a given Segment shares the same Mesh Topology and UV Layout with its neighbors.
Segments¶
Samples of stabilized data in Holoedit are grouped into portions called Segments. Segments are introduced to a HoloEdit Track using Stages such as Stabilize and Template Match, or by adding a Clip including segment data in a Load Asset Stage.
In the composition view, segments are displayed as dashed lines dividing segment borders in a stabilized interval.
Some processes and workflows only work with Stabilized Segments, such as SSDR and Mari Export.
Track And Composition Results¶
To understand your HoloEdit Composition, it helps to understand the Track Result and Composition Result. HoloEdit is a non-linear editor, which means that rather than having a single, edited version of your Volumetric Clip, the state of the Track at each individual stage is available at any time. In HoloEdit, a Track Result is the state of your entire clip at any given point in a track. This contains any new edits to your data applied by the current Stage, in addition to any non-edited data inherited from all previous stages. In HoloEdit this is sometimes called the Waterfall, because un-edited data flows down from through previous stages like a waterfall.
The Track Result is used whenever a clip is exported, displayed in the HoloEdit viewport, or dispatched for processing in a Stage. This is the product of each Stage that has been processed in your Track. The final product of every visible Track combined is called the Composition Result.
Samples contained in hidden Stages or that have not been completely processed are excluded from the Track Result displayed in the Viewport and in Exports.
When Executing a stage, it helps to understand the Result up to the point in the track where that Stage appears. If the required data for your Stage is not present in the current Result it will not be possible to execute. To help understand the concept of the Track Result, please read the example below.
For example, imagine a Track with three Stages
The first Stage is a Load Asset Stage with a single interval from frames 0 - 200
The next is a Stabilize Stage with intervals from 0-100, 101-150, and 151-200. The first and third intervals are complete, but the second has failed.
The final Stage is a SSDR Stage, with corresponding intervals at 0-100, 101-150, and 151-200. The first and third have been successfully processed, but the second is blocked by the preceding Stage.
The Track Result, in this case, will be frames 0-100 from Stage 3, frames 101-150 from Stage 1, and 151-200 from Stage 3. This Track Result is what is visible in the viewport with the Track selected, and is also what would be output from holoedit when exported.
Note: when an Interval is Blocked by an incomplete interval in a previous Stage, the entire Interval will fail to compute. I.e., in the previous example, if there had been two intervals in the third Stage – 0-100 and 101-200, the entire 101-200 interval would be blocked by the failed 101-150 interval in the second Stage.
Compositions And Job Data¶
Processing in HoloEdit is done via Jobs run on the Local or Remote Job Server. Each job is made up of individual Work Units, and as work units complete processing they incrementally send finished data back to HoloEdit. If jobs corresponding to an open Composition are being run, results from that job will be fetched as they are completed. If that Composition is closed, the corresponding data will all be fetched as soon as the Composition is re-opened. In some cases, such as after deleting the relevant Stage or intervals from a Composition, jobs may be considered abandoned within one Composition but not another.
See Processing & Jobs for more details on the job server.
Saving and Loading Compositions¶
Compositions can be saved and loaded using the “Save” and “Save As” options in the File Menu. Saved Compositions should be stored in the current workspace, and will be saved as Composition .json.lz files. Saved Compositions can be loaded by double clicking on the entry in the Project View.
Along with saving the current Stage and interval configurations, saved Compositions store job status, such as active, waiting to download files from the server, and so on. A saved Composition can be closed while individual intervals are processing on the Remote Job Server, and will fetch the current job status and download necessary files when it’s opened back up.
Autosave¶
HoloEdit will periodically automatically save your current Composition to the “autosave” folder located in the root directory of your Workspace. Autosaves include your current Composition name plus the date and time.
Autosaves will store Composition and job result status like any other save file, and may be deleted periodically.