Premiere Pro 14.4 is now available for download from the Creative Cloud desktop app. This update includes new features, several bug fixes, and performance improvements. It is recommended for all users.
New features & enhancements
Scene Edit Detection
Use machine learning to automatically detect and add edits where cuts occur in a video.
HDR for broadcasters
With the new Rec.2100 HLG color space, broadcasters can work with more vibrant and dynamic content.
You can now choose to use proxies while exporting if you want a quick export that doesn't require full resolution media.
Premiere Pro now scans VST 3 and AU (Audio Unit) plugins faster. Also, exporting an AAF with Breakout to Mono deselected preserves audio channelization.
Here is what we've fixed in version 14.4
- Playback does not stop when waveforms expanded with smooth scrolling and multicam view enabled
- Improved location of licensing information for Stock Audio
- Improved consistency of contextual menu behavior using search bins
- Deleting an empty Audio track prevents VoiceOver from being recorded
- Hardware encoding not available on Mac when encode height is greater than 2196 pixels
- DNxHR MXF files files exported as non-standard frame size that contain display aspect ratio of 16:9 may play incorrectly in external players
- Some files that play correctly in QuickTime Player import as audio only
- Improved ProRes Multicam Playback Performance
- Twitter 1080p preset now produces higher quality outputs with match source for frame rate and higher bitrate.
- Cannot log in to Vimeo
Update: This issue has been fixed in Premiere Pro v 14.4. Please update to the latest version using the Creative Cloud Desktop app.
We are investigating an issue with Premiere Pro (v 14.3.2) where the Time Remapping line doesn’t respond to click and drag actions.
Here is the workaround for this issue:
Instead of clicking on the Time Remapping line to adjust the speed, try clicking slightly above the line and you will be able to adjust the parameters.
If this doesn't help, you may install the previous version of Premiere Pro from the Creative Cloud Desktop app and check if it's working properly in that.
This is only applicable to Premiere Pro 14.3.2. If you are experiencing any Time Remapping issues with the other versions, please create a new post describing your issue.
Hope this helps in solving the issue. Let us know if you have any questions.
Adobe MAX—The Creativity Conference, October 20–22
It's that time of year, Adobe MAX! You can register now here! It's a FREE virtual event - Expect the unexpected!
Expect the unexpected
Make plans to join us for a uniquely immersive and engaging digital experience, guaranteed to inspire. Three full days of luminary speakers, celebrity appearances, musical performances, a global collaborative art project, and 350+ sessions — and all at no cost. Register now to build your schedule and get sponsor giveaways.
More info to come. Let me know if you have any questions.
We used to have our video content spread out across a few different Twitter handles, but we've restructured with you in mind! By the end of this month, all Twitter conversations will be happening @AdobeVideo.
Join us there to stay up-to-date with changes to the application and opportunities to connect with other artists like you! We hold contests, share tutorials, and collect feedback for future improvements. By consolidating the Twitter handles, we're hoping creators of all types will share their work – we can all learn from each other!
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.
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.