Bug Reports

I'm running out of steam and desperate for help as this is starting to impact my ability to make a living.  Premiere Pro crashes for me roughly 5-10 times a day and I continue to receive BSODs but not sure what else to do at this point. Within in the software, I've already:removed/installed latest versioncleaned up cachereset preferencesupdated all NVIDIA driversmade sure all windows updates are in placeun-installed/re-installed clean version of Windows 11 Here's the specs of my machine:i7 13700K64GB ram (DDR5 4800)RTX 3080 (running studio driver 536.99)Crucial P3 internal SSDs (even though I edit from external Samsung T7 drives typically) Here's the debugger from the latest dump file since I can't attach it directly: ************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true AllowNugetMSCredentialProviderInst

Source patching caption tracks is not working. If I'm editing from one captioned sequence to another (timeline as source), it doesn't matter if I patch the caption track of the (source) timeline or not, it will overwrite or insert the captions from the source timeline regardless.Video and audio track patching works fine. Is this a bug?  PP 24.3Mac Studio - Sonoma 14.2

I edit videos which are shot at 60p, then slowed down 40% and edited into 24p timelines. Normally you can select all your footage in the project/bin panels and change the speed/duration before editing. But now there's a weird bug after the latest update where clip speed/duration is greyed out (and keyboard shortcut doesn't work) on most clips in the project/bin panels (it still works as expected when selecting clips in a timeline). The only clips that seem to work are .MOV files with no audio, or mograph preset clips. Workaround is to select one of the above clips at the same time as the others (ex. place an audio-less .MOV into the footage bin and select all) and then speed/duration works as expected. Bit annoying but at least it's an easy and quick workaround. Hopefully the bug gets fixed soon. Version 24.3.0 (build 59)Windows 10 Pro 22H2 19045.4355

When a timeline has video assets that are .mov using the HEVC codec, a couple of frame shifting bugs pop up. If the sequence frame size is changed, the timeline will lose a frame and each asset in & outpoint is shifted.  In this use case, the timeline is exactly 24 frames and the source videos are exactly 24 frames, encoded with .mov with HEVC compression.  The timeline timecode shifts one frame. If the timeline started at 0, it now starts at 00:59:59:23. If it ended at 1 minute exactly when at 1920x1080, after changing to 1080x1080, the timeline now ends at 59 seconds and 59 frames.  Immediately after the hitting "ok" after entering the new sequence frame size, the playhead is flipped backwards (the bar is on the left side instead of the right side). It flips back to the normal side once you move the playhead.   The in point for the HEVC clips is one frame later. The clips have not shifted on the timeline. The in point of the content ha

minha estreia foi atualizada para a versão 24.1 e ela não está transcrevendo meu vídeo, ela começa a transcrever e para, preciso de ajuda

Problem:I am unable to save a rendered video from Premiere Pro to my iPhone's Gallery via AirDrop. Instead, the video is saved to the Files app. The "Save to Gallery" option is grayed out and unavailable when I open the video in the Files app. This prevents me from sharing the video on social media platforms.Details:The issue does not occur when I render the same project files on a different computer. This suggests that the problem lies with my computer or Premiere Pro installation.The "Hardware Encoding" option is disabled in the render settings.The AirDrop settings are set to "Everyone".The video format is MP4.My iPhone's iOS is up to date.Attempted Solutions:Rendering in a different format.Enabling and disabling the "Hardware Encoding" option.Changing AirDrop settings.Reinstalling Premiere Pro.Problem Source:It is currently difficult to determine the exact cause of the issue. The problem could be due to a bug in Premiere Pro, my computer's hardware or software, or compatibility issu

Reproduction steps:1. Click on the sequence window so it has focus2. On a video track, highlight some clips and right click and select "make subequence"3. The source panel opens and no subsequence is created in the project window. Workaround:1. Click on the sequence window so it has focus2. On a video track, highlight some clips.3. Click back on the project panel so it has focus (with the highlight around it)4. Go back to the highlighted sequence (do not left click on anything to give the window focus), right click on the highlighted clips and select "make subseqence"5. The subseqence then shows up in the Project panel with the "sub" text in the naming.and right click and select "make subequence" 

Hello, I am trying to edit a video in Premire Pro. However, something is cuasing the video ti display with increased brightness and contrast when I import the file into my project. I have tried doing File > Import as well as dragging the video into the project and both import methods are seeing this issue. Anyone have any ideas of what's causing this? My app is up to date and. Attached is how the footag elooks in QuickTime vs. immediately importing into Premiere.Thanks in advance! 

When undocking the Program panel to put it on my second monitor, I'm no longer able to double-click and select objects in that view (to resize, move around, etc). Re-docking the panel doesn't fix it, resetting the workspace also doesn't fix it. The only thing that brings back the ability to select anything in the Program panel is closing and reopening Premiere. On Mac OS Sonoma 14.4.1 with Premiere Pro 24.3.0 Build 59.

