Insert and overwrite doesn't work

thanks for the note. But yeah, as for now, my described bug is already fixed in release build 44.

@Tanuki M,

I think this is a different issue than the one in the original post of this thread, which is the bug @R Neil Haugen described. I think this should be its own Beta bug report.

I see what you describe in Release 24.6.1 (with focus in timeline, insert/overwrite uses the last selected clip in Source monitor or Project Panel) and Beta 25.1.0.39 (focus in timeline does nothing). The Clip -> Insert/overwrite is greyed out when the timeline is in focus.

Stan

Also can add to this post (instead of writing new one, or i should do that?) that after updating to Adobe Premiere Pro 25.1.0 BETA (build 42) insert ( , ) and overwrite ( . ) seems to be functional only while Source monitor or project window is active and performs... by inserting/overwriting with clip from source mon. or project window accordingly... while timeline or program monitor is active nothing happens when said shortcuts are pressed.

not as is in regular release 24.6.1 (build 2) or  few previous BETAs (before 25.1.0  (build 42)),  when regardless to selected window - program monitor or timeline - pressing ( , ) and ( . ) works (as expected?): executes desired functions for clip in source or project window according to which was active before switching to program monitor or timeline.

This occurs on multiple Intel machines with different Windows 10/11 releases with drastically different specs (GPUs/other hardware/drivers with or without NAS sollutions), where said Beta release is installed for testing purposes.

Only thing to notice: all source patching is correct, preferences hasn't been trashed due to lack of spare time this week to re-add/build what's customised, and resetting workspaces, (+ using default "editing one") also doesn't affect anything. and it's the same for all types of media (multicam clips, video/audio clips). also changing default media scaling to any option doesn't change a thing.

Mine is normally set to 'fit' ... which used to be "scale to" but they changed the verbiage.

Have not seen that one as my scaling is set default to NONE.

Should be fixed in public beta 25.0.1 build 31.

Make sure the tracks are source patched.