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

Midi feedback for motorized faders #1382

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

Off-IT
Copy link

@Off-IT Off-IT commented Dec 21, 2022

I have a midi control surface with motorized faders.
When moved, those faders get back in their original positions.
These forum topics are describing the issue:

https://www.qlcplus.org/forum/viewtopic.php?f=29&p=66484
https://www.qlcplus.org/forum/viewtopic.php?t=14190

With the help a of midi sniffer, I found that qlcplus don't send any midi feedback. It is needed to keep the sliders in place.
Here is a flow for a simple project with only one slider and its external input mapped to a pitchweel message :

  • fader moves
  • midi controller sends a pitchwheel message to qlcplus
  • VCSlider changes its value

To make the fader stay in place, this extra step is needed :

  • VCSlider sends feedback (pitchwheel) to the controller

I added a sendFeedback call in vcslider.cpp and it works great (at least for my Icon Platform M+).

@mcallegari
Copy link
Owner

I'm not sure if this is OK for every motorized fader controller.
I need to test it with my BCF2000. IIRC sending a feedback while moving a fader will block the fader itself.

@Off-IT
Copy link
Author

Off-IT commented Dec 26, 2022

There could be an option on the Input profile, under midi global settings.

@Off-IT
Copy link
Author

Off-IT commented Dec 26, 2022

I also found a little bug when retrieving the original midi channel, in Omni mode, when the slider is on an even page of a frame.

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

Successfully merging this pull request may close these issues.

None yet

2 participants