Production · podcast production cards and drives
podcast production: repair an incomplete ingest workflow
How do I investigate an incomplete ingest from the podcast production?
Short answer
Not by copying again: compare each recorder track and camera clip on the untouched card with the destination. A missing guest track often means an import filter took only the stereo mix, or a WAV of 4 GB or more failed on a FAT32 destination. Files missing from the card itself need a read-only scan.
The situation
The destination contains only part of the material from the podcast production.
A podcast ingest that arrives short usually loses whole channels rather than pieces of them. The destination holds fewer files than the card, and the pattern in what is missing, a single guest track or every long take, points straight at the cause.
01 / Diagnose
Work out what actually disappeared
Two mechanisms dominate. An import preset that was built for the mix imports the stereo master and leaves the individual microphone tracks on the card, which looks like a complete session until someone needs to fix one speaker. And an uninterrupted multitrack WAV passes 4 GB after a few hours, which a FAT32 destination refuses outright, so the longest and most valuable take is exactly the one that never arrives.
A copy interruption, filter, duplicate name or delete-after-import action can leave gaps. For podcast production, this matters because the podcast production combines several sources, takes and handoff steps that must be reconciled as a set
Check the last known path, trash and backups without writing to the original device.
02 / Protect the source
Preserve the best recovery chance
- 1
Leave the recorder card in place and unchanged, and do not run the ingest preset again until it is clear which tracks it skipped.
- 2
List the card side by side with the destination, counting one entry per microphone channel and noting the file system of the destination drive.
- 3
Copy the missing tracks straight from the card to an exFAT drive, which carries takes past 4 GB, and bypass the import tool for this transfer.
- 4
Only if a track is absent from the card as well, scan the card read-only and export the recovered WAV files to a separate drive.
Do not let the ingest tool delete the card after copying while tracks are still unaccounted for, and do not fix the import by reformatting the destination. The card is the only complete copy of the session until the comparison says otherwise.
03 / Choose the method
Match the tool to the source
For stable, readable exFAT, NTFS and FAT16/FAT32 or uncompressed IMG, DD, RAW and BIN images.
Unconfirmed exports are marked .UNVERIFIED.
A WAV that was cut short when the recorder lost power stays short; File Recovery Hero recovers files, it does not repair damaged single files. It reads exFAT, NTFS and FAT16/FAT32 sources read-only on macOS and Windows, and no other file systems.
04 / Verify
Check the recovered content, not just its name
The ingest is complete when each microphone channel exists once in the destination with the same byte size as on the card, every track runs the full session length, and the waveform shows sound rather than silence at the very end.
Keep the source until two verified copies exist. One working preview is not enough.
Sources and technical references
FAQ
Questions about this recovery case
Can podcast production cards and drives be recovered in this situation?+
A podcast ingest that arrives short usually loses whole channels rather than pieces of them. The destination holds fewer files than the card, and the pattern in what is missing, a single guest track or every long take, points straight at the cause. The result still depends on what remains readable on the source.
What should I avoid before scanning?+
Do not let the ingest tool delete the card after copying while tracks are still unaccounted for, and do not fix the import by reformatting the destination.
Does scanning write to my memory card?+
Your memory card is only read. Nothing is saved to it.