Skip to main content

Filter by idea status

10000+ Ideas

Serj Shtefan
Serj ShtefanParticipant

Native FFT (Fast Fourier Transform) Filter for Pattern, Texture, and Moiré RemovalOpen for Voting

I am writing to address a critical, long-standing gap in Lightroom’s toolset that has remained unresolved for decades: the lack of a native FFT (Fast Fourier Transform) filter.As a photo restorer and long-time Creative Cloud user, I frequently work with archives where physical paper textures—such as "silk," "honeycomb," or linen finishes—create repetitive patterns that severely degrade scan quality. While Lightroom has made incredible leaps with AI-powered Denoise and Generative Remove, these tools still struggle to distinguish between high-frequency noise and the structural, mathematical patterns of paper textures and digital moiré.The Problem: Currently, to remove periodic patterns or heavy moiré interference, we are forced to export files to Photoshop and rely on outdated, third-party 8-bit plugins or complex manual workflows. The current "Moiré" slider in Lightroom is often insufficient for deep texture patterns and lacks the precision that an FFT-based frequency domain approach provides. This breaks the non-destructive RAW workflow that is the core of the Lightroom experience.The Solution: In an era of "Neural Filters," a mathematical FFT implementation is long overdue. Integrating a "Pattern Suppression" tool based on FFT directly into the Masking or Detail panel would: Allow restorers to neutralize paper textures and complex moiré without losing essential image details or sharpness. Maintain a fully non-destructive workflow for high-volume archiving and professional retouching. Finally solve a problem that the community has been requesting for over 20 years. We don't just need more generative features; we need professional, fundamental tools that handle the reality of physical photo restoration. It is time to listen to the restoration community that has been waiting for this since the early versions of Lightroom.Please consider making FFT a native part of the Lightroom ecosystem.

narisanKnown Participant

Feature Request / Feedback: Mask Editing Behavior in Premiere ProOpen for Voting

I would like to request improvements to the mask editing behavior in Premiere Pro.Currently, when editing a mask, double-clicking allows entering a mode where individual vertices can be adjusted, and keyframes can be added to the mask path. However, in this state, if I drag the entire mask to reposition it, the movement is applied as a “Transform (Position)” change instead of updating the mask path itself.This leads to the following issues:If there is a previous keyframe far back in time, the position animation starts interpolating from that earlier frame Movements that should be treated as mask path adjustments are instead treated as position changes This often results in unintended and difficult-to-control animationsIf I am in mask path editing mode, I believe moving the mask should be recorded as mask path keyframes, not as transform position changes.Additionally, the system should take into account the previous mask path state, including any vertex adjustments, position, and scale changes.I understand that this behavior may be influenced by After Effects. However, for more complex animations, After Effects is a much more efficient tool. Premiere Pro should prioritize intuitive and straightforward editing workflows.Personally, I am currently using both the latest and previous versions in parallel, but I know editors who have switched to other editing software due to these kinds of changes.Also, the recent change that fixes zoom behavior to the mouse wheel has significantly reduced usability for me.I would appreciate an option to customize or toggle this behavior in the settings.

Return Navigational Arrows To The "Edit" section of the "Firefly Image 4" ModelOpen for Voting

Though Adobe Firefly has a long way to go, it’s “Firefly Image 4” model actually yields pretty decent results (if prompted correctly), so I use it often. Unlike the other models, it outputs four pics instead of just one. I would click on any of the four pics, and it would take me to the “Edit” page, where I could quickly navigate through those pics, using the navigational arrows that USED to be there.. However, at some point in Firefly’s update history, they decided that we didn’t need these navigational arrows.🤦🏽WTF, ADOBE - PUT THE NAVIGATIONAL ARROWS BACK. What tf is wrong with your UX team?? Which one of y’all decided that we no longer needed navigational arrows???? I am truly baffled. I honestly don’t understand how ANYBODY thought this was a good idea.  This might not seem like a big deal, but for me, it absolutely is, because “workflow” is important when I’m creating, and there is nothing more aggravating than software that INTERRUPTS my workflow, rather than aiding or enhancing it. Now, when I click on a pic, and it takes me to the “Edit” page, I have to go BACK to the “Generate” page JUST to select another picture. It’s MADDENING. WHY would you cripple the software like that?? in 2026?????? Folks are paying y’all WAY too much money for impractical SaaS. The UI could be better, but it’s sufficient. The UX, however, SUCKS - this is NOT how human beings actually work. 😠

Serj Shtefan
Serj ShtefanParticipant

P: Need for a Native FFT Filter to Combat Paper Texture and MoiréOpen for Voting

