Benjamin Mertzic
Forum Replies Created
-
Thanks Jeff. I only have Avid and FCP on this one machine. I could get a short clip to you if you wouldn’t mind giving it a try. Thanks.
-
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.
-
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).