The company I'm cutting for recently traded in their TerraBlock system for Unity ISIS. After a week of editing we've noticed two things. i think they only have about four Avids hooked up to it.

While I'm cutting in a bin with a green unlock, I will suddenly get a warning that my 'Bin does not have a lock and will not be saved, would I like to save a copy?' Nobody else in a dfferent bay even has this bin open when this happens (about twice a day). So I save it to the desktop, create a new bin, drag the cuts over, etc. It's a drag.

Also we are noticing some slower responsivess in the interface: opening bins, adding audio dissolves, saving bins -- all these simple steps take between one and six seconds to execute whereas they used to be near instant.

Here are our specs:

Mac Pro Quads 2.66, OS 10.5.6, MC 3.5.6, QT 7.6, 4 GB RAM

Any ideas would be greatly appreciated.

Hi,

Are you connected through ethernet or fiber with the Unity ISIS system?

We're connected though ethernet.

When this happens, is at the same time one of the other workstations disconnecting from the unity system?

As far as I know, nobody is disconnecting fro the system when this happens.

I'm on plain unity. not Isis. The sluggishness is something I see as well when projects get bigger and especially on ethernet clients.

Then about the bin locks. I'm not sure and just guessing. Could the system get so slow that the automatic save takes so long that it times out and you get this message?

A call to avid support I'm afraid.

Hey funckdren, we are having the same bin lock issues with ISIS as well.  We've experienced  the problem on multiple projects and users.  Have you had a chance to open the .lck file for that bin and see who owns it?  We haven't had the chance to do that yet. 

We are on Unity not Isis so this might be a little different. We were seeing the same issues.  It was driving the editors nuts. We have 4 edit bays. 3 mac (OSX 10.5.5, QT 7.5.5, MC 1.3.1) and 1 PC. Avid tech was unable to offer any helpful suggestions on this one. We believed the issues were related to the OSX Finder and permissions but were never quite sure. However, when we started Optimizing our workspaces and rebooting the Unity more frequently than we had been the issues we happening less and less. We now noticed that when we don't reboot the Unity hardware at least once a week we start getting weird things happening. At this time we can't unmount some workspaces but we forgot to reboot the system last week. We are at the whim of the editors as to when we can reboot. Hopefully tonight. Weird.

Anyway, just thought I'd mention our solution. Good luck.

-Cable

There is only ethernet on ISIS.

What version of ISIS-

And most importantly, has anyone modified the hosts file?

JDS

We are on version 2.0.2 and have modified the hosts file on all clients.

Avid Basic Phone Support recommended we change our Bin Settings to the following:

Auto-Save Interval: 15 minutes

Force Auto-Save: 30 minutes

This seems to have improved our situation. I'm not positive, but I don't recall this happening since I tweaked this setting last week. FWIW.

What were your settings before that change?

Auto-Save Interval: 5 minutes

Force Auto-Save: 5 minutes

Seems to me that changing autosave to 15/30 mins means that eventually, and possibly sooner rather than later, the MC application will hang as it has just started to save.

You'll then be restartiing the app - and will now be at least 30 mins behind schedule. And you'll have to remember everything you did in that 30 mins.