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.

Sign up for GitHub

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

Jump to bottom

Virtual MIDI controller names not shown properly #2201

Closed
mkruselj opened this issue Jun 26, 2020 · 3 comments · Fixed by #2202
Closed

Virtual MIDI controller names not shown properly #2201

mkruselj opened this issue Jun 26, 2020 · 3 comments · Fixed by #2202
Labels
Host Automation Issues related to DAW (host) automation VST3 VST3 plugin related issues Windows Windows related issues
Milestone
1.7.0

Comments

@mkruselj
Copy link
Collaborator

On Studio One, Windows:

image

image
@mkruselj mkruselj added VST3 VST3 plugin related issues Windows Windows related issues Host Automation Issues related to DAW (host) automation labels Jun 26, 2020
@mkruselj mkruselj added this to the 1.7 0 milestone Jun 26, 2020
@K0rrid0r
Copy link
Collaborator

K0rrid0r commented Jun 26, 2020 •
edited
Loading

Can confirm the same in FL Studio. Also only in VST3

@baconpaul
Copy link
Collaborator

Yeah its a wide char thing. That code should make a whidechar but it doesn't. There's a different incantation I have to use and I got them all but not that one. Will fix.

@baconpaul
Copy link
Collaborator

The VST3 SDK Validator shows the same. Fix inbound.

baconpaul added a commit to baconpaul/surge that referenced this issue Jun 26, 2020
@baconpaul
Fix a WideChar VST3 Windows Midi CC problem
8b66b9e 
VST3 requires Midi CC "fake" params. They were named with a
widechar, and I was mis-using the widechar API so their names all
showed as "M". Correct that so names now show properly in vst3 validator
all 3 platforms

Closes surge-synthesizer#2201
@baconpaul baconpaul mentioned this issue Jun 26, 2020
Merged
baconpaul added a commit that referenced this issue Jun 26, 2020
@baconpaul
Fix a WideChar VST3 Windows Midi CC problem (#2202)
1e29814 
VST3 requires Midi CC "fake" params. They were named with a
widechar, and I was mis-using the widechar API so their names all
showed as "M". Correct that so names now show properly in vst3 validator
all 3 platforms

Closes #2201
@bobobo199733 bobobo199733 mentioned this issue Mar 5, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Host Automation Issues related to DAW (host) automation VST3 VST3 plugin related issues Windows Windows related issues
Projects
None yet
Milestone
1.7.0
Development

Successfully merging a pull request may close this issue.

Fix a WideChar VST3 Windows Midi CC problem baconpaul/surge
3 participants
@mkruselj @baconpaul @K0rrid0r