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

How to understand LMMS's internal plugins nature? #4916

Closed
ghost opened this issue Mar 26, 2019 · 3 comments
Closed

How to understand LMMS's internal plugins nature? #4916

ghost opened this issue Mar 26, 2019 · 3 comments

Comments

@ghost
Copy link

ghost commented Mar 26, 2019

I am very curious about music plugin's standarts, such as VST, LADSPA, LV2 and others. But how to understand LMMS internal plugins, such as audio_file_processor. Is it LADSPA or something else type of plugin? Can I use it somethere outside of LMMS, for example in Ardour? Same about other plugins, such as bit_invader

@SecondFlight
Copy link
Member

SecondFlight commented Mar 27, 2019

These plugins are native to LMMS and use a built-in plugin format that is tied very closely to LMMS. They cannot be used elsewhere.

I'm closing this, as questions aren't what our Github issues are for. Feel free to ask questions like this in #techtalk on discord.

@tresf
Copy link
Member

tresf commented Mar 27, 2019

Can I use it somethere outside of LMMS, for example in Ardour? Same about other plugins, such as bit_invader

As @SecondFlight mentions, the plugins won't work elsewhere. To make your own, the internal working are best described here: https://github.com/LMMS/lmms/wiki/Plugin-development

That said, several years ago, @pgiblock ported some of the native LMMS instruments to LV2 format, which can theoretically be used elsewhere. https://github.com/pgiblock/lmms-lv2

@JohannesLorenz
Copy link
Contributor

Good sources to start:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants