I work for a medium-sized TV station that does short-form and long-form documentaries on newscutters, we've just switched over to Interplay from MediaManager in the past few weeks, and we've been running into several of issues noted in the "Mind Boggling" threads, as well corrupt media, and indexing remote media issues...  

I've been reading the appendix of the Avid's Interplay for Editors workbook -- the Do's and Don't's last page--- and it says "DON'T"-- Share Bins ;  and 'DON'T"-- Share Projects (i.e. do not work on a project that another editor is already using)--

Editors with us have traditionally "shared" projects by backing up on a project workspace, and sharing bins here too...  But is it safe for multiple editors/assistants to be checking items in and out of one project w the same name on the Interplay Server??? Do editors working on the same project now have to create different names for it in Interplay / locally???  And does anyone with more interplay experience know if this might be affecting media corruption issues??

Thanks in advance.  

 Joe

No, Joe. While we say in the docs that project sharing is not officially supported, many, many customers are doing just that.

Technically, you do take a bandwidth hit using shared projects on ISIS but, most customers see that as a small price to pay.

Also, I haven't seen shared projects corrupting media.

Do you have support on this system? What are the call letters for your station?

Make sure your interplay folder path is set correctly on ALL users who are sharing the project-   otherwise your Interplay project folder becomes a bloody mess.

JDS