VST3 Automation in Bitwig doesn't move Surge UI #752
Comments
|
As discussed on slack: The problem is that bitwig 2.5 hides a vst2 if a vst2 and vst3 are both available; and as documented elsewhere, the vst3 surge is broken. So I'm gonna change the name of this issue to "vst3 doesn't handle automation with a repaint" or something. |
baconpaul
changed the title
|
cool yes i couldnt easily check in bitwig 2.5 which version i was using .. it turns out VST3 .. which always had this problem of not moving sliders :) |
|
And picking this "show all version" thing in bitwig settings restores your ability to load the vst2 |
|
just in time .. to show me the ONE Surge i have installed now :D |
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
Previously sliders and knobs assigned from the bitwig knob gui would move when pressed in surge and routed to the inbuilt interface in bitwig for modulation ..
Previous version of bitwig 2.4.3 ...
Change of behaviour where knobs and sliders dont respond .. in surge to bitwig .. in Bitwig v 2.5
The text was updated successfully, but these errors were encountered: