This guide is for the original, first-generation DJI Mic. It describes a backup-handling workflow, not a recovery guarantee or a measured synchronization test.
The camera’s audio track and the recording inside a wireless transmitter are different files from different parts of the signal path. If a camera clip contains a dropout, the transmitter file may be useful—but only if local recording was running and the file was preserved. Pairing a transmitter with the receiver does not prove that an internal backup exists.
Quick answer: verify local recording before the take, copy the transmitter audio to a clearly identified project folder, keep a second copy, and synchronize in a duplicate sequence. Listen at the start, middle, and end before replacing the camera track.
Confirm What Was Recorded Before Looking for a Fix
DJI’s original Mic FAQ documents standalone recording, a solid red recording indicator, 8GB of internal storage, and export by connecting the transmitter to a computer over USB. It also says standalone files are divided at 30-minute intervals and that new recordings replace the earliest files when storage fills. That makes early offloading important.
The same FAQ distinguishes a fully charged transmitter’s recording time from the longer storage-duration figure possible with constant power. Do not plan a full day solely around the “14 hours” storage claim. Also do not transfer a newer DJI Mic generation’s 32-bit-float claims to this first-generation model: DJI describes this recording as 24-bit.
Before a real interview, record a short trial, stop it, and confirm that the local file opens and contains the intended voice. Listen for clothing contact and placement problems. An independent file location does not make the microphone immune to noise already captured at the capsule.
Copy by Transmitter, Not Into One Unlabeled Folder
Connect one transmitter with a known data-capable USB cable. Identify the mounted device and its audio files before copying anything. If it does not appear, check the cable and connection first; do not format the device as a troubleshooting shortcut when it may contain the only recording.
Keep separate destinations for separate transmitters, even if they contain identically named files. Use neutral labels such as TX-A and TX-B until a spoken slate or actual listening establishes who is on each. A folder name chosen from memory is not reliable evidence of speaker identity.
PROJECT/03_AUDIO/DJI_MIC_1/TX_A/ORIGINALS/ PROJECT/03_AUDIO/DJI_MIC_1/TX_B/ORIGINALS/ PROJECT/03_AUDIO/DJI_MIC_1/NOTES/
Preserve original names in these source folders. Put descriptive labels in the editor or in a separate log. Record the take or subject, approximate recording interval, and any gaps. Copy all relevant segments, not only the first file that happens to play.
Verify the Copy Before Reusing the Transmitter
Check that the expected files arrived, then open representative files from the destination itself. Listen at more than one point. For a critical job, use a copy-verification method appropriate to the project and retain another independent copy before clearing the device. A filename list or a completed progress bar alone does not establish that the entire interview is usable.
Keep the device untouched if a needed file is unexpectedly missing. Continued recording can make the situation worse because of the documented overwrite behavior. This article does not promise deleted-file recovery; involve a qualified recovery service when the material’s value warrants it.
Synchronize in a Duplicate Premiere Sequence
Import the copied WAV files and keep the camera’s original audio. Create a duplicate working sequence so the original edit remains available. Put the relevant camera and transmitter clips on separate tracks with enough room before the first picture; avoid starting an alignment exercise at a timeline boundary that hides the beginning of the sound.
Adobe’s Synchronize Clips documentation describes selecting the clips and choosing Clip → Synchronize. Use the available audio-based synchronization choice when the recordings share useful reference sound. Do not select timecode merely because the clips have dates; this workflow has not established a common timecode source.
If the reference is weak, use a visible and audible slate or another identifiable event to align manually. Zoom in and verify speech against the picture, not just two peaks that happen to look alike. Preserve an explanatory note if you need an offset.
Check Long Takes and Every File Boundary
A good alignment at the beginning is not a guarantee for the entire take. Check the middle, the ending, and each boundary where the transmitter created another file. If sync changes over time, investigate the recordings and sequence settings before stretching audio or cutting sections blindly. Apply any repair to a working copy, and verify the result across the whole affected passage.
Audition the chosen backup by itself before mixing. Leaving a slightly offset camera track under it can create an objectionable combined sound. Mute rather than delete the alternative during evaluation, then export a short dialogue sample and listen outside the editing timeline.
A Backup Is a Workflow, Not a Receiver Mode
The useful result is a labeled, copied, verified source that stays in sync with the delivered picture. Do not confuse that with a receiver safety channel or with fixing left-only playback. For the separate camera-input question, see the FX3 audio-source and input-setting guide. Capture, copying, synchronization, and final listening each need their own check.