Skip to main content

Filter by idea status

10000+ Ideas

deborah_6803Participant

Feature Request: One‑Click “Remove All‑Black Layers” CommandOpen for Voting

已思考若干秒 Feature Request: One‑Click “Remove All‑Black Layers” Command Background & Pain Points In complex PSD files, it’s common to accumulate dozens or even hundreds of layers that contribute nothing to the final image—either because they’re pure-black pixel layers or their layer masks are entirely black. Manually hunting down and deleting these layers is tedious and error‑prone. Existing script‑based workarounds require setup, can be fragile across versions, and still force users into multi‑step workflows. Key Requirements Auto‑detect Pure‑Black Pixel Layers Identify and remove any normal pixel layer where every non‑transparent pixel is RGB(0,0,0). Auto‑detect Fully‑Black Masks Identify and remove any layer (or group) whose layer mask is 100% black (i.e. completely hides its contents). One‑Click Cleanup Expose a single command (e.g. in the Layers menu or right‑click context menu) labeled “Remove All‑Black Layers” that scans the document and deletes all matching layers. Preview & Undo Before deletion, present a brief dialog listing the layers flagged for removal with an option to confirm or cancel. All deletions should be fully undoable via Photoshop’s History panel. Use‑Case Scenarios E‑commerce Design: Designers iterating on product mockups often leave behind black fill or mask layers used for testing backgrounds or alpha mats. Photo Compositing: Photographers maintain multiple hidden masks during retouching; final exports should purge any masks that hide 100% of their layer. Animation & VFX: Compositors need to quickly strip out unused black‑filled adjustment layers or track mattes before rendering to reduce file size and improve performance. Benefits Dramatically Faster Cleanup: Deletes dozens of useless layers in seconds, saving designers valuable time. Reduced File Size & Complexity: Removes dead‑weight layers that bloat PSDs and slow down performance. Consistent, Native Workflow: Built‑in command avoids reliance on external scripts and ensures compatibility across Photoshop releases. Thank you for considering this enhancement! It would greatly streamline layer management for professional workflows.

Izotope Post Production Suite Full Integration with Premiere ProOpen for Voting

So, I'm going to make movies and I did quite a bit of research to decide which NLE to go with. Most people on the internet said Avid Media Composer is the best NLE for people who want to make movies, but they said that Adobe Premiere Pro is also a good option. The main down side to Premiere Pro is that you really can't do much to edit and enhance audio. I've done extensive research on how to edit and enhance audio and I've found that the industry standard is Izotope's Post Production Suite, in particular, Izotope RX 10 Advanced. It seems that much of Izotope RX 10 Advanced is compatible with Premiere Pro, but there are some very important features that are not compatible with Premiere Pro (for example, Dialogue Isolate, De-rustle, Ambience Match, and others). Much if not all of the rest of the Izotope Post Production Suite seems to only be compatible with Pro Tools and not Premiere Pro. This is a major problem for filmmakers like myself who need the very best audio editing, mixing, and mastering tools on the market. Dialogue Match is an Izotope app that would be especially useful to filmmakers, but it is not compatible with Premiere Pro at all and you can only use it if you have Pro Tools. So, I'm asking Adobe to talk with Izotope and make everything in the Izotope Post Production Suite fully integrated with Premiere Pro. Maybe Adobe could even build a standalone app that works with both Premiere Pro and the Izotope products. Everything else about Premiere Pro seems to be terrific and fully capable of making Hollywood movies, but the lack of integration with the industry standard for audio editing and solving audio problems is a major setback for any filmmaker or content creator who purchases Premiere Pro.

0mx9Inspiring

P: Continually pull photos from Apple PhotosOpen for Voting

I use LRC for all photoediting and photo and video organization. I use an iPhone for all photo and videography. My workflow: Take photo/video. Auto upload to iCloud. Rule in Photos keeps all in a Smart Album until I move them into an album. Periodically delete unwanted photos/videos from Smart Album, then export all unmodified original contents of Smart Album to a folder on my desktop. Switch to LRC to import all photos/videos. Continue to discard, keyword, rate photos & videos. File videos by year on external drive. Copy all photographs to a collection which is synched to Adobe Cloud (which allows viewing in LR on my iPhone), and then move the photos to files by year. This solution keeps all photos and videos on my hardware (which is backed up by Time Machine), allows me to see all my photos on my iPhone in LR. SInce they are also availabe in Photos, I can use search tools in both.   Here's what I'd like to see: 1. LRC continually pulls all photos and videos directly from Apple Photos. 2. LRC plays videos a lot smoother than it does now, supports setting poster frame (current ability), clipping both ends of the video, and adding a title frame. 3. Keywords added in LRC are searchable in LR on iPhone (although AI is getting pretty good).   I find it very useful to have the same tools for finding videos as I do for finding photos. This is an existing feature of LRC that I've never seen advertised. 

jyunte9Inspiring

Easy Way to Retrieve Asset License Number?Open for Voting

