Re: Premiere Pro randomly not working

Francis-Crossman · ‎May 19, 2023

I'm very sorry you are experiencing this frustrating problem. Unfortunately, you haven't provided enough info for us to help you. Please take a look at these guidelines for submitting a bug report How do I write a bug report?

Francis-Crossman · ‎May 19, 2023

HDR graphics white can be a very confusing parameter. Despite the name, it has no control over graphics. It controls the scaling of video levels when converting between color spaces. The nit value (100, 203, 300) refers to how bright a white card should be in an HDR scene. Imagine putting Rec709 into an HDR sequence. In the Rec709 scene, you are shooting a white card, and it's exposed all the way to 100% IRE (100 nits). PPro will automatically do a colorspace conversion, but we need to know how bright the result should be. Graphics white says to scale the values such that the white card lands at 203 nits in the HDR sequence (or 100, 300). 203 is generally the industry standard. 203 is 75% of the signal in HLG. You wouldn't want to scale 100% in Rec709 to 100% in the HDR scene because it would be far too bright. The setting gets its name from the industry recommendation that pure white graphics like subtitles or end credits should land at a specific nit value - generally 203. But our graphics tools are not affected by this value. It's up to you to set the level properly for graphics. There is a lot more detail here: adobe.ly/hdr

Francis-Crossman · ‎May 19, 2023

Did you submit the crash report and include your email? If so, we can find it and take a look. You can DM me if you don't want to post your email here. Here are some troubleshooting steps to try - You say your graphics card driver up to date? Which version are you running? Be sure you are using Studio drivers, not game drivers - Do you have any third-party plugins installed? Try bypassing the loading of third-party plugins - Try resetting your plugin loading cache - Try resetting your media cache - Try resetting your preferences You can run these ^ options by holding down CTRL or ALT when launching PPro. Even if PPro is crashing on launch every time, you should still be able to run these troubleshooting steps because the Reset Option window will pop up before PPro launches fully.

Francis-Crossman · ‎May 18, 2023

@KazuT you can download the beta from the Creative Cloud Desktop app. In the categories on the left, find "Beta Apps". From there find Premiere Pro. It looks like the beta version is a few days behind our internal builds. The fix is in 23.5.0 build 39 or later. Looks like the most recent is 37 as of today.

Francis-Crossman · ‎May 18, 2023

Thanks @Ann Bens. I tracked down our internal bug and it indeed is related to loading audio clips. We have a fix in beta now!

Francis-Crossman · ‎May 18, 2023

@Shamgar are you able to reproduce this bug consistently? What are the steps to make this happen? I've seen this myself occasionally but can't reproduce it when I try, making it a very tough bug to fix. Any help from you would be very appreciated.

Francis-Crossman · ‎May 18, 2023

@artofwot I recommend using the built-in Prores encoding that comes standard with Premiere Pro. Prores encoding has been available natively on Windows for a few years now, so there really is no reason to use Miraizon anymore.

Francis-Crossman · ‎May 17, 2023

We have a fix in beta as of version 23.5.0 build 39. If you can try the beta, please let us know if it fixes things for you. I made an official known issue post in the bug forums and will post further updates over there Known issue: Certain custom keyboard shortcuts are reset to default in 23.4. This issue has also been added to the Known issues for Premiere Pro on helpX.

Francis-Crossman · ‎May 17, 2023

This issue is fixed in 23.5 which is available now. Please update to get the fix. We are aware of an issue in Premiere Pro version 23.4 that causes certain custom keyboard shortcuts to be reset to their default on launch. If you are using custom keyboard shortcuts from the list below, they will get reset to the default value on the first launch after updating to 23.4 or on the next launch after customization when using 23.4. This problem is fixed in public beta as of version 23.5.0 build 39. Workarounds and recommendations: Workaround #1 – update to 23.5 Open the Creative Cloud Desktop app Click on updates Find Premiere Pro Update to 23.5 or later Workaround #2 – stay in 23.4 – launch with the default set and switch back to default before quitting Setup your shortcuts the way you like and save a custom keyboard setup Switch back to default before quitting After PPro is up and running you can switch to your custom shortcut set Switch back to default before quitting Make a backup of your keyboard shortcut file. Look for .kys files here: Mac: ~/Documents/Adobe/Premiere Pro/23.0/Profile-[USERNAME]/Mac/ Win: C:\Users\[USERNAME]\Documents\Adobe\Premiere Pro\23.0\Profile-[USERNAME]/Win/ Duplicate the .kys file and save it somewhere else on disk Any .kys file you put into that folder location will be available as a custom shortcut set in Premiere Pro. Full list of commands we believe are affected: Application File Production... Linked Team Project... New Open Production... Edit Team Project Update Publish Resolve Conflicts... Convert Project to Team Project... Convert Team Project to Project... Browse Versions Browse Auto-Saves Clip From Source Monitor From Source Monitor, Match Frame From Bin Replace With Clip Window Audio Clip Mixer Audio Meters Audio Track Mixer Effect Controls Effects Essential Graphics Essential Sound Events History Info Learn Libraries Lumetri Color Lumetri Scopes Markers Media Browser Metadata Production Program Monitor Progress Projects Reference Monitor Review with Frame.io Source Monitor Text Timecode Timelines Tools

