Non Avid machine hooked up to Unity.

[Dom Silverio]

You can install the client software as long as you follow certain guide lines (correct version of OS, proper R/W permissions, etc).

As long as you have dongle license for more clients and you have proper configuration – I don’t see why not.

Unity is just a SAN with extra features for Avid based NLEs.

[Mark Burton]

I do this on every film. Two MCA’s connected via fibre, then my Mac laptop connected via Gig-E with a single workspace mounted to share files. I make a workspace called ‘GRAPHICS’ and export and save all non Avid files to this space. Very handy and works perfectly.

–Mark

[Rep_eric]

We have the same sort of setup and it works great with one small exception: We have a Sonic Scenarist DVD authoring workstation that we hooked up to Unity, and everything worked fine except that if I output multiplexed files (temp files) to Unity when outputting the DVD, the menu highlights would disappear. Simple workaround – just mux to a local drive and use Unity for everything else. Just an odd problem.

That’s just a long-winded way to encourage you to check your work flows to make sure there aren’t any weird problems.

[Scott Davis]

Thanks, We have Scenarist on this machine also. I am freelancing PT at this shop and am not to familar with Unity set up (was always done by IT) How do you go about “hooking up” to the Unity?

Scott

[Rep_eric]

“How do you go about “hooking up” to the Unity?”

As far as the physical connection, it’s the same as for the Avids, but we have an engineer that takes care of that side, I’m not familiar with the process.

From an operational side, Create a workspace on Unity for your Scenarist projects, then using Unity Connection Manager mount that workspace as a drive. In Scenarist, you can set your “Target” and “DVD Root” Directories to a location on the Unity Drive, just make sure to set your “Mux” directory to a local drive.

Hope this is what you’re looking for.