Nova Master Identity 🪪

Every music folder on every drive has a master_final_v3_ACTUAL.aiff in it. The naming is a symptom: the file carries the identity of a release in its filename, because nothing else in the pipeline knows what it is.

Nova Master Identity 🪪 turns a mastering report into release and archive identity - what source, what settings, what came out - and emits a deterministic archive name plus a fingerprint you can validate against later.

How it works

You feed it the report_json from Nova Audio Master. It attaches a publication identity to that report: artist, title, track number, version, catalogue number, ISRC, label, credits, territory, language, explicit flag, plus a target format (target_bit_depth of 24 or 16, target_sample_rate of 48000, 44100 or 96000). Then it computes:

• An archive name, built from track number, artist initials, title, version and target format - sanitised into something filesystem-safe, and deterministic, so re-running produces the same name rather than a new timestamped mess.
• A fingerprint - a JSON record of the source PCM SHA-256, the master PCM SHA-256, a settings hash, the reproduction fingerprint, a report payload hash, hashes of the recording and publication identities, and a hash of the fingerprint record itself.

The report also records lineage: a parent report id and a root report id, so a re-master of a re-master can still be traced back to the take it came from.

Outputs: identity_json (the enriched report), fingerprint_json, and archive_name - which is the one you wire into the validator.

Inputs

Required: report_json and artist_name and track_title. Everything else is optional - and "everything else" is about two dozen fields: artist_initials, track_number, version (Master by default), album_title, catalog_number, isrc, publisher, label, mastering_engineer, mastering_company, copyright_owner, release_year, composer, producer, mix_engineer, project_name, territory, language, explicit_flag, upc_ean, work_id, client_reference, notes, and the two target-format combos.

Do not retype those from a spreadsheet. That's what identity_fields_json is for: wire it from Nova SQLite Reader's identity_json output with that node's column_set set to identity. Every field it carries replaces the widget below it, blanks are ignored, and fields it doesn't mention keep whatever the widgets say. Your catalogue stays the single source of truth and survives a browser reset.

The coercion is worth trusting here: an integer field gets range-checked, and the two combo fields only accept their exact legal strings - so a database value of 24-bit is reduced to 24 rather than trusted, and an unrecognised value leaves the widget alone instead of breaking the graph. Somebody thought about the fact that a database is not a form.

Install

ComfyUI Manager → Nova Audio Player → install → restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/NovaFemme/ComfyUI-NovaAudioPlayer.git

Under ▶️ Nova Audio → 🎛️ Mastering Process. Nothing to install, nothing to download - it's all string, hash and dict work over a report you already have.

Where it fits

Nova Audio Master 🧾 ── report_json ──▶ Nova Master Identity 🪪
                                              │ identity_json
Nova SQLite Reader 🗃️ ── identity_json ───────┘
                                              │ archive_name
                                              ▼
                                   Nova Final Master Validator

That last wire is the point. The archive folder is full of working names, and filenames lie; the validator matches on identity recorded inside each report instead. Give it the archive name and a selector and it can find the right reference without anyone maintaining a naming convention by hand.

If you're making one track for yourself, this node is overkill. If you're shipping anything - to a distributor, a client, or just to yourself in six months - it's the difference between an archive and a pile.