I concur. We have an Archives department here which is archiving all the audio and video from years past. I am responsible for the infrastructure. I configured an Apple Xsan so that we could expand if the need ever arose (and it did). I have a second RAID that is NOT a member of the SAN as a backup, because if I ever lost a controller, I could lose the metadata (different kind of metadata) and lose the data on the SAN. Keeping the backup storage separate from the SAN (and off site if you can) is something to consider.
Now about the concur part. The original guy who set all this up didn't have any really good workflow, and he was keeping records, first in old Filemaker documents, then in Excel, then in a mix of other things, and today they cannot tell you what state any message is in or what forms it has been saved in, as in Radio Masters, web MP3,s aiff originals, aiff edited etc. The reason for that is they never developed a consistent workflow. Your situation may be simpler, but a consistent workflow is ESSENTIAL to this kind of work. The words, "I'll get to that later" should NEVER enter into your mind. If it needs to be done, make it part of the workflow. Bob On Feb 24, 2011, at 9:57 AM, stephen barncard wrote: > As one who archives audio and video all the time, I can pass along some > pointers for this task. > > I don't think you can expect Livecode to handle recording that many audio > streams, and there is no reliable way to 'monitor' the audio stream to > detect level thresholds in Livecode. I've tried it. Audio in Livecode is > primitive at best, and timers to stop the recording will fail eventually - > some cassettes are 30, 60, 90, 120 minutes long. <snip> _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
