You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using JUCE through pedalboard for a project and I am encountering an issue with parameters names being conflicted when using it with the Diva synthesizer audio unit. One example of such conflicted parameter is for example 'model' (which can be 'osc model' or 'hpf model'). Or 'attack' (for 'env1 attack', 'env2 attack', etc.).
For v7.0.10 (for an updated pedalboard version using v7): changes here
That way, it displays almost the same parameter names as the VST version for example.
I am not sure if this is the right approach. Maybe the parameter clump name could be available in the Parameter structure and it would be up to pedalboard to "compose" the new parameter name?
What is the expected behaviour?
Have different parameters names and - more importantly - complete name (like 'env1 attack' instead of 'attack').
Operating systems
macOS
What versions of the operating systems?
14.1
Architectures
ARM
Stacktrace
No response
Plug-in formats (if applicable)
AU
Plug-in host applications (DAWs) (if applicable)
pedalboard using JUCE for hosting AU
Testing on the develop branch
The bug is present on the develop branch
Code of Conduct
I agree to follow the Code of Conduct
The text was updated successfully, but these errors were encountered:
Detailed steps on how to reproduce the bug
I am using JUCE through pedalboard for a project and I am encountering an issue with parameters names being conflicted when using it with the Diva synthesizer audio unit. One example of such conflicted parameter is for example 'model' (which can be 'osc model' or 'hpf model'). Or 'attack' (for 'env1 attack', 'env2 attack', etc.).
The changes below could resolve the issue:
For v6.4.1 (used by pedalboard): changes here
For v7.0.10 (for an updated pedalboard version using v7): changes here
That way, it displays almost the same parameter names as the VST version for example.
I am not sure if this is the right approach. Maybe the parameter clump name could be available in the Parameter structure and it would be up to pedalboard to "compose" the new parameter name?
What is the expected behaviour?
Have different parameters names and - more importantly - complete name (like 'env1 attack' instead of 'attack').
Operating systems
macOS
What versions of the operating systems?
14.1
Architectures
ARM
Stacktrace
No response
Plug-in formats (if applicable)
AU
Plug-in host applications (DAWs) (if applicable)
pedalboard using JUCE for hosting AU
Testing on the
develop
branchThe bug is present on the
develop
branchCode of Conduct
The text was updated successfully, but these errors were encountered: