Skip to main content

Filter by idea status

10000+ Ideas

Kanye YuskiParticipant

Feature Request: Locking Specific Clips to Absolute Timeline PositionsOpen for Voting

Dear Premiere Pro Development Team,I am a video editor specializing in commercials and music videos, and I use Premiere Pro daily. I am writing to propose a new feature: "Absolute Clip Lock" (the ability to lock selected clips to a specific point on the timeline).The Problem: Currently, when editing commercials (e.g., a 30-second spot), specific elements like the Brand Visual Identity (VI) at the final 2 seconds must remain fixed. Similarly, in music videos, certain shots must align perfectly with specific beats. However, when trimming or ripple-editing adjacent clips, these "fixed" shots often shift. Constantly double-checking their alignment is a significant source of stress and slows down the creative process.The Solution: I request a feature that allows users to lock an individual clip (or multiple selected clips) to its absolute position on the timeline. •Unlike the current Track Lock, this would only affect the specific clip, allowing other clips on the same track to be edited freely.•This would be invaluable not only for CM and MV editors but also for TV editors who need to lock commercial break timings to specific timestamps. Additional Suggestion: It would also be incredibly helpful to have a "Solo" button for individual clips, allowing us to isolate a specific clip’s audio/video without muting entire tracks.Thank you for your hard work and for considering these ideas to make Premiere Pro even more powerful for professional editors.Best regards,   

P: Different style of cursor for Masking/HealingOpen for Voting

