Multiuser project

[Andy]

Working on a project at the moment and thought how this would greatly benefit the workflow.It would be great to have multiple access to a project where for instance one editor could be operating/editing in one location on the timeline while another is working somewhere else in the timeline while all the time edits etc are updated on both machines same project. Hope this makes sense, kind of like a multiuser project.

[Adrian]

Hi

A way of doing this is to create a global library and open it on both machines. Anything you drag off the timeline in to the library appears on both machines. So one of you could be working on fx and another on music. Drag the tracks in to the library and you can build a master timeline.

This might help

Adrian

[phaseboy]

I work as Adrian suggests all the time. If you open the same network accessible library (either global or document) on multiple machines they will all see updates made. It's really nice on film dubs as I can have one ore more editors working on different parts of the timeline and as they make changes they just select the areas with changes and copy them to the library - which then automatically shows up on the other machines so everyone can quickly just spot to tc - which you can also do while the machine is playing so I never have to take a machine offline to update the session with edit changes.

[Andy]

Yeah that's how I'm doing it too, however it does require management by the user of the master project and when things get really busy with updates its hard to keep track of all the changes.

[phaseboy]

True enough, but that management also means all the users have to pay attention and know what's going on in the session.

However I think something like you suggest could be good if it were implemented similar to a source code control system in software development. Whereby the database keeps track of the changes made, who's making them etc..., and also allows the user to lock out a portion of the session so that you can't have two people editing the same section. In effect what this would mean is that no-one actually has the master session open as it is only a reference database and everyone works with a copy of it updating their session against it.

I could be wrong, but I suspect we're in the minority on desiring something like this and I have to say I'd much prefer some other big beasts to be slayed first.

Best Regards,

Mark