You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I have a ROLI Seaboard and the default pitch bend range for gliding is 48. The maximum pitch bend range allowed in the synth is 24.
Describe the solution you'd like
The pitch bend range slider should go up to 48.
Describe alternatives you've considered
Modifying the configuration of my ROLI Seaboard to match the same pitch bend range.
Additional context
I am able to build the plugin locally and I am willing to submit a pull request for the code. However, I couldn't find exactly where it is. I am assuming it is in Source/BendParamsComponent.cpp, perhaps on line 44. If you could point me in the right direction I can try to adjust it.
ROLI Dashboard for configuring the hardware
Pitch bend parameter
The text was updated successfully, but these errors were encountered:
If you want to modify the range, you only really have to modify a single line in the PluginProcessor.cpp file. This file initializes all the settings for the plugin as well as min and maxes. :)
Is your feature request related to a problem? Please describe.
I have a ROLI Seaboard and the default pitch bend range for gliding is 48. The maximum pitch bend range allowed in the synth is 24.
Describe the solution you'd like
The pitch bend range slider should go up to 48.
Describe alternatives you've considered
Modifying the configuration of my ROLI Seaboard to match the same pitch bend range.
Additional context
I am able to build the plugin locally and I am willing to submit a pull request for the code. However, I couldn't find exactly where it is. I am assuming it is in Source/BendParamsComponent.cpp, perhaps on line 44. If you could point me in the right direction I can try to adjust it.
ROLI Dashboard for configuring the hardware
Pitch bend parameter
The text was updated successfully, but these errors were encountered: