Build better products with our product team
Following the recent introduction of AI-based photo culling, I am writing to ask if there are plans to implement a personalized AI batch-editing feature in Lightroom. Specifically, a tool that learns a user's editing style from previously edited photos and automatically applies it to new RAW files.Currently, professionals must rely on external, third-party services like Imagen or Aftershoot to achieve this. Having this capability built natively into Lightroom would solve this problem and allow users to keep their entire workflow within a single application.
I’m trying out Stacks to help with culling sports photoshoots, motivated by the automatic stacking feature added a little while ago. It looks like the only way to “enter” a stack is to click the small number in the top-right corner of the photo? It’d be nice to be able to do this from the keyboard.
Currently, Premiere Pro displays an "Estimated File Size" in the Export window, meaning the software is fully aware of the projected file size and the destination path. However, it does not cross-reference this data with the actual available space on the target drive before starting the render.Recently, during a long 1.5-hour documentary export, my export crashed on the very last frame, throwing a generic, misleading "Error Code 39 / Selector 9 (Component: H.264 of type Exporter)". After hours of troubleshooting effects and source clips, the actual culprit turned out to be a full destination disk.The Request: Please implement a simple pre-flight check in the Export workflow. If the available space on the selected drive is less than the Estimated File Size (or within a 15-20% safety margin), Premiere Pro should pop up a clear warning BEFORE processing: "Warning: The destination drive may not have enough space to complete this export. Please free up space or choose a different drive."Furthermore, if an export fails due to a full disk mid-way, the error code should explicitly state "Disk Full" instead of crashing with a generic encoding/frame error. This would save editors hours of needless troubleshooting.
Add a feature where you can add a shadow behind your text
I use Libraries a lot due to the extent of brands I work with, but when I put the window on the side bar I am only able to see 2 or 3 items because the search bar, folder name and icons use a lot of the window space (about 50%). I work on a 27” screen and on the same sidebar I have “properties” and “layers” so I have to sacrify one of them and constantly rearranging the size of each of these windows. Maybe I coudl use other configuration of my space, but other than this particular issue It’s the most comfortable workspace on my +10 years using photoshop.
Many things done in a Python plugin can cause a C++ crash on exit. Fixing the crash is VERY difficult, as it happens once Python is finished so it can’t be caught by a Python Debugger or log message. The crash dialog on exit gives no hints as to what caused the crash, and the painter log doesn’t either. We need a way to know what from our scripting is crashing C++ on exit. This often occurs with events, connections, and UI elements. The only way to figure out what is causing the crash is bisecting your scripts line by line which is incredibly time consuming.
With advanced technology and software, I can imagine at this point that Adobe has not and cannot implement bulk file and folder downloads. If you pay for a software in the amount that I do, you expect that a feature so simple is included on the app. The task of downloading one document at a time is tedious and for someone like myself who is sick, this stresses me. If you can bulk delete items, you can darn well bulk download items.
Need a good stitch tool for generating panoramas from multiple photos. Needs to work both vertically and horizontally.
I can't find anywhere to cancel the membership when the free trial ends
I need a way to nativly edit all selected Sequence's Settings at once. Also, I would like to golabaly edit Premieres default new Sequence Settings, instead of it trying and guessing based on the type of media already loaded into the project.I would even accept Premiere mathcing the imported media exactly, for example, when I drag a Apple Prores 422 Proxy file into the empty timeline window, it creates a match sorce sequence at every step, accept for the codec. It creates an Apple Prores 422 LT.
*feature request*Blackmagic announced support for drag and drop .af files into DaVinci Resolve, including access to individual layers via “Split Layers into Place” in Fusion. Much like the way Resolves supports .psd files. I’m receiving more and more affinity files. Would be good if Ae and Pr supported .af natively too. Now I need to open the .af in Affinity and use the save as psd option.
Skip this. Ia m not a child. It’s embarrassing having this on my screen.
close-up product photo, vertical wooden framed digital calendar magnet on a brushed stainless steel fridge door, soft kitchen lighting highlighting the screen display, vibrant weekly meal plan app interface visible on the digital screen, clean, modern aesthetic, ultra sharp focus on the calendar screen, realistic reflections on the fridge surface, professional commercial product shot, no distractions, photorealistic, --ar 1:1 --style raw
Sya ingin mengajukan permintaan dana kak karna dana saya langsung di potong adobe sedangkan saya tidak pernah mengonfirmasi untuk berlanggana saya pernah cuman menggunakan gratis saja kak
When placing a file using File>Place Linked... there should be an option to not store any pixel data of that Linked file into the PSD file to keep the file size as small as possible.For example: When I take a bracket shot with my drone (DJI Air 3) in 8K, each of the RAW photos (DNG) is about 100MB in file size. When I now import 3 of these DNG files into Photoshop using File>Place Linked... and just save it as a PSD, the total file size is 792MB which is absurd in my opinion considering that each RAW photo is only 100MB.When I do exactly the same by using File>Place Embedded... and save it again, the PSD file size increases to 1,98GB (which is completely insane by the way).So there is definitely a benefit of using the Place Linked... option but it's still pretty clearly saving a large amount of pixel data into the PSD file even though I set Image Previews and Maximize PSD Compatibility both to Never under the Settings>File Handling tab. My file explorer (macOS) also doesn't show any previews or thumbnails for those PSD files, so I really don't understand what makes the PSD files so huge.In my opinion a Linked file should work similar as it does in Lightroom Classic and only store the Camera RAW settings of each linked RAW file and then create the actual image when opening the file in Photoshop and store it temporally in the RAM or the Scratch Disk.I actually discovered an interesting hack/workaround for this problem which doesn't make any sense but it definitely works:The trick is to change the Image Size within Photoshop from originally 8064 pixel down to 80 pixel and then save again. This alone decreased my file size from 792MB to only 134KB!!! That's a massive reduction in file size of 591000%!!!Once you open your PSD file back up again you can just increase the Image Size from 80px up to 8064px again without loosing any image quality since all the photos are Linked files.The same trick also works with Embedded Smart Objects but only reduced the file size in my example by 40% from 1,98GB to 1,19GB which is still a lot!Of course this hack doesn't work if you have other pixelated layers or masks in the same file but in that case you can just scale down each Linked layer individually and then change the Canvas Size to 80 pixel again. If you have masks applied to the Linked layers, you can just move the masks to new empty layers before scaling down the Linked images to keep the masks in its original size.This will still drastically decrease the PSD file size, for example my file with 3 Linked RAW images and 1 mask went from before 826MB to only 28MB since Photoshop only has to store the pixel data of the mask now in the file.Of course you have to scale everything back up again and reapply all the masks when you open the PSD file later but this could still be a good workaround if you just want to keep the files as backup and store them on your hard drive without taking up an unnecessary amount of space without loosing any quality.Another huge benefit of doing this is the time it takes to save and open those compressed files. For comparison: the 792MB file takes over 30 seconds to save on my Mac Studio M2 Max which is already a very fast and powerful machine.The scaled down 134KB version basically saves and opens within 1 second. So it's actually faster to open the small file and scale it back up then opening the large file!!! especially when you create an Action for scaling up & down the File Size.That's why I think this should be the standard behaviour of Linked files within Photoshop or at least give us the option to NOT save any pixel data of Linked files to keep the file size as small as possible so we don't have to do these tedious & unnecessary workarounds anymore!This would actually make the Place>Linked... feature much more useful for many users!
Preset Masking: Apply Presets Non-Destructively to Specific ParametersThe ProblemLightroom presets currently apply to the entire image and overwrite all settings — making it impossible to combine multiple presets selectively. This creates real friction in certain workflows.A concrete example from my own practice: when I want to apply my black-and-white preset to a color-graded image, I have to export a JPEG first, re-import it, and then apply the B&W preset — otherwise it wipes out all my color work. This roundabout workaround degrades image quality and breaks the non-destructive editing philosophy Lightroom is built on.The IdeaAllow presets to be applied as parameter masks — meaning a preset could be scoped to affect only a defined subset of parameters (e.g., tone curve, HSL, B&W mix) without touching the rest of the edit.How It Would HelpCombine presets freely: apply a color grade from one preset and a grain/vignette look from another, without either overwriting the other. B&W conversion without a destructive workaround: apply a B&W preset that targets only luminosity and B&W mix settings, leaving your color parameters intact for possible reuse or toggling. Faster, cleaner workflows: eliminates multi-step export/import hacks and keeps everything inside a single raw edit.This would make presets significantly more versatile — effectively turning them from blunt all-or-nothing tools into composable building blocks.
Film emulation is a frequent deliverable in my professional work as a cinematographer and photographer. Clients regularly request a "film look," and right now that requires third-party plugins or manual workarounds that add complexity. Having robust, built-in film simulation tools would keep the workflow inside Lightroom, reduce dependency on external plugins, and give more precise creative control over the final aesthetic.Expand Lightroom's grain and effects panel with:More granular control over grain structure its already great but would be nice to have control over shape, clumping, response to luminance zones Film stock presets or profiles that replicate the tonal and grain characteristics of popular stocks (Portra, Tri-X, Ektar, etc.) A halation/glow effect slider that simulates light scatter around bright areas Diffusion and blur options Options for color grain vs. monochrome grain behaviorThe film look is always in demand and is a style that will never go out of fashion, these additions will help many achieve the look they are thinking of! 🎞️
As you compare the grain effect beetwen Lightroom Classic and Silver Efex, you can see that SE is more natural, as the LR grain seems to be plastered on the entire image: the shadows and highlights are equaly recovered with grain while very bright zones shouldn't. It is very visible on B&W pictures.On a picture if I add film grain effect, I use a Luminance mask and reduce the grain slider to reduce grain impact on the Highlights. Not bad but not quite satisfying. I wish LR could implement a better film looking grain. Maybe a slider "preserve HL" could be added in the Grain panel, as it exists in the Vignette panel. Hope this idea helps.
I think is not so clear the quantity of credits that are used. Many of the results are not succesful and consume the credits very fast. It is not nice.
The potential of Media Replacement in MOGRT's for creating responsive design is huge, but it is hamstrung by the inability for expressions to access any information about the media itself. A simple, concrete example is that I am building some MOGRT's for photo treatments, with a simple white frame that needs to match the aspect ratio of the photo the editor drops into it. This would be trivial in After Effects using footage replacement, but with Media Replacement through Essential Properties in AE or in Premiere, when expressions reference the footage they only see the original footage used in the template. This means the editor has to manually adjust the dimensions of the photo frame using fiddly controls in the EG Edit panel.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK