Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy FCP6 won’t launch w/o Avid Unity workspace mounted.

  • FCP6 won’t launch w/o Avid Unity workspace mounted.

    Posted by Benjamin Mertzic on March 25, 2009 at 10:35 pm

    When launching Final Cut I am asked to login to the Avid Unity LanShare. I have to force quit fcp mount workspaces(through the Avid Connection Manager software) then relaunch FCP. This only happens for some user accounts on the Mac OS (10.5.6). I have verified and repaired permissions for all users and in FCP under User Preferences I have deselected open last project when launching FCP. Any ideas? Thanks.

    Sean Oneil replied 17 years, 1 month ago 2 Members · 5 Replies
  • 5 Replies
  • Sean Oneil

    March 26, 2009 at 6:04 pm

    Sounds like the Unity is set to be your capture disk.

    Sean

  • Benjamin Mertzic

    March 26, 2009 at 7:53 pm

    The Unity has been set as the capture scratch in the past but currently only local drives are used with FCP. We leave them attached to the Unity Lanshare because we use Compressor and DVD SP4 for DVD authoring of projects created in Media Composer 3.1.1 on Macs that have no encoding or authoring apps.(this also can cause headaches with permissions errors and encoding from quicktime refs pointing to media living on the lanshare is inconsistent at best).

  • Sean Oneil

    March 26, 2009 at 10:28 pm

    So you’re saying FCP has no reason to look for your Unity, yet it won’t launch until you’ve mounted it? That’s very odd.

    Sean

  • Benjamin Mertzic

    March 27, 2009 at 12:25 am

    FCP has no reason to look for the Unity, unless I’m missing something. Perhaps the Avid client software “Connection Manager”(v5.1 I believe) has something to do with this.

    Another thought, in previous versions of Media Composer(2.7-3.0) we had problems with MC closing before the temporary bin lock files were deleted. This would cause those bins to be locked if you tried to open them in a different suite. You would have to go back to the first suite and relaunch Media Composer, close the bins then exit the app. to release the bin lock. Also, when we had FCP projects on the Unity I discovered that if two editors opened the same FCP project from the Unity both could edit as if they both had read write access to the same files simultaneously until the editor who open the project 2nd tried to render or save any changes at which point he would get an error message.

  • Sean Oneil

    March 27, 2009 at 6:47 pm

    You should try the Avid forum. I don’t know enough about it.

    Sean

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy