Skip to content

Your project’s VoxMark data

VoxMark keeps everything tied to a timeline — the saved transcript, voice names and colours, hidden marker text, marker durations — beside your project file, in a Chroma folder:

MyJob/
├─ Edit_v1.aep
└─ Chroma/
└─ VoxMark/
├─ voxmark-data.json
├─ voxmark-data.json.bak
└─ replaced/

Chroma is shared by Chroma plugins — each has its own folder inside it.

Keep the Chroma folder with the project when you move it, archive it or hand it to someone else, and the transcript comes with it, no re-transcription needed.

Each project keeps its own transcripts, even when projects share a folder and a Chroma folder.

Saving a new version — Edit_v2.aep from Edit_v1.aep, or Edit copy.aep — picks up the earlier version’s transcript the first time you open a comp in it. It’s a copy: the earlier version keeps its own. A different job that only happens to have a number at the end (Ep 12, Ep 13) is treated as a different job.

An unsaved project has nowhere to keep its data yet, so VoxMark holds it in the panel’s own settings until you save. When you save, it moves into the Chroma/VoxMark folder — so save before you close the panel or the app, or the transcript stays behind in the panel’s settings.

Transcribing again, or importing an SRT over an existing transcript, first keeps the old transcript as its own file in replaced/. The 20 most recent are kept.

Every save keeps the previous good copy as voxmark-data.json.bak. If the data file is ever found damaged — after a crash mid-save, say — VoxMark repairs it from the backup and tells you in the log.

Earlier versions kept this data in a VoxMark folder beside the project. The first time you open a project in 2.1, its data moves into Chroma/VoxMark automatically. Caption files made by Premiere’s Convert to Captions stay where they are, so your caption tracks keep working. If the move can’t happen — a file held open by Dropbox, say — VoxMark keeps using the old folder and tries again next time.