Native FFT (Fast Fourier Transform) Filter for Pattern, Texture, and Moiré RemovalI am writing to address a critical, long-standing gap in Lightroom’s toolset that has remained unresolved for decades: the lack of a native FFT (Fast Fourier Transform) filter.As a photo restorer and long-time Creative Cloud user, I frequently work with archives where physical paper textures—such as "silk," "honeycomb," or linen finishes—create repetitive patterns that severely degrade scan quality. While Lightroom has made incredible leaps with AI-powered Denoise and Generative Remove, these tools still struggle to distinguish between high-frequency noise and the structural, mathematical patterns of paper textures and digital moiré.The Problem: Currently, to remove periodic patterns or heavy moiré interference, we are forced to export files to Photoshop and rely on outdated, third-party 8-bit plugins or complex manual workflows. The current "Moiré" slider in Lightroom is often insufficient for deep texture patterns and lacks the precision that an FFT-based frequency domain approach provides. This breaks the non-destructive RAW workflow that is the core of the Lightroom experience.The Solution: In an era of "Neural Filters," a mathematical FFT implementation is long overdue. Integrating a "Pattern Suppression" tool based on FFT directly into the Masking or Detail panel would: Allow restorers to neutralize paper textures and complex moiré without losing essential image details or sharpness. Maintain a fully non-destructive workflow for high-volume archiving and professional retouching. Finally solve a problem that the community has been requesting for over 20 years. We don't just need more generative features; we need professional, fundamental tools that handle the reality of physical photo restoration. It is time to listen to the restoration community that has been waiting for this since the early versions of Lightroom.Please consider making FFT a native part of the Lightroom ecosystem.

Jruterh
JruterhParticipant

Granular Control for "Recent Files"Open for Voting

The current "Recent Files" implementation in Photoshop and Illustrator follows a rigid "all-or-nothing" logic. Professional users need the ability to curate this list to maintain a focused, clean, and secure workspace. This isn't just about privacy; it's about removing "workflow noise"—files opened for quick edits, assets used once, or outdated versions that clutter the dashboard and slow down navigation.The Problem: Currently, the "Recent Files" list is a chronological log rather than a managed workspace. This leads to several issues: Workflow Clutter: Opening a dozen small assets for a quick task pushes important, long-term projects off the list. Version Control Confusion: Multiple iterations of the same file appear as identical thumbnails, leading to accidental openings of the wrong version. Privacy & NDA Risks: In screen-sharing or over-the-shoulder client sessions, sensitive or unrelated projects are exposed with no way to hide them without wiping the entire history. Non-Relevant Assets: Assets opened via Bridge or Lightroom for a "round-trip" edit stay in the Recents list forever, even if they were only needed for a 30-second adjustment. Suggested Solutions: Selective "Remove from Recents": A simple right-click option on any thumbnail to remove it from the list immediately without deleting the source file or clearing the entire history. "Pin" Critical Projects: The ability to pin specific files to the top of the Recents list so they aren't pushed out by minor tasks. One-Click "Presentation Mode": A toggle to instantly blur or hide the Recents panel for screen-sharing or client meetings, maintaining professionalism without losing one's history. Auto-Filter by Type: Options to exclude specific file types (e.g., .PNGs or .SVGs) from appearing in Recents, keeping the list dedicated to main project files (.PSD/.AI). Benefit: Implementing these features would transform the Home Screen from a passive history log into a powerful, professional dashboard. It enhances user productivity by reducing visual clutter, improves security for professionals under NDA, and gives users the same level of control over their "Recent" list that they already have over their Layers and Assets.

_nicdean
Community Expert
_nicdeanCommunity Expert

Remove All Transitions: Feature RequestOpen for Voting

The Film Impact acquisition brings great video transitions to PPro. But working with them is clunky, as there is no way to remove multiple transitions at once.   Over the past 15+ years editors have used various workarounds which all have downsides.   Workarounds: 1. Change Speed/Duration of all your clips from 100% to a higher percentage (ex. 200%). Transitions are deleted. Problem: Ruins your sequence if you uniquely edited Speed/Duration for each clip 2. Simplify Sequence > Remove Transitions Problem: Creates a duplicate sequence instead of editing your current sequence 3. Select all the clips holding the Ctrl key so all edit points will be selected Press Ctrl+Shift+T to toggle trim type three times so that all out points will be marked in red Press Ctrl+left Arrow to Trim Backwards  once Press Ctrl+Right Arrow to Trim Forward once Problem: Unintuitive.   Solution: I propose 3 simple solutions. Do one, or do them all.   1. Allow Simplify Sequence to affect active sequence, without creating a duplicate sequence. Add a checkbox enabled by default for "Duplicate sequence". If user turns off checkbox, it affects active Sequence and does not dupe. 2. Add command in the right-click edit-point Context Menu for "Remove Transitions". This should delete all transitions at selected edit points. 3. Use the existing "Clear" command when user right-clicks on a transition. If user has multiple clips selected, clear all the transitions instead of only 1.   Old threads: https://community.adobe.com/t5/premiere-pro-discussions/deleting-multiple-transitions-at-once/m-p/9529912 https://community.adobe.com/t5/premiere-pro-discussions/how-to-remove-all-transitions/td-p/1631643/page/2 https://community.adobe.com/t5/premiere-pro-ideas/function-to-quot-remove-all-transitions-from-selected-clips-quot/idi-p/13515737 https://www.reddit.com/r/premiere/comments/190qzn7/how_do_you_remove_a_multiple_audio_transitions/   Please add. Big help. Thank you.