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.

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

Linux VST3 issues #191

Closed
GModal opened this issue Aug 18, 2020 · 4 comments
Closed

Linux VST3 issues #191

GModal opened this issue Aug 18, 2020 · 4 comments

Comments

@GModal
Copy link

GModal commented Aug 18, 2020

  1. Describe your environment
    Debian Buster, stable
    Carla 2.2.0-RC1
    Camomile 1.0.7 Beta14

  2. Describe the problem or the feature request

When the camomile script is invoked, two folders are created in /Build/"ProjName".vst3 --

  • /"ProjName".vst3
    • /CamomileFx.vst
      • /Contents
        • /x86_64-linux
          {
          CamomileFx.so file only
          }
    • /Contents
      • /x86_64-linux
        {
        CamomileFx.so file (not renamed)
        project files (.pd, .txt, etc.)
        }

--#1) In folder with project files (/"ProjName".vst3/Contents/x86_64-linux/), "CamomileFx.so" not renamed to "ProjName".so. The plugin works when the library is renamed manually...with the exceptions noted below (#3).

--#2) The /"ProjName".vst3/CamomileFx.vst folder is redundant. It also seems override plugin registry for some applications. For that folder the "ProjName" is replace with "Camomile", and that doesn't instantiate a plugin correctly (no project files).

--#3) Each vst3 plugin registers a list of extra MIDI CC parameters (192 total). I don't know if this is behavior is unique to Carla, or to the plugin. The number of vst3 hosts is currently limited for Linux, so it's difficult to test. Pic below --

vst3_params

@pierreguillot
Copy link
Owner

First: Please, can you create several issues if there are several issues and can you use a name more explicit for the issues?
Short answers:

  1. Indeed, this should be fixed.
  2. Did you use the pre-compiled binaries? And how did you invoke the script?
  3. This should be related to this: https://forum.juce.com/t/what-is-the-intention-of-macro-juce-vst3-emulate-midi-cc-with-parameters/17858. This must be investigated.

@GModal
Copy link
Author

GModal commented Aug 18, 2020

Sorry about that -- I'll be glad to open separate issues, if you want to close/delete this one...

@pierreguillot
Copy link
Owner

Yes, can you do it please?

1 similar comment
@pierreguillot
Copy link
Owner

Yes, can you do it please?

@GModal GModal closed this as completed Aug 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants