Participant

ALT+drag not using in and out points of original clip

Forum|Forum|3 years ago
December 20, 2022
9 replies
1828 views

It's been like this for the last few updates--When I alt+drag a clip from the project panel onto a highlighted clip on the timeline, it used to preserve the inpoints (along with whatever effects were applied on the timeline clip). This was especially great for replacing watermarked stock clips with full res clips and/or updating animation clips. Now when I ALT+drag the footage from the project screen always begins at the beginning of the clip. I can't believe that more people aren't complaining about this. It is super time consuming to update a lot of clips any other way.

This happens on any and all computers I have worked on--not just on my personal, home system.

This topic has been closed for replies.

hellopaul4

Inspiring

I discovered that alt+shift drag-replacing a clip does what I need (i.e. copied the in and out points to my new clip). After decades of being able to alt-drag-replace a clip in AE (and maintain the in and out points), I'd assumed PPro would behave the same.

More details:
I open a clip (let's call it A) from the Project Panel, and set its in point to 3secs and out point to 5 secs.

I insert it into my timeline.

I then decide I'd like to replace clip A in the timeline with clip B.

I have not set any in or out points on clip B.

I alt-drag clip B over clip A.

PPro sets clip B's in point to the start of clip B, not to 3 secs as would be logical.

I realise I should've used alt+shift to replace the clip and maintain the correct in and out points.

Kevin-Monahan

Community Manager

Any other details you can give, @jadmintun, @иоанн, @hellopaul4, @isaacw59128721, or @zak27010097qder?

See: How do I write a bug report?

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio

И

иоанн

Participant

Same, Drag + ALT + SHIFT

hellopaul4

Inspiring

I'm having exactly the same issue - but I'm not sure if it was ever any better - I've seen people complaining about this behaviour back in 2015 (I am trying to replace a bunch of 16:9 clips with 1:1 versions - the clips are exactly the same length and codec - but PPro always just ignores my in-point, so I have to set it manually on EVERY ****ing clip). I'm on PPro 24.3.0 Beta Build 43.

isaacw59128721

Participant

Update, I'm having the same issue now in V23.6.2

I'm not sure what's causing this or if I have a setting checked that I didn't know about.

isaacw59128721

Participant

I'm having this exact same issue on a Macintosh. In investigating this issue, I'm pretty sure that this function worked normally for me in v24.0. I opened up the same project a week later after the software updated to 24.1, and OPT+drag doesn't use the original in and out points anymore. It defaults to using the beginning of the replacement video as the in point and then the duration of the original clip is applied to calculate the out point.

I'm looking into options right now of opening the project in an earlier version of Premiere and seeing if it is indeed the problem.

Z

zak27010097qder

Participant

This is still not working. This unbelievable bug ridden software is pushing me to a point where I'm honestly considering switching away from Premiere Pro. I have hundreds of files I need to replace and no simple way of doing this because of Adobe's inability to patch this simple error.

Harold Silva

Community Expert

Hola, ¿qué tal?, trabajo con la versión 2023 y uso dicha función a diario y hasta ahora no he tenido ningún tipo de problema con ello, me parece raro lo que comentas. Quizás si grabas tu pantalla y vemos los resultados de dicha acción te podamos ayudar
Saludos

Harold Silva B.

Z

zak27010097qder

Participant

I am currently trying to use ALT + Drag to replace clips in the timeline while keeping the same settings. All it does is replace the video without any settings, and the program will also not allow me to replace the clip through the clip edit options. I have tried resetting my preferences already but nothing is solving this so far.