You are here
file deletes and FAT32 system continuity
the Fostex manual explains DAT file deletions are best done on Fostex unit and not on a computer...to maintain FAT system continuity.
I have had to make x2 programme deletions (x8 track/files and x2 track files)on computer as i was unsure of Fostex instructions on deleting in the recorder unit. I am still trying to get to grips with the latter.
For now, can someone briefly explain FAT 32 system continuity, how my computer can mess it up, and how it can result in slower read/write operations.
Do you think my x2 deletions have compromised the CF card much.
A few questions there but many thanks in advance.
- Posts: 465
- Joined: Mon Mar 07, 2011 12:00 am
- Location: Stroud UK
<Note on deleting a DAT file>: The unit can save a DAT file but cannot delete a DAT file. You can delete a DAT file from a personal computer. Do not delete the BACKUP storage folder (only delete a DAT file). Also note that, by deleting a file, the continuity of the FAT system is lost, which may result in slower data reading/writing speed. If you want to delete an individual program in a DAT file, load the DAT file to the unit and use the program delete function of the unit.
Sounds like they're talking about fragmentation -
I shouldn't worry about it. I guess you could always defrag the drive if it starts to slow down noticeably.
- Frequent Poster
- Posts: 2991
- Joined: Fri Aug 05, 2005 11:00 pm
- Location: Norwich UK
The file system will remain intact if you delete on your PC
But it is entirely possible that your system, stores a WAV (the recording) plus other files associated with the recording, say metadata files or files associated with effects settings or whatever.
When you used the delete function on your unit, it clean up all the files, if this is the case.
On your PC you just delete the WAV file.
The file system will be intact, but you will possibly have files that are orphaned from the original WAV file. Or there could be a parent file which points to the WAV and other meta data files associated with this recording.
Of course it depends on the design and how it is implemented. If it were me designing this the files would all have the same name but different identifiers, i.e. recording1.wav, recording1.dat etc... and be stored in relevant folder (WAV, DAT) with the parent file in the root direct directory.
Just my thoughts any way
- Frequent Poster
- Posts: 535
- Joined: Thu Dec 07, 2006 12:00 am
PCs can also keeps tabs on stuff that can be recovered, so it doesn't write over it in a sequential or efficient way - the most efficient use of the hard disk would be to keep data in sequence, but PCs don't do that, but your Fostex might by the sound of the manual's advice.
- Posts: 16
- Joined: Sat Jun 30, 2012 11:00 pm
Who is online
Users browsing this forum: No registered users and 3 guests