Skip to main content

Filter by idea status

10000+ Ideas

Virtual Doll
Virtual DollParticipant

Firefly Image History and Gallery NavigationOpen for Voting

I'd like to provide feedback on the user experience when accessing my image history in Firefly. The current navigation flow is causing significant frustration and disrupting my workflow.Specific Issues:Confusing navigation between Canvas and History The path from the main canvas to viewing my image history feels unintuitive and awkward. It's not clear or easy to access my past work.Viewing images requires too many steps When I click on an image from my history to verify it's the one I want, getting back to my history gallery requires unnecessary extra clicks. This back-and-forth should be seamless but instead feels clunky."Back to Gallery" button goes to the WRONG gallery This is the most frustrating issue: When I'm viewing one of MY images and want to return to MY gallery, the first/default option takes me to the PUBLIC gallery instead—where none of my images are stored. Why would the navigation default to a public gallery when I'm working with my personal images?Suggested Improvement: The navigation should keep users within their personal workspace. When viewing my own images, the "back" or "gallery" option should return me to MY image history, not the public gallery. The flow should be intuitive: Canvas, My History, Individual Image, Back to My History.This navigation issue is disruptive enough that it makes me want to close the application entirely. I hope this feedback receives attention, as improving this flow would significantly enhance the user experience.Thank you for considering this feedback.

Native, Reusable Transcript Assets (Beyond SRT Limitations)Open for Voting

In team-based editing environments, transcripts are frequently recreated for the same source footage across multiple Premiere Pro projects. While formats like SRT exist, they are fundamentally limited and not suitable for treating transcripts as reusable editorial assets. Current problem:SRT files are designed only for subtitle display. They are flat text files that contain basic timing and text, but they lack any meaningful connection to the source footage. As a result:They cannot verify whether a transcript matches the correct clipThey do not retain clip metadata such as duration, frame rate, timecode, or codecThey lose internal transcription structure and accuracy generated by PremiereThey cannot support validation, versioning, or reliable relinking in team workflowsBecause transcripts live only inside Premiere project files, and SRTs cannot act as a true source of truth, teams are forced to re-transcribe footage that has already been accurately transcribed in the past. Proposed solution:Introduce native Premiere transcript assets that exist independently from project files and go beyond the limitations of SRT. These assets would:Preserve rich transcript data and internal metadataMaintain a strong identity link to the source footageBe stored externally on shared storage or serversBe reusable and relinkable across multiple Premiere projects When linking a transcript asset to a clip, Premiere could validate the match using properties such as duration, timecode, frame rate, or audio characteristics. If a mismatch is detected, Premiere could warn the user before proceeding. Workflow improvement:This approach would eliminate redundant transcription work, reduce errors, and establish transcripts as first-class editorial assets—similar to media, proxies, or audio waveforms. It would allow teams to collaborate more efficiently and maintain consistency across projects without relying on fragile subtitle formats like SRT. By providing a native solution that preserves accuracy and context, Premiere Pro would enable scalable, professional text-based workflows that SRT files were never designed to support. SRT is a delivery format. Transcripts should be editorial assets.

Link Sequence Caption Corrections to Source Clip TranscriptOpen for Voting

In my workflow, I often create multiple versions of a video from the same source footage (for example, different edits, durations, or platform-specific versions). This is especially common with interviews or talking-head footage, where I rely heavily on auto-transcription and captions.The current problem is that transcription corrections made inside a sequence are isolated to that specific sequence. When I correct errors in captions (names, terminology, repeated misinterpretations) and later reuse the same footage in another sequence, those same errors reappear. This forces me to correct the same transcription mistakes multiple times across sequences, which is inefficient and increases the risk of inconsistencies. Proposed solution:Add an optional linking mechanism (for example, a chain/link icon in the Text panel) that allows the editor to choose:“Apply caption corrections made in this sequence to the original clip transcript.”When enabled, this would: Update the master transcript of the source clipTreat the clip transcript as the single source of truthEnsure future sequences generated from that clip reuse the corrected textPreserve current behavior as default (opt-in and non-destructive) Workflow improvement:This feature would significantly improve multi-version editing workflows by eliminating repetitive transcription corrections and ensuring consistency across edits. It would be especially valuable for interviews, podcasts, educational content, and social media repurposing, where the same footage is reused across many sequences. By allowing editors to propagate corrections back to the source transcript, Premiere Pro’s text-based editing would feel more efficient, consistent, and aligned with real-world editorial workflows.

braydon
braydonInspiring

Please allow us to generate a text-based log or summary of our Preferences settingsOpen for Voting

Clearing our Preferences is the first suggestion that's given to every problem. But do the people who direct us to do this know how long it takes to get Premiere back to the way we've set it? I've done it a few times in the past and it's taken me weeks to iron out all the little settings and get Premiere behaving the way I like. This process become a huge disincentive for me to clear my Preferences. Since it's the first port of call for every little problem, it would be WONDERFUL if Adobe would provide us with a way of generating a log or digest of what our settings are before we clear them, so that rebuilding them can be a straight-forward process. Yes, I take screenshots of every page of the Prefences dialogue box, and I take screenshots of the layout of the panels in each workspace, and I try to take screenshots of all the menus in the main menu bar, and the hamburger buttons, and the wrench buttons... but it's unweildy and complicated. It would be great if there was a one-click method of exporting all Preferences and ancillary settings to a text file (just like Premiere can easily export EDLs) so they can be easily rebuilt manually. I'm not saying a way of exporting and re-loading our preferences, because the bugs would just carry over. Just a way of being able to see what they were, once they're gone. I did try to put this the Feature Request forum, but it's broken, there's no way to advance past the introduction screen (at least, not with the two computers and three different browsers I tried).