If I leave Lumetri Scope open (typically with RGB Parade and Waveform on 'float') over night then I will return to a "You have run out of system memory" OS arror. Premiere will have consumed 300+GB of memory. Premiere will show as "Paused". There is a 'resume' button, but it does not work even long enough to save or quit Premiere. The only solution is to force quit Premiere.  Steps attempted to resolve:-- Remember to close the Lumetri panel - WORKS-- Trash preferences (including dissabling the Creative Cloud sync) and cache - ERROR-- Restart Mac / Reset Mac Pram etc - ERROR-- Disable non-Adope plugins - ERROR Steps to confirm:-- Restart everything / Creat new, empty Premiere project / Add one h264 video file, open Scopes / Leave overnight - ERROR-- Same as above but with ProRes 444 - ERROR MacPro 2019OS : 12.5 MontereyCPU: 3.2 GHz 16-Core Intel Xeon WRAM: 192 GB 2933 MHz DDR4GPU: 2x AMD Radeon Pro W5700X 16 GB

In the Media section most of my videos it says  “media pending” when I select a video.When I play my sequence nothing happens, the video goes black, it doesn’t show time passing in the video, and once I play it I can’t stop it.Overall everything is laggingSo this has been happening all day and I can just wait a bit about it will work again but now it just won’t go back to normal, I’ve restarted my computer twice but I’m scared to again because of…Everytime I try save my work this pops up and i have no idea what is means.I’m not that good at premeire pro and I don’t necessarily trust its and my capablity to save the work I’ve done.So please, help.  

This is the second time that this has happened to me and it is a disaster. Last time I assumed it was the text-based editing that caused it. I still think that is really what is causing it. I will never use text based editing again. What a nightmare.I used text based editing in this project, but not on this sequence, and I am guessing that's why this problem is happening again. What a disaster. So as it stands now, I have a sequence that I was up editing for hours last night and into the morning, on a deadline. Today all the audio is wrong. It is synced audio from an audio recorder. The sound was all synced up. I did all my edits. At one point today. I adjusted the gain on one clip and then the audio did play at all. I restarted the computer and now all the audio is off in the entire timeline. I export from the timeline, the same thing. Even backups and earlier versions of the project. This sequence is consistently out of sync. The sequence is currently ruined.I tried opening

So I recorded my video in 4k when it's time to export and I match bitrate it matches to 1080 p then I change it to 4k UHD and the export has glitches in it where my adjustment layers are I have tried everything, exporting software only, changing it to h265 nothing is working!!

Bonjour, je travaillais sur un projet première sur mon mac avec mes fichiers sur mon disque dur externe. Lorsque je l'ai réouvert hier, les médias demeuraient en attente, aujourd'hui ils sont hors ligne. Lorsque j'essaye de les lier impossible d'ouvrir le disque dur, lorsque je clique sur le disque dur rien ne s'ouvre. Pourtant je n'ai pas touché à mon disque dur depuis la dernière fermeture et mon disque fonctionne sur le mac si je passe par Finder. Que faire ?merci d'avance 

About a month ago,  my copy of Adobe Premiere started hanging when I try to edit settings in the "Text" window and also when I clicked the "Export" tab to render out a video. Things eventually happen, but it can take 5-minutes to go from Edit tab to Export tab. This happened gradually too. Everything was working perfectly and slowed over a week. I assumed it was related to the specific project I was working on because it had dozens of hours of audio clips with transcribed text. However, it now happens on every project (even those without transcribed text). I used this performance issue as an excuse to upgrade my edit system. I am now working on a completely unrelated system (new motherboard, new operating system (Win 10 to Win 11), new RAM, new Adobe installation, new everything). Despite being on a completely overpowered system, opening the Text or Export windows literally takes several minutes. It also seems to be getting worse. All other features of Pre

We are having a lot of problems editing C70 and other misc footage types in Premiere 2023 and I wanted to see if anyone else is having a similar experience.  I mention c70 specifically as this codec performs the worst in all of our test.   I'm hoping to share some test results here to see if anyone else has any ideas.  Fist, I would like to note that we tested importing files on two different machines.  When I mention PC below I am referring to a i9 13900K 3.0Ghz 24 Core machine with a Nvidia 4080 built by Puget Systems.  For our mac test, we used a M1 Max Mac Studio.  For both of these systems our primary storage is a 10Gbe Network Attatched storage appliance from a very reuptable vendor who is also helping us look into this issue.  For both machines an AJA network speed test is showing around 800MB/s Write Speed and 1100MB/s Read speed connecting to the storage.  Straight file transfers from both machines seem to backup these speeds a

