Moving Frame By Frame with Arrow Keys in VP10

losinglegend wrote on 11/27/2017, 6:32 AM

Hello,

I recently got a new computer and had to re-install Vegas Pro 10. Previously when in the "Edit Video FX" screen, I was able to move frame by frame when using the arrow keys. Now, it moves at some odd increment (usually takes 2 to 3 arrow key movements to move 1 frame, depending on how far i'm zoomed in and how big the media i'm editing is). Does anyone have any ideas as to why this is happening? I understand that by holding alt + arrow key you can move frame by frame, but that only applies to the track and the "Edit Pan/Crop" screen. When trying to use alt + arrow key on the "Edit Video FX" screen, the cursor will not move. I've tried re-installing VP10 and reset everything to default, but nothing has worked.

Any ideas? Anything is appreciated, i've tried a whole lot of stuff by looking at forums and looked through settings for hours but nothing seems to be doing the trick. This is just super annoying because the type of editing I do requires me to move frame by frame in both pan/crop and video fx but only editing video fx does not allow me to move frame by frame when using the arrow keys.

Comments

vkmast wrote on 11/27/2017, 7:34 AM

Did you "select the Sync Cursor button to synchronize the cursor positions on the main timeline and Keyframe Controller timeline"?

losinglegend wrote on 11/27/2017, 7:41 AM

Did you "select the Sync Cursor button to synchronize the cursor positions on the main timeline and Keyframe Controller timeline"?

Yes, I have that selected. That only keeps the cursor in sync with the timeline, but it doesn't control the keyframe spacing with the arrow keys. If i move the arrow keys, the cursor on the timeline will move but it will move at the amount I was explaining before, not frame by frame.

vkmast wrote on 11/27/2017, 9:10 AM

The right/left arrows work for me in the Video FX window, though somewhat intermittently it seems. (VPro 10e build 737 32bit). Are you not able to use the arrow keys for what you want to do with keyframing when focus is set to timeline?

(edit: corrected the build number)

Former user wrote on 11/27/2017, 9:12 AM

I don't know why they aren't working in the Video FX window, but you should be able to change the timeline to arrows for right and left frame by going to Preferences>Keyboard shortcuts

losinglegend wrote on 11/27/2017, 9:20 AM

The right/left arrows work for me in the Video FX window, though somewhat intermittently it seems. (VPro 10e build 373 32bit). Are you not able to use the arrow keys for what you want to do with keyframing when focus is set to timeline?

The arrow keys work fine for me as well, but I want the left and right arrow keys to move 1 frame exactly, like how they do in the timeline (when zoomed in properly) and the pan/crop screen. Pressing the left or right arrow keys seem to move 1/2 or 1/3 of a frame in the video fx screen no matter how far I zoom in or out when editing fx keyframes.

vkmast wrote on 11/27/2017, 9:30 AM

Pressing the left or right arrow keys seem to move 1/2 or 1/3 of a frame in the video fx screen no matter how far I zoom in or out when editing fx keyframes.

I could not replicate that as they moved 1/1 of a frame.

losinglegend wrote on 11/27/2017, 9:35 AM

Pressing the left or right arrow keys seem to move 1/2 or 1/3 of a frame in the video fx screen no matter how far I zoom in or out when editing fx keyframes.

I could not replicate that as they moved 1/1 of a frame.

That is exactly what I want the arrow keys to do but they seem to not want to do that. I have checked so many settings and have just run out of ideas.

vkmast wrote on 11/27/2017, 9:48 AM

Are you on the last build of VPro 10? Quantize to Frames selected?

john_dennis wrote on 11/27/2017, 9:52 AM

[wild stab in the dark]

Is your project properties frame rate set equal to the frame rate of the media on the time line?

[/wild stab in the dark]

losinglegend wrote on 11/27/2017, 9:57 AM

[wild stab in the dark]

Is your project properties frame rate set equal to the frame rate of the media on the time line?

[/wild stab in the dark]

No. The project media is in 60 fps and the project is in 30 fps.

However, this was never an issue as this is the media is the same kind of media that I was editing before I had to re-install VP10 and started experiencing these issues.

losinglegend wrote on 11/27/2017, 10:03 AM

Are you on the last build of VPro 10? Quantize to Frames selected?

Quantize to frames is selected.

I am on version 10d build 670. Most likely I was using an earlier build before I re-installed.

Marco. wrote on 11/27/2017, 10:04 AM

This is strange. The only case where I'm able to repro this behaviour is with Quantize to Frames being deselected.

losinglegend wrote on 11/27/2017, 10:48 AM

This is strange. The only case where I'm able to repro this behaviour is with Quantize to Frames being deselected.

I'm absolutely stumped. Hopefully it's just something silly but i've never had this issue in the past and i've used both VP10 and VP9.

john_dennis wrote on 11/27/2017, 12:08 PM

The final build for Vegas 10 was 10.0e Build 738.

 

losinglegend wrote on 11/29/2017, 5:18 AM

The final build for Vegas 10 was 10.0e Build 738.

 

John,

Do you happen to have the .exe for this build? I do not have it as the .exe file I had was for 10d.

vkmast wrote on 11/29/2017, 5:53 AM

https://www.vegascreativesoftware.info/us/forum/faq-where-can-i-download-vegas-pro-and-other-vegas-software--104782/

4. MAGIX DOWNLOAD CENTER

Your software can also be downloaded by entering your serial number(s) at the MAGIX Download Center

See also point 3. there..

losinglegend wrote on 11/29/2017, 5:56 AM

https://www.vegascreativesoftware.info/us/forum/faq-where-can-i-download-vegas-pro-and-other-vegas-software--104782/

4. MAGIX DOWNLOAD CENTER

Your software can also be downloaded by entering your serial number(s) at the MAGIX Download Center

See also point 3. there..

Thank you very much! I will try using this build of VP10 and see if it helps.

losinglegend wrote on 11/29/2017, 6:05 AM

Using the latest build was the solution to the problem. Thank you everyone for your help everyone.