I hope I'm wording this problem correctly. I used to be able to click and drag a clip (or end points of a clip) and then move that on a timeline to see the result live while editing. Now I cannot see what happens when moving a clip (or dragging endpoints) until after I release the mouse click.
Here is another way of wording the problem.
I would click the mouse on a clip and then drag it on the timeline to a new position. During this I would see in real time the arrangement of the clip to make a choice about how far I want to move the clip. Now I cannot see the patch of the clip on the timeline. I need to release the clip to see the movement. This is annoying because the movements are not as precise. I have to drag the clips multiple times to see the result. This same problem goes for selecting in or out points of a clip on the timeline.
I cannot see any preferences to change the way I view movement of clips on the timeline.
This problem started with the new update a few days ago.
That's super weird! I bet it's really frustrating to not be able to see where the clip is going. Have you tried resetting your preferences?
Nothing will happen to your project, but it'll reset some of the program's behaviors.
Let me know if that helps!
I believe Premiere Pro is working better now. I also had weird instances of markers not being applied to the correct spot of a clip when I applied them. I think trashing preferences helped with that issue too.
This problem started up again about two weeks after clearing preferences. I cleared cache and previews today. Maybe something positive happens?
When I switched from the Move Tool (V) to another tool the cursor doesn't change the shape to match the new tool.
I have this same problem! The playhead starts flashing and I start seeing unusual behavior, including the one the original poster mentioned - I can't see clips as I'm moving them or edit points as I'm trimming them. For me, the problem seems to only occur in projects where I'm using multicam clips. Is this the case for you?
Same experience for me - seems to only occur for my when I'm working with nested multicam sequences.
So, the one thing that usually works for me in instances like this is to check to see if there is an update for Premiere Pro. For whatever reason, the program starts acting stupid and does all sorts of useless and random bullhonkey when it's time to update. This was happening to me and I just fixed it by updating, but maybe it's just resetting the preferences as Caroline said. Nice work, Adobe. An update reminder might be nice, instead of trying to make us feel insane.
I've noticed this happens on occasion for me, but can usually be fixed by closing and opening the program again. Really annoying tho.
I fixed this by going to Window > Workspaces > Reset to Saved Layout!
I've got this same problem, and I can't shake it. I've done everything. Including uninstalling/installing. How has this been a a bug for more than two years?
I have the same issue. What is going on with this software?
it sucks is what's up with it
Yep. Same for me as well. I've reset the preferences but it did nothing to fix this behavior. This really sucks. Hard to place things correctly.
I've solved it removing all the nested clip: I've opened each nested sequence and I copy the clips insiede it, pasting in the timeline in place of the nested clip.
I hope it may solve your problem too.
Yes seen this too: deleted just the audio in the nested clips.
That worked, thanks Ann!
Thank you so much this worked for me
it works for me too but it's not a solution, i need that clip !
Thank you very much for your fix Ann.
any chance of the bug getting fixed anytime soon?
Thankyou! this worked for me, its been driving me nuts!
yes I had the same problem and the problem was is that I was nesting audio files
so I went ahead and render out just the audio files by themselves and then put them back in Adobe Premiere delete the ones that was nested, and problem solved after I deleted the nested files..
That's not "solved" — it's an annoying work-around to a problem that shouldn't be happening. It'll be solved when Adobe fixes it so it doesn't happen again.