Skip to main content

Filter by idea status

10000+ Ideas

Joe HohnerInspiring

P: Folder Favorite Setting Cannot Be ChangedOpen for Voting

After installing the latest release of Lightroom Classic 7.4 I'm unable to unmark my favorite folders.  In other words, folders that were marked as favorites before the latest release can no longer be unmarked.  I can, however, select a folder that was not a favorite before release 7.4 and mark it and also unmark it as a favorite.  I use this feature a fair amount so I'm pretty sure this issue started after the latest release but I cannot be sure.  Thoughts?  Seems like one of those pesky software bugs to me. I'm an experienced user so I do not think this is some type of user error.  The catalog is my master catalog and has about 600,000 images.  I did not have any favorites marked in my sub catalogs before the release.  They work fine but, again, the problem seems limited to the folders that were marked as favorites before the release.[Update: All of the reports here except one can be explained by the confusing design of LR's "favorite groups".  See Robert Somrak's post and John Ellis' post. Thus, this topic is marked as an Idea, rather than Not A Problem, to capture the concept that the UI design is very confusing.Patrick Philippot identified a bug where right-clicking an unselected folder creates two folder groups. It has been forked into this bug report.There's another topic expressing similar confusion. I'm not going to merge the two, since that will hide all the useful replies.- John Ellis, 3/10/20]

NYU Dm194Participant

MacOS Adobe Creative Cloud desktop app sign in with DUO authentication issueOpen for Voting

When users of MacOS devices attempt to sign in with the Adobe Creative Cloud desktop application and signing in with DUO authentication set to block sign ins with unsuporrter OS or unknown OS', DUO will block Adobe Creative Cloud deskt top app sign in with an error for "Unknown OS" (even if running the most current MacOS). Alternatively, signing in with the web browser option, passes this DUO security check. Also of note, the same issue is not found on the Windows Adobe Creative Cloud desktop app when signing in with DUO. This leads me to believe the Adobe CC imbedded web app for the Creative Cloud app on the Mac either does not allow DUO to view the OS version, or repersents itself as a generic OS to DUO.  My request is for Adobe to update this Mac Adobe Creative Cloud desktop application to allow DUO to verify the MacOS version as the Windows version of Creative Cloud desktop app does. When requesting support on this matter, Adobe support suggested using the web browser sign in as a work around for MacOS and to submit a feature request: "Regarding your query, "Is there not an option to have Adobe look into the Mac version of their Adobe CC desktop application with regards to Duo?" After consulting with our experts, I would like to inform you that there are currently no plans for this feature. I kindly request you to submit a feature request so our team can be aware of your suggestion and consider including it in future updates."

Czar Hey
Czar HeyParticipating Frequently

P: Automatically use Originals for AI tools when availableOpen for Voting

Since version 14.4, when a user enables the “Use Smart Previews instead of Originals for image editing” option, and are editing an image where both the originals and Smart Previews are available, they may be shown the following message when they edit an image:   You have enabled "Use Smart Previews instead of Originals for image editing" in the preferences. When using the latest Al features, it is highly recommended that you always work on Originals. For best results disable this preference.   A better implementation for this is to automatically load the originals when needed, rather than telling the user to disable “Use Smart Previews instead of Originals”. For instance, if the user attempts to use an AI tool that works better with the originals, and the originals are available, Lightroom should automatically load the original and use that. The user should only be warned if the originals are not available, telling them that the tool might not work as well on a Smart Preview. Lightroom already does this when exporting: the originals are always used regardless of setting unless they’re unavailable, in which case the user is warned about using Smart Previews to export.   The advantage from an end-user that finds the “Use Smart Previews instead of Originals for image editing” feature useful is that they could make basic adjustments using the Smart Preview first, taking advantage of the improved performance, and then Lightroom will automatically switch to the originals when they need to use an AI tool. This is a much more seamless experience than asking the user to turn off a setting they find useful.   Currently, the workaround to use the originals without turning off the “Use Smart Previews instead of Originals for image editing” feature is set the zoom to 100%, which will cause Lightroom to load the original for pixel-level editing. It’s doable, but the user needs to know about this first, and it seems to make more sense for Lightroom to just load the original automatically.

