This is EXACLY what we're going through right now.

Not only are our editors not used to working in a managed environment, but neither are our producers.

We have just convinced our management that there is the need for a Media Manager position, so things are moving in the right direction.

We're writing an in-house Interplay manual right now, trying to make sure information gets shared across shifts and to take some of the teaching burden off of one or two editors (always seems to the ones who have the tightest deadlines.)

What types of topics do you cover with freelancers?  All of our editors are on staff but we're all new to IP.

We are also revising our training right now, as initially we tried to make Interplay as unobtrusive as possible by making minimal changes to their workflow (we mainly use interplay for frame chase editing of files from EVS servers etc.). This meant we covered the whole check in/check out thing, folder srtucture (almost impossible for an editor to work out if they were working using a mix of their local bins and folders in the project, as well as the Interplay project. The folder structure they would create in the MC was different to the way Interplay puts the bins in the Interplay project). So basically we are going to be a lot more inflexible on the way they work from the start, and tell them to use the Interplay window as much as possible (Eg. Digitise to Interplay folders and so on). This seems to be easier to grasp. Folder creation, catalogs, projects, and reservations are what we cover for a freelance editor. We normally don't use dynamic relink, so do not cover that, and we do not do any admin training, as we have system admins with the kit. If we can train them for a day, and watch them for a day, then things are O.K. I also think the latest IP versions have ironed out a lot of  the issues we were having earlier, but ask me that question again in a month!

As for producers getting in to Interplay, that is another story...It is hard enough dragging them away from a tape machine!

jimmyt72:

We covered the whole check in/check out thing, folder srtucture (almost impossible for an editor to work out if they were working using a mix of their local bins and folders in the project, as well as the Interplay project. The folder structure they would create in the MC was different to the way Interplay puts the bins in the Interplay project). So basically we are going to be a lot more inflexible on the way they work from the start, and tell them to use the Interplay window as much as possible (Eg. Digitise to Interplay folders and so on). This seems to be easier to grasp. Folder creation, catalogs, projects, and reservations are what we cover for a freelance editor.

As for producers getting in to Interplay, that is another story...It is hard enough dragging them away from a tape machine!

Sounds like your editors are using Access quite a bit.  Since editors on our system don't have permissions to delete or move folders I get frustrated with it easily and I find I just want to manage things on the Windows level or just use the interplay window inside MC.  Mind you, that is probably why I am ending up using bins :(  I understand this workflow is not advisable but I was hoping it would change once producers were more into creating folders in Assist.

How do you manage your non-Avid assets?  Where are they stored and what exactly is the check-in and import procedure?  We are looking for a good solution for stills & VOs.

BTW, I will take your tape-addicted producers...Sometimes I think ours just cut and paste out of transcripts :-/

starwipe:

jimmyt72:

We covered the whole check in/check out thing, folder srtucture (almost impossible for an editor to work out if they were working using a mix of their local bins and folders in the project, as well as the Interplay project. The folder structure they would create in the MC was different to the way Interplay puts the bins in the Interplay project). So basically we are going to be a lot more inflexible on the way they work from the start, and tell them to use the Interplay window as much as possible (Eg. Digitise to Interplay folders and so on). This seems to be easier to grasp. Folder creation, catalogs, projects, and reservations are what we cover for a freelance editor.

As for producers getting in to Interplay, that is another story...It is hard enough dragging them away from a tape machine!

Sounds like your editors are using Access quite a bit.  Since editors on our system don't have permissions to delete or move folders I get frustrated with it easily and I find I just want to manage things on the Windows level or just use the interplay window inside MC.  Mind you, that is probably why I am ending up using bins :(  I understand this workflow is not advisable but I was hoping it would change once producers were more into creating folders in Assist.

How do you manage your non-Avid assets?  Where are they stored and what exactly is the check-in and import procedure?  We are looking for a good solution for stills & VOs.

BTW, I will take your tape-addicted producers...Sometimes I think ours just cut and paste out of transcripts :-/

we've actually separated the editor projects from the producer work folders in the Interplay architecture. for example, each series has a folder named whatever series it is, then there is a sister folder called series editor projects. the Interplay folder root on the MCs is set to the editor projects folder and appended, so the editors can check in willy-nilly and not worry about the clutter, since they'll be the only ones digging around in there. after a roughcut is checked in from the MC, the editors drag from the Interplay Window into the producer's folder for review and approval, and the producer can drag to air, transfer, archive, etc.

the check-in function of the Interplay (in that it will new copy a bin with a modified name, requires redundant deletion of unwanted elements, etc) makes it nigh impossible to keep organized on any kind of scale. it's pretty non-destructive, which is good in a way, but doesn't lend well to keeping the project tree organized day to day. we've solved that by pretty much neglecting to do it. the editors are allowed to leave their socks all over the floor, as long as they do it in their own room.

Non-avid assets are stored on the same server as the interplay database, unless you split the database to store assets on an ISIS or Unity workspace, and managed exclusively with the Access program. the documentation on how to actually split the databse is a bit vague, and i've been hesitant to give it a go. i will work through it shortly though. its likely just to make a Unity or ISIS workspace, and find where in the Interplay admin you set the file path for non-avid assets, and set the path to the workspace, and set NxNuser or IPadmin user to have read/write to it.

Thanks - that's definitely another take on it.

 Is it possible for you to mail me a copy of your Interplay Manual??

thx