Bug Reports

Issue - When using 'Enchance Speech' in the Essential Sounds tab, the audio is duplicated, it sounds like its playing the enchanced audio and the original audio at the same time. It's been happening for quite a while, today I invesigated and realise it happens when Proxies are turned on, turn them off and Premiere plays the enhanced audio only. It's not the worst thing in the world but frustrating anyway. Only one audio track is on the timeline when this happens.Adobe Premiere Pro version number: Version 24.3.0 (Build 59)Operating system - MacOS - 14.5System Info: CPU, GPU, RAM, HD: Retina 5K, 27-inch, 20193.7GHz 6-core Intel Core i5Radeon Pro 580X 8 GB64 GB 2667 MHz DDR4Macintosh HD - Media on External 5TB HDD over USB3.0Video format:Type: MPEG MovieFile Size: 320.13 MBImage Size: 3840 x 2160Frame Rate: 50.00Source Audio Format: 48000 Hz - 16-bit - StereoProject Audio Format: 48000 Hz - 32 bit floating point - StereoTotal Duration: 00:00:12:24Pixel Aspect Ratio: 1.0Alpha: No

Weird bug, but I've noticed that when exporting a timeline with proxies present AND I have anything copied to the clipboard via command C (usually timecode) the below button becomes unclickable, and I have to force quit premiere.  Premiere 24.3.0 MacOS Ventura 13.6.1iMac Pro 1,1 (2017)  

Scene Edit Detection has stopped working on clips with no audio / audio unlinked. See attached video for steps to reproduce:I duplicate the clip in the timeline. Remove the audio from duplicate on the right.The copy of the clip on left with audio detects the scene edits and cuts perfectly.The copy of the clip on the right with audio unlinked doesn't make any cuts.  Thanks!James 

As of the update to latest today the save file doesnt include warp stabilizer so I just lost hours of it analyzing. It also didnt load any previous stabilization from the past saved files so any stabilizing I have done is no longer there and a stupid blue bar is telling me to stabilize again which is days if not weeks worth of computational time.

After using mogrt assets regularly for a year, they are suddenly causing Premiere to crash instantly. I've been troubleshooting for two days, including rendering the video from one project and opening it up in a new project (in case the original project was corrupted), but with the same results once I add a MOGRT.

If you have a caption graphic, and you duplicate it (using the alt + click to drag), or simply slice of a bit, to create a new one, and you do this several times (perhaps 5+ times), Premiere pro starts to lag considerably.The only way to overcome this, is to create new caption every time, instead of simply duplicating. I'm guessing some kind of memory cache is being flooded with previous + new data, multiplied by every time you duplicate the caption.Please fix. thank you.

My laptop is very tired when editing a movie with Software Only, so I use GPU Acceleration (CUDA) when editing. Then it works much better. There are differences, however: all options regarding subtitles; stroke, background and shadow are much less saturated. However, this is the smallest problem. The biggest problem for me is that all graphics with the Transform effect applied to them are buggy. They move strangely diagonally and many others. Similarly, transitions in Premiere Composer by Mister Horse look a bit different. They have a small black bar on the left side. The editing itself with the above-mentioned problems is not that bad. The worst thing is, however, that just before exporting my video I am forced to change it to Software Only so that the video looks good. The consequence of this is that my short 20-second movie in 1080x1920 in 30 FPS exports for 10 minutes. Has anyone had a similar problem? Thanks in advance for your help.

Running Pr 2024 24.3.0 on a Macbook Pro M1 Max 64GB RAM Sononma 14.4.1 When working on a project, Pr just keeps taking RAM up over 100GB as shown on the activity monitor, until the app freezes up. I reinstalled it. Cleared media cache.  It just keeps eating the RAM. Even if I'm not actively editing. What the heck is going on with it??  

There is a lag in the timeline playback cursor. Earlier it was working fine, I even tried reinstalling the Premier Pro but the problem is not going away. I have even deleted all the cache files as well.

Das projekt besteht ausschliesslich aus Handymaterial 30,00fpsDer HEVC Codec wurde instaliert und aktualisiert. Alle codecs liegen vor. Trotzdem erkennt Premiere nicht und der Fehler bleibt. Auch wurde das Verzeichnes gelöscht wie angegeben.  Siehe Fotos. Fehler bleibt. ich kann das fertige File nicht rausrendern.        

