We have made several fixes in the PPro 2020 to address many stability issues. If you are still running into crashes, please submit a specific issue on the crash you are observing and include the crash log, specific steps, and your system configuration including driver and OS versions.
Having a catch all thread makes it impossible to respond to specific issues.
The more specific information we can get, the more we are able to take action to resolve these issues. The key here is that we are able to reproduce the issue so we can address it asap.
Please make sure to separate requests into single threads. That way, we can properly mark the status of requests. As Matt Stegner notes, Drag/copy track effects to a different slot or separate track - is already done
Thanks for the report. We are reviewing this issue.
There are several threads on multiple forums but they aren't always indicative of the same problem. What would be useful here are specific steps and information to reproduce the bug per Annika's request:
If anyone on this thread has a step by step scenario by which they can reproduce this issue, it would be much appreciated.
Have you updated/reinstalled your driver from NVIDIA's site (not the automatic OS update). Often drivers require reinstallation on updates but we do recommend going to the manufacturer's site for the driver/installer.
There are a couple of possible options that we are looking into and discussing with editors both shorter and also longer term that pose unique challenges:
1) Keep the project file compatible across a version so that, for example, version 19 won't have project changes for the entirety of that version. That will allow for compatibility for that version regardless of which version of 19.x you own. Of course this would limit the work we can do that impact project files until the next major version
2) Create a feature that allows for an XML level export with support for a baseline of edits and effects only that would be backwards compatible moving forward.
Which NVIDIA GPU are you using? Have you updated the drivers from NVIDIA (not the OS)?
V12.1.1 UI Audio Bug
The issue could occur when an audio track was muted in a sequence and then the v12.1.1 project was saved and closed. When you reopened the project, the UI for the sequence no longer showed the audio track as being muted as the UI reset the toggle to show it as on. When a user would play back the sequence , not all of the audio tracks would appear to play causing them to possibly think it was a caching issue or codec related issue. Premiere was actually playing the sequence back correctly as those tracks were muted from the previous save state but the UI bug caused the issue where there was no indication that the track was muted.
Solution: (the Fix)
Once a v12.1.1 project shows this UI behavior it needs to be corrected and resaved. **Note** v12.1.2 will not correct this issue simply by opening the project in V12.1.2 .
You need to follow these steps to repair the project.
1. Toggle the Solo button on/off and the Audio track will correct the playback state. To keep it simple, Solo/Unsolo each audio track.
2. Playback the Sequence to insure that all audio tracks can be heard and monitored.
3. Save the Project
4. Quit Premiere Pro
5. Relaunch and issue should now be fixed.
As stated, the fix for this issue is included in the recent update, v12.1.2. This update keeps the UI bug from occurring so the user should not run into the issue again.
First. Thanks for the feedback.
Second. We work with a broad set of clients on both our PreRelease program and also as direct engagements. We have sent our engineers on-site to directly debug and share our development versions with real customers that rely on our product day to day
Does that mean that the issues you are running into aren't real? Absolutely not. Clearly there is more work to do.
Share with us the specifics of your issues. Generalizations as well as huge buckets aren't helpful. As I think you will see over time, we will be releasing updates that directly address the issues that are being reported here.
You are right that words by themselves are meaningless. I am hoping we can prove that we are committed to improving the product as every release contains not only features but bug fixes for the specific issues that are reported here.
When threads are taken down, they are often non-actionable. We want to help and we do want to improve the product. So thank you in advance for taking any time to share any specific problems that we can address.
Reg Santo Tomas
Senior Engineering Manager
Adding information from the forum thread:
I am having a problem trying to render the full sequence (timeline) in one instance. This is a consistent fail. Premiere Pro freezes. I force close the app and then have no renders. The only color filters on the video clips are Lumetri color and Video Limiter. I have been doing this editing process for years. This failure to allow the full sequence to be rendered is a new development. The only thing I can do is render portions of the sequence.
The camera footage is from three Canon 1920x1080 .mxf and one Sony 4K .mxf camera.
The timeline is 29:30 long.
1920 x 1080
ProRes 422 (LT)
Matt please check the latest 12.1.1 update and see if this issue is addressed for you