its good to see that someone else can reproduce the problem, (ie im not going crazy).

I would have expected the default behaviour for Vegas to be 'retain last settings'.

cheers
jc

Yes!

G

This is a real pain in the butt!
You can I think do an attributes copy and paste but that will only work within the one project. Whats the point of being able to do a Save As on an fx with a new name when it doesn't save everything.

BTW this has been winged about before.

farss - yes, not having the Last Item would be good . . . what would be better, would at least tell me WHAT I'd done - yeah? Not saying whatever is a bit - putting it mildly - silly, for a Pro Package!

C'mon SonyV - get a grip! - pppoooarghhh that's strong for me . . .

Grazie

I just went to the main page and under SUPPORT selected PRODUCT SUGGESTION. and in the FEATURE you want to see box, put the URL to this thread to request an amendment to the default behaviour to retain last settings (or to atleast make it optional)

and also request SONY to post to this thread whether it is something they could do for the next VEGAS release.

If we get enough people posting it, they may take notice and do it.

post a message to this thread if you do it.

post here

. . jamcas . . I'm on the case NOW!

G

Somehow, you guys are using the preset incorrectly. Presets or chains that are saved will apply the exact same attributes every time. Even if you have different lengths of media and have keyframes saved, it will distribute those keyframes in relation to the longer or shorter media time.

SPOT - Fly that past me again - please? What I'd like to see is what I had "done" to a clip - nothing more, nothing less. What I get is the Default not what I've done . . but maybe, as you suggest, I'm somehow missing the point . .

Regards,

Grazie

What you get is the "Default" word listed in the drop down, however, the *values* of your previous setting (preset) are correct...yes? If yes, then program limitation, see below. If no, then serious bug. But I think the answer is yes. Please confirm.

What is happening is that Vegas is saving the values of the preset, but not the name of the preset. So when you open it again, the values are correct, but Vegas has no idea that it was a named preset, so it just displays "Default" for lack of anything better. This is a coding choice, but I agree it is an inferior one.

Would this be cool? Vegas saves the preset name, not the values, then if you change the preset values, everything that uses this preset gets updated to the new values. Like Styles in Microsoft word. But then you'd also want the ability to use a preset as a starting point for a particular case, then "disconnect" this case from the preset. And/or when you change the preset and save it, you'd also want the option to "apply to all" or not.

RMD - I'm going to give your response a lot of thought before I jump back with something . . . thank you for taking the time to collect your thoughts over this matter . . we'll get there . . . and yes, overall I do understand what you say . .

G

"What you get is the "Default" word listed in the drop down, however, the *values* of your previous setting (preset) are correct...yes? If yes, then program limitation, see below." - I'm not sure it does in fact show the applied numbers - I think I pushed up one of the values to 32, but I think it came back with 16 - not sure . . . .

If no, then serious bug. But I think the answer is yes. Please confirm. - I'll try and do this later, RMD.

I understand your 3rd paragraph - no problem with your explanation. Problem with it being inferior . . . .

"Would this be cool?" - This is fairly complex - I'm looking for whatever the clip had applied to it then that clip would:

1 - Show the name of the Preset , IF I had applied a Preset or one of my own
2 - The values would also be reflected allowinbg a starting point to "re-adjust".

Problem . . . .

The clip might have KFs applied to it as well. I suppose each KF would then have to reflect thos values and Presets for each and everyone of those KFs . . . . this is getting more complex than I thought . . .

Grazie

>Problem with it being inferior . . . .

To contradict myself, me too. (1) Its inferior because it reduces our options and doesn't give us control. (2) OTOH, its not inferior because it will definitely increase complexity and allow us to screw up easier, e.g., I could change a preset value, save it, then see a whole rash of changes I had forgotten about.

>"Would this be cool?"

Just as I value being able to change my styles in a Word document and see the global changes, I can see value in "global presets" being changed and updating in every place they are used. OTOH, that's why we can also apply FX to tracks and busses, rather than clips, so we already have an alternative workflow, arguably superior since it keeps complexity under control and lets us see clearly how our changes will propagate.

> KFs . . . . this is getting more complex than I thought . . .

Oops. Quite right.

Frankly, this is something I can definitely live without. Yes it is annoying that the previous applied preset name doesn't appear. (This gets me every time with the BroadcastColors filter; I can never remember which preset I applied, so I just wind up resetting it; monkey at a keyboard unfortunately :-) But its clearly a slippery slope to implement something useful *and* simple. I can imagine the SoFo engineers sitting around discussing this, then finally throwing up their hands and saying "hell with it". I don't fault them.

Yeah . . . but . . . isn't that why we went to the Moon?

G