-
Notifications
You must be signed in to change notification settings - Fork 386
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
VST3 parameter names not correct when learning #766
Comments
baconpaul
added a commit
to baconpaul/surge
that referenced
this issue
Mar 10, 2019
This commit implements the core non-MPE VST3 features which were missing on mac and windows. * Parameter names are long names in VST3 and were swprintfed as such even though they are non-wchar in surge internals * Parameter changes in VST3 flow to the UI and adjust widgets * Bound parameters in the DAW are named correctly * Midi controllers and pitch bend are captured and sent to surge * Unicode support is corrected for systems where wchar_t != char16 (like mac) Closes surge-synthesizer#766 VST3 names not correct when learning Closes surge-synthesizer#752 VST3 Automation in Bitwig Closes surge-synthesizer#26 VST3-Win MIDI Control Issues
baconpaul
added a commit
to baconpaul/surge
that referenced
this issue
Mar 11, 2019
This commit implements the core non-MPE VST3 features which were missing on mac and windows. * Parameter names are long names in VST3 and were swprintfed as such even though they are non-wchar in surge internals * Parameter changes in VST3 flow to the UI and adjust widgets * Bound parameters in the DAW are named correctly * Midi controllers and pitch bend are captured and sent to surge * Unicode support is corrected for systems where wchar_t != char16 (like mac) while still working on Windows, albeit in a somewhat clumsy fashion * Handle oddities around call type allow the plugin to also work 32 and 64 bit windows (Although demand for 32 bit VST3 seems more a formality than practicality, it does work) Closes surge-synthesizer#766 VST3 names not correct when learning Closes surge-synthesizer#752 VST3 Automation in Bitwig Closes surge-synthesizer#26 VST3-Win MIDI Control Issues
baconpaul
added a commit
that referenced
this issue
Mar 11, 2019
This commit implements the core non-MPE VST3 features which were missing on mac and windows. * Parameter names are long names in VST3 and were swprintfed as such even though they are non-wchar in surge internals * Parameter changes in VST3 flow to the UI and adjust widgets * Bound parameters in the DAW are named correctly * Midi controllers and pitch bend are captured and sent to surge * Unicode support is corrected for systems where wchar_t != char16 (like mac) while still working on Windows, albeit in a somewhat clumsy fashion * Handle oddities around call type allow the plugin to also work 32 and 64 bit windows (Although demand for 32 bit VST3 seems more a formality than practicality, it does work) Closes #766 VST3 names not correct when learning Closes #752 VST3 Automation in Bitwig Closes #26 VST3-Win MIDI Control Issues
baconpaul
added a commit
to baconpaul/surge
that referenced
this issue
Jul 10, 2019
This commit implements the core non-MPE VST3 features which were missing on mac and windows. * Parameter names are long names in VST3 and were swprintfed as such even though they are non-wchar in surge internals * Parameter changes in VST3 flow to the UI and adjust widgets * Bound parameters in the DAW are named correctly * Midi controllers and pitch bend are captured and sent to surge * Unicode support is corrected for systems where wchar_t != char16 (like mac) while still working on Windows, albeit in a somewhat clumsy fashion * Handle oddities around call type allow the plugin to also work 32 and 64 bit windows (Although demand for 32 bit VST3 seems more a formality than practicality, it does work) Closes surge-synthesizer#766 VST3 names not correct when learning Closes surge-synthesizer#752 VST3 Automation in Bitwig Closes surge-synthesizer#26 VST3-Win MIDI Control Issues Former-commit-id: b3221642eea1a25e891b1ca35963ad88dad02f00 [formerly 97d1366] Former-commit-id: 800f3f331fd31395ec96148e296f9154ee835761 Former-commit-id: b5c26e2c53dacfc4bf4489f77090ab4476b761c7
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Use whatever mechanism your DAW wants to learn a parameter name; you'll see in VST3 the wrong name comes through.
The text was updated successfully, but these errors were encountered: