Skip to main content

Filter by idea status

10000+ Ideas

P: needs a Queue Management System i.e. exporting photosOpen for Voting

Problem:   When I export more than 11 photos, my computer will be slowed down significantly. This might not be a problem, when I export just one folder, but in order to separate photos from an event of different people, I need to start several export processes and also have to wait for them to finish. Additionally, I cannot work on anything else. I usually have a lot of photos around 20.000 to 60.000 in one catalog. They are distributed/organized in several folder by date and by events. My usual process is to import all my photos, sort them, discard them, edit every photo, export those in different folders. An export of around 1000 photos (32MP) can take around 1/2 hour up to 1 hour easily. I want my computer to work on them, when I don't use it.   I have a decent computer (AMD Threadripper 24 cores, 64GB RAM, NVMe SSD 2T, NVIDIA Geforce RTX 2060 Super), which needs to work on 45MP Photos in RAW.   What I need and probably other users as well: I need to queue an export process. By queueing, I mean initiate an export, put it into a queue and immediatly pause it. I need to have the ability to queue several exports. I need to have the ability to start executing the queue, when I'm done working on all my photos. For example, when I go to bed. I need to have the ability to restrict the amount of executed tasks in the queue. On task means sequential processing. More than 1 means parallel processing. Solution:   Lightroom really needs a Queue Management System! Every Process uses this System and you can configure it with settings like: How many Tasks / Processes  should run in parallel? Which processes are allowed to run in parallel? Which processes should run sequentially? Which processes should be enqueued on default? Is there a timer, which can start all processes in the queue on it's own at a certain time? (For example, the queue gets executed at midnight) You should be able to move processes in front or in the back! You should be able to priorities tasks (CPU power) You should be able to priorities tasks (order in the queue) When Lightroom shuts down, the queue has to have a backup! Therefore, you can resume every task after a crash or a needed shutdown after an update or a general restart! Every process should be pausable, resumable, cancelable or restartable! There should be a history of all tasks executed! Every Task should be editable (Editing the list a file been exported, deleted, converted, etc.) I probably could go on for the features, but this is really basic stuff and this was already implemented in many programs handeling files. Lightroom isn't any different, but it really is unpleasent, when working with it when files are touched! 

AphermionParticipant

Option to make Anchor/Transform persistent for each layerOpen for Voting

Example: If you wanted to align duplicates of a layer/smart object around a circular orbit,you currently have to do what is shown in the screenshot.CTRL+T → change transform location → rotate → confirmDuplicate LayerCTRL+T → change transform location → rotate → confirmDuplicate LayerCTRL+T → change transform location → rotate → confirmetc… Layer rotation around a custom anchor point.Problem:After confirmation, the transform origin resets back to the center of its specific layer. Repeats of the action require a tedious setup every time.Feature request:Checkbox for “Persistent Anchor Location”, or just “Persistent Anchor”.Something like that.How should it work?The user checks the box located in the transform control bar. When moving the anchor point, it’s relative location is saved to the layer, it should not reset to the center of the layer after exiting the transform tool. Thus when selecting that layer and entering the transform tool again, the transform anchor should be where you’ve moved it to before. When duplicating the layer, it should copy the anchor location from the original. It should be a local variable, not a global one.So the checkbox only remains ticked on the layers the user performed the action on and its duplicates.Entirely new layers default to the standard behavior.This behavior could be relegated to a setting, so the user can specify the default behavior.Additional features:Reset Anchor button  Resets the anchor for all selected layers to the center of each layer. Relative/Global Anchor switch “Relative” (default) retains the anchor position relative to the layer’s location on the canvas. “Global” sets the anchor relative to the canvas itself, so when moving the layer, the anchor stays put. Again, the default behavior could be added as an option to the settings.Benefits:Greatly increases efficiency for workflows that aren’t grid aligned, enabling intuitive creation of fluid designs and keeping symmetry more easily. Side note:I am aware of workarounds, but they add clutter.There shouldn’t be a necessity for workarounds to achieve rather basic functionality. 3D tools like Maya and Blender have a similar feature, it is quite important and I don’t know why Photoshop doesn’t have it. 

DJ-VillA
DJ-VillAParticipant

P: Import orderOpen for Voting

Dear Adobe Lightroom Team, I am writing to complain about a long-standing issue with Lightroom Mobile on Android: imported photographs are displayed from the last shot to the first shot by default. For photographers working through an actual shoot, this is backwards. If I photograph a sequence from image 001 through image 500, I expect Lightroom to show me 001 first and allow me to work forward through the shoot chronologically. Instead, Lightroom shows the newest photograph first, forcing me to select Reverse Order. The bigger problem is that Lightroom does not provide a proper global preference to make chronological, oldest-to-newest sorting my permanent default. I have been dealing with this behaviour for a very long time, and having to repeatedly reverse the order is an unnecessary frustration in an otherwise excellent mobile photography workflow. I specifically use Lightroom Mobile/Cloud and do not want Lightroom Classic to be the solution. Lightroom Mobile should be capable of remembering how a photographer wants their photographs displayed. Please add a global setting such as: Default Photo Sort: - Oldest to Newest- Newest to Oldest Once selected, that preference should remain consistent across albums, imports, All Photos, and future Lightroom Mobile sessions unless the user deliberately changes it. This seems like a very small preference to add, but for photographers processing entire shoots in capture order, it would make a significant difference to the Lightroom Mobile experience. Thank you for considering this request. Respectfully, Adrian

Stan Jones
Community Expert
Stan JonesCommunity Expert

Downgrading PR 2026 Projects to Earlier VersionOpen for Voting

Premiere 2026 projects cannot be downgraded for import to PR 2026 or earlier due to changes in the 2026 project data structure. Recent discussions about this have not yet been ported to the new forum. The primary previous feature request is here, but may be missing some interim posts. Also, it was primarily an explanation for how to use the non-Adobe methods for changing the project file version number. https://community.adobe.com/feature-requests-730/open-premiere-project-in-older-version-downgrade-project-version-1329162?postid=1329162#post1329162 At a minimum, there needs to be a method for downgraded a PR 2026 project to 2025. A longer term issue is the need, for years, for a more robust converter or for the After Effects procedure for doing a “save as” from a later PR version to some number of earlier versions. January 26, ​@hellopaul4 started a thread titled “Has version "2026" killed the ability to downgrade a project to a previous version?” The most important reply was by ​@Fergus H: “We are considering options for backwards compatibility, but we have nothing to announce at this time.We haven’t intentionally prevented downgrading tools from working with Premiere v26. As you likely know, those tools only change the internal version number without modifying the project data itself. However, in v26, the project data structure has changed significantly – largely due to the new Object Mask feature. Because of this, a v26.x file that has had its version number changed cannot be parsed correctly by v25.x or earlier, leading to the crashes or error messages you encountered.Fortunately, there is a simple remedy for your current situation: you can open the project created in the v26.x beta directly in the shipping version of v26.0. The file formats are identical, so you can move your work out of the Beta environment without needing to downgrade the file.” As Fergus says, The official Adobe recommendation for downgrading is XML export:https://helpx.adobe.com/premiere-pro/using/backward-compatibility.html However, when I tested, XML export/import was not working for me on Win 11. My reply in that thread included:“I tested this, and trying to open a PR 26.0.0 XML export in PR 25.6.4 crashes, as it does if creating a new project and importing it. It did import to a new project in 24.6.5, and, once saved there, I could open the PR 24 version in 25.6.4.”I have not retested this. Stan