Local collaboration on two macs PLUS remote editing via parsec in realtime

[Guest]

A little tricky usecase:

In this project, I am working as a director and work together with an editor.

We usually do this in the same room on two computers.

I am writing the voiceover text and discuss the content, but I would like to be able to log and grab some interesting clips/bits and send them to the editors machine, so I dont have to tell him at which timecode he can find all those clips all the time. Thats a huge timesaver!

Is it better to work with "team projects" for that or just exchange an xml?

We will definitely have a copy of all source footage on both devices because I prefer to work with SSDs instead of using a shared NAS storage (with limited bandwidth) - so I guess Premiere "Productions" is not an option.

Now it gets even more complicated:

The editor isnt able to come here, so he needs to work on my "main" mac remotely in real time via parsec.

(Basically video screen sharing my desktop)

I will be able to see what he is doing in realtime and we will communicate via phone in the meantime.

As parsec needs lots of internet bandwidth I am not sure if a "premiere teams project" would cause a lot of traffic and interfere with the parsec screen transmission. Could this interfere?

And is a "team project" stored ONLY in the cloud or locally on my hard drive as well?

Will I be able to perform time machine backups of the project?

The other workflow would be to import all my footage into a project, copy it and then work in this copy on my second machine. Now I could just send xml-files via airdrop to the project he is working on. As be both have a copy of the same source footage I hope it will automatically relinked. Does this work flawlessly?

Thanks for your help!

[John V Knowles]

You can still use Premiere Productions, provided you store the Productions folder in Cloud storage; it would be similar to the Team project but with more features and options. Linking to the media might be the only hitch, but if both drives are named the same with the same structure then linking should be automatic. As far as Parsec goes I'm not familair with it, but if you're just accessing a Project file in the cloud then that doesn't take up much bandwidth at all. Project files just get loaded into RAM and are only written to when saves occur.