WAV/"FDMS3" archiving

  • Thread starter Thread starter Paj
  • Start date Start date
P

Paj

Well-known member
All:

It works:

(1) Save your program as WAV data (this takes about three times longer than an FDMS3 save).

(2) Erase all your tracks.

(3) Resave your "blank" program as "FDMS3" (this happens quickly, since there is no WAV data left---the file is less than 1 MB).

ADVANTAGES:

(A) WAV data is portable to other systems and not machine dependent. It is also possible to port WAV data to different programs within the VF.

(B) All program settings are preserved in the small FDMS3 file for future use/reuse with your VF. This includes Scenes, Event Maps, Locate points, etc.---all the settings that are normally saved under FDMS3.


DISADVANTAGES:

(A) Saves/Reloads take longer and require at least one more disk. WAV saves, in general, require more disks/space than the FDMS3 save.

(B) You must reload the FDMS3 disk first if you want a complete restoration of your original program (i.e., with the scenes, event map, etc.)

(3) Programs with a track longer than 135+ minutes will have to be broken up for WAV saves. WAV saves abort if any single track exceeds the capacity of the storage medium (e.g., 700MB for a CD-R).


I've been doing this now for a couple of months and have had no problems (archived over 80 hours of 7-10 track recordings).


Later,
Paj
8^)

P.S.: Using VF160CD, OS 2.02, 80-min CD-R's.
 
Last edited:
Back
Top