Skip to main content

Filter by idea status

10000+ Ideas

hellopaul4
hellopaul4Inspiring

Audio ducking should create TRACK keyframes not CLIP keyframesOpen for Voting

I'd love this to be an option! I am, once again, trying out different music clips against an interview, and want to apply my ducking keyframes to the TRACK and not the CLIP. That way, I could easily delete the music clip from the track, drop a new one on there, and it would be ducked in all the right places. PPro does not need to know or care what clip I have on my music track - it just does the ducking at the TRACK level, regardless of what music is on the track. The ducking keyframes that PPro creates are in no way related to what's on the music track - they depend solely on the presence of dialogue and the settings in the Ducking panel. Talking of those controls - the "Sensitivity" is the wrong way round - setting it to High creates fewer keyframes, and setting it to "Low" creates a keyframe for even the briefest pause in the dialogue. It would be wonderful if we had two "Generate Keyframes" buttons: one that says "Generate Clip Keyframes" and one that says "Generate Track Keyframes"...and did just that! Or at least if PPro had the ability to copy keyframes from a clip to a track, that would mean I'd only have to do the ducking process once (on the clip, as it currently does), then I could copy the clip keyframes to the track, then delete the keyframes from the clip. And then do whatever I liked with the clip(s) (eg. extending it via Remix or replacing the clip with another music clip) knowing that my ducking keyframes are safely tucked away on the track. OR possibly even better - the ducking keyframes could be applied to a Submix track; that way, it'd be possible to route several tracks (music, FX, etc) to the submix track and they'd ALL get auto-ducked! Upvote! Upvote! Let's get this happening!

Edgar_HuParticipating Frequently

Thoughts about important updatesOpen for Voting

Hello everyone,I only use After Effects with ACES 32-bit. That's why my wish list only refers to effects that support 32-bit.I hope this will not only be helpful, but also show what could make this programme more popular.1. There is no denoiser or renoiser for the 32-bit version. And even if existing 16 effects were optimised for 32-bit, these effects would be 10 years behind the times. Currently, it is necessary to purchase DaVinci separately, add or remove noise there, and then export it to After Effects.2. The camera lens blur is far too limited. This effect needs to be updated, as absolutely every other programme offers more bokeh options than this one. Even Premiere has announced an effects library that can create better bokeh than After Effects, which is very strange. 3. Rotoskoping gets worse with every update. In my opinion, the best version is V25.1. But even this is much too slow or much too inaccurate compared to other options such as magic mask in DaVinci. Here, you have to go back to DaVinci and export for After Effects. The biggest problem with the tool in After Effects is that the refinement brush does not follow the contour of the Roto brush, which is incomprehensible to me. When the light in the scene changes stroboscopically and the Roto Brush follows the contour cleanly, the refinement brush completely freaks out. AI is much more advanced today than what After Effects offers, and I am very sure that a mind-blowing improvement is possible.4. Working with mask effects: I have already mentioned in a post that these should function more like stencils and not be determined by the position and scaling of the layer.5. It would be good if After Effects didn't blindly interpret all imported footage as ACES2065-1. Sometimes it says that After Effects has recognized the footage as rec 709, but still interprets it as ACES. Completely incomprehensible.It would be good if After Effects didn't blindly interpret all imported footage as ACES2065-1. Sometimes it says that After Effects has recognized the footage as rec 709, but still interprets it as ACES. Completely confusing.6. It would be good to make all effects, or as many as possible, accessible for 32-bit as well. For example, why is Vibrance still in 16? Is it because it needs a 100% limit? Can't that be worked around? Color Boost in Davinci does the same job in 32-bit depth.7. Tracking can now also be done with AI using photogrammetry, which would be a brilliant option to switch to. The free point tracking system, where you track more points yourself, could create a 3D camera as a result. Then it would be similar to the solution in Blender. What is definitely missing is a preview of the track points you select. A square window that displays the track point live. This allows you to see very clearly if there is any deviation, even if the footage is blurry. And while we're at it, a lens distortion pipeline is essential if you want to create clean, professional tracks. This needs to be built into the track, either with precise AI recognition or presets, or the ability to interpret distortion grids. Mask tracking can also be improved, perhaps with better shape recognition. 8. Removing objects in After Effects is only possible in a tutorial. When it comes to real shots, you can forget about it. Manual frame-by-frame retouching in Photoshop is more accurate. Please enhance this with AI. Today, it is possible to replace and remove anything, and it must work with 32-bit. The only workaround right now is to convert the project to ACES CC, create a reference frame, retouch it in Photoshop, update it in After Effects, and switch back to ACES CG. That can't be normal. (This workflow is not optimal because the retouched colors and highlights are not displayed correctly.) 9. Small but annoying 😄 When I save a new render job and select the storage location, can the location be saved by project or render job? Currently, the location that was last used is selected (no matter wich project you worked on). For example: If you create a project file for each shot and render V1 everywhere, it would be good if you could also save V2 in the same folder when duplicating the render job without having to search for it again in the folder structure. This problem arises when you are working on several projects at the same time and have to jump back and forth between them. Then you have to select the new storage location each time. This saves sooooooo much time on a large project with hundreds of shots.  So, thank you very much for reading this far 🙂 I would be pleased to receive your feedback. These are the most important aspects of my workflow, and perhaps they will be helpful to others as well.Thank you! 🙂 

SeriamonParticipant

Option to Hide One Channel in Stereo Waveform Display in TimelineOpen for Voting

Premiere Pro currently displays both Left and Right channels for stereo audio clips in the timeline waveform view. This is often unnecessary and visually cluttered, especially when only one channel is relevant (e.g., dual-mono interview tracks, camera scratch audio, or boom/lav recordings with split tracks).Request:Please add a simple toggle or preference that allows users to hide either the Left or Right channel in the stereo waveform display, or to show just a mono/mixed waveform without needing to collapse the track height or remap channels.Why this matters:It’s difficult to work efficiently with stereo clips that only use one channel.Reducing waveform clutter improves timeline readability and precision.Audio interpretation workarounds are destructive or time-consuming.Collapsing track height is not a viable solution for serious audio work.Ideal Implementation:Right-click clip or track option: “Display Left Only / Right Only / Mix / Stereo”Global preference for default waveform display modeNon-destructive (doesn’t alter audio channel configuration)This would significantly improve workflow for editors who regularly work with dual-mono audio or multi-mic setups. Thank you for considering this!P.S. I've spent hours searching for a workaround or plugin to solve this, and it’s clear that no such feature currently exists in Premiere Pro. After many years of using Adobe’s product suite, I’m seriously considering switching to a competing platform if this issue isn’t addressed. It’s a surprisingly basic and frustrating limitation that significantly impacts my workflow.