Issue - When I Collect Files and Copy to a New Location, Pr is not including LUTs (.cube) files when copying media folders.Adobe Premiere Pro version number: 24.2.1 Build 2Operating system - WindowsSystem Info: CPU, GPU, RAM, HD:CPU Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz 3.60 GHzGPU and Driver Version NVIDIA GeForce GTX 1080 Ti, Driver version 551.61RAM 64 GBHard Drive Internal SSD Video format: RED  R3D Raw File. Red R3D Details: Camera Firmware Version: 7.4.1Camera Sensor: DRAGON-X 6K S35; Minimum Color Version: 2; Resolution: 5568x3132; FrameRate Num: 24000. Sample file is also attached.Workflow details: Sequence settings are 5568 x3132, 23:976, Color Space Rec 709.  Importing R3D Raw files directly from copies of camera media. Local copy was made using Shotput.  Imported via Media Browser.  Project started out on LucidLink Cloud Storage and was then Collected and Copied to local interal SDD at conclusion of contract. Ste

I have been having an issue with my new 4060 GPU laptop where quicktime previews are NOT rendering at all. They will maybe start rendering then fail and without an error mesage, just randomly stop, this happens all the time across many timelines.The adobe agent said 'Something in your system doesnt like quicktime, render in IMPEG instead' and thats obviously less than ideal. Anyone have any ideas or solutions on this?

I have mac mini m1 with 16 GB memory Running premeire pro before sonoma was fine , after the update it takes huge memory  and lags very irreverently.even simply dragging mosue cursor slows everything. even just working in 1080p timeline, forget about 4k.its really really slow, lagging very frustating way.Please resolve, Thanks

Somtimes I'm hunting for a word, but if I don't clear out the text panel, Premiere will continue hunting for words (and auto-scrolling) as I'm trying to edit in the timeline. I like auto-scrolling when I'm searching, so I don't want to disable it every time I want to edit and forget to delete the contents of the seach box.

Everything and everyone says this setting is only supposed to be for Graphics, however changing the value then changes the video levels in my monitor, on the scopes, and on my Blackmagic Decklink output. https://youtu.be/meafmMwLAZg Here is an example video, I spoke with Matt Christensen in the Adobe booth at NAB and he indicated this should not be happening. This is my video proof. Is there some setting or something i need to change that is causing this? thanks 

I had projects with ,avi files with alpha channels that worked file. Since the last update os Premiere when I open these projects, the video layers with the avi files do not load, If I hide those layers, they will not render. To get them to render I need to remove the file.I am currrently using 24.3.0 Build 59This worked before I updated to this versionTo reproduce made an avi file with an alpha channel in after effects and try and import it into Premiere.The expected result is that it would work.This worked as expected for over a year until I updated remiere and After Effects.Can you fix this please?

I believe I remember a time when Adobe Premiere Pro was more efficient when closing the program. Some time this year, when I started using Adobe Premiere pro, I was satisfied with performance. To be fair, I have the Microsoft Surface Laptop Studio 2 with the RTX 4050 and the i7 13700H, so it handles everything I throw at it. It is also more powerful than the M2 Mac that a sibling Of mine owns. There is one annoying problem, however... and it is what happens when you close the program. It takes a good 2-3 seconds to close... which is a bit strange in my opinion since it has never done that. I do have my GPU selected in preferences for processing, edits, and what not, I also have Play-back at full res which has never caused an issue, and it has yet too, which is why I am puzzled as to why it takes a good 2–3 seconds to close.  As for booting the program, I don't have too many complaints, though I wish it were a bit faster. For a laptop of my specs, it takes 8–10 seconds to

Hallo.Beim Start von Premiere nervt mich seit einer Ewigkeit, dass trotz abgespeichertem Workspace dieser bei jedem Start "zerstört" wird und sich auch über den Aufruf aus dem Menü, unter dem gespeicherten Namen, nicht korrekt wiederherstellen lässt.Da ich nicht über Monate an einem großen Projekt arbeite, sondern jeden Tag 10-20 Projekte öffne, passe ich diese Fenstergrößen täglich mehrmals an. Egal wie oft ich den Workspace nach korrekter Einrichtung neu abspeichere oder meinen zuletzt gespeicherten Workspace überschreibe, Premiere schafft es nicht, diese Einstellungen wiederherzustellen. In Zeiten, wo jeder User unterschiedliche Display-Auflösungen hat, geschweige ein denn über mehrere Monitore oder in meinem Fall über einen sehr breiten Monitor gestrecktes Display nutzt, sollte das doch funktionieren. Kann mir hier jemand eine Lösung nennen, oder muss ich darauf hoffen, dass Adobe dieses vermutlich recht einfach zu lösende Problem irgendwann doch mal in einem Update beseitigt? &#12

When I'm editing and using a second monitor as a full screen preview through Transmit Device Playback, Premiere's dialogue boxes should not appear on the monitor using Transmit. This has been a problem for years requiring me to force quit Premiere when I can't use keyboard cues like "Enter" or "Esc" to close the hidden box.