Francis-Crossman · ‎May 15, 2023

We believe this is the full list of affected commands. It seems most people are tripped up by the Window commands, anything involving switching panels. We believe only these commands will be reset on launch. All other custom shortcuts will be retained. Application File New Production... Linked Team Project... Open Production... Edit Team Project Update Publish Resolve Conflicts... Convert Project to Team Project... Convert Team Project to Project... Browse Versions Browse Auto-Saves Clip Replace With Clip From Source Monitor From Source Monitor, Match Frame From Bin Window Audio Clip Mixer Audio Meters Audio Track Mixer Effect Controls Effects Essential Graphics Essential Sound Events History Info Learn Libraries Lumetri Color Lumetri Scopes Markers Media Browser Metadata Production Program Monitor Progress Projects Reference Monitor Review with Frame.io Source Monitor Text Timecode Timelines Tools

Francis-Crossman · ‎May 15, 2023

Our engineers have been looking into this, and we definitely have a bug. Here is what we know. Premiere Pro loads in the keyboard shortcuts at launch A few specific commands fail to get loaded from the KYS file, and these commands are being reset to the default. Not all commands are affected. We think only about 5% show this problem. I'm working with engineering to see if we can create a specific list. Engineering is testing a fix now. If testing looks good, we will first roll it into public beta. I'll update this thread when that happens.

Francis-Crossman · ‎May 12, 2023

@tomc94919815 can you give me some more details about these problems? What version of Premiere Pro are you running? We do support closed captions, and we do support overwriting an existing file while exporting. These are solvable problems. I'm sorry you are frustrated. We're here to help.

Francis-Crossman · ‎May 10, 2023

This should not be happening. I logged a bug and asked some engineers to take a look. Would it be possible to share your KYS file with us so we can take a look? Feel free to DM me.

Francis-Crossman · ‎May 10, 2023

@Remote Index I don't know who removed your post but to answer your questions - The issue has been added to the known issues page for 23.3 and the fixed issues page for 23.4. We don't have any known issues for 23.4 as of now.

Francis-Crossman · ‎May 10, 2023

This issue is fixed in 23.4, which has just been released. Update to 23.4 to get this fix.

Francis-Crossman · ‎May 03, 2023

The issue is fixed in Premiere Pro beta as of version 23.5.0, build 20. Install the latest beta if you want to try this fix. Beta and Release versions can be installed side-by-side and the projects are compatible so you can open the project in beta to get the export done and not have to reset your preferences. More info on Beta apps here: https://helpx.adobe.com/x-productkb/global/creative-cloud-beta.html. We will be putting this fix into an official release very soon.

Francis-Crossman · ‎May 02, 2023

Our engineers have found out why the files play back so poorly. They have one single I-Frame at the very beginning of the file. GOP structure codecs are supposed to have I-Frames periodically throughout the file - like every 15 frames, sometimes much further apart than that, but never just one for the whole file. So the further you get away from the beginning of the file, the worse it gets in this case. The next step is to find why they are being encoded this way and then fix it. We believe this only affects HEVC on Apple M1. We're on the case. In the meantime, can you use H264 for your workflow? You can also use software encoding as @Kevin-Monahan suggests.

Francis-Crossman · ‎May 01, 2023

Just want to let everyone know the progress. We have an internal fix for this that we are testing and will put into beta in the next few days and then roll into an official release as soon as possible.

Francis-Crossman · ‎May 01, 2023

@Remote Index, we're updating that page soon.

Francis-Crossman · ‎May 01, 2023

@Deleted User Are you using "Match sequence preview settings"? Try avoiding that one, and your exports should be successful, and you won't have to reset your prefs all the time. Let me know if this is not the case for you.

Francis-Crossman · ‎Apr 28, 2023