But for me it is just duplicating buttons that I already had. I really do think that it is an excellent device that could be helpfull to many people. Again, I can do that fine with shortcuts on my regular keyboard. I jump through my song through markers or by measures. I never felt the need to jog at all (why DO you guys jog?). What difference does it make if I push buttons on a further-away device that I might as well push on my keyboard? My hand is always closer to the PC keyboard than the Shuttle, so I right no it seems it can only make my workflow slower. I can trigger functions on it, but i might as well set a shortcut on my regular keyboard, or use the ones that is already there. I am not really convinced what it's value is (in sonar context). There are numurous times I say to myself that I should try and use it more often, but somehow it always wears down. I have one standing next to my keyboard as well. It is one of those things that bring un the proverbial "Swiss Army knife" definition. It takes about five seconds to change al port numbers. I've assigned it to the jog wheel and I just need to select the first port field and scroll down the list of 400 sysex banks with the wheel. I have programmed a macro in the Shuttle Pro that presses "P", for port, types the selected number, presses "enter", and then hits "down arrow" to jump to the next sysex bank. To name one silly application I've come up with, I haven't found a way to send midi bank dumps to my Waldorf MicroQ, because Sonar puts patches in Sysex View and the midi port defaults to 1, while the synth is always in another. You can reprogram it on the fly, without closing Sonar, and even have several different presets and choose them, and it keeps a macro library so it is very fast to assign one to a button if you have some infrequent task that would require it. I like it very much, but I do not really see it as a control surface, but rather a device to program sequences of keyboard shortcuts and key macros. I like it because you can program key macros, and you can program buttons to cycle through them as you press, so one, for instance, brings track view, and each time you press the button shows a different panel tab. Voilà! You now have a jog wheel which actually behaves like a jog wheel.I have one, I use it mostly to navigate through screen layouts, zooming and such. Now at the very most, no more than eight K keystrokes will queue up in the buffer which play out so fast as to be virtually unnoticeable. Now scroll down to the Transitions Left and Transitions Right section and configure it as in this example:Įffectively, as you return the wheel to its neutral position you immediately send out a K keystroke stopping the playhead dead in its tracks as it transitions back from zone to zone. Note that Shuttle Zone 0 is configured to send out a K keystroke. Twist the wheel left or right and as it transitions to the next zone, another single keystroke is sent out mimicking the behaviour of repeated taps of the J or L keys. The trick is to use J,K,and L keystrokes as in this example: There is a solution and, frankly, it's so blindingly obvious that I've just had to flog myself with wet broccoli for not figuring it out earlier.īy default, the jog wheel is configured thus: Meanwhile your playhead has scurried long past the point where it should really have stopped. This floods the keyboard buffer with excess events, and when you return the wheel to its neutral position, the keyboard buffer has to empty which can take several seconds. The reason is that it uses repeated frame left and frame right events () and does so at an increasing rate as you turn the jog wheel further. Anyone who uses the Contour Shuttle Pro edit controller (and you really should as it's an excellent bit of kit) will know that in its default configuration, the jog wheel is virtually useless.
0 Comments
Leave a Reply. |