Comments

SonyDennis wrote on 8/5/2002, 5:43 PM
jetdv:

Right-click, "Add Point" shouldn't cause anything to move, just a new point to be created. Can you elaborate? I'd like to learn more about what you're seeing, perhaps include numerical readouts from the tooltips.

Is it just the double-click case that is bugging everyone? We can make it that a double-click won't drag the point afterwards, so a "messy" double-click shouldn't move the point. A Shift+click will still let you move the point. Right-click, Add, as I said above, doesn't do any moving. If the first click of a double-click moves between mouse down and mouse up, that will move the existing segment. Is that what people are seeing? Which points, exactly, are moving?

Thanks.
///d@
BarryB wrote on 8/5/2002, 6:05 PM
You can always right click and choose "add point" from the dropdown menu, and even type in a numeric value for more precise control.
Former user wrote on 8/5/2002, 6:18 PM
SonicDennis,

On mine, when I right click and ADD POINT, it creates a node. The node has altered the audio level. If I hover the mouse over the node (without moving) it shows .8 db. This is just a right click, add. No manipulation.

I did it a second time, and this time the level was .5 db. Same process, no moving.

If I enlarge the track, then the offset is less. Only .1db when added. Could this be related to screen resolution? I run at 1024x768.
Dave T2
SonyDennis wrote on 8/5/2002, 6:30 PM
Oh, would you look at that! It's using the mouse position instead of the y-intersect of the envelope. I'll fix that too. Also, I figured out a solution for the possible segment drag on the first click of a double-click style add. Thanks for your input.
///d@
Former user wrote on 8/5/2002, 6:59 PM
Man, that was fast. I am impressed!!!

Dave T2
SonyDennis wrote on 8/6/2002, 11:24 AM
I did some more research on this, and it's just the right-click "Add Point" method that's not compensating for the distance from the cursor to the line. If you double-click or Shift+click, you'll get a point closer to the actual line. Even in those cases, there were some small inaccuracies, when the line's value was not aligned with a pixel coordinate. I've changed it so that new points will always be created at an accurate y-intercept of the existing envelope, so that in a future version, all three methods will work equally well. Also, I added some additional logic so it won't adjust the position of a point during a "messy" double-click. Thanks for all your feedback on this issue. If we do a Vegas 3.0d, this will be in there, otherwise in VV4. It will also be in ACID4.
///d@
jetdv wrote on 8/6/2002, 11:59 AM
Thank you for this change. It WILL be appreciated.
SHTUNOT wrote on 8/6/2002, 12:20 PM
Thanks very much dude!!!