![]() ![]() Whether a "keyboard editor" or not, and regardless of physical disability, the ways to access playback functions are numerous even without the jog/shuttle controls of yesteryear. There are many different ways to locate the CTI at the frame, multi-frame, playback, reverse, fast playback and fast reverse levels using the mouse (dragging the CTI) the mouse wheel (scrolling and SHIFT+scrolling in the monitor), typing (using J/K/L or the arrow keys or the SHIFT+arrow keys, or space bar). I'd think that they'd be mousing around the timeline panel 90% of the time and rarely start grabbing an odd little wheel or rubber toggle. I used to say, "Get to Miller Time faster." Equating that faster speed equals the sooner you can get back to your real life!įor users who rarely use PPro, or aren't video people, then jog/shuttle are probably not the first thing they'd try to use. While training editors over the past decade, the goal in mind was to finish tasks more quickly and efficiently. Efficient means "Acting or producing effectively with a minimum of waste, expense, or unnecessary effort." Translation - faster is more efficient. My hope is that Premiere Pro will someday be able to do the same. You can edit blindingly fast, if you know all your shortcuts. So.one hand on keyboard, one on mouse for most efficient flow. It took a long time, but in FCP, I evolved into an all keyboard workflow with little or no mouse use.ĭespite all the improvements made for keyboard editors, you still can't escape using the mouse at some point in an NLE. That's the way I was trained too at Avid school. All keyboard shortcuts are under the left hand, the mouse is under the right hand. That part of the keyboard is under your left hand. While the JKL keys do much the same thing, the technique needs more explanation. I think the key is, the jog/shuttle controls needed little explanation to operate. Left and right arrows, previewing, subclips, etc.There is very little information about how to operate JKL properly out there on the web. I can, and hope to show others how they can too. Let go of the mouse button, and the overlay subtly fades away. How about middle mouse button support? There'd be a 'magic spot' in the UI somewhere that you place the cursor over, hold the middle mouse button, and an overlay appears on the UI to provide a 'scale' for your shuttling. JKL feels seriously unresponsive - I always to seems to shuttle too far either side of the points I'm looking to hit in footage. I could get through hours of footage like that, fast. I'd use the left and right arrow keys to get the out point frame perfect, hit O to set my out point, preview the edit with CTRL + SPACE, and finally hit ` (custom shortcut) to make a subclip. With the shuttle control in CS5, I could easily zip through minutes of footage at 3x speed (to get an overall feel for a scene), then slow down 1x speed (to watch the last few seconds), then to ~0.3x speed (to find my out point). ![]() Just to chime-in on the the whole JKL issue: JKL works, but the shuttle control gave you an intuitive speed control that was fluid, granular and efficient. It's not perfect, but JKL is the workaround for shuttle/jog comtrols and most people have found that quite acceptable once they get used to it.ĭavid, you can remap the 'J' 'K' and 'L' to be other keys in the 'Keyboard Shortcuts' dialog, so I would suggest trying that if it's simply a matter of key location. I do wish there was a way to still be able to bring the shuttle/jog UI and other retro funtionality back but the fact is that there's not. I was against these UI changes at first until I saw how much the higher-volume pro users needed them and how easily I could work around them with other methods. Streamlining the UI and enabling a more keyboard-driven workflow was our # 1 feature request for sometime. We try to enable these different user needs but of course we can t please everyone all the time. Our users have different speeds which they are comfortable at. To me that definition reads more like: 'work at a reasonable speed but don't be afraid to go a little slower at times to avoid dumb mistakes.'
0 Comments
Leave a Reply. |