The steps you're describing are as designed. The checkbox controls whether or not label color and clip name are kept in sync inside a single project.   Productions work differently and so the checkbox is not visible when inside a Production.   In a Production the clip name is kept updated across projects but the label color is not. This is intentional and there is not a workaround. In developing productions it was clear that this was the best path for most use cases. If label colors were allowed to sync freely, you could be in a situation where one user changes label colors in their timeline, then another user in their timeline, and one user would have to "lose" when the sync happened.   We are exploring future improvements to productions that could help in this area. ... View more

A new build of Premiere Pro Beta has been posted to Creative Cloud that should resolve this crash when exporting. It will be shown as version 14.3.2.27 ... View more

A new build of Premiere Pro Beta has been posted to Creative Cloud that should resolve this crash when exporting. It will be shown as version 14.3.2.27 ... View more

Part of the goal of the public Beta is that it will keep things more generally stable as we get immediate feedback on crashes like this. There's always going to be some risk of issues like this, though we'll do our best to fix them as soon as we can.   Another workaround would be to open the project in the shipping version of Premiere Pro (14.3) as the projects are compatible, and do your exporting from there. It can be installed side by side with Premiere Pro Beta. ... View more

I'm sorry this is happening. The good news is that this crash has already been identified and there will be a fix in the next Beta version for Premiere Pro. Keep an eye on the Updates section of the Creative Cloud app. ... View more

I'm sorry this is happening. Good news in this case is we've isolated what is causing this crash and a fix will be available in the next build you see for Premiere Pro Beta. Keep an eye on the Updates section of the Creative Cloud app. Thank you. ... View more

Thank you for the video and explanation. When you get to the point at 1:15 in the video where you click Send on the crash report box, could you include an email address in the box before clicking Send? If you are able to submit a couple times like that and then let me know what email address you submitted with I can pull up your exact crash report and hopefully get to the bottom of this. You can DM me your email so it's not posted here publicly. Thank you. ... View more

Thanks for sharing the videos, that's very helpful. Would you be able to post a copy of your project file here? If you'd prefer to DM it to me that is great too. Also I'm curious do you see the same thing happening if you use the non-Beta Premiere Pro 14.3? Thank you. ... View more

Thanks for posting your findings here. We are aware of this issue and have it logged as a bug. ... View more

I'm sorry but I'm not seeing anything there in your most recent post, just the text "Just had this..." ... View more

Could you give us some details about your computer? Mac/Windows, which OS version? Which beta version/build do you have installed? Do other versions of Premiere Pro launch without issue? Do you get a crash log window pop up afterwards, and if so could you share the crash log here? Thanks! ... View more

Thanks for letting us know! We're working hard on performance and stability but it's great to get features like this in as well. ... View more

What type of footage are you editing with, and what format and codec settings are you exporting with? ... View more

This forum is for Premiere Pro Beta. This issue has been fixed in the Beta version of Premiere, which you can find in the "Beta apps" section of the Creative Cloud desktop application. ... View more

Neil,   Okay thanks for explaining it further, that all makes sense. When you describe the workflow of having, say, sequences by scene that are all nested into a master sequence, that was all taking place in a single project, right? So there was only ever one editor doing that task. That is the same with Productions. Yes you could split up the scenes for multiple editors to cut them, but to see all the current sequences at once, the editors have to stop working on them and then one person has to combine them.   I can see how you might have hoped Productions could do that, but I'm afraid not.   I'll make sure the rest of the team is aware of what you'd like to maybe see Productions do in the future. I'm just spitballing here but perhaps you could be able to "promote" a sequence such that it will behave sort of like a Multicam but without forcing you to choose an angle, etc. I don't think we'd be able to make that the default behavior for sequences because it would break most other workflows.   I think the main takeaway here is: the new paradigm of Productions does mean if you are a heavy or specific user of nesting then you may have to alter the workflow a bit or at least be aware of it more than when working in a single project.   Matt ... View more

Neil,   I'm happy to offer suggestions about how to work around or find a different way to accomplish this, but after re-reading your posts in this thread I'm not 100% clear on what you're trying to do. Could you give me the high level of the workflow you would use in a single project and then maybe I can offer some advice?     Thanks, Matt ... View more

Neil,   I agree, I think a section in the documentation about nests to set expectations and give some pointers is a great idea. I think once a user understands that sequences don't link across projects they will be able to find a workflow that works for them. Ultimately it still comes down to users organizing how they want to work. If you want to split up scenes and then recombine them later you can do that, but it takes an agreed upon process to do so.   A note on Multicams like Paul mentioned – that works "technically" because multicamera source sequences are special cases where we handle them like self contained clips. While what Paul suggested does technically work, please understand that's not how it's intended to be used and I'd recommend against it.   Matt ... View more

Neil,   You're correct about the behavior where nests do not link across projects. This is on purpose because sequences themselves do not link across projects (nor would most people expect or want them to) and nests are actually just sequences. Nests don't rely on existing inside a sequence.   If you have Nest A inside Sequence 1 and then you delete Sequence 1, Nest A (in the project panel) does not also get deleted. Because of that expected/desired behavior, we aren't able to have nests behave in a special way in a Production.     Matt ... View more

