eliot wrote on Sat, 30 April 2005 17:36 |
I think the biggest problems really are: format standards (Bob mentions broadcast wave files - that's fine, but requires studios to actually generate the proper backups, and in some DAWs bouncing each track to a wave format is far from an easy and automated process).
|
Yeah, I'll agree with you on this, though there is absolutely no reason why an automated function couldn't be implemented in protools or nuendo or the like. It just requires a bit of pestering from record companies.
Quote: |
constant redundant backup (not a technical problem for a co-location type environment)
|
Agreed.
Quote: |
security (the hardest-to-implement concern). Who gets access to the files? The artist? The studio? The producer the band dumped half-way through the project? Besides that, potential (and incentives) for hacking are very high.
|
Hmmm...
Security: Surely banks manage to avoid being successfully hacked. If banks can do it the record companies will be able to do it? Of course all servers can be hacked, but I'd feel safer having my data on a secure server array than on a single piece of tape in a vault...
Permissions: This is a messy issue I'll agree. But couldn't the permissions be the same as they currently are for an analogue archive?
Quote: |
Though it's mostly automated, it's not free. We're talking tens of millions to build it, and several million a year to keep it runnning (minimum). And the costs would grow with the growth of the archive. Think of it as "the music industry's colocation".
|
Hmmm... I don't know if agree with this. The cost of storage space drops every year, so, it could be the case that new server purchases/staff training won't be needed. This depends on how much of the current archive is tranferred to the servers, mind...
-Fergal