Zelau / FAQ
Frequently asked questionsWhat sound editors ask us.
What exactly does Zelau do?
Zelau turns a picture AAF into a usable audio AAF. It reads the source AAF, indexes a local audio media folder, matches each clip back to its file, then writes a new audio AAF along with a log and an optional report.
How does Zelau find the right media for each clip?
The engine tries four methods in order: embedded timecode read through ffprobe, file name, a heuristic on the name tokens, then waveform comparison as an optional fallback. The method used is recorded for every clip.
Can I set the timecode tolerance and the frame rate?
Yes. The frame rate is configurable, including for projects at non-standard rates, and the timecode matching tolerance is expressed in frames and set according to your rushes.
Do I need to use a terminal?
No. Zelau is a standalone macOS application that opens with a double-click. The conform backend is embedded and driven by the interface; no command line is required from the end user.
What happens to a clip Zelau cannot resolve?
The clip is marked « to check » and detailed in the log with the possible reasons. Zelau never guesses a match silently: doubtful cases are reported to you.
Is my media sent to a server?
No. Processing happens locally on your Mac, from your own media folder. Your files never leave your machine.
Does Zelau handle retimes, transitions and nested sequences?
These advanced cases are at the very least detected and flagged in the log so they can be checked by hand. The application stays stable even when it cannot fully interpret a complex element.
Is there a processing report?
Yes. Besides the live execution log, Zelau can produce a CSV report listing, for each clip, the media selected, the method and the timecode difference.
Let's talk about your workflow.
Write to us with your exact need: formats, frame rate, volume. We will answer concretely.