Feature Request: Streamlined Batch Export for Individual Edited ClipsOpen for Voting

 Problem StatementCurrently, exporting multiple individually edited clips from a Premiere Pro sequence with all effects and color corrections applied is unnecessarily time-consuming and inefficient. Users who need to export dozens of edited clips must either:Manually set In/Out points for each clip and export one by oneUse Project Manager (which only exports unedited source files)Manually nest each clip individually and export separatelyRely on third-party scripts or workaroundsThis workflow is particularly problematic for:Content creators managing social media clipsEditors delivering multiple revised assets to clientsPost-production teams working with multi-clip projectsAnyone who needs to deliver individual edited clips rather than a full sequenceProposed SolutionFeature: "Batch Export Individual Clips"Add a native function that allows users to export all clips on a timeline as separate files with all edits, effects, and color corrections preserved.Implementation SuggestionsOption 1: Right-click Context MenuSelect multiple clips on timelineRight-click → "Export Selected Clips Individually"Opens batch export dialog with options:Export preset selectionAutomatic naming based on source clip names or custom naming patternDestination folder selectionOption to include handles (extra frames before/after)Queue all to Media Encoder or export directlyOption 2: Enhanced Project ManagerAdd "Export Edited Timeline Clips" option to existing Project ManagerDetects all clips on selected sequenceExports each with effects applied (not just source files)Preserves clip names automaticallyBatch processes to destination folderOption 3: Batch Nest FunctionSelect multiple clips on timelineChoose "Nest Each Clip Individually"Automatically creates nested sequences for each clip with unique names based on source filenamesProvides option to immediately batch export all nested sequencesMaintains organized project structureKey Features NeededAutomatic Unique NamingUse source clip filenames by defaultSupport custom naming patterns (e.g., "ClientName_ClipName_v01")Sequential numbering optionMaintain original file naming conventionsPreserve All EditsExport with all effects, color corrections, and adjustments appliedRespect clip trimming and in/out points on timelineInclude nested sequence contentsApply sequence settings (frame rate, resolution, etc.)Batch ProcessingQueue all clips to Adobe Media Encoder for background renderingProgress indicator showing current clip being exportedError handling for failed exportsPause/resume capabilityFlexible Export OptionsChoose export presets per clip or apply one preset to allSelect destination folderOption to organize exports into subfoldersInclude/exclude specific tracks (video only, audio only, or both)Use Case ExamplesExample 1: Social Media Content CreatorEdits 30 short clips on one timeline with color grading and effectsNeeds each exported as individual MP4 filesCurrent workflow: 30+ minutes of manual exportsWith feature: 2 minutes to set up, automated batch exportExample 2: Commercial EditorDelivers 15 different cut-downs of a commercial to clientEach needs specific color correction and effectsCurrent workflow: Manual export of each version with careful namingWith feature: One-click batch export with automatic namingExample 3: Event VideographerColor corrects 50 ceremony clips on one timelineNeeds individual ProRes files for client archiveCurrent workflow: Hours of repetitive export tasksWith feature: Quick batch export while working on other projectsBenefitsTime Savings: Reduces hours of manual work to minutesReduced Errors: Eliminates mistakes from repetitive manual processesImproved Workflow: Allows editors to focus on creative work, not technical tasksProfessional Efficiency: Matches competitor features in other NLEsBetter File Management: Automatic naming ensures organized deliverablesCompetitive ContextOther NLE platforms (DaVinci Resolve, Final Cut Pro) offer more streamlined approaches to exporting multiple timeline clips. Adding this feature would bring Premiere Pro to parity and enhance its appeal to professional editors.Priority LevelHigh - This addresses a common pain point across multiple professional use cases and would significantly improve editor productivity.Additional Enhancement: Batch Nest Individual ClipsAs a complementary feature, add ability to:Select multiple clips on timelineExecute "Nest Each Individually" commandAutomatically creates separate nested sequences for each selected clipNames them based on source filenames or custom patternOrganizes in Project Panel folder structureThis would support the export workflow while also providing organizational benefits for complex projects.Thank you for considering this feature request. Implementing efficient batch export functionality would significantly improve the daily workflow of countless Premiere Pro users.