MIDI Maker Sparrow - How to set this up in Studio One?

[Crescendo]

I recently acquired a MIDI Maker Sparrow fader box.
It looks like I can program it to where certain instruments respond to it, but it never works globally on all instruments.
E.g. If I set one fader to CC1 it does not move the mod wheel data on just any virtual instrument, but I have to program it in cumbersome ways within Studio One - how can I have this work globally (like all my MIDI keyboard controllers do)?
Any help appreciated!

 

[Trucky]

Welcome to the Forum!

Please update your signature (see link and example in mine) with your system specs.
This helps us when responding to what may be causing your issue(s)...

Have you contacted MIDI Maker support yet? MIDI Maker Support

 

[OutrageProductions]

I have the Sparrow 3 and it works on almost all my VSTi's without fail.. BUT I do not have any assignments to CC1 (my controller has a mod wheel). I use CC11, 14 and 23 (? IIRC).

 

[Crescendo]

I have the Sparrow 3 and it works on almost all my VSTi's without fail.. BUT I do not have any assignments to CC1 (my controller has a mod wheel). I use CC11, 14 and 23 (? IIRC).

How did you set it up? Do the encoded CC values on the faders propagate through various plugins within S1 without individual configuration of each VI?

 

[Crescendo]

Welcome to the Forum!

Thanks!

Have you contacted MIDI Maker support yet? MIDI Maker Support

I contacted them. No reply yet. I thought maybe someone here has experience with it.

 

[apessino]

How did you set it up? Do the encoded CC values on the faders propagate through various plugins within S1 without individual configuration of each VI?

Assuming you have setup a "control surface" external device (which I assume you did since you see the device working in some form), then all you should need is to have the MIDI/instrument track hosting the plugin set to "all inputs" (or just the fader device if that's all you want to record) and you will get whatever MIDI CCs the unit sends read and recorded. Most plugins (at least samplers and synthesizers such as Kontakt, SINE or Serum) will respond to basic CCs, such as 1, 11 and 7, without any further configuration.

If not, no idea what could be wrong... just make sure the input is received by the track (MIDI activity is received and reported by the yellow meter in the track header), again make sure "all in" or the device is set as the input, then try recording some data (just move the fader to send CC 11, for example), and you should see it being recorded. If that all works, then the problem is just with whichever plugins you are using.

 

[Crescendo]

Assuming you have setup a "control surface" external device (which I assume you did since you see the device working in some form), then all you should need is to have the MIDI/instrument track hosting the plugin set to "all inputs" (or just the fader device if that's all you want to record) and you will get whatever MIDI CCs the unit sends read and recorded. Most plugins (at least samplers and synthesizers such as Kontakt, SINE or Serum) will respond to basic CCs, such as 1, 11 and 7, without any further configuration.

If not, no idea what could be wrong... just make sure the input is received by the track (MIDI activity is received and reported by the yellow meter in the track header), again make sure "all in" or the device is set as the input, then try recording some data (just move the fader to send CC 11, for example), and you should see it being recorded. If that all works, then the problem is just with whichever plugins you are using.

Yes, I have the Control Surface set up. In general I can see MIDI messages coming in (also via an independent MIDI monitor).
However, Studio One seems to not allow the messages to go through in global focus mode.
My other MIDI controllers all work flawlessly (faders, knobs and all).