This discussion is archived
2507 Views 2 Replies Latest reply: Oct 23, 2009 10:51 AM by LucasSaldanhaWerneck
Currently Being ModeratedOct 21, 2009 7:04 PM (in response to wilsonbyu)When a FireWire drive mounts, it does so at /Volumes/, and when Final Cut Server creates a device, it does so at a specific path. In your case, that path is /Volumes/PostBackup01. Mechanically, Archiving is just moving the data for an asset to an alternate location. So apparently, Final Cut Server will make any missing directory it needs to on its way to writing the file in the path where it expects to find the Archive device.
The developers apparently didn't intend for Archive devices to be disconnected from the system. Maybe that's a head-shaker for you, but it is what it is. So, based on the way FCSvr was designed, the thing you are doing wrong is dismounting the archive device from the host.
Currently Being ModeratedOct 23, 2009 10:51 AM (in response to wilsonbyu)BUT, as always in FCS there's a workaround:
You can setup a script, inside a production let's say, that would check first if the drive is present and if it's not it can show some warning in log or in jobs, from there (or from the script) you can trigger a notification (email or anything you like, just not a popup inside the FCS interface). If the device is present than would trigger archive just fine.
Take a look at Object Matrix ( http://www.matrixstore.net/2009/07/24/final-cut-server-15-plugins/ ). They have some scripts and you can start from there.
While you're there take a look at the long archive solution that's simple brilliant.
If it's not as clear as I intended to be, please let me know and I'll try to summarized better.
RegardsMac Pro 8 core, Mac OS X (10.5.6)