Skip to main content

Filter by idea status

10000+ Ideas

RDCM creative mediaParticipating Frequently

a specialized Generative Extend feature for Premiere Pro and After Effects designed for interview footageOpen for Voting

I would like to request a specialized Generative Extend feature for Premiere Pro and After Effects designed for interview footage, talking-head clips, documentary editing, corporate video, and other dialogue-based production.A common editing problem occurs when an interview clip contains strong usable content, but the subject restarts a sentence, opens their mouth, blinks, leans back, changes expression, or moves awkwardly near the edit point. Even if the content is good, the last few frames can make it difficult to create a clean transition, dissolve, J-cut, L-cut, title overlay, or cutaway return.Current generative extension tools are promising, but for interview editing the goal is often not to create new motion. The goal is to create a short, usable editorial handle that preserves continuity while keeping the subject natural, stable, and believable.I would like Premiere Pro and After Effects to include a Pose-Locked Generative Interview Hold mode.Suggested workflow:The editor selects the end of an interview clip and chooses a command such as Generate Interview Hold, Generate Editorial Handle, or Pose-Locked Extend. The software analyzes the preceding 3–5 seconds of the clip and presents a plain-language visual inference summary, such as: “Subject is seated and facing camera. Subject is speaking near the edit point. Mouth opens during the final frames. Subject begins leaning back slightly. Eye line remains mostly stable. Background is static.” The editor can then confirm or adjust the desired result using a chat-style panel, modal window, or preset controls.Useful options could include:Generate 1, 2, or 3 seconds of extension Use current frame as reference pose Use earlier stable frame as reference pose Keep subject still Preserve eye line Keep mouth closed or relaxed Minimize blinking Prevent leaning backward or forward Prevent new gestures Prevent head turns Preserve facial expression Preserve background continuity Generate multiple variations Make suitable for dissolve / transition / title overlayThe most important part is that the tool should prioritize editorial usability over inventing new performance. If the AI causes the person to lean back, open their mouth, blink strangely, or change expression, the extension may technically work but will not be usable in a real edit.Editors should also be able to save guardrail presets for common scenarios.Example preset: Interview Transition HoldNo invented speech No new mouth shapes No major posture change No new expressive performance No head turns No eye-line changes Minimal blinking Preserve lighting and background Allow only subtle natural micro-motion Generate multiple versions for reviewThis would be useful for documentary editors, corporate video editors, interview editors, wedding editors, educators, broadcasters, and anyone working with spoken-word footage.The goal is not to alter the meaning of an interview or generate new dialogue. The goal is to create clean, ethical, editor-directed visual handles that allow smoother transitions and better timing when the original footage ends on an awkward facial movement, repeated sentence, blink, or posture change.This feature would be especially powerful if available in:Premiere Pro as a timeline-based editing tool After Effects as a more advanced shot-repair tool with masks, tracking, reference-frame controls, and deeper compositing optionsThis would save editors from using awkward freeze frames, unnecessary B-roll coverups, jump cuts, or time-consuming manual workarounds.

ed_ezra
ed_ezraParticipant

Prioritise / Standardise and Reflow the PACKAGING, SAVING and FINDING files workflow.Open for Voting

Standardise, give more options, and increase the detail for linking / re-linking / finding files and packaging inside ALL Adobe software. The workflow should be more holistic across ALL Adobe software. Finding files, relinking files, packaging files and even linking files can be a complete nightmare depending on the software used. Every piece of software has a different way of doing it and alternative options. And a lack of options. Adobe software is NOT intuitive or up to standard with the way creatives and professionals use multiple types of files that link to each other.I feel that with modern storage, the amount of files we produce on a daily basis, the size of these files, and the way designers and creatives use Adobe software fluidly, should be mirrored in the ‘find links’ and saving options of all your software. We use multiple bits of software, with multiple types of files.In this case Adobe is lagging behind in its file organisation and structure handling. You have given us key changes (multiple artboards, multi export options) but not a way of managing our filing from the apps. Re-linking and sharing flies in a professional environment is slow, laborious and painful and now feels ‘legacy’. I think Adobe should take professional workflows into consideration and build a file management system that compliments this, not going against what we use as professional creatives. A simple example would be changing the default “copy” addition at the end of a file name to “-v01” No professional i have ever met use COPY on the end of their filenames. Also people work in teams and never in isolation, so even the linking file and SEARCH dialogue should be more detailed, intuitive and specific to the files you are using. I want to be able to automatically search for files with specific filenames within a folder structure and the software understand the folder tree so you don’t have to re-search. Also searching for the filename if it is a server address, you can’t even see the filename to copy paste it into the search dialogue. This really needs updating and wastes so much time. Thanks!

