Per-Take Overrides
Jobs are disposable — Clear Queue drops them, and with them everything the pipeline worked out about a take. Some of that is worth keeping. The plugin keeps a second record keyed by take instead of by job, so the tuning you did and the calls you made outlive the jobs that ran on them.
Two files, two lifecycles
MHAManager/Takes.jsoncommitted Provenance you were told and decisions a human made: actor and slate, source footage path, Wwise ids, accepted calibrations, per-take option overrides, notes, and your own custom ids. Real work. None of it can be recomputed.
Saved/MHAManager/takecache.jsongitignored Everything derivable from the project: framing verdict, frame count, discovered calibration and identity, solve quality numbers, and the artifacts of the last run. Time only. Delete it freely.
The durable file sits outside Saved/ on purpose — it is meant to
be committed with the project and travel to the rest of the team. Disk paths inside the project
are stored relative to it, so a record still matches on someone else's machine, drive letter,
or checkout location.
Overrides are a sparse diff
When you edit a job's options, what gets recorded against the take is only the fields that differ from its category template — the Mono, Stereo, or Audio defaults in Global Settings. One character exported as a single mesh while the studio default stays split records exactly that one field.
That sparseness is the whole point. A full copy would pin every unrelated option to whatever the template happened to say the day you touched the take, and later changes to your global defaults would quietly stop reaching it. With a diff, a take keeps tracking the defaults for everything you never customized.
Re-adding a take seeds the job from the current category template first, then lays the recorded fields on top. Delete the take's entry and it reverts fully to the defaults.
What comes back when a take is re-added
How takes are identified
Records key on a take's stable identity, not on a job id:
wwise:<object id> — so a re-transcode or a moved scratch WAV still lands on the same take wav:<absolute path> Related
Per-Job Options covers what you can actually change per take. The queue itself — jobs, statuses, artifacts — persists separately as a manifest or batch asset.