Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How can you map a Controller with Touch Senstive Faders ? #23

Open
JuriaanGregor opened this issue Dec 27, 2018 · 5 comments
Open

How can you map a Controller with Touch Senstive Faders ? #23

JuriaanGregor opened this issue Dec 27, 2018 · 5 comments

Comments

@JuriaanGregor
Copy link

JuriaanGregor commented Dec 27, 2018

Hi there,

Just wondering or there is any workaround for MIDI Controllers that have Touch Faders. They will send a Note On, but currently, you can't map them correctly.

@xQuakes
Copy link

xQuakes commented Mar 6, 2019

This is the last step I'm trying to fix in an X Touch Sound/Lighitng desk project. I have even installed a midi translator so only the fader position (pitch bend) gets sent to luminosus not the note on from the touch sensitive fader and still it doesn't work properly. Would love to work out why this is or where in the code i could start looking to debug this.

@luminosuslight
Copy link
Collaborator

Filtering out the messages from touching the fader is the right way to go. Changing it in the source code would be definitely harder.
Do other buttons / non-touch-sensitive faders of the MIDI controller work?

@xQuakes
Copy link

xQuakes commented Mar 11, 2019

Hi Tim

Thank you for Luminosus it has made my life so much easier.

All other controls have programmed fine. I am using Bome Midi Translator, The only thing that has worked has been to convert the pitch bend to a note on intensity and then connect a custom midi block to a single fader. This is leaving me trying to find a solution where paging over the fader bank allows those same mapped faders to control the next bank which is proving difficult.

EDIT - WIth the faders set to note intensity they will map directly to the fader bank so my issue is resolved. Interesting that even with the touch ignored with the midi translator it still doesn't work as a pitch bend

@luminosuslight
Copy link
Collaborator

Glad to hear that it works now, at least with this workaround!

Another option to map the touch sensitive faders without the Midi translator could be to place the finger on the fader before clicking on 'Map MIDI to Control' so that the touch message is send before the mapping is done.

Regarding the pitch bend: I can't find anything in the code that would prevent it to work, but unfortunately I can't investigate it further at the moment :-/

@xQuakes
Copy link

xQuakes commented Mar 12, 2019

It's strange it still behaves strangely even if you map after holding the touch not sure why as the midi log shows a clean pitch bend going to Luminosus but just not being applied correctly.

For anyone reading this the workaround I am using is -

Using a midi translator to receive the midi messages from the X Touch apply this logic to the pitch bend from the fader -

Create a variable from the received pitch bend (which will be between -8192 and +8192) we will call this variable pp

Modify the variable with this logic

qq=pp+8192 (To make sure its a positive number)
qq=qq/128 (To turn the number into an intensity for a note)

then on a virtual out port configure a "Note On" message with qq as the intensity for any available note/channel combination and then map it within Luminosus (0 Intensity sends a Note Off message so that will need to be mapped to a separate rule for the bottom fader position)

Hope this helps someone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants