Copy link to clipboard
Copied
One of the common issues is slow and stuttering playback. Here is a video by the inimitable Colin Smith about how to combat this issue:
Copy link to clipboard
Copied
Did this video help you solve any of your issues? Let us know!
If you are still having performance issues, your media is probably too heavy for your computer. It's a common problem as footage these days is so highly compressed. Even expensive computers can struggle with certain footage.
For example, 4K H.264 or HEVC media from your camera or mobile device needs additional handling in order to edit with it smoothly in most cases (especially 4:2:2 10-bit video). In that case you'll need to do one of the following:
Thanks,
Kevin
Copy link to clipboard
Copied
Thanks for the advice, it really helped speed up Premiere.
Copy link to clipboard
Copied
Yeah explain why my M1 Max on my Macbook pro cant run Pr? Most Adobe products run on my brand new computer like crap! These programs are not updating and having any functionality on the newest computer platforms and GPUs....when are you actually going to speed up Adobe and not give us filler (oh look the heal brush can fix hair)...
Copy link to clipboard
Copied
@MadPlaid
Did you migrate the apps or do a clean install?
I just have the M1 Mac mini and Photoshop, Illustrator, Premiere Pro, After Effects, and Media Encoder each run really, really well. The main thing I had to avoid was installing any third party options that are not Apple Silicon ready.
Copy link to clipboard
Copied
Yes I’ve done several clean installs using the Adobe cc uninstaller
software. --
Christopher
(PII removed by moderator)
Copy link to clipboard
Copied
Performance is low. Media support from cameras from well-known world brands such as Sony FX3, FX6 and FX9, as well as Fujifilm XT3 and 4 is not implemented at all. Users of these cameras write an outrageous number of comments that are still unsolvable. People complain about the poor performance of viewing media received from these cameras. We live on the threshold of a new era, and problems with the most popular cameras, among users and not only, persist. The Premiere program should not cause problems with media playback during the initial assembly of the material. Yes, of course, any files that are not written in editing codecs should be translated into editing ones (ProRes, CineForm), but in general, viewing performance should not depress and distract from the idea of creating a product. It turns out that the user is struggling with figuring out how to make it so that it's easy to see. It's not professional. I will also touch on the number of supported camera profiles when translated into the desired color space, which are only a few. Excuse me, gentlemen, answer me a question, but what do people in the world use only Sony, Panasonic and Red and Alexa? Where are other supported profiles from cameras from well-known manufacturers with their color spaces in the Interpret Footage tab? There are very few of them. Consequently, the user is restricted from using the tools of the program for the correct interpretation of the media. They do not work out LUTs professionally and part of the data is lost. There is an article about this by an Adobe employee. There are ideas and thoughts, but it takes a very, very long time for everything to be realized.
Copy link to clipboard
Copied
Hi Baffy,
Sorry for the frustration. The 4:2:2 10-bit formats that the cameras you mentioned do require the latest CPUs and Quick Sync. If you don't have those, you won't get the performance you might expect. I'm afraid that color profiles and LUTs are off-topic from this particular post about performance. Please upvote any feature requests for color workflow on User Voice.
Thanks,
Kevin
Copy link to clipboard
Copied
Yes, transcoding to ProRes is a professional choice (and highly recommended as it minimizes having a yellow line appear above the footage and allows for faster rendering and exporting).
Premiere Pro should see an embedded LUT if present or use the Media Color Space from the file if present. In the case of Red footage, users have the RED Source Settings Effect automatically applied at the source level to manage Color Settings.
I think all of the companies that you listed post LUTs for preofessional to download for free:
There is a lot to learn and know about. Rather than get frustrated about it, I try to enjoy that there's always more to learn. Formal training or mentoring with someone extablished in the field are ccommon approaches to learning a workflow.
Fortunately, Adobe maintains the Adobe Support Community that has a weath of information to suppliment the user guides that anyone almost anywhere can access.
Copy link to clipboard
Copied
I do not require the application of LUT to frames to redefine the color profile of the raw material. I'm asking Adobe to embed camera profiles in the Interpret Footage tab. Not LUTs, but color space profiles. Your employee fixed a topic on the forum about the quality of the use of LUTS and himself confirmed that the quality is lost with it. Color space profiles are needed.
Copy link to clipboard
Copied
"There is a lot to learn and know about. Rather than get frustrated about it, I try to enjoy that there's always more to learn."
-That's all well and good and we all want to remain as positive as we can, however when there are long standing performance glitches that are reported daily and update after update after update after update do absolutely nothing to address those issues, it's really difficult to stay on the "silver lining" side of things when we have deadlines to meet and clients to satisfy.
Copy link to clipboard
Copied
Which performace glithces are you referring to and with which versions of Premiere Pro and which OS?
Is your workflow built around ProRes, DNxHD, or Cienform? In other words, is your workflow built around CODECs that are good for editing? This is just a guess, but 90% of the problems reported in these forums have to do with trying to force one video file format or another to be good for editing.
Copy link to clipboard
Copied
Hey Warren,
A couple glitches I'm going to mention aren't related to speed but are glitches nonetheless. I'm referring to:
1. Choppy playback (my specific case is in multi-cam and I actually just created a new post about it with hardware details)
2. Audio autosynch being incredibly slow and/or inconsistent.
3. Multi-cam audio panning hard left.
4. Image stabilizer applying random cropping to clips.
To be more specific to the choppy playback, I work around DNxHD. I've had 3/4 of those listed issues since 15.0. I've cleared my cache, fixed my audio input, lowered my res to 1/16 while editing. My computer was handling this exact file and exact source footage one week ago with complete ease and now premiere has crashed on me twice without the chance to save and has set me back over an hour now.
Copy link to clipboard
Copied
no it didnt, this is frustrating. Paying for what is supposed to be a premier software that it behaves this way .
Copy link to clipboard
Copied
Hi one little thing that helped me with this problem was not having overlapped videos on different tracks.
Copy link to clipboard
Copied
I was so excited at the prospect of finding a solution... but sadly I have yet to find one. Editing in Premiere has been terrible. Here's footage of the stuttering playback:
https://vimeo.com/1069712653/a95354d9d4?share=copy
It gets worse (much worse) the longer I'm in the application. Quitting and restarting does seem to help a bit. Also not sure why I have a yellow render bar. I have a fully spec'd 2025 m4 MacBook w 128GB of RAM... and yellow render bar with four different kinds of footage (Drone, iPhone S1H, c300).
Copy link to clipboard
Copied
@ebenabbaan
The Yellow bar only goes away when we're using the Smart Rendering workflow. That is, all of our source footage is a format that can be it's own Preview file and the Video Preview setting of the Sequence is set to those settings. For example, since the default Video Preview setting is ProRes 422 LT, ProRes 422 LT source should not have the Yellow bar for standard playback and speed changes. Yellow may show up as we add effects. If the project is for social media, I usually use ProRes 422 LT. If the edited is the product (like feature film, episodic television/streaming, promos/trailers) ProRes 422 HQ or better.
Based on your sample video, have you tried setting the Playback Resolution to 1/4?
Also, I would suspect that you can do your rough cut at 1/2 or maybe even Full Playback Resolution with smooth playback (so, single stream playback in one Video Track) and then switch to 1/4 as you get to your fine cut. Then when smooth playback is important to watch down a Sequence at Full, render the effects such that the Time Ruler is green.
Copy link to clipboard
Copied
Thanks for writing. I was hoping (and still hope) it is some setting that's off because I have tried setting the Playback Resolution to 1/4 (and 1/8) and still it stutters. One potentially useful clue is that [in the video I posted] playback stutters at the very end, after we have faded to black, and only the song underneath is still playing + fading away.
Playback stutters even with ProRes proxies, when I delete the Media Cache and prefs, and when I use Project Manager to create a new project AND transcode to ProRes. And of course I know it's not my machine, which is top of the line. It has to be some setting/mismatch.
I've also tried moving projects (and different projects, with different types of media) to different drives, including a RAID 0 made up of SSDs that I know is super fast.
One thing I should mention, because it DOES pertain to audio: I have two monitors plugged into my laptop (which is in clamshell mode), and both monitors (an LG Ultrafine, and an Apple Studio Display) have speakers. But there's no mismatch in the audio output settings (that I can see anyway).
Copy link to clipboard
Copied
Hmmm...
I don't see clamshell mode or having two displays with speakers causing an issue, but in troubleshooting I would try editing with just the built-in display of the laptop for a little while - then introduce the Apple Studio Display and then introduce the LG display. I'd also double-check that all source footage is a frame rate that either matches the sequence frame rate or is a whole-number multiple of it. For example, a 60fps clip can be used in a 30fps timeline without interpolation, since 60 is divisible by 30. I'd also try doing a project from scratch where all source is transcoded to ProRes 422 LT or ProRes 422 HQ with Sequence Video Previews set to match.
Copy link to clipboard
Copied
Since my last post I tried editing without the external displays plugged in, I still get the same issue. And yeah... all the footage is is 23.98, sequences match.
Copy link to clipboard
Copied
Just installed Premiere 2024, and older project files of some of my multi-year projects that reference a lot of the same media I'm having problems with currently work perfectly well. So there's definitely something up with Premiere 2025, maybe the plugins I have installed in Premiere 2025... I'm not sure.
But yeah, Premiere 24.2.1 is running perfectly on my machine.
Copy link to clipboard
Copied
Beleive it or not there are many things that can effect playback when using Preiere Pro. Quick Sync, CUDA Open CL and ASIO etc. It takes a while to get Premiere Pro tweaked out 100% as seen in the video below.
Copy link to clipboard
Copied
That video is from 2020, on a windows machine...
Copy link to clipboard
Copied
Hi,
I may be the only person in the world with this issue but I eventually figured out that my playback was laggy because the default audio input was wrong. I went to Edit --> Preferences --> Audio Hardware --> Default Input. The default input was the mic on my ancient webcam from like 8 years ago. I switched it to a more modern microphone and the playback improved a lot. I assume switching it to be nothing would have worked to (I'm not using the audio input for anything) but I didn't confirm that.
Regards,
John
Copy link to clipboard
Copied
Thanks for mentioning this, John. I have added your comment to my list of Performance issues I am advocating a fix for. There are numerous bugs to upvote with the following search on User Voice. Please upvote the bug that most closely matches your case here.
Thanks,
Kevin
Find more inspiration, events, and resources on the new Adobe Community
Explore Now