Brickwad:

jwrl:

As far as that goes, is the problem really Advanced Keyframe mode, or just the lack of keyframes?

There is also a difference when moving keyframes, Advanced mode sometimes makes things difficult by only moving one out of a set of keyframes. Add a bundle clicks and some ctrl+z when this happens.

editor11HD:

...allowing keyframes that have been CUT OUT of a cilp somehow remain out in the ether to behave like small moons exerting a undesired gravitional effect on my scale or position sliders...

I hearby nominate this sentence for the 2011 Avid Community Forum Simile of the Year Award™.  Well done, sir.

daapap:

...i can decide very well wether advanced keyframe mode is needed or not!  and i still do not hear any argument clarifying why it is like this now.

I read in one of the "we all hate MC5 keyframes" threads that it has something to do with lowering the amount of RAM in use.  As I recall (can't find the thread, so maybe I've got it wrong), each keyframe on a parameter eats up a little memory, so when you add a keyframe to the Z position parameter on a 3d Warp (for example) in "classic" mode, you're eating up more memory than you'd think, because even though you're only doing a simple move in Z space, "classic" keyframe mode adds keyframes to every other parameter, too.

With Advanced Keyframes, when you add keyframes to the Z position to do a 3d Warp Z space move, you're only adding them to the Z position parameter; all the parameters you haven't adjusted remain keyframe free, using up less memory.

I look forward to all the "that's a stupid way to design software, I'd do it by ________" and "RAM is cheap and when MC goes 64-bit this won't be a problem; put it back the way it was" responses.  

ciao,
Carl 

camoscato:

I look forward to all the "that's a stupid way to design software, I'd do it by ________" and "RAM is cheap and when MC goes 64-bit this won't be a problem; put it back the way it was" responses.  

Hi Carl,

There's nothing wrong with that, although personally, I'd leave the stiupid part out . .Give us the choice of whether to use RAM, or not use Ram. Go back to choice. Repeal Keyframe-a-care!! I would like to use my RAM as I see fit.

You forgot "You can have my RAM when you take it from my cold, dead hands."  :)

camoscato:

You forgot "You can have my RAM when you take it from my cold, dead hands."  :)

I think somebody already said that about simple keyframes . . .

Brickwad:

camoscato:

You forgot "You can have my RAM when you take it from my cold, dead hands."  :)

I think somebody already said that about simple keyframes . . .

...and dongles!

I would like to add some more flammable liquid to the fire here, if I may. What would be helpful is the following option: If there are no keyframes and you are not at the head frame of the segment, adding a keyframe would add a keyframe at the frame you are parked on and also to the starting keyframe. While adding two keyframes may sound like even more lunacy, it actually makes sense, to me anyway, LOL! Here me out :)...

Having one keyframe for a parameter does literally nothing; it needs another keyframe to work in opposition with. Put another way, changing the value of a keyframe when there is only one keyframe is exactly the same as changing the value of the parameter when there are no keyframes.

So adding a starting keyframe as well makes sense b/c b/c it gives the keyframe you've just added another keyframe to work in opposition with.

BobbyMurcerFan:

adding a starting keyframe as well makes sense b/c it gives the keyframe you've just added another keyframe to work in opposition with.

Next to the restoration of the 'classic' mode, this the best suggestion I've heard yet!

agreed.

Has this been fixed in 6.5? What took me literally under 5 seconds now takes a lot longer. I can't just click on my Add Keyframe hotkey even in keyfram graph view. Annoying.

Videojon:

I'm running 6.5 and am not having issues adding keyframes using my keyboard shortcut or mouse clicking either in the effects editor advanced timelines, the graphs, or under the effects monitor window. Is there something else you're referring to that I'm missing?

For example, when I used to apply a PIP, I was able to click the Add keyframe button (or in my case, hit the keystroke) in the effects window and it would add a keyframe. Now I'm finding myself having to go into the keyframe graph mode, and click on an actual parameter (similar to AE) then click my keyframe button for each desired parameter change. It was so much quicker last time to be able to apply a keyframe in the effects monitor window and then adjusting the movements.

Larry Rubin:

Videojon:

I'm running 6.5 and am not having issues adding keyframes using my keyboard shortcut or mouse clicking either in the effects editor advanced timelines, the graphs, or under the effects monitor window. Is there something else you're referring to that I'm missing?

I understand where you're coming from and using the advanced keyframer takes some getting used to because you're now working with keyframe modes, but here's how I handle it. Let's use 3D warp as an example. I apply a 3D warp effect and then in the advanced keyframer, I right click on the keyframe button and select "Add Keyframes to Enabled Group". (If you don't see the various keyframe options, enable "Show Add Keyframe Mode Menu). Now, I click on the various parameter panes I intend to use, like scaling, position, border, shadow, etc., then add keyframes. As you'll see, there are several modes to choose from regarding how keyframes are created, including open graphs.

And, IMO, working with the wireframe icon tools on the right column of the effects editor is the easiest, fastest and most efficient way to adjust parameters. Hold down ALT (OPTION on Mac) while adjusting for realtime updating.

Oddly enough, it's working how it should now. I think I played with a setting. Now and then, if I go back and change a keyframe parameter in the effect composer window, the video jumps, immediately after that frame. When I delete that keyframe, there's a keyframe underneath it which is causing the jump. I have to recreate the keyframe. Bottom line is that it's still funky now and then but at least it seems to be working again.

Thanks