I am constantly getting copyright violation notices from YouTube for music I've licensed from Adobe Stock. This requires me to file a dispute with the copyright holder via YouTube. To do this, I have to find the music I used in the video and then find the license number on the Adobe Stock website. To get the license number on the Adobe Stock site seems to require several steps:1) Find the name of the music track - which may no longer be an exact match to the name of the track reported by the copyright holder.2) Use the Adobe stock Search feature to find the track on the Adobe Stock website.3) Copy the track's ID from the search results.4) Copy the track's ID.5) Click on your account icon (top-right corner of the website).6) Click on License History.7) In the results page, copy the asset ID into the Search bar and click the search button.😎 Click the "Info" button next to asset's license type (Standard or Extended).9) Copy the license number. That's NINE operations, just to get to your previously assigned license number for a single track! Imagine having to do that several times for each piece of music (or video, or image) used in a video? Can't adobe make it a bit easier to get the license number for previously licensed assets? How about providing a button on the intial asset search result (right after step 2, above) that you can click to quickly get the license info? This button could be enabled only if you're logged in and would only provide the license number if you licensed that asset. Seems like a simple update which would make things so much easier for Adobe's customers!

JboProd.Participant

Hybrid Acceleration for Media Encoder: Cloud Power, Local ControlOpen for Voting

Hello Adobe Community and Product Teams, I want to share an idea aimed at significantly improving our experience with resource-intensive Creative Cloud applications, such as Premiere Pro, After Effects, Media Encoder, and potentially others. --- ### **The Current Problem: The Local Performance Bottleneck** We love the power of Adobe tools, but many of us face major challenges: * **Prohibitive rendering and encoding times:** Hours of waiting for complex projects, which hinders creativity and productivity.* **High hardware requirements:** The need to invest in expensive workstations to achieve acceptable performance.* **Slowdowns and lack of fluidity:** Choppy previews, less responsive interfaces on heavy projects, even on good machines.* **Lack of flexibility:** Difficulty working efficiently on less powerful machines or on the go. These factors limit our ability to fully exploit the potential of the software and meet our deadlines. --- ### **The Proposed Solution: Controlled Hybrid Acceleration** I propose that Adobe develops a **hybrid acceleration** system. The core idea is to keep the main software operations running on our local machines, while having the **option to send the most computationally intensive tasks to optimized remote servers**. --- ### **How It Would Work (Key Principles):** * **Solid Local Foundation and Guaranteed Offline Functionality:**    * Creative Cloud software remains installed and fully functional on our computers.    * Offline work must **always** be possible. Remote acceleration is an *option*, not a mandatory dependency. * **Targeted On-Demand Acceleration:**    * The user could choose to send specific tasks to servers for accelerated processing. Typical examples:        * Final rendering (Premiere Pro sequences, After Effects compositions).        * Encoding/Exporting via Media Encoder.        * Complex calculations (motion analysis, Warp Stabilizer, physics simulations, demanding preview renders, etc.).    * The main interface and light interactive tasks would remain handled locally for maximum responsiveness. * **Full Data Control and Maximum Security (Crucial Point):**    * **Primary Local Storage:** Project files (.prproj, .aep, etc.) and all source media (rushes, assets) **remain stored on the user's local hard drives**. This is our intellectual property, our client data.    * **Temporary and Secure Transfer:** For a remote server to perform a calculation, it is technically necessary to send it the *strictly required* data for that specific task (e.g., the relevant video segments, assets used, calculation instructions). This transfer must be:        * **Secure:** Using robust end-to-end encryption.        * **Temporary:** Data is only present on the server for the duration of the calculation.     * **IMPERATIVE DELETION GUARANTEE:** This is the most important point for trust. Adobe must **guarantee explicitly, contractually, and transparently** that all user data temporarily transferred to its servers (or authorized third-party servers) is **permanently and irretrievably deleted** as soon as the calculation task is finished and the result is retrieved by the user, or in case of cancellation/disconnection. No residual retention should be possible. This guarantee must be central to the privacy policy and terms of service. * **Plugin and Script Compatibility:**    * The remote processing environment must be able to load and use the same third-party plugins and scripts that the user has installed locally, ensuring the consistency and fidelity of the final result. * **Choice of Processing Infrastructure:**    * To offer maximum flexibility, users should have a choice regarding the source of remote computing power:         * **Option 1: Adobe Cloud Servers:**            * An integrated solution offered by Adobe. It would be essential for this option to be offered with **reasonable, transparent, and predictable pricing** (perhaps power tiers or a clear usage-based cost).         * **Option 2: Third-Party / Private Servers:**            * The ability to configure the software to use:                * External cloud computing services (Render Farms on AWS, Azure, Google Cloud, etc.).                * **Private** servers (on-premise or hosted) managed by the company or user. Adobe could provide recommended technical specifications and potentially server software or APIs to facilitate this integration for organizations requiring full control over their infrastructure. --- ### **Expected Benefits:** * **Massive Time Savings:** Drastic reduction in waiting times for renders and exports.* **Increased Accessibility:** Allowing those with less powerful hardware to tackle complex projects.* **Flexibility:** Working more smoothly, potentially from different machines.* **Potential Hardware Cost Reduction:** Less pressure to constantly upgrade to the most expensive local hardware.* **Scalability:** Adapting computing power to the specific needs of a project.* **For Adobe:** Strong added value to the Creative Cloud subscription, addressing a major user pain point, and potentially new service offerings. --- ### **Conclusion: A Logical Step Forward** Implementing a controlled hybrid acceleration solution would be a major step forward for the Creative Cloud ecosystem. It would address a pressing need for performance while respecting the imperatives of control, security, and flexibility for creative professionals. Of course, implementation presents a technical challenge (transfer optimization, remote plugin management, server infrastructure), but I am confident that the Adobe teams have the expertise to meet this challenge. I invite other community members to share their thoughts on this idea, and I hope Adobe will seriously consider this path for improvement for the future of Creative Cloud. Thank you for reading.