DallbatrossParticipant

P: Photoshop does not recognize this type of file error is an incorrect error needs improvementReleased

Adobe, a request for you please.  A request born from two decades of working with applications, application developers, and application error messages: Please, for the love of God, when you present an error to a user, make sure that error is accurately descriptive.  For the exorbitant rates we pay to use this software, the least you can do is not pepper it with error messages that waste our time in addition to our money.   To wit: this afternoon I spent over an hour fighting the sudden appearance of an error message when trying to open .webp files (which were working fine yesterday, then suddenly not fine today).  Various iterations of this message included:   First, out of the blue: "Could not load the user measurement scale presets file becasue Photoshop does not recognize this type of file".  Then after resetting my measurement scales to the defaults: "Could not import the clipboard file becasue Photoshop does not recognize this type of file".  And lastly the most generic version, as if Photoshop had just given up: "Could not complete your request because Photoshop does not recognise this type of file".   You may notice all of these errors have one core theme in common: Photoshop couldn't do something because "Photoshop does not recognise this type of file".  Weird, considering it's been recognizing the .webp file format fine with zero issue up through just yesterday.Thinking maybe the file was corrupted, I tried opening it in Windows' native MSPaint.  It opened fine.  A bog-standard baked-in application that's practically an afterthought in modern days could open a file that this top-tier premium industry-standard design application choked on. And you know why?   After over an hour of searching forums, Googling the messages, messing around with the file, messing around with my computer, messing around with Photoshop, and almost resorting to uninstalling & reinstalling the whole application...it turns out the file path was too long for PS to handle.  That's it.  Not that the file format was bad.  Not that it was corrupt or damaged.  Not that it suddenly became unsupported.  And certainly not because "Photoshop does not recognise this type of file", because as soon as I cut the file name down to just "001.webp" it was magically recognised by Photoshop!  Fancy that.  No, this was all just because the file path +  file name combo was too long, and becasue Adobe's developers coded the most distractingly inaccurate and just plain wrong error message I've seen in recent memory. Now, I'm not saying directory-structure length limitations aren't a thing, but come on.  Those are issues intrinsic to Windows and the deisgn of thier OS which have haunted us for decades, so at this point they're well-known quantities (260 characters, in case anyone's keeping notes) which can and should be easy to identify and call out.  Yet I state again that MSPaint had no issue opening the full-fat file path.  So this is actually an issue purely on Adobe, for whatever reason, and that means the handling of the issue is also purely on Adobe, including giving us an accurate and actionable error message!  This is Appdev 101 and I can't belive I'm here saying it, but just stating "the file path is too long" or something would have IMMEDIATELY called attention to the issue, allowed me to fix it, saved me an hour of troubleshooting, and never would have necessitated this post.  But here we. So, Adobe. Please. PLEASE take this as an opportunity to review your application errors for consistency, accuracy, and veracity.  Don't just stop at PS.  Do it across your whole suite.  This is on the level of amateurishness and/or laziness where unhelpful errors like "Task Failed Successfully" live, and for the amount people are paying you & the trust we've invested in your software, that's beneath you. Do better.And for anyone else encountering any of those errors above...hey...try shortening up your file paths and/or file names.  That has nothing to do with the actual error, but you never know.  You might just get lucky.