Sessions and permanent histories

Keeping track of everything ever done to the audio

CEDAR Cambridge Sessions

In most applications, Undo/Redo stacks and histories are limited to the decisions you have made since you most recently opened the file on which you're working. In contrast, a CEDAR Cambridge session comprises a CEDAR Cambridge Workspace file plus a linked folder that can contain the source audio, an edit decision list (EDL) that contains the history of the operations carried out upon that audio, audio files saved at each stage of processing, graphic files that illustrate the processing decisions that you have made, and data regarding things such as the processes loaded, the relevant parameters, the screen layout, and other metadata.

The session folder make it possible for you to reload a previous session complete with its undo/redo history, so you can return to a job after it was completed and still be able to move forward and backward through the steps taken. It also means that, if you work on a job at disparate times, you will still be able to Undo and Redo as if you were working on it at a single sitting. Any report generated will document all of the changes to the audio from the time when the audio file was first loaded and worked upon.

BACK