Bug Reports

Hello there, we are working on a big project for tv where we use alot of bodycams. We used GoPros/GoPro 360 models before and now we added some insta360 x5 models, because the processing of the GoPro360 files into "High Quality" mov files takes up alot of storage and time.The insta360 ".insv" files are supposed to be importable and editable in Premiere with their Premiere Plugin "Insta360 Reframe - Plugin for Adobe Premiere" (https://www.insta360.com/de/download/insta360-x5)Also shown in this video for instance:https://youtu.be/yDod5TlK7zQ?si=pV7Ybj04D5Noup3C&t=240 Whenever I try to import the .insv files into Premiere i get the Error "A low-level exception occurred in: Insta360Importer (importer:47)" (also shown in the screenshot i uploaded here). I've been in contact with the insta360 Support Team for over a month now and we could not resolve the issue.This is kind of a big Problem because there is already a lot of footage filmed with these cameras and our post pro

1. The anchor point itself changes the direction 2 When the full screen is turned on, the program freezes or the computer turns off, when the project is opened, a window with a font error will appear but fonts are installed in the system. 3.In the sound panel, when I make a remix track, when playing sound, panenl rendering constantly appears, in the sound panel I can make the length of the track only 10-15 seconds, then the mouse cursor does not move 4. When turning on the iconView, the program begins to slow down and the icons are blinking https://www.youtube.com/watch?v=51pb5zK2hdY&feature=youtu.be   The problem from version 25.1 and above. Reinstalling the program, reinstalled Windows, changed the mouse, setup default settings Windows 11 Pro 64-bit Intel Core i7-14700K MAG Z790 TOMAHAWK MAX WIFI (MS-7E25) NVIDIA GeForce RTX 3060 Ti Samsung SSD 990 PRO 1TB (SSD)   All drivers are updated, even for the monitor. For example Nvidia Driver Studio

Hello, I am trying to export a 50min project, with a lot of edits and adjusment layers.I can not export. I have been trying since 2 days using Media Encoder, and my MacBook Pro Late 2023 restarts and freezes. Sometimes there is a tab who says: Run out of application memory and completely my mac is blocked. I never had this issue and I would really appreciate some help. I tried deleting the mac temp files, media encoder cache as well as premiere cache

Hi,Does selecting text really have to be that annoying? It requires pixel perfect precision, otherwise it's extremely unforgiving. With words it would take too long to explain, but I made a screenshot video, please take a look.Windows 11. Extremely easy to replicate - just try to actually edit the captions once, and you will instantly realise. Note: I am reporting a bug, but not planning to engage in any discussions: once the bug is reported (by posting this post), I'm not gonna return to this forum thread anymore. I shall do my editing, and tech support shall do their fixing. I believe enough information was posted (if the screenshot video can be viewed successfully), and further discussions will provide nothing culturally enriching. Respectfully,GJ

Hi everyone. I've been having an issue with Premiere Pro for a few weeks now, and it's driving me crazy. Every time I click on the "Sequence" > "Sequence Settings" menu, Premiere crashes for no reason, simply displays an error screen and closes. I've already contacted Adobe support, and nothing has been resolved. I'm using a MacBook Pro m4 Max 36GB 1TB, so the problem isn't with the machine itself. I have all the programs updated and original. I've tried reinstalling, deleting caches, restarting the computer, and cleaning with CleanMyMac, but nothing works. The program keeps closing every time I click on the sequence settings menu. Is anyone else experiencing this or something similar?

If a clip has been warp stabilized, the user can't get the 'Auto' button in Lumetri Color to work UNLESS the Lumetri Color effect is dragged ABOVE the Warp Stabilizer effect in the Effect Controls window first.  This bug is present in versions 25.3 and 25.4 (running on a Mac with MacOS 15).  In the past, this bug didn't exist.  It was introduced sometime in version 25.  This bug is extremely annoying.  Please fix it!

Creating a New Thread for User @clkn Description: We are a professional film production and have encountered a critical bug in Adobe Premiere Pro that has completely disrupted our project and caused unpredictable issues.   Problem: After restarting the program, numerous audio files that were previously synced using Tentacle Sync and functioning correctly suddenly went OFFSET.. This leads to the following issues: 1.The audio tracks are no longer in sync – neither in the master sequences nor in the edit sequences. 2.The original sync map also becomes entirely faulty. Adobe Premiere Pro version number: 25.1 Operating system - Mac OS 14.6.1 (23G93) System Info: CPU, GPU, RAM, HD: Apple M3 Max 64 GB RAM 32 GB G-Raid  Video format: 4k, ProRes 422LT, 50fps Steps to reproduce:  This issue arises within the sync map sequence containing the footage synced via Tentacle. 2.In the sync map, a cut is made and that section is used in a diffe

Buenas..premier 2025 no me deja exportar con audio.si silencio el canal de audios; exporta normalmente.he intentado varias opciones; cambiar el formato. cambiar la entrada, bits.. todo lo que se pueda.y no me deja exportar.en cualquier version del premiere 2025.he tenido que volver al premiere 2024 para poder trabajar.

EnvironmentLaptop: Dell XPS 16 9640 (Intel Arc + NVIDIA RTX 4060 Laptop)OS: Windows 11 Version 10.0.26100 (Build 26100)Premiere Pro: 25.4.0 – Build 99Display setup: external monitor via USB-C hub → HDMI (reproduced with two different hubs; sometimes OK with a different hub or when only the monitor is attached)Audio in Premiere: MME, Default Output = Speakers (built-in), Default Input = No Input, 48 kHz IssuePremiere becomes unresponsive (preview freezes, UI lags; requires hard power-off) when Windows detects/activates the monitor’s audio endpoint (“HD Audio for Display Audio”) or after a USB/Display re-enumeration, only when launching/using Premiere on the external monitor. On the laptop’s internal screen, it’s OK. Most reliable reproductionCold boot with external monitor connected via USB-C hub (sometimes also another 5V USB device like a cooling pad on the same hub).Sign in and launch Premiere Pro.Start playback in the timeline → Premiere freezes. (Often coincides

So I started a project yesterday. Everything was fine until I added adjustment layer by creating item like I usually do. But it soon got laggy when I tried to drag it into the timeline. The timeline was freezed and couldnt be moved although the playback was fine and still very ok. I have checked my CPU and also GPU temp or their usage percents but everything was completely normal. However, the thing is that the adjustment layer from my previous project is fine, it doesn't have the situation like that.

I use enable transmit to get as full screen preview on my second monitor. Sometimes if Premiere needs to launch a dialogue box, like to import footage or relink media, it will pop up BEHIND the full screen preview. I then can't exit out of it because I can't see it, and Premiere is totally bricked. The ONLY thing to do is go into Task Manager and end task, losing work and having to restart Premiere. How is this still an issue in 2025????

"viewer gamma" settings dont act the same wether a clip color space is unchanged or not   Adobe Premiere Pro version number: 25.1.0 (build 73) Operating system : macOS sequoia 15.3.1 System Info: Apple M2 MacBook air 3,5 GHz apple GPU 10 16Go DDR5 RAM Hard Drive 1To Video format: any image media Workflow details: any project, any sequence Steps to reproduce - (Very important!) I'm french so excuse my english please. Place any image media clip with rec709 2.4 profile (video, png, jpg...) on a timeline (any settings) select the clipIn the lumetri color settings panel :Display color management is on working color space : rec709   Set the "source clip" section on "use media color space" (so rec709) "viewer gamma" on 2.4   export the clip as an h264 file (any settings) this is FILE 1Achange "viewer gamma" to 1.96then Image should look different inside Premiere's program monitorexport the clip as an h264 file (any settings) this is FILE 1BNow Set the "sou

Hi, my name is Haris Ahmed, and I’ve been working in video editing, animation, and graphic design for the past 2 years. Recently, after switching to Premiere Pro 2025, I started facing a major issue. Whenever I try to export a long project with hardware encoding, the export fails and gives an error every time. If I switch to software encoding, the export works, but it takes a lot of extra time, which slows down my workflow. I’m using a system with an 8GB dedicated GPU, so hardware encoding should normally work without a problem.As you can also see from the image I posted, my projects are usually long and heavy, so this issue is making the workflow very difficult. I’ve already tried multiple solutions and troubleshooting methods, but the problem is still there. Can anyone guide me on how to fix this, or let me know if this is a known issue in the 2025 version? Any help would be greatly appreciated.

I have Premiere Pro on 3 computes, 2 Macs and a Windows 10. Always keep software and OS up to date on all of them. For a couple of years now, I keep encountering an issue where the max output volume is always -3db until I add another "Volume" after it to bump it up to 0db, or use the audio track mixer to compensate. It's every effect, both stock and third-party. EQs, compressor, distortion, limiter, etc. Haven't been too annoying of a problem, until recently where I have to repeate the process of adding the "Volume" effect to compensate a lot in a short amount of time. I've tried making it a preset, but it doesn't add the 2nd "Volume" at the end of the effects chain, and adjusts my settings to the first "Volume" in the chain.I've looked periodically, and it seems like no one else has talked about this problem.I would prefer not to reset preferences and go directly to whatever's causing this, if possible.Any advice would be appricated.

This one keeps me buggin for quite a while now. Whenever you work with media that doesn't match the sequence framerate, the info panel will always show the sequence frame rate for selected media rather than the media's frame rate. This is incredibly annoying because you need to verify the media framerate by revealing it in the project panel every time. After doing so the info also switches to reflect the actual source media's framerate. But back to sequence framerate whenever that panel is active.   Media info as shown from Sequence (false info):   Media info as shown from Project (correct info):  

I am an editor on an animated series working remotely with one other editor using Lucidlink. All our assets and project files are stored on Lucidlink.I have been converting our edit projects to use Productions, so I can spread out our assets to various projects instead of having every asset in one bloated project per episode. It was working great until the Productions panel stopped responding to the changes I would make, like create a project/ folder, or rename a project/folder.The only way to get the Productions panel to refresh is to completely restart the Production which sometimes means closing my projects.  How do I fix this? Beyond this really disruptive and annoying bug, the system works perfectly. I saw another post from Marjorie Sacks that is supposedly the correct answer to this question but it only seems to apply to local servers (and to teams with resources like an IT department lol)https://community.adobe.com/t5/premiere-pro-discussions/production-panel

When dragging a timeline into a destination timeline, I see a preview of the clips in the timeline UI, but it never actually completes the operation and adds the clips to the timeline.  Scrubbing through the timeline, there is no video from the ghost clips.  Trying to click on or interact with them doesn't work.  Here's a screen recording of the issue:  https://youtu.be/7KVmIZiTfsQ Expected behavior:  the destination timeline should have the dragged content in it. Windows 11.  Premiere 25.3.0  (was happening on previous version, I think it was 25.2.0, but updated to see if that effected it but no change.)The screen capture is done with a Teams project.  Tried publishing.  Tried exporting as a local project and opening that and it had the same issue.  So it's not specific to teams or publishing.  Tried making a simple test case and if I make a new timeline with a handful of clips for testing,  I can not replicate

On Mac M1 machine (SEQUOIA 15.6) Steps to Reproduce:a. Updated Premiere pro version to: 25.4.0 (Build 99)b. Opened a Team projectc. Selected all media, right click and selected "Link Media" OR "Proxy-->Reconnect full resolution media"d. Selected a file and located it in a folder on SSD Expected result: All media should be automatically linked. Actual results: One few files got linked automatically, and a bunch didnt. No other option other than linking them manually.  Refer attached video for details

Hello Team!We have a 42, stereo track sequence in Premiere 2024. Audio clips all have Parametric EQ and volume keyframing applied on a clip level. We exported an AAF (embedded or otherwise) broken out to mono with effects rendered.The resulting AAF when brought into Pro Tools or even back into Premiere has all the volume keyframing in the wrong place. I've attached a screenshot. On the left is the AAF, broken out to mono and with 'include un-rendered clips' checked. On the right is the Premiere project.You can see the keyframes are completely off on the rendered clips in the AAF.We have tried every possible combination of AAF and the only thing that works is not to render the effects. When we do that, the volume keyframing is fine.Any idea why this is happening with this project?

I’m having a serious issue with Adobe Premiere Pro after upgrading my GPU.My setup:MSI B450 Pro motherboardRyzen 7 5800XT processor64GB DDR4 RAM1TB NVMe SSDPreviously using an RTX 2060 Super (everything worked fine)I recently upgraded to an RTX 5060 to stay up to date and improve my workflow. Unfortunately, it’s been the worst decision so far. Since switching GPUs, Premiere Pro has become almost unusable: I experience playback issues, dropped frames, export problems, and even playing a simple 4K iPhone video has turned into a nightmare.Things I have already tried (please don’t suggest these again):Complete reinstall of Adobe Premiere ProClearing cacheUpdating driversMaking sure Premiere Pro is set to use the GPU in the NVIDIA Control PanelSystem restart / power cycleAt this point, it feels like Premiere Pro and the RTX 5060 are simply incompatible.

Product: Premiere ProVersion: 25.4.0 (Build 99)OS: Windows 11 proBug Description:In Premiere Pro 25.4.0 Build 99, the playhead can no longer be moved by seconds.“Go to Time” command is missing from the Sequence menu and Help search.Typing a timecode in the Program Monitor (e.g. 15. to jump 15 seconds) resets the playhead to 0 instead of moving to the correct time.Keyboard shortcuts for Step Forward 1 Second and Step Backward 1 Second do not work as intended; they still move the playhead by frames, not seconds.“Display Format” options for the timeline (timecode vs frames) are no longer present in Sequence Settings.Expected Behavior:Ability to move the playhead by seconds using numeric entry or shortcuts.Proper recognition of timecode input (HH:MM:SS:FF).Restored access to “Go to Time” or equivalent functionality.Steps to Reproduce:Create a new sequence in 25.4.0 Build 99.Attempt to use “Go to Time” (command is missing).Click Program Monitor time display and type 15. → playhead rese

I’ve run several tests sending LTC timecode to my Zoom H5 audio recorder using Deity timecode generators (TC-1). I’ve tested a variety of setups: sending timecode to a single input while recording separate audio to another, and recording stereo files with LTC on the left channel and clean audio on the right.Regardless of the setup, when I import the WAV audio file into Premiere Pro, convert the LTC timecode, and sync it with other cameras that also used LTC, the WAV file is always 30 to 50 frames out of sync. I’ve followed all the proper steps—right-click, Modify > Timecode > Audio LTC—but the result is consistently inaccurate across multiple files and devices, including my Zoom H6.However, when I import the same files into Deity’s Timecode Toolkit to decode the LTC, then bring the decoded file into Premiere and sync by timecode, everything works perfectly. This clearly indicates that the issue lies within Premiere’s handling of LTC from WAV files.This seems to be a bug in Premie

I'm facing severe lag with playback and of course, dropped frames! This is not the first time this has happened, usually every 2-3 updates this problem occurs and I have deadlines just like many other people do! To give you a brief, my hardware:- 64GB RAM- RTX 4070- AMD Ryzen 9 processor- Windows 11 64bit- 4k Monitor- Changing audio hardware input to all options available- Working off a 5th generation 2TB SSD I'm using NRAW raw files transcribed using REDCINE X PRO since adobe still doesn't support Nikon raw files. they are 12 bit. I have already tried the following:1- Changing audio hardware to no input.2- Changing codecs (all of them)3- Playback quaity (all of them)4- deleted media cache files5- reinstalled studio driver (and rolled back to previous versions) NOTHING IS WORKING!! someone please help! 

A transcrição não corresponde ao video da timeline após eu ter duplicado a timeline e trocado o vídeo anterior na nova timeline, o video novo, ou trecho de vídeo, já tem transcrição criada mas não aparece no visor da transcrição então não consegui criar legendas novas, tá me deixando muito insatisfeito, só funciona e volta ao normal se fechar o programa ou criar a transcrianção estático e voltar pra de edição depois, o que é muito chato de ficar fazendo e nem sempre funciona!

my 4k video is not rendering properly.. and premier pro stopped automatically