-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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 extension plan #4954
Comments
@JohannesLorenz URID should be marked as done now, shouldn't it? |
@Spekular Yes, I forgot that. Thanks, fixed now. |
@JohannesLorenz Did #5691 implement all ot the Atom extension? I've played around with LV2 now and it's brilliant. Thank you so much for working on this! I installed a whole bunch of plugins via the ubuntu repo and of the ones who wouldn't load into lmms on start the most common message was: Next most are: and the 'zyn' stuff calling for: |
Thanks @zonkmachine . I updated Atom, we only support MIDI atoms now (all other are discarded). This whole plan may be a bit inexact sometimes. My next plans are indeed options and buf-size. If worker is easy, we can add that, too. Too many audio output channels: I don't know how this could be fixed best. If you have more than 2, which ones shall be sent to LMMS and which ones shall be ignored? Btw: Which ubuntu lv2 plugins did you install? Can you please add it on the Lv2 wiki page? |
I've added a wiki note. |
@JohannesLorenz for the too many outputs case I would route 1 -> left and 2 -> right, ignoring the rest. |
I don't think it's a good solution... For many plugins, the use might not make sense or even be unclear if only 2 of >2 audio outputs are connected. Imagine a "2 -> 4 split" plugin that takes a stereo signal and sends out the left signal to the first stereo output and the right signal to the second stereo output. If you only offer one stereo output for this, this plugin will always ignore the right signal, looking like a bug. |
I'll code "worker" next. |
I marked Buf Size done in the list above. |
I've been checking for lv2-plugins which have features we don't support (this can be seen by starting lmms with |
Edit: I was wrong...
|
Actually, it only prints "can not be loaded" if it has at least one reason, so it's really strange you get these. At least, I get messages for them:
|
Yes. I had made some changes to poke a couple of plugins a bit. Reverted that and now I get those messages too. Sorry... |
Yes indeed! I'm now running "Super Whammy" from MOD Devices with automation on the knobs. Bliss! All that was needed was to set the buffer to a multiple of 2 and to insert m_supportedFeatureURIs.insert(LV2_BUF_SIZE__powerOf2BlockLength); in Lv2Manager.cpp . Totally worth it! Issue opened: #6492 |
Whoops yes, I think I was meaning #5330 |
#5330 is interesting, but how related to Lv2 core? Is there an Lv2 plugin existing with that functionality? |
More that it's a basic use of CV interacting with/bridging other track elements, generating note CV from audio (and MIDI) and issuing that to modulate things. https://github.com/moddevices/mod-cv-plugins/tree/master/source/mod-audio-to-cv https://github.com/moddevices/mod-cv-plugins/tree/master/source/mod-midi-to-cv-mono https://github.com/moddevices/mod-cv-plugins/tree/master/source/mod-midi-to-cv-poly https://github.com/KottV/LV2Plugins/tree/master/lv2cvport/CV_AudioToCv |
Most non-extraordinary extensions seem to be done/in progress. As I think we should target UI ASAP, this should be the next target. Only state and preset seem to be useful to do before it (not sure yet). Other interesting stuff seem to be CV ports. Other things seem extraordinary to me. |
** This is WIP **
Background
Lv2 has many extensions, and some of them contain features. Extensions are things the plugin provides for a host, and features are things the host provides for a plugin. Note: Even if a host does not care about a specific extension, the plugin can require a feature from that extension, which means the plugin won't run without it.
Purpose
This plan helps to identify
Table
The text was updated successfully, but these errors were encountered: