This is a small problem, and it does bring some unnecessary clicks.

Maybe it would be nice to add a small clock button like OFX for Pan/Crop to enable/disable keyframe feature.

 

I can't be the only one this has been a thorn for since the early Vegas days?

Basically, I only enable/check the pan/crop Sync Cursor when I need to set two or more keyframes for that event or to initiate a keyframe that is intentionally not at the beginning of the event.

Probably you're the only one, because others like me and Dexcon only enable the Sync Cursor when needed (more than one keyframe at specific timeline position). The default is disabled for Sync Cursor and than Pan/crop behaves like you ask, only the first keyframe at position 00:00:00,00 is changed.

The only annoying thing is that Pan/crop remembers the setting of the Sync Cursor. So when you enable you have to disable again when not needing anymore.

The only annoying thing is that Pan/crop remembers the setting of the Sync Cursor. So when you enable you have to disable again when not needing anymore.

Oh yes! I can't count the number of times that I've enabled pan/crop Sync Cursor to do multi-keyframing, forget to disable it, and then do basic pan/crop reframing on a heap of following events only to find that they've taken effect mid-event rather than at 00:00:00. Grrr!

Perhaps an alert to Sync Cursor being active could be done similar to the way that Ripple has been highlighted (red timeline cursor and following timeline events being framed in red - which is excellent) by red framing the pan/crop window and pan/crop timeline cursor when Sync Cursor is active. But to be fair, the consequences of not disabling pan/crop's timeline cursor is considerably less than the mess-ups that can happen with Ripple mistakes.

>right-click the first keyframe and delete OR drag it over (or click it)

Or right click and change the keyframe mode to Hold

But to be fair, the consequences of not disabling pan/crop's timeline cursor is considerably less than the mess-ups that can happen with Ripple mistakes.

Rippling is also something I prefer to do manually (when needed and with the appropriate shortcuts) and not automatically.

Rippling is also something I prefer to do manually (when needed and with the appropriate shortcuts) and not automatically.

@3POINT  ... I'm a bit confused by this in that Rippling is done manually by moving an event L or R and all other events behind the highlighted moved event move simultaneously - depending on which of the three Ripple settings are chosen (i.e). Are there additonal shortcuts over and above the 3 Ripple choices that I'm clearly not aware of? Perhaps you're moving events by highlighting them and then just moving the highlighted grioup which, really, isn't using the Ripple feature to which I was referring.

@Dexcon I prefer to have Auto Rippling disabled. When moving or trimming an event on the timeline and when I want the following events to ripple this movement/trim, I just hit F (or CTRL+F or CTRL+SHIFT+F depending on the desired ripple mode) directly after the edit.

@3POINT  ... Thank you for that. I see what you mean - another Vegas Pro feature that I wasn't aware of. This could be very useful because it seems to avoid the possibility of errors by Auto Ripple remaining enabled when not wanted. I'll have to play with it a bit more to get used to it. Thanks again.

@Dexcon Such valuable tips can also be found in the online help:

 

I can't be the only one this has been a thorn for since the early Vegas days?

Basically, I only enable/check the pan/crop Sync Cursor when I need to set two or more keyframes for that event or to initiate a keyframe that is intentionally not at the beginning of the event.

Probably you're the only one, because others like me and Dexcon only enable the Sync Cursor when needed (more than one keyframe at specific timeline position). The default is disabled for Sync Cursor and than Pan/crop behaves like you ask, only the first keyframe at position 00:00:00,00 is changed.

The only annoying thing is that Pan/crop remembers the setting of the Sync Cursor. So when you enable you have to disable again when not needing anymore.

Hmm.. I do keep my sync cursor enabled.. me thinks my default will be disabled.

So odd.. before posting this Q I turned off the sync cursor option, closed my pan/crop window, went to the middle of a timeline event, pan/crop button and the cursor was mid-event in that window ( not at the start). I presumed changing the crop would then insert a key frame at that point.. maybe I was wrong! A wonderful mistake? 🤗 (only 15 years using Vegas near-daily and still more to learn lol)

Either way then, a good discussion by this group with the CTRL-F tip emerging and helping some.

I'll check it out and hopefully this one is "closed".. thanks everyone!

UPDATE: I wasn't completely off when I thought unchecking the "Sync Cursor" didn't solve the problem. It does, but there's a quirk that makes it unobvious.

When Sync Cursor is unchecked, the Pan/Crop keyframe position will be wherever it was last time the Pan/Crop was used. IF that happened to be the start of the Pan/Crop keyframe timeline then indeed the first keyframe will be the one affected by a change. But IF it happened to be in the middle of the Pan/Crop timeline, then a new point will be created.

For someone who turns it on sometimes, and off other times, they'll still need to remember to click at the beginning after turning it off. ** EDIT * Sometimes it seems to be where it was last clicked or last keyframe placed when opening -- other times back at the beginning.

NEW WORDING to the ENHANCEMENT REQUEST:

When the "Sync Cursor" button is first ticked off in the Pan/Crop dialog, automatically move the pan/crop playhead to the beginning of the pan/crop timeline (first keyframe).