Hi,
I'm in the middle of a larger project that is suddenly behaving very strangely.
It consists of source from two DV (AVI) cams, synced manually, on two tracks, and only one additional audio track. I still do not fancy the multicamera mode since I want to keep all tracks separate during the whole project, instead of letting it combine everything as takes on one track...
During the syncing I used the track motion to halve the size of both tracks, and placed them side by side in the output (for easier vievwing of both - during syncing). This is a method I use often and before, without any problems in earlier versions of Vegas.
After the sync and most of the cuts between A/B I kept both source on separate tracks, and returned the track preview to normal size.
ThenI contunued the editing. Suddenly the track motion does not do anything (both tracks behaving the same). Whatever track motion I set the output of the track just stays at the default. An much earlier saved version of the project lets me use track motion without a problem.
Is there somewhere an override for the track motion? Why does it not suddenly work? This drives me nuts...
Running Vegas Pro 9.0e (32-bit - mainly due to lacking 64 bit FX support) on an WIN7 64 bit quad core with 8Gbyte DDR3 ram.
Anyone else seem similar behavior? Is there a solution? Can a project be corrupt so that the track motion gets dysfunctional?
Cheers,
Christian
EDIT: I found the problem. Somehow there had sneaked in an additional key frame, one frame later than the first frame, in both track motion windows. This is rather hard to spot, since you have really to zoom in very far to see that there are two diamond shaper object on the track motion timeline.
I am a little confused about how they got there in the first place. I have not a single time during this project used the "sync cursor" function in the track motion mode. It is often the culprit if you forget it selected.... Swear that I have not caused these additional key frames. One proof is that BOTH tracks had these additional key frames exactly at the same location at the very beginning of the track (1st and 2nd frames)... Very odd...
I'm in the middle of a larger project that is suddenly behaving very strangely.
It consists of source from two DV (AVI) cams, synced manually, on two tracks, and only one additional audio track. I still do not fancy the multicamera mode since I want to keep all tracks separate during the whole project, instead of letting it combine everything as takes on one track...
During the syncing I used the track motion to halve the size of both tracks, and placed them side by side in the output (for easier vievwing of both - during syncing). This is a method I use often and before, without any problems in earlier versions of Vegas.
After the sync and most of the cuts between A/B I kept both source on separate tracks, and returned the track preview to normal size.
ThenI contunued the editing. Suddenly the track motion does not do anything (both tracks behaving the same). Whatever track motion I set the output of the track just stays at the default. An much earlier saved version of the project lets me use track motion without a problem.
Is there somewhere an override for the track motion? Why does it not suddenly work? This drives me nuts...
Running Vegas Pro 9.0e (32-bit - mainly due to lacking 64 bit FX support) on an WIN7 64 bit quad core with 8Gbyte DDR3 ram.
Anyone else seem similar behavior? Is there a solution? Can a project be corrupt so that the track motion gets dysfunctional?
Cheers,
Christian
EDIT: I found the problem. Somehow there had sneaked in an additional key frame, one frame later than the first frame, in both track motion windows. This is rather hard to spot, since you have really to zoom in very far to see that there are two diamond shaper object on the track motion timeline.
I am a little confused about how they got there in the first place. I have not a single time during this project used the "sync cursor" function in the track motion mode. It is often the culprit if you forget it selected.... Swear that I have not caused these additional key frames. One proof is that BOTH tracks had these additional key frames exactly at the same location at the very beginning of the track (1st and 2nd frames)... Very odd...