I am running Premiere Pro 23.5 on Windows 11.  I have a Threadripper CPU, a 4080 GPU, 64 GB of RAM, and I use proxies.  I make 5 minute wedding videos with 2 songs on 2 seperate tracks and about 5 or 6 dialogue tracks.  Learning from my past mistakes, it is habit for me to lock all tracks and video layers I am not currently editing for risk of accidently deleting a major part or accidently moving a carefully edited song throwing off all the creatively edited music.  When tracks are locked, clicking around the timeline is delayed, zoom in and out of timeline is lagged, and during playback, the playhead stutters down the timeline even though the video playback itself is smooth.  It is frustrating to risk an accidental major mistake just to free up the editing process to be a smooth experience.  Any ideas?

I'm opening this issue again since I can't edit my last post for some reason (https://community.adobe.com/t5/premiere-pro-bugs/quot-replace-with-after-effects-composition-quot-doesn-t-copy-hold-keyframes/idi-p/14764886)I also can't add a reply, it removes the reply automatically. Issue: "Replace with After Effects composition" doesn't work with hold keyframesWhen using the "Replace with After Effects composition" feature in Premiere Pro, hold keyframes from Premiere Pro aren't imported to After Effects. They are ignored when importing to After Effects.Adobe Premiere Pro version number: 24.3.0 (Build 59)Operating system - WindowsCPU: 11th Gen Intel(R) Core(TM) i7-11700KF @ 3.60GHz 3.60 GHzGPU: NVIDIA GeForce RTX 3080, GeForce Game Ready Driver: 560.70RAM: Crucial 16GBHard Drive: Samsung 980 PRO 1TB M.2 PCIe 4.0 NVMe SSDVideo format: AnySteps to reproduce:1. Open Premiere Pro2. Import any footage layer into a new blank sequence3. Right click and choose "Add Frame Hold"4. Right

Hi, Adobe. An issue that seems to exist for ages and that hasn't been fixed so far, perhaps, because no one can explain how it even happens. There's certainly a co-relation between these two standard effects mentioned in the title which makes them glitchy. No big projects, only a new empty project with the media cache flushed, no third party plugins, only these two.1) I create a new sequence with the following settings:2) I import the footage. Any will do. I downloaded mine from the Storyblocks. It has the following specs:3) I drop it onto the timeline (no change of the sequence settings) and apply the two effects to the clip - Basic 3D and Transform.Now (see the first video) - if the Transform effect is above the Basic 3d in the effect controls panel and the Basic 3d values are unchanged, the Transform effect works. Once you change the Tilt or any other Basic 3D value, the Transform's position and anchor point stop working. If you change the tilt gradually and it hits the 0 value, the

When i edit multicam and change one camera it changes the camere before. To be more exact, i change from MC1 to MC2 back to MC1 in multicam editind. All of a sudden when i press button 2 for second camera, the frame before who was in MC1 changes to MC2 and vice versa depending on the camera i am trying to select. The end result is not having  camera 1, camera 2, and camera 1 again but three of the same cameras. I have to go back and check every time i do a sequence of changes. This doubles my time and work and is very annoying. I have a video below where you can see that i have camera 1 or MC1 selected, when i change the camera to MC2 the camera before which was originaly MC1 becomes MC2 resulting in 3 of the same selections 

I've been having problems editing on my 2023 Mac Studio and i'm wondering if this could be the issue?  For context i'm editing a 3 minute sequence with everything proxied and i cant even watch the sequence back because its too laggy. my specs are:Chip: Apple M2 UltraMemory: 64 GBGpu: 60-coreNeural Engine: 32-core 

Wenn ich den Verkrümmungsstabilisierer auf einen kurzen Clip anwende, braucht dieser seit einigen Wochen extrem lange zur Stabilisierung.Für 63 frames werden 7 min benötigt. Das war früher besser, deshalb kann es nicht am PC liegen.Ich arbeite mit dem Mac Mini M1. Update auf die neueste Version habe ich auch gemacht (23.5.0)Was kann man da machen? Woran kann das liegen?

Issue was encountered on Premiere Pro v24.5 (Windows)As I was importing some 4k - 59.97fps (around 5 - 20 seconds in length each) footage to a current project I was working on, I continually encountered an issue where during the importing process, Premiere would start acting very strange, my monitors would flash, and the application would need to be forced to quit. After some investigation via my task manager, I managed to diagnose that my system was using 14 gigs of RAM to import the footage, however, I had only allocated 8 to the application. Even importing the footage in smaller batches of 10 - 20 clips would cause issues in the importing process. Each time I would attempt, premiere would throw a flurry of seemingly random errors (they would all be different every time). The specific behavior I was experiencing would show that Premiere had imported the clips to the project successfully, but after sitting idle for about 10 seconds after the importing process was complete, the ap

