Is it better to use Generic Remote or MIDI Remote for this?
I want it to be a fairly smooth and low speed control ideal to navigate the cursor to different sections of MIDI notes within a part before executing LE commands. I don’t want it for speeding past multiple bars at a time… but rather navigate within bar(s).
I’ve never used Touch OSC, but I did create a jog wheel and zoom in/out, and previous/next track setups on my controllers.
It involves using controllers where the “wheel” (or a knob) is able to send different note messages (repeatedly) depending if it was turned left or right. A more thorough description is on my blog: Not just for DJs: Native Instruments vintage controllers as Cubase MIDI Remote - eMXR.com Look for the section with the heading " The secret weapon: Click encoders".
p.s. I think with the MIDI Remote API, one could also program this with CC messages, but I think with the MIDI Remote GUI you need to use MIDI Note messages for that kind of thing.
p.p.s. However even on my pretty fast system turning the “jog wheel” too fast, seems to cause Cubase (I’m still running 14) to behave weirdly.
Interesting, thanks. I’ll have a look when I have the time.
Sounds like a bit of a “hack” (hence probably, the lag problems), was hoping for something a little more official/refined.
I think probably MIDI Remote has the more official amenities for this. Maybe @m.c knows (sorry to call on you now and then, you just seem to know everything… I might have some bucks coming your way soon)
I recall at some point I used the dedicated Jog Left/Right commands assigned to a knob, using scripting. The outcome was poor, and I remember I got a notice that these commands are optimised for qwerty use only.
With the recently added Direct Access object, we can now use the jog in a much better way, again with a knob assigned. However, in my tests here, I always notice some weird returns to previous positions, it’s not happening all the time, it’s kind of random and it mostly appears when turning fast. I didn’t really get into this behaviour, mostly because I don’t use this feature. At the same time, I don’t have a real Mackie here, in order to see how this one behaves with the MCU protocol, maybe I get one soon, for other testing purposes too.
I can provide a snippet for jog, I have no idea how this can get implemented using touchOsc.
Thanks for the response. I don’t use Jog often myself, but I have an idea to use it in conjunction with LE Scripts that use Before/After Cursor targets. ie I can have one hand hitting LE buttons on the Touchscreen, while jogging with the other with a virtual jog.
Maybe @Jochen_Trappe or one of the devs know what best jog wheel implementation is.
TouchOSC is free (start up 5 second timeout) if you care to explore
Since I’m at a stage of building something on my own, I don’t wish to see what others do in similar fields, simply because I need to stay completely focused on the implementation the way I find it best for the end user.
Probably it’s the one I’ve described earlier, and adopted already by some manufacturers However, it’s always nice to hear Jochen’s opinion on this.
However, it’s always nice to hear Jochen’s opinion on this.