Production · podcast production cards and drives
podcast production: check a backup size mismatch
Why is the backup from the podcast production smaller than the source?
Short answer
Compare exact byte sizes, not folder totals: a podcast session consists of a few very large WAV files, so one failed copy removes gigabytes at once, while cluster differences only change the size on disk. If a track is shorter or missing, keep the recorder card unchanged and copy that file again to a verified destination.
The situation
A copy exists, but byte totals or file counts do not match the recorded cards.
In a podcast backup the arithmetic is unusually blunt: a session is a handful of very large WAV files, so a deficit of several gigabytes means one file is missing or short, not that many small items slipped through unnoticed. The file list, not the folder total, settles it.
01 / Diagnose
Work out what actually disappeared
Uncompressed multitrack audio grows fast: at 24 bit and 48 kHz each channel needs about 8.6 megabytes per minute, so a long session with four microphones fills gigabytes. A copy that broke off mid-file leaves a shorter WAV with a valid 44-byte header that still opens. On a FAT32 backup drive a take beyond 4 GB cannot be written at all, while cluster size changes only the size on disk.
Hidden sidecars, failed large files, filters and allocation errors can all change totals. 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
Keep the recorder card as it is and leave the backup untouched as well; nothing is copied again until the missing bytes have a name.
- 2
Compare the two sides file by file with exact byte sizes and durations, because a track that is minutes short still appears in the list as present.
- 3
Copy every short or missing WAV again from the card to an exFAT backup drive, one file at a time, and let each transfer finish before starting the next.
- 4
Open one recovered track per session to the last minute, then record the final file list with sizes beside the backup as the reference for later.
Do not clear the recorder card because a backup exists, and do not treat a WAV that opens as proof that it is complete. A truncated file plays normally until it stops early, which is easy to miss in a quick check.
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.
File Recovery Hero recovers deleted files from exFAT, NTFS and FAT16/FAT32 media read-only, and exports only to another drive. It does not lengthen a WAV that was copied incompletely, compare checksums for you, or work with an encrypted backup volume.
04 / Verify
Check the recovered content, not just its name
The backup matches when every WAV has the same byte size on both sides, each track reports the full session duration in the editor, and the last minutes contain the closing conversation rather than silence or a playback error when scrubbed to the 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?+
In a podcast backup the arithmetic is unusually blunt: a session is a handful of very large WAV files, so a deficit of several gigabytes means one file is missing or short, not that many small items slipped through unnoticed. The file list, not the folder total, settles it. The result still depends on what remains readable on the source.
What should I avoid before scanning?+
Do not clear the recorder card because a backup exists, and do not treat a WAV that opens as proof that it is complete.
Does scanning write to my memory card?+
Your memory card is only read. Nothing is saved to it.