Pitch Wheel on UI - control from keyboard?

[d.healey]

@DanH Your keyboard will always send pitch wheel information.

In your on controller callback of your interface script you need to check if the incoming CC is pitch wheel data.

if (Message.getControllerNumber() == Message.PITCH_BEND_CC)

And if it is you forward the value to your slider.

Then in your slider's callback you need to send out a pitch value using Synth.sendController()

Slight rant:
I see in a lot of instruments the developer adds a mod-wheel and a pitch-wheel slider, and I never understood why. Who uses it to send pitch info into their daw? Isn't it easier to either use your pitch wheel or write the automation in the daw's automation lane? And why do you need it for visual feedback when you already have a physical pitch wheel on your keyboard? 99% of the time you open an instrument's UI, twiddle some knobs to set it the way you want and then close it, never to open it again in that session.

[DanH]

@d-healey thanks will give it a try.

Re rant - probably because kids produce on the sofa without any keyboard...

[DanH]

@d-healey so how do I get the value from the pitch bend cc?

[d.healey]

@DanH said in Pitch Wheel on UI - control from keyboard?:

pitch bend cc?

Message.getControllerValue()

[DanH]

@d-healey said in Pitch Wheel on UI - control from keyboard?:

Message.getControllerValue()

great got it! Thanks :)

For anyone else the slider's range needs to be set from 0 - 16383

[DanH]

@d-healey not getting an error but nor am I getting any pitch movement - have I done it wrong?!

inline function onPITCHWHEELControl(component, value)
{
	Synth.sendController(Message.PITCH_BEND_CC, value);
};

Content.getComponent("PITCHWHEEL").setControlCallback(onPITCHWHEELControl);

[d.healey]

@DanH Oh yeah getting MIDI out from instruments is tricky, search the forum and see what comes up.

[griffinboy]

@d-healey

I had use of it (draggable ui modwheels) once or twice.
It has uses if the synth uses it as an important modulation macro and I don't happen to have a keyboard turned on or near me.

But yeah it's very likely a waste of CPU.

[d.healey]

@griffinboy I just don't get it because as a user I'll usually assign my mod-wheel to control some knob/slider on the UI (via MIDI learn).

So if the knob is already on the UI I don't need a second slider that is only controllable by CC0. The only reason for this mod-wheel slider is because you don't already have a control on your UI for the thing you want the user to control. And now you're restricting their choice of CC to control this thing to CC0. Why not design your UI with the control on it, and let the user assign the CC they want to use?

[griffinboy]

@d-healey

Yep you are right that is a better architecture I don't disagree.

[DanH]

@d-healey Well the modwheel on my ui will be another modulator that you can drop onto almost any control, but I also quite like it as a hardwired vibrato pitch modulation effect!