Hi, here's what I think after some months using the app on a Pixel 8 Pro phone and a Samsung a9+ tablet.    I have some issues with the UI   Let me see what I'm doing:   For ALL drawing operations - brush mask, heal, clone, etc. - give us something that looks like a dodging tool or a brush: an easily grasped handle at one end and an actual representation of the brush size, feathering , and opacity at the other, and enough distance between them so that we can see what we're doing.      OR   Allow much more zooming in, so that the area I'm working on is much bigger than my fingertip.       (The current mode of trying to do this with the affected area HIDDEN by the fingertip is awf       Make it easier to grab the handles:       Disable context menus and actions when handles are visible and the fingers are touching *anywhere* near them.  (Example: when moving/rotating/shaping a radial mask.)         Since I'm clearly trying to use the handles:  Make it easier to grab the handle!        Don't show me the original image if I touch the screen "too long".  There's nearly zero chance the I want that.       Don't show me the context menu when I'm trying to move the mask. I can get that from the right side of the screen, it's just in the way when I'm touching the mask itself.       Don't flip something back to it's default position based on your interpretation of how I'm touching near it. I already moved it  away from the default, there is pretty much zero chance I want it back there. Make it easier to grab the handle and I' ll put it where I want it.            Thank you.      

Improvements to the Film Impact EffectsOpen for Voting

This is something that's always been the case with the Film Impact effects, but now that they're the defualt effects it's a glaring issue - effects like Blurs, and Mossaics are capped at arbitrary values that make specific looks and effects impossible to achieve. For instance:- Gaussian Blur is capped at 100. Most of the time, I'm using Gausian blur at much higher values, typically closer to 500. It should be capped at the same limit as the original effect 30000.0. I never use it at that value, but it should still be an option. I'm aware the original is still available but that's still stupid that the legacy version is better than the replacement - the only benefit the new versions offer is built in chromatic abberation. This applies to all blurs, not just Gaussian Blur.- Mosaic is capped at 200, which is terrible. Not only that, but it's locked to uniform scaling rather than individual axis like the original effect. A lot of the time when I use mosaic, I use it to create a slight pixelation effect where items are still legible in which case I might not want a uniform scale, or in other cases I'm keyframing it so it mosiacs out to reveal an unblured image, which requires the pixel count to be identical to the resolution which isn't possible when it's capped at 200. Granted, this effect offers a lot of benefits to the original mosaic effect, but it's still not something I can use practically because of this arbitrary cap

Liwinmac
LiwinmacParticipant

Speed Ramping in 2026: Premiere Pro Is Falling BehindOpen for Voting

Speed ramping is now a basic requirement in professional video editing. In 2026, editors expect to create smooth, cinematic speed changes quickly and intuitively. DaVinci Resolve and Final Cut Pro meet this expectation. Adobe Premiere Pro does not.Final Cut Pro makes speed ramping straightforward and fast. Speed changes are visible directly on the clip, easing is handled automatically, and results are smooth with minimal effort. The workflow is designed for speed and consistency.DaVinci Resolve offers an equally modern experience. Its speed curve editor gives editors full visual control over motion, allowing precise shaping of ramps without unnecessary steps. The system feels current, efficient, and purpose-built for modern footage like drone and gimbal shots.Premiere Pro, on the other hand, still relies on an outdated time remapping workflow. Editors must dig through menus, split keyframes manually, and carefully adjust small handles just to achieve basic results. Even after all that, motion often feels stiff without extra tweaking.For professionals working under deadlines, this is more than an inconvenience — it’s a workflow problem. Many editors now leave Premiere entirely or use Resolve or Final Cut specifically for speed ramps.The frustration isn’t about missing features. It’s about missing modern design. In 2026, speed ramping should be visual, intuitive, and fast. Resolve and Final Cut prove this is possible. Premiere Pro’s approach feels stuck in the past — and that gap is becoming harder to ignore.

Feature Request: Performance Diagnostics PanelOpen for Voting

Quick Preface:Sorry for dumping a quick AI written feature request. I'm currently mid project and I wanted to quickly get this up before I forget, but after realizing that premiere's console feature is so robust at isolating and identifying bottlenecks, I at a loss for why they don't just translate this information for less technically inclined individuals. Of course, a lot of these issues are true RTFM or "let me google that for you" type things, but realistically it would be way easier if they were to cut out the middle man and just identify your bottlenecks and recommend solutions / link to help or FAQ threads.SummaryPremiere Pro should include a user-facing "Performance" or "Bottleneck" panel that surfaces the diagnostic information the application already collects internally. This would help users identify what's causing timeline slowdowns without needing to dig through debug logs or guess at solutions.The ProblemPremiere Pro already tracks detailed performance metrics internally:Async source timeouts (with specific file names and frame numbers)Frames dropped during playbackPreroll and prefetch timesRender times per frameCodec decode issuesGPU acceleration failuresVFR detectionProxy/source mismatches This information is logged to debug consoles and log files that most users don't know exist, can't easily interpret, and aren't designed for troubleshooting. Meanwhile, users experience sluggish timelines and have no insight into why—leading to hours of trial-and-error troubleshooting, forum searches, and frustration.The application knows exactly what's causing the slowdown. It just doesn't tell the user.Suggested SolutionAdd a "Performance" panel (Window > Performance) that displays real-time and historical diagnostics in plain language:Real-time indicators:Current playback status (smooth / dropping frames / buffering)Which clip or effect is causing delaysWhether the bottleneck is CPU decode, GPU render, disk I/O, or RAMIssue detection with recommendations:"Variable Frame Rate detected in [clip]. This may cause proxy sync issues. [Learn more] [Conform to CFR]""Async decode timeout on [clip]. Consider transcoding to an edit-friendly codec or creating proxies.""GPU acceleration unavailable for [effect]. Rendering on CPU.""Disk read speed insufficient for [resolution/codec]. Media is on [drive type]."Session log:Scrolling list of performance events during the sessionFilterable by severity (info / warning / error)Clickable entries that navigate to the problem clip in the timelineWhy This Matters:Users shouldn't need to enable debug consoles and parse log files to understand why their edit is lagging. When Premiere detects a problem—and it does detect these problems—that information should be accessible in a way that helps users take action.This is especially important as source media becomes more varied. Content from smartphones, screen recordings, streaming rips, and consumer cameras often uses codecs and frame rate modes that aren't ideal for editing. Users working with this footage deserve to understand what's happening rather than assuming their hardware is inadequate or that Premiere is simply "slow."Surfacing existing diagnostic data in a user-friendly way would significantly improve the editing experience and reduce support burden.EnvironmentPremiere Pro 2025Windows 11Issue encountered while troubleshooting VFR HEVC footage with proxy workflow