Pipelines

AVAA features an advanced pipeline system easing automation of complex tasks.

A pipeline is created for each section of the document, and initially contains a virtual copy of the corpus and its associated media files. The corpus and its media files are then modified sequentially by each processor inside the pipeline.

Pipeline Input Modes

The pipeline can be fed different initial media files, by defining the processor-pipeline-input setting.

• corpus this is the default mode if the processor is placed at the beginning of a section, and will feed the pipeline with the corpus media files
• section-assets this is the default mode if the processor is placed after a view which exported clips, and will feed the pipeline with all the exported clips/snapshots (of the section) until this processor was reached
• all-assets this mode must be manually selected, and will feed the pipeline with all the exported clips/snapshots of the document until this processor was reached

The corpus mode is useful to process corpus files directly (audio-anonymization, formats conversion...), while for instance all-assets mode could be used to apply effects only on the exported media of the document intended for sharing with peers.

Pipeline Chain

Processors inside a pipeline (that is for now, a section of the document) are executed one after another, each processor using the results of the previous one to work on.

Complex chains of processors can be built to automate heavy tasks alleviating the burden of manually running each step and verifying its consistency.

Pipeline and Views

Views placed after a processor (in the same section) will inherit its modified media files when exporting clips and snapshots. This can be helpful extracting annotations from cuts of raw media files, to avoid processing long corpus media file when testing samples ; or preprocessing a media file before it is exported into clips during later views generation.

Processors generating annotations will make these annotations immediately available in the main corpus (and not only for the current pipeline), hence for all subsequent views and processors in the document.