stealth117
Level 1 (0 points)

Q: Edit-in-place without SAN

I have read that you can configure edit-in-place even if you don't have a SAN. But I can't figure out exactly what needs to go into the edit-in-place URLs and also anything else they may need to be done on the server/client side.

For a little more information we have a dedicated server running Final Cut Server, this system is not running Final Cut Pro and no one works on it. We have an external drive array connected to the server via Firewire. This is where our information lies. I have already shared out the Drive array via AFP and SMB.

Please let me know what I may need to do to get this working.
If you need any more information, just let me know.

Thanks in advance for the help!

Posted on Jan 14, 2011 4:44 PM

Close
stealth117

Q: Edit-in-place without SAN

  • All replies
  • Helpful answers

  • by A. Richards,

    A. Richards A. Richards Jan 15, 2011 10:50 AM in response to stealth117
    Level 3 (625 points)
    Jan 15, 2011 10:50 AM in response to stealth117
    Go to the admin panel of the Java client (not the System Preferences). Go to Devices. Open the Device that corresponds to the drives you are sharing out. In the Mac EIP URI space, enter "file://<path to share as listed in the path value for the device>". After you leave the field it will change. This is normal.

    So you might enter, "file:///Volumes/Media Drives/" and it will reformat itself to "file://localhost/Volumes/Media Drives/". Save and close.

    Now when your clients have the share connected and open FCSvr, they will have edit-in-place access to the assets on that device.

  • by stealth117,

    stealth117 stealth117 Jan 18, 2011 2:59 PM in response to A. Richards
    Level 1 (0 points)
    Jan 18, 2011 2:59 PM in response to A. Richards
    I have it setup exactly like that. but when I go to check out the files it wants to download them to my client from the server. What I don't understand is the localhost part. How can it be localhost, when the files reside on the server. I know it would be local to the final cut server install, but not to the client.

  • by John F. Whitehead,

    John F. Whitehead John F. Whitehead Jan 18, 2011 6:35 PM in response to stealth117
    Level 2 (380 points)
    Jan 18, 2011 6:35 PM in response to stealth117
    The path needs to be the same for every computer, then no matter where it does localhost/volume/name it will resolve correctly.

  • by BenB,

    BenB BenB Jan 18, 2011 7:33 PM in response to John F. Whitehead
    Level 6 (10,036 points)
    Audio
    Jan 18, 2011 7:33 PM in response to John F. Whitehead
    The network drive has to be mounted to the workstation's Desktop.

  • by stealth117,

    stealth117 stealth117 Jan 19, 2011 1:27 PM in response to BenB
    Level 1 (0 points)
    Jan 19, 2011 1:27 PM in response to BenB
    I found some documentation that stated I needed to change the capture scratch location in the FCP to the server location. Is this true? or is this more of a work around of the actual edit-in-place functionality?

  • by BenB,

    BenB BenB Jan 19, 2011 8:20 PM in response to stealth117
    Level 6 (10,036 points)
    Audio
    Jan 19, 2011 8:20 PM in response to stealth117
    Only if you are on a SAN system, and want a centralized Capture Scratch location for your organization for some reason. It is an option, not a necessity.

  • by John F. Whitehead,

    John F. Whitehead John F. Whitehead Jan 20, 2011 11:00 AM in response to BenB
    Level 2 (380 points)
    Jan 20, 2011 11:00 AM in response to BenB
    It makes it so you don't have to copy your files anywhere after capture, they are captured directly to their permanent storage location.

    But it has to be to a SAN so it's fast enough to not drop frames.