Nextcloud and Premiere Productions pipeline. Thoughts and ideas on duplicate project errors?

Question

I work in a post production facility that utilizes a local nextcloud instance in combination with premiere productions.

This allows for pretty reliable sync times due to every workstation and the server being on the same network.

We haven’t had many issues but, have run into duplication errors due to remote editors jumping into the production when the project locks do not sync fast enough.

The workaround for this at the time being is to remove the duplicate project and then copy it back in through the productions dialogue. This assigns a new ID to the project and the errors go away. We have also moved to consolidating projects for remote editors. This way they do not touch the production that in office editors use.

I was wondering if the community had any tips or ideas on methods to increase productivity and reduce these duplicate errors.

Please let me know your thoughts!

Thank you for reading and I hope you have a great day!

PaulMurphy · Answer

Re-importing them through the Productions panel should be fine, as long as they don't have media in them. If they do, you'll be creating duplicate versions of your media that are referenced by different projects.

A couple of thoughts:

For remote editors, a better workflow might be to prep their sequences, then use File > Export > Selection as Premiere Project. This creates a project that contains the sequences, but no media in the Project panel, only in the sequences. Send this project file to the remote editor to work on. When you import it back into the Production, it will link up to the other Production projects.
I use automation to create .prlock files for certain projects, which don’t disappear after users close the project. This means a project is locked by default unless someone edits the name of the .prlock file. I find this is a good way to protect files by default. I often use it for backup projects in the Production, so no one accidentally starts editing a backup.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.