Move Event using Arrow Keys - I get an "UNDO"?

Grazie wrote on 6/21/2012, 2:06 AM

Title says all.

I can drag NORTH - np.

I can drag SOUTH - np.

But when I try and use the arrow keys on the Numeric kp, VP11 believes I want to do an UNDO, and spends 5 minutes thinking about it, and then I get the WHITEOUT and an opportunity to "PhoneHome".

Standard PAL project. Done this a gazillion times before.

Media Manager - OFF

DRP - 64mb (I have 16gb RAM!)

GraphAccel - OFF

Trimmer = Cleaned

Bins = Cleaned

Cheers

G

Comments

ushere wrote on 6/21/2012, 4:10 AM

not down here grazie. all according to plan.

john_dennis wrote on 6/21/2012, 8:59 AM

Working as designed in the USA.

diverG wrote on 6/21/2012, 1:28 PM

Learn something new everyday. I usually drag & drop.

Nunlock 'On'. Works perfectly up here in Warwick.

I think my pc rather similar to yours.

One of the pleasures of using VP11.

Geoff

Former user wrote on 6/21/2012, 8:28 PM

I don't get an UNDO but I get a REDO

Try this. Select an event on the lower video track and move it up using the NUM Arrow UP Key, now hit the same key a few more times.

Now hit the down key, I am finding that I have to hit the down key as many times as I hit the UP key to get it to move again, and the REDO arrow is highlighting each time.

EDIT: got it to work correctly by turning OFF lock envelopes to events.

So if you leave LOCK ENVELOPES TO EVENTS on like I do, then you get a weird Arrow up command that will perform a REDO when repeated.

Dave T2

Grazie wrote on 6/21/2012, 11:04 PM

Thanks Dave. Bizarre and unexpected behaviour.

I found that having the Video Events needing to vertically "transverse" existing Audio Track with/without an Audio Event in the way or NOT, I'd get this UNDO request.

I've been using VP for 10 years, and it's when I stumble on unexpected outcomes like this I write them up here.

Cheers

Grazie

FilmingPhotoGuy wrote on 6/21/2012, 11:55 PM

Working fine for me.

Check keyboard config in crontrol panel or if you like me change some hotkey configs inside Vegas.

farss wrote on 6/22/2012, 7:36 AM

You might have stumbled upon something I complained about long ago.
Somewhere along the way and I don't recall exactly where now, moving tracks up/down went from being easy to being like pushing them through treacle. 80% of the time the Click didn't select and even when it did they just wouldn't budge and this was using the mouse.

The other problem I've noticed with Vegas is it can go off to do its "thing" and appear breifly unresponsive. We (the user) keep hammering away on the keyboard / mouse and those commands queue up in a buffer. Vegas finishes whatever it went backstage to do and then tries to catchup with the backlog of user input. Problem is while is this is happening the user is acting upon a state of Vegas that is changing as the previous requests are being processed and the whole thing becomes a mess or falls over.

Now,... I've developed an aversion to doing anything too quickly with Vegas that prevents this from happening. I suspect others are not so patient or haven't developed the same aversion which was in part forged in the fires of me having an ancient, slow, C2D CPU. It'll be interesting to see how I go with Vegas on my new 6 core monsta :)

Bob.