Some other clip is in the way, and the sync locks are enabled, preventing a clip collision. Can you post a screenshot of your timeline panel where you're having the problem?
To add to Colin's request, be sure to show all used Tracks - both Audio and Video, and there will very, very likely be a Clip keeping everything from closing ranks, as desired.
Question for Colin: with CS5 and Track Targeting, if one ONLY has, say Video Track 1 Targeted, will the other Clips still affect this? Inquiring Minds [SIC] want to know.
Thanks and good luck to the OP,
PS - Colin, you are going to have me up to speed with CS5, since Curt's CiaB seems delayed a bit.
Actually, track targeting doesn't have any effect on drag-'n'-drop clip insertion or overwrite, and it doesn't effect ripple deletes, either. Rather, CS4 introduced the concept of sync locks, borrowed from Avid and FCP, as a means of tying tracks together for these operations:
They work--mostly. I actually don't think they're particularly well implemented in Premiere, to be honest. If I turn off the sync lock on a track I want to ripple, the rest of the tracks still ripple as well! This is wrong, I think. To get the functionality you'd expect, you have to turn off the sync locks on the OTHER tracks. Put simply: that's dumb. It should not work that way, but instead by turning off the sync lock on a particular track, I'm telling Premiere that only the "unlocked" clips should be free-floating. Maybe this is by design, but I think it's awful, clumsy, inefficient design. Reminds me to submit a bug report... err, feature request.
OK, back on track... pun intended
If I turn off the sync lock on a track I want to ripple, the rest of the tracks still ripple as well!
That seems right to me. With sync lock on, tracks should ripple. After all, they're synced! You turn it off for tracks you want to stay put (which would NOT be the track you're rippling.)
I disagree, but my experience with sync locks stems from my Avid years. I don't think the sync locks should necessarily dictate what happens when you ripple, but rather how a track or tracks move in relation to other tracks. I realize this seems like a semantic issue, but it's the key to my disappointment with how this feature works.
If I turn a sync lock off for a particular track, I expect it to be "unlocked" from the rest of the tracks when I move its clips, regardless of the sync lock status of any of the other tracks. If I have a sequence with 10 tracks, and I want to ripple just one of them, I want to toggle ONE switch instead of the other nine. This is how sync locks work in Avid, and I think it's a far more useful implementation--turning a track's sync lock off disengages it from the rest of the locked tracks. Moving a track's clips when its sync lock is on SHOULD affect all other tracks with the sync lock on, and this part Premiere does correctly.
Functionally, what Premiere is doing may be "correct" in regard to sync locks, but I think that practically, it's not useful.
Thank you for the information.
This sounds like a feature request
Reminds me to submit a bug report... err, feature request.
I want to toggle ONE switch instead of the other nine.
That's what the Track Select tool is for.
I mean, the very name says it all. Sync lock. You ripple, all clips locked also move, so they remain in sync. Doing it your way seems counterintuitive.
Hey I may have figured something out. It won't ripple delete because a ripple delete shifts the video as well as the audio. If the audio doesn't like up with the clips, it wont be able to peform the function. Just lock the audio track, and then perform Ripple Delete. Hope this helps.
This worked. Thank you oh mighty internet stranger.