-
Notifications
You must be signed in to change notification settings - Fork 11
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
LV2 port #12
Comments
I backported some of their changes when they started. but now I see they made some non-backwards-compatible ones. I cannot import that as it would break the existing plugins. |
You mean that thread pierreguillot/Camomile#70 ? I'll try to use their code in my builds. Just to see if it work at all for general plugins. |
No, that is an old conversation. There was something newer, in yet another LV2 wrapper fork. One potential task/change to do is stop using control ports and use new lv2 parameter API, so that DSP side can change their own parameters. But usually this ends up being abused by plugins, so I am not sure this would have a good impact long-term. |
I see. I have look a little more and think that Camomile's code won't work in common case. It's heavy modified for their needs (?).
Cannot say I understand that. But I trust You :) On my side I've managed to build lv2 versions of some plugins with JUCE's cmake paradigm (pretty rough yet). At least these "new" plugins can be build automatically now. |
It just breaks the DISTRHO-Ports plugins that want state as a string (so it is understandable by humans, and editable too), also always enables latency port (most plugins do not have a need for this) among other similar things.
Would be nice to push these changes here at some point. |
Yes, it's possible to build plugins without Projucer(cmake, make, that's all), though for complex project may still better to use PJ. https://github.com/jatinchowdhury18/ChowPhaser (worth to check :)) |
I mean, can you add lv2 support to a project by using an alternative juce version, without opening ProJucer? |
Exactly. It needs your's LV2 Wrapper and modified https://github.com/juce-framework/JUCE/blob/master/extras/Build/CMake/JUCEUtils.cmake But the project has to be in cmake already, like two mentioned above. |
Alright that is great to know! Sadly I do not have time to do much about this right now, finishing other projects first. But near the end of the year I will resume work on DISTRHO/LV2 and DPF as well. |
I understand. And yes, LV2 port is working well) I'd like to ask your thought about two things:
and it seems to work Potentially it allows use wrapper as fetchable module without modifying juce_AudioProcessor.h
|
Pinging @atsushieno as they might be interested in jatinchowdhury18/AnalogTapeModel#7 and this thread given https://github.com/atsushieno/JUCE/tree/juce_emscripten / https://github.com/atsushieno/aap-juce / https://github.com/atsushieno/aap-lv2 |
@mxmilkiib Hey. I'm seeing various LV2 ports in the world and I know this is one of those. A fact that might be interesting for you is that my Therefore there is not actually things that my repos can be of any help, or anything that our codebase benefits from LV2 ports. When I created the plugin wrapper in aap-juce I learned from another LV2 port on how to generate metadata (for our own) in the past though. |
To those listening, I just updated this fork against latest JUCE There is still no direct LV2 support in ProJucer, so we are basically in the same situation as before. I have cleaned up all the patches, feel free to grab at |
Good news. |
another ticket to close, juce7 has official lv2 support now, no need for this ticket here |
Hi,
There is active work on JUCE LV2 in Camomile sourcetree: https://github.com/pierreguillot/Camomile/tree/dev/imp-lv2-support/Dependencies/juce_audio_plugin_client_LV2
Could You look at that and maybe better to join yours code?
The text was updated successfully, but these errors were encountered: