saving keyframes...

Active wrote on 9/6/2002, 8:50 AM
we have a created a pic in pic effect using the motion tracking, our image moves from left to the top and then off to the right using 4 keyframes.

I want to save this effect for use on other clips/projects, if i rename the fx and then click save it saves it, however if i go to use the effect on another clip the only thing it has saved is the very last keyframe !!!!

any ideas ??

GLEN.

Comments

SonyDennis wrote on 9/6/2002, 10:06 AM
You can copy/paste the keyframes themselves to paste into the new copy of the effect.
///d@
Active wrote on 9/6/2002, 10:37 AM
true, but if i exit vv3 and reboot and want to use the same effect again on a different project the full effect with keyframes will not be there !!!!!

are there any workarounds for this ?

Glen.
bcbarnes wrote on 9/6/2002, 12:21 PM
Copy the effect as described above, then create a new project and paste the effect in, and then save the project.

Now, whenever you need that effect, you can easily open that project in a second instance of VV3 (while continuing to edit in the first instance) and copy the effect, then go back to your first instance, and paste it in.

You can save all kinds of stuff, not just keyframe effects, this way. I believe I read about this from someone else, so it isn't my original idea.
ibliss wrote on 9/6/2002, 1:48 PM
Glen, here's the link to the tutorial I posted in the forums - hope it helps.

http://www.sonicfoundry.com/forums/ShowMessage.asp?Forum=4&MessageID=101977

(copy and paste it into the address bar.)

Mike K
jetdv wrote on 9/6/2002, 2:35 PM
OR:

http://www.sonicfoundry.com/forums/ShowMessage.asp?Forum=4&MessageID=101977



Links are MUCH easier to use if they are simple clicks.
swarrine wrote on 9/6/2002, 10:16 PM
I believe what Glen wants is to be able to save as a preset including keyframes. Why else would there be a save button? Unfortunately, you can not Glen.

You can save to another veg file and then recall it by opening that veg and copy/paste to the one you are working on, la di da - it is a bogus workaround, however it does work. There is a bunch of stuff like this which I hope will be addressed in VV4.

SF/VV3 policy is to only correct bugs. Design flaws have to wait for the next generation. Having said that, VV3 (IMHO) is the best DV software available despite the quirks.
magicman wrote on 9/7/2002, 9:12 PM
So what is the keyframe save button (or any effects save button) good for in this version?
shaunn wrote on 9/8/2002, 9:24 AM
[SF/VV3 policy is to only correct bugs. Design flaws have to wait for the next generation.]

Saving keyframes in my opinion should be implemented in an future update (VV3d?) I still don't understand Sf stand on this. Ok they kill out the bugs first, fine... but not to add any improvements at all seem weird...and stingy
For example the "media management" issue of VV3, this is one of the worst and foremost critizism VV3 gets from the crowd...Wouldn't it be simpler to fix this design flaw right away then holding up because they want to implement it in VV4 and ahem charge for an upgrade!?!?
A simple BIN solution would help a great deal!

This really doesn't seem like asking for much, please sofo change some codes and let us be able to save keyframes in pan/crop - FX - and track motion to a specific media or preset

At least please explain why aren't you going to do it in VV3?

PS: sorry for my tone, just trying to be straightforward.



Tyler.Durden wrote on 9/8/2002, 10:40 AM
Speakin for myself...

Say I would like to save TM keyframes, event keyframes, presets and FX:

I might actually make some folders on my drives like Presets, TM Keyframes, Event keyframes, and FX and save those elements in their respective folders.

I can do that now, but they are not called: .tkf, .ekf, .efx, .ept or whatever, they are all called .veg files.


I would like to see other issues higher on the priority list... Issues that currently have no provision, like saving rendering templates and edl.


It took some time for me to accept that an additional instance of Vegas is a very legitimate feature that is useful for many needs. When I consider what the accomodation of these needs would look like within one instance, I imagine a myriad of sub-menus or dialogues that are for one limited use; rather than using a flexible, known process that can fulfill numerous needs in the same fashion and even in the same operation. i.e. saving fx, presets, keyframes in the same file.


(soapbox)
I think for software so young, the depth of concept and implementation in Vegas is nothing short of awesome. What SoFo could stand is more complimentary publicity to garner more sales... *That* will certainly fuel the engine of development faster than a litany of gripes.


My .02, MPH


fongaboo wrote on 9/8/2002, 11:38 AM
I also think there should be some way to make adjustments that apply to multiple keyframes. My worst-case scenario was this:

I made a video that had narration at the beginning of each segment. But I had a .PSD of a cartoon character who was supposed to be the source of the narration. I very simply made the character 'talk' by making the him zoom forward and backward on the Z-axis in time with the narration. The idea was to make him surge forward and retract really quick in time with the speech in a motion similar to a speaker cone. (You can see the video at www.twistedpairvisuals.com)

This endeavor was most tedious to begin with: I had to meticulously look for each and every peak in the soundfile of the narration track and place a keyframe there. This took me quite some time to do, but there's nothing really to help that. The problem came in later, though, when my partner asked that the character should be raised up slightly on the Y-axis. This involved me having to adjust the Y value of a good thousand keyframes. I had no choice but to sit for an hour or two selecting and pasting values into each and every keyframe.

It'd be nice if there was a way to select multiple keyframes and then tell VV to apply an offset of a certain value to every keyframe. If this had existed, the afforementioned task would have taken me about 5 seconds.