Why Do My RØDE Central Recording Names Disappear on Another Computer?

Separate a missing label from a missing take

Identify what changed: the computer, the displayed recording title, the available recordings or an exported file. A renamed take appearing unnamed on a second workstation is a different condition from its audio being unavailable.

RØDE's Naming Recordings instructions explicitly distinguish names stored in Central from data stored on the transmitter. The same section says a name is retained after export. Those two locations explain why a named exported file can remain portable while a transmitter connection alone does not transfer the local naming view.

Keep this model-specific behavior separate from ordinary filesystem renaming or another audio application's project labels. Do not assume that every visible title is embedded in the recorder's stored file.

Build a handoff that contains actual files

On the workstation where the takes are identified, confirm each intended recording before exporting. Match its content with the shoot notes; similar durations and similar titles can still describe different performances.

Use the documented Central naming and export workflow, then inspect the actual exported filenames and audio. Supply those exports together with a small take map when the recipient needs the labels. Handing over only the transmitter does not establish that a second computer will reconstruct the same named list.

The take map can include the shoot identifier, intended spoken opening, selected source and exported filename. These are proposed production fields, not a claim that Central automatically creates such a report.

Hypothetical example: two similar demonstration takes

A fictional seller records two versions of a kettle demonstration. On computer A, they label one take Kettle-short-intro and the other Kettle-detailed-controls. Computer B displays the recordings without those saved names.

That result is consistent with the documented storage location of Central's names. The operator on A verifies each performance, exports the intended files and supplies a mapping that identifies their spoken openings.

Suppose B then receives those named exports and confirms the expected speech. That would validate the handoff for those files. It would not demonstrate that names had been written back onto the transmitter. No devices or audio files were used for this example.

Resolve uncertainty before choosing an apparently similar file

If the original naming workstation is unavailable, inspect the actual recordings and available shoot evidence before assigning replacement labels. Do not claim that the first unnamed take is the approved one simply because its duration is close.

When the content cannot be identified confidently, leave the selection unresolved and preserve the recordings. Exported filenames and the take map should reflect the verification actually performed.

For the next handoff, confirm that the recipient received playable, correctly identified exports. The useful test is whether they can select the intended demonstration without access to the first workstation's local naming state.

Record your own observations

The filled rows are illustrative examples. Use the blank row for your own files and observations.

Download the editable CSV worksheet

What the references establish

• RØDE Wireless GO II — Naming Recordings: Documents the local storage of Central recording names, their absence on another computer and retention after export. The proposed take map is editorial workflow guidance.