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

Plugin DSP and UI binaries do not need to be split #2

Closed
falkTX opened this issue Oct 1, 2021 · 2 comments
Closed

Plugin DSP and UI binaries do not need to be split #2

falkTX opened this issue Oct 1, 2021 · 2 comments

Comments

@falkTX
Copy link

falkTX commented Oct 1, 2021

Another correction.

Having the plugin dsp stuff in a binary and the UI in another binary is not a requirement.
Developers are free to place everything inside a single binary, even multiple plugins and multiple UIs.

You can also split the binaries inside an LV2 bundle so each plugin in the bundle gets a different one.

In resume, there is no restrictions for this whatsoever, and implying there is, is misleading.

@sjaehn
Copy link
Owner

sjaehn commented Oct 1, 2021

You are right, of course. There is no need to have two ore even more binaries. And I know that you don't do splitting ;-). But you CAN do it. I used LittleFly by brummer10 as an example it the video 01. And he's one of the programmers who prefer to split DSP and GUI code into two binaries.

@falkTX
Copy link
Author

falkTX commented Oct 1, 2021

The splitting makes sense typically, but not always.
I most definitely do it as much as possible. In some stuff like JUCE it is not possible by design, sadly.

@sjaehn sjaehn closed this as completed Mar 3, 2023
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