Andy,   You are correct with regards to Search Bins (and also Usage Counts). It's sort of a catch 22 in that the core fundamental benefit to Productions is splitting up the project data, meaning that if a project is closed it is not in RAM and essentially invisible to your copy of Premiere. For a Search Bin or Usage Count to be comprehensive to the whole Production would (at least today) require all the projects to be open and using RAM and then basically negating the benefits of a Production. That's not to say we want to just leave it in that state – we are looking at ways to get some of this functionality into Productions while not losing the core benefit of breaking apart to smaller projects. ... View more

Could you also confirm the version number of your Creative Cloud desktop app? The current version is 5.1 and it's possible if you're still on an older version that it isn't able to show the new Beta section. ... View more

I'm glad to hear your first test with Productions went well!   The process of migrating a Production back down to a single project should actually be pretty straightforward. Here are the steps I would take: Make a duplicate of the Production folder as a backup, since the following steps basically deconstruct the whole thing In the production, create a new project that will end up as your fully self-contained .prproj at the end. I'll refer to it as "master" for now Identify any of the projects in the production that have things that need to be moved over and open those projects all at once. I'm thinking for purposes of archiving a finished project, this would be all source master clips and any sequences you want to keep. Go through each of the projects you opened in Step 3 and drag/drop the master clips and sequences into the new master project, making bins in the master project and organizing as you go to maintain however much structure you like When all has been moved over to the master project, do a File > Save All and then close the Production. Go on disk and locate your master project and copy it outside of the production folder Open the master project and inspect it. It should be self contained at that point   The only need to use the Generate Master Clips command would be if you realized you forgot some clips that are in a timeline, but technically if you are thorough on steps 3 and 4 that won't be a problem.   Let me know if that works or doesn't make sense. The key is as long as you do all that combining while all the projects are open, Premiere will take care of essentially undoing all the links across projects and you will end up back with a single self-contained project. It's essentially the reverse of the steps in the documentation to break apart an existing project, but you can selectively leave behind old dupes of sequences, etc, that you don't want to combine. ... View more

Could you be more specific as to what you'd like optimized? It would be helpful to know what kind of AMD CPU you're using, what kind of footage and workflow you're using, and what specifically you think is not optimized or could be better optimized. Thanks! ... View more

Apologies I missed your meaning there specifically about discrete GPU based accelerated decode. It's not something that will be added for the next upcoming release, but keep an eye on the forum discussions here for when we do have it in a state that it is ready to be beta tested. ... View more

Premiere Pro and AME do support hardware decoding using Intel QuickSync:   https://helpx.adobe.com/x-productkb/multi/gpu-acceleration-and-hardware-encoding.html#HardwareacceleratedEncodingDecodingIntelQuickSync ... View more

Thanks for the feature request! I agree, this sounds like it could be a great way to work more quickly with a stringout of all yoru source media. If you haven't already, make sure to create a User Voice post about this idea. ... View more

Thank you so much for the video and sending the production – I was able to get to the bottom of what's happening. The short and simple version is what you're seeing is indeed a bug. We're hoping to get it fixed soon. I also just wanted to share that when breaking apart an existing project into a production, it's best to add the project to the production (like you did) and then just move the master clips to new projects. There's no need to duplicate them and use the Reassociate command. I don't mean to suggest that to excuse the bug, just a tip for the future.   I also have an easy workaround for you. Open both projects like you have set up in your video, then drag the master clip from the organized project back into the original project, making sure to drag it to the root level of the original project. Then, just drag it right back to the organized project. After doing that, you'll be able to delete the empty folder, and your Reveal In Project command from the timeline will still work, taking you to the organized project.   Thanks, Matt     ... View more

Thank you for giving Productions a try, and thanks also for your thorough write up. I'll make sure your feedback gets back to the team. I have some follow up on some of your points that could help clarify things for us:   1. Could you give a more specific example (or a production without media for us to look at) where reassociate isn't working? The Reassociate command is designed for situations where clips in a timeline were linking to master clips in a project and the master clips have been moved while the timeline was closed. It's not intended to to be a regular part of a workflow, but more of a tool to fix things up if they were moved. Knowing more about how you're trying to use and what it's not doing will be helpful.   4. This does happen, if the project containng the sequence where those clips are used is open. The links across projects will update. If the clips that are being moved are in a timeline that is in a project that is not open, there's not much we can do there.   7. You can duplicate media into other projects if you want to have two copies of it. I'm guessing that your ask for a "clone" would somehow link the two master clips? That seems to be fighting against the point of using a Production – you want there to be only one copy of a master clip. It can be used in any number of sequences, but there's only one master clip in a bin. Could you elaborate a bit more on why you'd want to clone a master clip and what the properties of a clone might have that are different from just duplicating it?   8. We totally hear you on the pain points with Merge Clips / Multi-Cams.  ... View more