Skip to main content

Filter by idea status

10000+ Ideas

joshuaf62375374
joshuaf62375374Participant

P: Introduce a "Convert Mask to Remove" bridge.Open for Voting

Feature Request: Integration of Masking Selections into Generative RemoveThe ProblemCurrently, the Generative Remove tool operates in a silo. Even if a user has already generated a precise AI mask (e.g., Select Subject, Select Sky, or Objects) within the Masking panel, they must manually re-brush that same area using the Remove tool’s independent brush. This leads to: Redundant Effort: Painting a mask twice for the same object. Inaccuracy: Manual brushing is often less precise than the AI-powered "Select Subject" logic, leading to poor Generative AI fills. Proposed SolutionIntroduce a "Convert Mask to Remove" bridge. This could be implemented in two ways: From the Masking Panel: Add a "Remove with Generative AI" option to the "..." menu of any existing mask layer. Within the Remove Tool: Add a "Use Existing Mask" button that allows users to pick a selection (like Subject or Sky) as the source for the Generative Remove brush. Use Case ExampleA photographer wants to remove a distracting person from a complex background. They use Select Subject to get a pixel-perfect outline. Instead of re-painting, they click "Apply Generative Remove to Mask." 3. Lightroom uses the existing high-fidelity mask to inform the Generative AI, resulting in a cleaner edge and a faster workflow. User Benefit Speed: Eliminates the need for manual brushing on complex subjects. Precision: Leverages the superior edge detection of the Masking engine to ensure the Generative AI knows exactly where the object ends and the background begins.  Please feel free to reach out for any clarification. Thank you.  -Josh F.

RenaldyDParticipant

Even More Optimisation Save Files & Cache Temp/ FilesOpen for Voting

Hi, i’m Renaldy a freelancer working with limited storage capacity, I'm requesting for Adobe implement intelligent cache management and storage optimization features. Current cache systems can consume 5-10x the original file size, creating unsustainable storage demands. With SSD/HDD prices skyrocketting because of AI, hardware upgrades aren't always feasible.with help from claude, let me deliver our suggestion for Save files & Cache Temp/ Files optimization: 1. Intelligent Cache ManagementAdaptive cache sizing: Automatically scale cache based on available storage (e.g., if <50GB free, limit cache to possible performance (like in photoshop with Web/ Photos/ Huge pixel option) instead of each users manually choose what they think is best) Priority-based cache: Keep cache for active layers/effects; compress or purge cache for unused elements User-defined cache limits: Set maximum cache per project or application-wide2. Optimized Save File OptionsSmart linking toggle: Prompt users to link large assets instead of embedding (with easy re-embedding if needed) Compression profiles: Offer "storage-optimized" save presets that use efficient compression without quality loss Proxy workflow improvements: Better integration for working with lightweight proxies3. Storage Monitoring & WarningsReal-time storage dashboard: Show current file size, cache size, and projected storage needs Proactive warnings: Alert users before storage becomes critical (e.g., "Your cache will fill remaining storage in 15 minutes") Quick cleanup tools: One-click cache optimization without closing applications4. Cross-Application Cache SharingUnified cache pool: Allow multiple Adobe apps to share a common cache allocation Smart purging: Automatically purge oldest/least-used cache when storage is tightand that’s my feature request for storage/ cache files/ temp optimization. i hope this help adobe to aware that their users is not only using with the best setup possible to operate Adobe app

Bridge 2022 versions 12-13 were better at keyboard based file organizationOpen for Voting

As a bridge user for over 5 years I can't help but complain about no longer having Bridge 2022(12.01, 12.0.2, 12.0.3, and 13.0.1) available to download via the creative cloud app. I take a great deal of bracketed images that I manually group via the shift key + arrow keys and the Command+G Grouping keyboard shortcut. In the newer versions of Bridge this workflow is virtually impossible without countless mouse clicks instead of using the arrow keys. As you group(Command+G) your photos and press the right arrow key to then group your next photo group your cursor gets placed back at the origin of the files instead of on the next image. For Example: You've just completed 20 photo groups and are about to group the next photo set. You hit the right arrow key and now your cursor is back at photo group 1 instead of being at the next photo. Now you must arrow key over the next 20 photos or take your hand off the keyboard and use your mouse to click the next photo group. I have submitted countless user complaints to adobe via Bridge yet still this issue has not been solved for me. It seems rather simple as someone has programmed the cursor(or pointer) value in the list to reset to 0 after every group creation rather than picking up where it left off.  The automatic HDR/Bracket stack still is virtually unsuable and leads to more time wasted unstacking incorrectly stacked images.  I'd greatly apprecaite anyone's insight for improving these features in future bridge updates, or at least getting access back to the previous versions of bridge where this feature works properly. Thank you!