If I understand your intention , you can use track motion and key frame, using the X and Y movement.

All I'm doing is just some panning and zooming on a large JPG.

It seems to me like a big disadvantage that the keyframes cannot be tied to such event - it's all so often that we want to move it around the timeline, or simply resize...

Think about this logically.
Yo're doing something to the EVENT. Move the event and logically what you are doing to it should move with the event. If you think of editing as being like a hierarchy such as a family tree it makes sense. Starting from the top you have Project>Buss(es)>Tracks>Events. Inheritance flows down from the top.
Where Vegas seems to break it's logical design is at the track level where keyframes are tied to the first event.

You could get around your problem with nesting although that many nested projects could be problematic.

Bob.

Bob,

When thinking about it logically, I'd say using "Track Motion" should be tied to the track, while "Event Pan/Crop" - to the event. I'm using the latter, hence the surprise...

So, should I just accept that "Vegas seems to break it's logical design", or am I still missing something?

Thanks,

Piotr

"So, should I just accept that "Vegas seems to break it's logical design", or am I still missing something?"

YES.

I just went back and tried this to refresh my memory. You're right, they way track keyframes behaves is wierd. Put some keyframes where there's no event on the track and they stay put UNTIL you slide an event over them. Then they 'stick' to that event and move with it. Also unlike Event keyframes you cannot select a group of them to reposition them.

It'd be good if we had some control over this behavior, combined with how keyframe are interpolated this is not something easy to grasp or work with. I've certainly been caught out by it more than once in the past.

Bob.

Bob, do you have "Lock envelopes to events" turned on? If you turn that off, track motion keyframes will not attach themselves to the events.

I do have "Lock envelopes to events" turned on. And indeed, the keyframes DO seem to be attached to events - except the first one !

For some reason, moving the first even in the timeline (e.g. to make room before it for another event) does NOT take its keyframes along - they seem to be attached to the timeline.

However, all events AFTER the first one behave as expected - i.e. when moved/reside, their keyframes DO follow.

Unless there is some logic behind it, we've just revealed another serious bug...