We've found that in Premiere Pro 14.3 the app.encoder.bind() function is not correctly exported. This means that, while rendering still works, attempts to connect to the usual render status messages will fail.
We apologize for this.
The problem is already fixed in Beta builds of Premiere Pro, and will be fixed in our next official release as well.
Premiere Pro 14.3 is here!
Today marks the release of Premiere Pro 14.3.
- How do I update Premiere Pro?
- To update Premiere Pro, open the Creative Cloud desktop application and choose > Update.
- What should I do if I don't see the update in my Creative Cloud desktop application?
- Choose Help > Check for Updates from the Creative Cloud desktop application to refresh the list of available updates.
Use Adobe Stock Audio within Premiere Pro
Adobe Stock is launching an entirely new content category, audio, making music tracks available for license. And you can now search, download, and license royalty-free audio soundtracks from Adobe Stock via the Essential Sound panel in Premiere Pro.
Afterburner support (macOS only)
You can now use the Apple Afterburner card with Premiere Pro to decode ProRes 422 and ProRes 4444 media (decoding in hardware instead of software).
New file format support
Premiere Pro now supports the following file formats:
- Enhanced bitrate controls for JPEG 2000 MXF export
- Import of Canon EOS R5 footage
- Import of Canon EOS-1D X Mark III footage
- Import of RED Komodo footage
For a complete list of supported file formats, see Supported file formats.
- Complete list of the new features
- List of Fixed Issues
- Release Notes
- Known Issues
- System Requirements
Adobe Digital Video and Audio Team Blogs:
- Accelerate Workflows and Craft Better Stories With Adobe Creative Cloud Video and Audio Applications
- How Beta is Helping Us Build Better Products
Let's now discuss the new features, including new Adobe Stock Audio within Premiere Pro feature!
Update: This issue has been fixed in Premiere Pro v14.3. Please download the latest update from the Creative Cloud Desktop app.
We are investigating an issue where Premiere Pro v14.2 might crash or get in a non-responsive state while using the Export Settings window. This issue has been observed on systems using NVIDIA GPU not supporting NVENC. If you are using such GPUs and experiencing a crash or freeze while using the H.264/H.265 format, please follow these steps to fix it.
Navigate to Premiere Pro Preferences > Media and uncheck Enable hardware accelerated encoding and decoding. Restart Premiere Pro and try to export.
Hope it helps. If you are experiencing a crash while exporting with any other format/codec, please create a new community discussion and we will get that issue checked.
With the release of Premiere Pro version 14.2, you can take advantage of dedicated H.264 and H.265 (HEVC) encoders provided by NVIDIA and AMD on Windows-based systems. These encoders can accelerate the encoding (export) performance when using H.264 and H.265 (HEVC) codecs in the export settings.
To enable Hardware Encoding, navigate to Export Settings and select H.264 or H.265 as Format.
Under the Video tab scroll down to Encoding Settings and set Performance to Hardware Encoding.
Also, enable Hardware accelerated encoding and decoding from Premiere Pro preferences.
For the Hardware Encoding to work, ensure that you have NVENC supporting NVIDIA GPU or AMD VCE/VCN supporting AMD GPU.
Refer to this link to check if your NVIDIA GPU supports H.264/H.265 encoding.
Please, note that a few of the Pascal, Maxwell and Kepler series NVIDIA GPUs don't support the H.264/H.265 encoding. NVIDIA GPU based Hardware Encoding won't be available on these GPUs.
Though, if you have an Intel CPU with Quick Sync support, then that can be used for Hardware Encoding (but it might not be as fast as NVIDIA based encoding).
To check for AMD GPUs that support H.264/H.265 encoding, please refer to this link.
Also, please ensure that you have the latest NVIDIA/AMD drivers installed on your system. If after installing the latest driver you are still not able to utilize Hardware Encoding, try doing a clean installation of GPU drivers. Here is how to do it.
Here are a few points to remember while using Hardware Encoder.
- If Premiere Pro noticed any problem with the GPU driver, then the Hardware Encoding option might get disabled. Try updating or doing a clean installation of the GPU driver.
- Premiere Pro will use only one GPU for Hardware Encoding.
- AME can use two cards if one is Intel and one is Nvidia in case of Parallel encoding.
- A higher CPU utilization might be observed during the Export if software decoder is used for the source files (like for MXF, R3D, ProRes) or if multiple non‐GPU accelerated effects are used.
- Hardware encoder performance may change as per CPU and GPU combination.
- Some features are not supported for Hardware Encoding like VBR 2 pass and 5k & 8K export for H.264.
If you are getting this error while selecting Hardware Encoding, try changing the above-mentioned export parameters.
- On macOS, Hardware Encoding is done through Video Toolbox. There is no change on macOS based systems with regards to Hardware Encoding in Premiere Pro 14.2.
(to be able to use Hardware Encoding on macOS, please ensure to have macOS 10.13.5 or later).
Hope it helps in answering your questions related to the new Hardware Encoding in Premiere Pro v14.2.
If you are experiencing Premiere Pro crash at launch you may try these steps to fix the issue.
Before proceeding, verify that your system meets the minimum requirements for the app to run properly.
Here is how to check the system specifications of your computer.
Open the System Information app from the Start menu
The System Summary page should give you the basic info about the Windows version, CPU model and amount of RAM installed.
To check the details about the GPU, navigate to Components > Display.
To check the system specifications on macOS, navigate to Apple menu > About this mac.
Premiere Pro crashes may occur in different stages. Follow the troubleshooting steps depending upon the stage in which Premiere Pro is crashing at your end. If you are not certain about the stage in which Premiere Pro is crashing you may follow the steps in order.
Stage 1: No Splash Screen
- Check if any instance of the app is running in the background. If so, force quit it using Activity Monitor (macOS) or Task Manager (Windows).
Reset app preferences to isolate any preference corruption issue that might be causing the app to misbehave.
Here is how to reset Premiere Pro preferences.
If the app still crashes try to manually rebuild the preferences.
Navigate to Documents\Adobe\Premiere Pro and rename the folder with the app version number.
If you are using Premiere Pro 2020, navigate to Documents\Adobe\Premiere Pro and rename the folder named 14.0 to old14.0.
In the Premiere Pro folder, you may find folders with different names like 14.0, 13.0, or 12.0.
These numbers correspond to the different Premiere Pro versions installed on your system.
Rename the folders based on the version of Premiere Pro that you are using.
The next time app is launched the default settings will be recreated.
Check for Read & Write Permissions.
Create a new user account with administrator privilege and check if the app is launching properly in this new account. This will isolate any possibility of user account corruption failing the app to load.
Here is how to create an administrator account.
- Try updating your GPU drivers. If they are already up to date, try a clean installation of GPU drivers.
Here is how to do it.
- Reinstall Premiere Pro from the Creative Cloud Desktop app.
Stage2: Stuck at Splash screen
- Check the component at which the app is getting stuck at the time of launch.
If you notice that the app is getting stuck at loading any third party importer/exporter component, try uninstalling or removing that third party component.
- Stuck at Initializing MediaCore or while loading third-party plugins.
Navigate to the default plugin location and move all the plugins from the MediaCore folder to a folder on the desktop and then check if the app is launching properly.
Default plugin location:
Windows: C:\Program Files\Adobe\Common\Plug-ins\7.0\MediaCore
macOS: /Library/Application Support/Adobe/Common/Plug-ins/7.0/MediaCore
If the app is still crashing try resetting preferences as mentioned in Step2 of Stage1.
- Stuck at Preferences read only or Directory access error.
Check if Premiere Pro has necessary read & write permissions for the essential folders. Refer to this link to understand how to assign these permissions on Windows and macOS.
If assigning the permission didn't help try Step4 of Stage1.
- Stuck at Startup error: Premiere Pro could not find any capable video play modules.
Follow the instructions mentioned in this article to troubleshoot this error.
Hope it helps in fixing the crash issues. If you are still experiencing the crash, please create a new community post with a brief description and your system specifications.