Skip to main content

Filter by idea status

10000+ Ideas

AaronPWheeler
AaronPWheelerParticipant

Smart SequencesOpen for Voting

Suggesting a new feature called Smart Sequence! Similar to the Smart Bins feature, this Smart Sequence function will create a new sequence, automatically pulling clips into the timeline that meet the criteria defined by the user, similar to Smart Bins or Search Functions.  This seqeunce will not be editable, as it is dynamically created based on clip metadata. It will be used as a scrubbable reference for footage, rather than a scrollable list view when using Smart Bins. Once a Smart Sequence is created, there would be an option to convert the Smart Sequence to an Editable Sequence, similar to generating Static / Dynamic Transcripts. This feature will make creating footage stringouts simpiler, as well as automatically updating pre-exisiting stringouts with additionally ingested footage.  Because it is a dynamically created sequence, there would be view options to better display media in the Smart Sequence, sorting footage by metadata, ascending or descending. You could even add a pre-determined gap between footage that has previous been displayed in the Smart Sequence, seperating it from newly added media. (Example: A Smart Sequence is created, displaying 3 clips. Then, 2 more clips are ingested into the project, matching the Smart Sequence criteria. These 2 clips will then be added to the Smart Sequence, with a gap of say 2secs between them and the previous 3 clips.) This funtion would solve a potential issue of media being ingested into a project, but without it being imported into a footage stringout sequence. Overall, this function will essentially be a Smart Bin, but for Sequences instead. Great for editors who prefer to work in sequences rather than bins to pull footage.

Request for Full MTS/AVCHD (AC-3) Support in Adobe Premiere Pro 2025Open for Voting

 Dear Adobe Premiere Pro Team,I am writing to express my concern regarding the handling of MTS/AVCHD files in Adobe Premiere Pro 2025. While these files worked flawlessly in previous versions such as Premiere Pro 2022, the 2025 release appears to have introduced serious compatibility issues.The main problems that many users, including myself, are experiencing are:No audio playback due to the missing AC-3 (Dolby Digital) codec.Distorted or noisy audio when MTS files are imported.Audio/video sync issues that were not present in earlier versions.In some cases, the files fail to import at all, even though they are industry-standard AVCHD recordings.MTS/AVCHD remains a widely used recording format for professional and semi-professional camcorders. Many editors have extensive archives in this format, and being unable to work with these files in the latest version of Premiere Pro disrupts workflows and forces us to downgrade or use third-party conversion tools.We kindly ask Adobe to:Restore full AC-3 audio decoding support in Premiere Pro 2025 (or provide an official codec solution).Fix the import and sync issues affecting MTS/AVCHD files.Ensure future updates maintain backward compatibility for legacy but still widely used media formats.Adobe Premiere Pro has always been known as a professional solution that supports a wide variety of formats. Addressing this issue will greatly improve user confidence and maintain the software’s reputation as an industry leader.Thank you for your time and consideration. I hope this matter can be resolved in an upcoming update.Sincerely,Firat

Comments on things that Break your Creative Flow in Premier, and suggestions.Open for Voting

Premier really needs to add a few things to level up its performance and avoid breaking the creative flow.1) When running warp stabilize, there are so many ways for the process to be stopped, such as doing a render and replace, that seems to stop any active warp stabilize - I dont normaly do Warp stabilize, but I have a 50 min video recorded with a gimbal that was slighty not as nice as I wanted, and it had some sharp direction changes, so I found a quyick test setting that allowed me to take the  sharp gimbal movement I wanted, with only a 5% zoom which was good enough for this project.  However there are 104 clips in the 50 min and every one needed this treatment.  You cant actualy start them all as this crashes the system I can to do about 3 or 4 at a time and pace myself.When you are running a warp stabilize and render and replace, the warp stabilize stops, no notification it stopped eitherWay in the world can we not have render and replace as a media encoder process so I can continue to edit.  Every modern machine has plenty of power to do this.  consuming premier as a forground task for render and replace is silly.There should be a que system for warp stabilize and probably a ton of other things, have them all qued up, and the user can decide how many the system is allowed to do at the same time, show which ones are done.  Also, if you use media encoder for this, PLEASE do not only allow one task to run at a time,  something like a warp stabilze can run while a  render and replace can run, also allow me to chain commands,  like after a warp stabilize, render and replace.The warp stabilize data needs to come out of the main project file.  use a concept like you are using for media intellegence and create a seperate warp stabilize file outside the main project file, because if you have 50 min of warp stabilize data in the project it takes a VERY long time to save the file, load the file, and when loaded, it takes a huge amoung of time before you can start working after the file 'appears to be loaded'.  Not to mention,  the warp data seems very sensative, and can be lost under some circumstances within the project, and it would be nice to protect that data, and if you use the clip in other projects, have that data available without processing it again.Clips with Warp stabilze applied really need to have have an indicator on them (small shaky hand icon thats green, red or yellow - so we know whats going on when we are in the timeline, without having to click on the clip to load the effects panel, and look at the effects status for each clip.Render and replaced clips also need so some sort of visual indicator also, like the proxy indicator, currently they add the _rendered text the clip name but that is only visable when you are zoomed in enough the read the clip name not actualy usefull when scanning a moderetly sized project, and it also doesnt follow the same design langauge as a proxt is kind of like a render and replace, and it has a nice icon to know.  I'm sure there are lots of other things, this happens to be on mind mine because I'm active in a project that these things are haunting me.  

AlissaBaoParticipant

Compilation errors in Premiere Pro point to the wrong file instead of the real cause (Motion GraphicOpen for Voting

Dear Adobe Team,I would like to share some feedback based on a recurring experience in Adobe Premiere Pro that may be useful for your development team.I often work on long-form videos (over 1 hour) and frequently use many Motion Graphic Templates (.mogrt) to add subtitles and callouts throughout the timeline. Recently, I faced multiple export errors such as:"Error compiling movie""Error in accelerated rendering""Error retrieving frame"The error reports consistently pointed to the original video files (MP4) or even to the H.264 export module as the source of the problem. However, after many hours of troubleshooting, I discovered that the real issue was specifically related to the Motion Graphic Templates placed on the upper video tracks (e.g., V2).Once I removed these graphics temporarily, the project exported smoothly and much faster. This confirmed that the problem was not with the video files themselves, but with the rendering of the MOGRTs.ImpactThis behavior leads editors to spend countless hours chasing solutions in the wrong direction, such as:Re-exporting the source video files.Transcoding with external tools.Cutting sections of the timeline.Changing export settings repeatedly without success.In other words: we follow misleading error messages, and only after significant wasted time we discover that the actual problem is with the graphic templates.SuggestionIt would be extremely valuable if Premiere Pro/Adobe Media Encoder could:More clearly identify when the error is related to a Motion Graphic Template (MOGRT).Provide logs or error messages such as: "Rendering error in Motion Graphics Template (Track V2 – Template Name)".Suggest to the user to apply Render and Replace or export an intermediate file to avoid failures during final render.ConclusionPremiere Pro is a powerful tool, but improving the accuracy of error messages would save professionals a great deal of time and frustration when working under heavy production workflows.I hope this feedback helps improve the experience for all users.Sincerely,Alex