Automating the Joystick

Post a reply


This question is a means of preventing automated form submissions by spambots.
Smilies
:D :) :( :o :shock: :? 8) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :!: :?: :idea: :arrow: :| :mrgreen:
BBCode is ON
[img] is ON
[url] is ON
Smilies are ON
Topic review
   

If you wish to attach one or more files enter the details below.

Maximum filesize per attachment: 25 MiB.

Expand view Topic review: Automating the Joystick

Re: Automating the Joystick

by John Bowen » Fri Mar 31, 2017 11:50 pm

The joystick info was not being received by the Solaris is any OS prior to v1.3, so please update to get this functioning!

Re: Automating the Joystick

by valis » Tue Sep 03, 2013 4:20 am

So I'm curious, if the X/Y is sending NRPN's what is the resolution? If greater than 128 steps and you assign CC1 > CC16 to achieve similar control, is a slew limiter necessary to smooth param jumps?

Re: Automating the Joystick

by Toby Emerson » Mon Jul 29, 2013 3:48 pm

In the meantime I have found a workaround which works pretty well (just an extra step of linking). I used CC1 in the modulation source to link the parameters I want and then in the MIDI page on the main screen I just set CC1 to 16.

Re: Automating the Joystick

by John Bowen » Sun Jul 28, 2013 3:11 pm

Toby,

I'm not sure if the standard CCs other than Pitch Bend (which is a sort of 'special' controller number) are being implemented, because of the NRPN approach to MIDI data communication. I'll have to ask Julian.

Automating the Joystick

by Toby Emerson » Sat Jul 27, 2013 7:05 pm

So I'm really liking assigning parameters to the joystick for control and am trying to automate the X and Y axis in my DAW.

It appears JoyX and JoyY are general purpose controllers 1 & 2 (CC16 & 17?) however that doesn't seem to be working. I seem to be able to automate the mod wheel CC1 fine - anyone know if I am doing something wrong or have some ideas?

Cheers

Top