I've been excited to use Productions as my Premiere projects are pretty big and by the end of a project, which typically last a couple of years, the project takes a while to load, save and just starts to act a bit funky!
My first look at shifting my last project over to a multi-project Production was pretty straight forward and it does pretty much what I want, with what was one big monalithic project being split into 4-5 smaller projects and now I can open up these projects quickly and I think this will be a big help but one issue. It would seem that a sequence can't be shared across projects, ie you can't nest a sequence X that is in one project A, inside a sequence Y in another project B without getting sequence X copied over to project B. Which is a real shame as I have had to use nested sequences a lot over the years to get around limitations in Premiere. Anyone else seeing this or am I doing something wrong?
I think I am running into a similiar issue. I have been migrating a feature documentary project over to the new Production workflow, and as you reported everything was rather straightforward and funtioning, except my nests.
In the new Production organization, I was attempting to have a Project entirely dedicated to my nested sequences, as I had a folder for such in my old massive project. Similar to yourself, my nested sequences are almost entirely FX workarounds for my b-roll clips. Thus, they are inside of and throughout my larger "Chapter" sequences for the film, and have litle need to be consistently opened/accessed after initial generation.
Upon attempting to move the nests from the old organizational structure to the new "Nests" project in the Production, I ended up with a new Nests project full of duplicates of all the sequences that are not linked to a use in any Chapter sequence. And the original copies of the nest sequences seem to have not moved and remain in the Project that contains the Chapter sequence they are nested in.
In conclusion, this is perhaps not exactly your issue, but I can at least confirm something seems to be less than optimal in how nested sequences are stored/handled in this new workflow.
Finally got some down time today and have migrated a copy of my current doc project over to a production. Process was simple enough, if time consuming, and now my 'current edit' timeline is super responsive. Very happy with that.
But, yes, my quick and dirty PPro 'comps' aren't quite getting into the spirit of things, separate 'Comps' project wise. In retrospect, I probably should have used After Effects compostions.
I'm also currently seeing an issue with Reverse Match Frame not working across sequences in separate projects (within same production) ... but that may be because I'm testing this with the public beta.
Well good to see it's not just me that has had to use nested comps and how is stuck with lots of duplicates across projects. Going forward I can probably work around the issue for new projects/productions but such a shame because I still need to access and work on these older projects and they are so dog slow as one project, way faster as productions but I now have the overhead of needing to ensure I update a nested sequence across half a dozen projects if I make any small changes.
Be great if someone from the Premiere Team could let us know if this is ever something they might fix or whether we need to put up with it and adapt in the future?
I've created an "idea" on the Premiere Uservoice forum too as this seems to have more chance of getting through to the people at Adobe (well that might be wishful thinking!). Vote it up and maybe we'll get some resolution to this in the future:
Currently, if you bring a sequence from one project into another with the 'nest-or-not' button active, or bring a previously nested sequence, it adds that seqeunce to the second project essentially as a "clip", though if you double-click that nest on the timeline, it does open up the original layout of the clips involved.
And yes, it appears that when we bring in a sequence as a nest, that new nest "clip" is definitely divorced from other uses of it in the Production folder. So you would have to go into each project and change that nested sequence.
If you bring in a 'regular' (non-nested) sequence, without the nest-or-not button active, it simply adds the media of that sequence to the current timeline without adding media to that project's file.
I too would like an explanation on how to get "standard" behavior of a nested segment. As yes, it would be preferable to be able to 'ripple' changes in a nest through other uses in other project files.
Hey All! Were there any fixes to the nested sequences in Productions? I need to have VFX comps sequences (nested) and it seems to carry them and make dupes, in a very disorganized way :/. Any advice on how best to handle this? Thanks!
No news to report.