instabilité complete de premiere pro , cela depuis quelques semainesreinstallé sur un autre PC les probleme sont identiques sous windows10 ou windows11impossible de travailler !d' autre part en multicam l ' affichage multi est alléatoirele logiel s' arrete message en rouge"premiere pro s'est arrete brusquement alors qu'un projet était ouvert  rouvrir"premiere pro derniere version le 27juillet2024

There is a FULL ON LAG on PP timeline to the point of unusable. Media of any kind on timelines are virtually frozen for so long - not populating or so slow. I thought it was exclusive to my new project (4K files) but now see it's occurring in all projects including: - a sequence containing 4K video clips from my Canon R5C whether FULL res or fraction; I normally don't have to create proxies, just change from FULL res to 1/8 or so if at all- a sequence of stills- sequences of separate pre-existing projects that were NEVER slow going back months I have closed everything. I have shut all tabs in Premiere to only work on one at a time (which I normally don't have to do). I have restarted countless times. working from:Apple M1 ProSonoma 14.5   

Warp stabilizer analysis slows down massivly when using Color Space Conversion from Rec 2100 PQ. to Rec 709. By massively I mean at least 90% slower.  Tested with Canon 4k/25 HDR PQ (Rec. 2100 PQ) footage and compared to regular 4k/25 Rec. 709 footage. Lumetri color settings used are default, i.e. HDR Graphics white to 203 and tone mapping for Max RGB.Reproduce: Create Rec. 709 sequence Add Rec. 2100 PQ footage Apply warp stabilzer   Environment: Pr. version 24.3.0 Macbook Pro (M2 Pro) with 32gb ram  

The colour picker tool doesnt read the viewer gamma, so when creating a colour matte to fill the background of a graphic, I can't match the colours without turning DCM off.

de facon alleatoire premiere pro s' arrette brutalement j' ai un message en rouge en bas d'ecranqui me demande de redemarrer je suis sous windows11 

I'm using 24.2.1 (build 2)Mac OS Sonoma 14.0  Using the remove filler word feature. Noticed few things I would consider as bugs. I'm using for editing a audio only podcast to give some context. 1. "oh" is considered filler. From what I've read about this feature it should only be catching "um" and "uh". I wouldn't consider "oh" a filler word. Would either prefer that's not included or pick what filler words I want Premiere to consider.  2. Whenever I do try to ignore "oh" as a filler the the auto-scroll in the transcript window gets all messed up. I get two blue bubbles highlighting my transcript. One bubble where the audio actually is in the transscript and another random bubble further back in the audio. It makes following along to find more incorrect filler words difficult.  3. Whenever I do remove an actual filler word my sequence timebar jumps ahead to some random place in the timeline and I have to go back to where I was when I deleted the fille

(I attached a video to show the bug, see below).I have been struggling with performance issues for a while now, before and after updating to 24.The timeline would become extremely slow, only when completely zoomed in would it be smooth. As soon as I zoomed out, it would freeze for several seconds, and the mac wheel would start spinning.I tried many things; resetting preferences, deleting cache, disabling 3rd party plugins, clean reinstall, moving scratch disks, deleting user workspaces, disabling AV headers/waveforms, moving everything to a new project; as many things as I could reasonably try while still needing to meet my deadlines.On a whim I tried disabling "Show duplicate frame markers", and suddenly everything is smooth again. I still have some "lagginess" when zooming in and out in the timeline, but it is now minimal and my projects are finally workable again.I saw a post from a year ago detailing the same issue, but I thought it would be appreciated to call attention to this bu

Computer: Mac Studio 2022OS: Ventura 13.6.7Software: Premiere Pro 24.5.0 (Build 57) Issue:I have some images that are oriented horizontally.  When I view the images in Bridge, they appear oriented correctly.  When I view the images in the Mac Finder window, they appear oriented correctly.  When I import the image into the media bin in Premiere Pro, in the file selection window the image appears correctly, but when the image is placed in the media bin and when the image is placed on the timeline, they are rotated 180 degrees. I seems like Premiere Pro is not correctly interpreting the orientation flag in the image metadata.