36
by TylerSavage_Archive
MRoyce wrote:bishopdante wrote:steve wrote:Nobody in a band is going to do any of the redundant file maintenance described. They barely change their strings.Agreed, but this is why professional technicians and service providers exist.I see no reason why a recording studio (or band) shouldn't be using a cloud server for archive, and paying a small monthly bill for high reliability.As an example Amazon S3 costs per month:Volatile: $0.023 / GB Infrequent access: $0.0125 / GBCold Storage: $0.004 / GBArchival of analog and digital materials using contemporary data center methods (and conversion to open/accessible formats) isn't happening enough, and it's something that should be happening more. Cold-storage archive, or original "hard copy" in a secure/fireproof facility is good, but making stuff globally accessible as full-backup digital archive and indexed like a library open to the world without requiring legions of staff and museum-sized spaces is a good thing, but isn't happening enough. Instead of serving as a grand library built to last, Internet technology is currently largely used as a commercial circus of the most temporary and ephemeral nature. That's not the only option, and large-scale nonprofit archival for artists is something that storage and bandwidth are now sufficiently available and affordable to be on the table.This is worth looking at: https://www.archiveteam.org/Not enough, studios and bands should use Git and their own cloud-hosted repository (NOT github) to fully document and store the entire recording, mixing and mastering process:More industries outside software development need to get on Git/Mercurial/whatever for revision control. I don't know if it's practical for recording, they weren't developed for large file management and lose their effectiveness. you will start annihilating storage space the further along you go maintaining a full history tree... although with Reaper, this might work out just fine especially if you're just working locally and pushing changes.You'll end up creating a repository for every project, which may not be a bad thing.I tried to do this for mechanical/control engineering projects and with Solidworks files alone I ran into a lot of problemsoh, this thread probably covers it well https://www.reddit.com/r/git/comments/3 ... \_projects/