Skip to main content

Filter by idea status

10000+ Ideas

P: Expanding and enhancing generative remove, with generative fillOpen for Voting

When Generative Remove was introduced to Lightroom Classic, it immediately became a game changer for me. Tasks that previously would have required importing an image into Photoshop and spending a significant amount of time removing background distractions, unwanted objects, or unexpected issues can now be handled directly within Lightroom Classic, from a workflow and time management perspective, it has been incredibly useful I have also found that Generative Remove can go beyond simply cleaning up a background. It has become surprisingly effective for refining subjects while still producing natural looking results. A few examples that come to mind are removing visible bobby pins from someone’s hair or correcting a distracting wrinkle in clothing while maintaining the natural shape of both the outfit and the person wearing it I have even experimented with using it for more detailed retouching. For example, I had a client who wanted some visible stomach lines reduced. Normally, that would be something I would handle in Photoshop, but purely as an experiment, I tried using Generative Remove instead. It produced almost exactly the result I had envisioned while still looking natural That made me start thinking about how the concept behind Generative Remove could potentially be expanded. I’m not sure how realistic this would be from a technical standpoint or how well it would fit within Adobe’s overall vision for Lightroom Classic, but I think an interesting addition would be a more limited version of Generative Fill I would not necessarily want Lightroom to become a full Firefly or Photoshop replacement. Instead, I imagine something focused specifically on photography, the ability to selectively add small elements, extend practical effects, enhance foreground or background details, or introduce minor environmental additions without having to leave Lightroom Classic There have been several situations where I have needed to move into Photoshop simply because I wanted to add a little more to an image. This could mean introducing an additional prop, enhancing an effect that was already created practically during the shoot, or adding another visual element to strengthen the final composition One recent example involved a photoshoot where I was working with water effects. We achieved most of what I wanted practically while shooting, but I went into Photoshop afterward to give the effect a little more impact. The process was manageable, but it made me wonder how useful it would be if I could simply mask the area in Lightroom Classic and use a restrained Generative Fill tool to enhance the existing water effect directly within my normal editing workflow For example, a photographer could potentially use it to add a few additional water droplets, extend smoke or fog, introduce a subtle practical light effect, add or replace a small background object, enhance environmental particles, or make minor additions to props and scener 

GrahamWillcox_OMC_StudiosParticipating Frequently

Option to retain local audio preview scratch disks within Productions by default per machineOpen for Voting

Feature Request: Option to retain local audio preview scratch disks within Productions by default on individual collaborators' machines. I work with several other editors and assistant editors, each of us on multiple machines, on a shared Lucidlink volume, using Productions.We are big fans of Productions and big fans of Lucidlink, but do have a small nuisance that we're hoping find a better workaround for. Our scratch disks are set locally (not on lucid), which seems to help render speed during sessions and prevents those with slower upstream connections from getting their bandwidth choked. Often, sometimes several times per day, one or all editors collaborating will need to reset their video & audio previews in the Production's scratch disk to their own individual local non-lucid cache folders. Ideally, there would be an option in Premiere to allow each machine to have its preview file paths stay locally assigned.  Within Preferences>Collaboration perhaps a "Productions" section that would have an option allow each local machine to override the "Same as Production" default scratch disk locations. Specific workflow details:On-premises workstations connected via symmetrical 1gigabit ethernet connections, speedtests typically at 700-900Mbps down and 600-900Mbps upRemote workstations connected by a variety of broadband speeds, lowest 350Mbps down / 150Mbps upWe generally are editing from HD-proxy files, not camera original or high bitrate mediaOn Lucidlink, we are pinning source edit mediaNature of our projects requires frequent preview renderingeffects and layering often beyond real-time GPU playback capabilitytypical preview renders are HD prores LT or prores proxy format