Backup Tracks with FLAC?
Posted: Sun Jun 22, 2008 10:27 am
Hi there,
currently I am a little concerned about the persistence of my tracks in the future, so I am willing to back up every track split into the individual tracks (separate bass-track, separate drum-track etc.). As I started doing this, I realized I had to install some older software on my windows pc and for example search the net for the (of course free) refills I used in the time I worked with reason. Software disappears more quickly that one would expect, so the only logical way to back up tracks and ensure accessibility over a long amount of time is bouncing all components in single tracks to disc, is it?
If you have a track with let's say 10 instruments, you'll end up in roughly about a gigabyte of data PER TRACK. Though I have about 400 gigs of free storage, that's very much, because I want to mirror the data for safety reasons (everything else would be naive I think).
I found out Ableton can handle FLAC, which I think maybe a great alternative instead of backing up the raw wave data. The problem is, that I always get warnings when encoding 24bit 44,1khz wave files (which is okay for a backup, I think).
Additionally some of the FLAC files I imported then into Ableton have the right length, but do only contain a tiny fraction of the data in the wave file. Very strange.
Now before I start backing up everything in FLAC and try to solve the strange problems, I wanted to know, what you think about this way of backing things up in FLAC, or if there is a better alternative.
The main constraints are:
1) The files must be at the most half as big as the wave files (I tried FLAC compression and I ended up in about one tenth of the size, surely depending in the amount of silence and richness of frequencies of the tracks)
2) The files must be decoded easily or even be supported by applications like Ableton, so no complex decoding process is needed.
Please let me know what you think.
Best regards,
Martin
currently I am a little concerned about the persistence of my tracks in the future, so I am willing to back up every track split into the individual tracks (separate bass-track, separate drum-track etc.). As I started doing this, I realized I had to install some older software on my windows pc and for example search the net for the (of course free) refills I used in the time I worked with reason. Software disappears more quickly that one would expect, so the only logical way to back up tracks and ensure accessibility over a long amount of time is bouncing all components in single tracks to disc, is it?
If you have a track with let's say 10 instruments, you'll end up in roughly about a gigabyte of data PER TRACK. Though I have about 400 gigs of free storage, that's very much, because I want to mirror the data for safety reasons (everything else would be naive I think).
I found out Ableton can handle FLAC, which I think maybe a great alternative instead of backing up the raw wave data. The problem is, that I always get warnings when encoding 24bit 44,1khz wave files (which is okay for a backup, I think).
Additionally some of the FLAC files I imported then into Ableton have the right length, but do only contain a tiny fraction of the data in the wave file. Very strange.
Now before I start backing up everything in FLAC and try to solve the strange problems, I wanted to know, what you think about this way of backing things up in FLAC, or if there is a better alternative.
The main constraints are:
1) The files must be at the most half as big as the wave files (I tried FLAC compression and I ended up in about one tenth of the size, surely depending in the amount of silence and richness of frequencies of the tracks)
2) The files must be decoded easily or even be supported by applications like Ableton, so no complex decoding process is needed.
Please let me know what you think.
Best regards,
Martin