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

VST3 Validation Errors #1396

Closed
baconpaul opened this issue Dec 4, 2019 · 1 comment · Fixed by #1503
Closed

VST3 Validation Errors #1396

baconpaul opened this issue Dec 4, 2019 · 1 comment · Fixed by #1503

Comments

@baconpaul
Copy link
Collaborator

If you run the VST3 validation you get a few errors and infos

  1. You get a midi control out of range. Connect this to CC- offsets are off in the VST3 for automation #1347 also
  2. You get that a parameter 644 has no name

Reminder to run this

  1. Grab a clean version of vst3sdk
  2. build it (mkdir build; cd build; cmake ../vst3sdk; make validator or what not)
  3. Run the validator on the VST3
@baconpaul baconpaul added this to the 1.6.5 milestone Dec 4, 2019
@baconpaul
Copy link
Collaborator Author

val.txt

there's the output

baconpaul added a commit to baconpaul/surge that referenced this issue Jan 24, 2020
@baconpaul
Fix VST3 validation errors
7949fe2 
The VST3 validation errors were caused by 2 things

1. The MIDI fake params didn't have a name; now they do
2. The MIDI controller would just ask for an assignment for
   controllers outside range, I guess to test if I returned false?
   Which I now do? I guess?

Closes surge-synthesizer#1396
@baconpaul baconpaul mentioned this issue Jan 24, 2020
Merged
baconpaul added a commit that referenced this issue Jan 24, 2020
@baconpaul
Fix VST3 validation errors (#1503)
177c26d 
The VST3 validation errors were caused by 2 things

1. The MIDI fake params didn't have a name; now they do
2. The MIDI controller would just ask for an assignment for
   controllers outside range, I guess to test if I returned false?
   Which I now do? I guess?

Closes #1396
@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
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix VST3 validation errors baconpaul/surge
1 participant
@baconpaul