In my limited knowledge for this, I can confirm one element. To use the dual function of a keyboard like this, it needs to be added as a keyboard, and an external device also to get the function of the faders and pads

Does this help ?

I think it's a combo between both answers. I found a video about Studio One v2 and the axiom pro where it did set up two things (a KB and a Controller) but I still can't get V3 to let me set up the controls yet. IT will play sounds but will not assign control sliders or knowbs yet.

Any one else that has some info please chime in, and thanks for the hints so far, they are leading down the correct path.... still trying to find the magic ending

I am working with AIR DB-33 and I can't get any of the sliders or faders to work with the plugin.

These may need to be mapped via control link. With the plug/instrument open, you will see default control listed at the top right of the gui. There is also an edit botton, that will expand the gui to show control link editing. Move a parameter on the plug, then move the control you want to map to that parameter, and you will see them listed side by side. Hit the link button between them, and that will map it.

First question: Do you see activity in the MIDI monitor when turning knobs on the Axiom?
Second question: Do you want to use the external controls (CC's) from the Axiom as automation data or MIDI data to drive VST's connected to Instrument tracks?
Third question: Did you learned any of the external controls through the External Device map?

niles wroteFirst question: Do you see activity in the MIDI monitor when turning knobs on the Axiom?
Second question: Do you want to use the external controls (CC's) from the Axiom as automation data or MIDI data to drive VST's connected to Instrument tracks?
Third question: Did you learned any of the external controls through the External Device map?

First question: Do you see activity in the MIDI monitor when turning knobs on the Axiom?
Yes, I am getting midi into the DAW from those sliders or knobs

Second question: Do you want to use the external controls (CC's) from the Axiom as automation data or MIDI data to drive VST's connected to Instrument tracks?
Yes, trying to get drawbars and rotor speed to work off the controller for DB-33

Third question: Did you learned any of the external controls through the External Device
Yes, It wont learn when I right click and select learn CC and move the faders or the drawbars on the plugin

tridyed wroteThird question: Did you learned any of the external controls through the External Device
Yes, It wont learn when I right click and select learn CC and move the faders or the drawbars on the plugin

As soon as you learn the CC's from your controller to Studio One's External Device map, all CC data will be picked up by the Control Link system and not passed through to VST's connected to the Instrument tracks as MIDI CC data. So if you want CC's to control VST's from Instrument Tracks as MIDI CC data, you should not learn those to Studio One's External Device map.

I too have an Axiom, AxiomPro61, it worked wonderful with PT, but with SO4.52 I can't control the Rotor speed. I am using a Presence XT Organ with the Rotor plug, I can see the mod wheel values change just fine, but cannot use Control Link, it is never displayed as an option. I also do not see any of my control surface for the controller and there is no MIDI Learn function available.

So I added a new keyboard and voila, now I can add my controls with MIDI Learn. I contacted support and they say this isn't necessary to do. But without doing that, I can't link a control surface button, knob, fader or pad to a specific parameter in Rotor.

I'm a NUBE in SO, so obviously I'm missing something crucial. The odd thing is that in other Presence XT sounds, the mod wheel performs functions as expected, like on the Rhodes pianos, it introduces tremolo.

Does anyone have a solution?

There was an issue with some recent updates that required your external instruments to be removed and replaced with new ones again. It's not a bad thing to do. If you have any trouble with external instruments just remove and replace.

Thanks Jemusic... I can do that and see if it makes any difference

update: Support had me go into the macro editor on the channel and set the mod wheel and Rotor properties I wanted it to affect. Interestingly, in the editor I can now move the button (increase/decrease) and Rotor responds, but using the mod wheel has no affect except for increasing/decreasing the value on that button - it's like it sees it but it doesn't respond. Stumped...

Support got back with me and said that my new issue is a bug and has been forwarded to QA/DEV - sigh

I think a lot of people with bug issues get frustrated by the process of convincing others that there's a problem and may just wind up dropping the issue rather than following though.

Glad you kept at it and didn't just accept defeat. Now let's see what the company does...

Roland1 - I understand the bug process quite well, I've developed software for over 40 years. When it comes to something not working, I'm like a dog with a bone

rosssantos wroteRoland1 - I understand the bug process quite well, I've developed software for over 40 years. When it comes to something not working, I'm like a dog with a bone

Can you fix the Scratch Pad for me?

ok, so support told me to ask you all what you use as a Organ plugin that has a leslie that actually can be controlled by the mod wheel. I've used db33 when I was on PT, wondering what everyone else uses.

Korg Legacy M1 should have it.
Ni B3 or one of the various NI organ patches should.
Probably FM8 / Reaktor

I'm not even thinking about it much. There should be a dozen.

Thanks I will check them out!