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

LinuxVST support #416

Closed
diizy opened this issue Mar 5, 2014 · 28 comments · Fixed by #6048
Closed

LinuxVST support #416

diizy opened this issue Mar 5, 2014 · 28 comments · Fixed by #6048

Comments

@diizy
Copy link
Contributor

diizy commented Mar 5, 2014

Again, another thing I'm just putting on the issue tracker, since it's been discussed on the mailing lists.

LinuxVST support should be relatively easy to implement considering we already have the VST code, and it would be beneficial, seeing as there's lots of interesting developments happening on the LinuxVST front right now (many new plugins being made and such).

And it's also a feature that has been requested by many people.

@diizy diizy added this to the 1.1.0 milestone Mar 5, 2014
@Sti2nd
Copy link
Contributor

Sti2nd commented Mar 29, 2014

So I guess it will run on Windows, right?

@diizy
Copy link
Contributor Author

diizy commented Mar 29, 2014

On 03/29/2014 03:34 AM, Stian Jørgensrud wrote:

So I guess it will run on Windows, right?

LinuxVST's do not run on Windows... that would require the reverse
counterpart of Wine, which no one has bothered to develop. Probably
because you can get perfectly good Linux distros for free...

But I don't really see how that matters. Windows users already have more
than enough choice of native plugins to use.

@Sti2nd
Copy link
Contributor

Sti2nd commented Mar 30, 2014

Does lv2 support Windows (through LMMS)?

@tobydox
Copy link
Member

tobydox commented Mar 30, 2014

LV2 is just an interface standard, the question is whether the actual plugin can be built for Windows. For LADSPA plugins this is easy as they do not have separate dependencies like UI frameworks or similiar. Many LV2 plugins use Gtk which in turn would add a massive overhead to Win32 binaries.

@grejppi
Copy link
Contributor

grejppi commented Mar 30, 2014

If an LV2 plugin chooses to use Gtk or any other huge GUI toolkit, it's their own dependency -- LMMS shouldn't care about that.

@diizy diizy modified the milestones: 1.2.0, 1.1.0 Apr 30, 2014
@diizy
Copy link
Contributor Author

diizy commented Apr 30, 2014

Reluctantly going to have to push this to 1.2...

@tresf tresf modified the milestones: 1.3.0, 1.2.0 Feb 4, 2015
@tresf
Copy link
Member

tresf commented Feb 4, 2015

Bumping out to 1.3 (likely after 2.0)

@hallogallo
Copy link

Are there any news regarding this topic? Google just brought me here 😆

@jasp00
Copy link
Member

jasp00 commented Feb 15, 2017

Are there any news regarding this topic?

A volunteer to code would be appreciated. Also, we should merge some fixes for Windows VST first.

@RichardJECooke
Copy link

I'm trying LMMS for the first time on Ubuntu and am unable to get VSTs to work - either Wine crashes trying to install them, or once installed LMMS' Vestige crashes trying to open them.

I hoped returning to Linux audio after seven years things would be much easier, but it still seems unusable. I really hope the team manages to get round to this 2014 issue some time.

@tresf
Copy link
Member

tresf commented Jan 9, 2018

This topic is about LinuxVST, so the Wine crashes seem to be misplaced. As for the state of Linux audio in general, this tracker isn't the place to discuss that despite many people sharing your feelings on the topic.

That said, although the frustrations you are having are real, we really don't tolerate people coming on this tracker pointing out the shortcomings of a few volunteers.

Please keep posts on-topic to the original bug report.

@Umcaruje Umcaruje mentioned this issue Jan 15, 2018
@vlad0337187
Copy link

Would be VST effects included into this issue ?
(I mean plugins, which are loaded after "add effect" button pressed)

@davidhedlund
Copy link

davidhedlund commented Apr 25, 2018

I added https://lmms.io/wiki/index.php?title=Tested_VSTs#Free_software and added a few VST's to it.

@davidhedlund
Copy link

davidhedlund commented Apr 30, 2018

http://linux-sound.org/linux-vst-plugins.html (Updated 13 February 2018.) is the most complete list of VST's for GNU/Linux that I've seen.

@tresf
Copy link
Member

tresf commented Jul 19, 2019

Why is this issue still open??

Because LinuxVST support has not yet been added.

@lukas-w
Copy link
Member

lukas-w commented Jul 19, 2019

@mrshroomy LinuxVST refers to support for native Linux VSTs as opposed to Windows VSTs, which we currently support using Wine on Linux.

@NoxWings
Copy link

NoxWings commented Sep 3, 2019

I recently decided to use lmms to create the music for my next 64k intro. It fits the purpose of what I need quite well except this. Unfortunately I need to work with a synth that is compiled as a linux vst :(

@tresf
Copy link
Member

tresf commented Sep 3, 2019

@NoxWings as a stop-gap you can try the Carla Instrument Rack. It ships with 1.2.0 and supports many more plugin formats than we do.

@tresf
Copy link
Member

tresf commented Sep 3, 2019

Correction, 1.2.0 ships with support for it. It needs to be available on the system for LMMS to detect it.

@NoxWings
Copy link

NoxWings commented Sep 4, 2019

So are you saying Linux vst are supported on LMMS as long as they are available on the system path?

@tresf
Copy link
Member

tresf commented Sep 4, 2019

Linux VSTs are not supported directly at all. The 3rd party plugin "Carla" can open plugins of various formats. Carla's a big app and it's actually bigger install than LMMS, so we don't bundle it, but direct Carla support is included in LMMS starting with version 1.2.0.

@NoxWings
Copy link

NoxWings commented Sep 4, 2019

Oh I didn't know that, thanks for the clarification.

@Spekular Spekular mentioned this issue Mar 31, 2020
35 tasks
@probonopd
Copy link

Linux VSTs are not supported directly at all.

Is this planned to be added? Wouldn't it be a quite natural thing to do for an app that has "Linux" in its name?

@tresf
Copy link
Member

tresf commented Apr 11, 2020

Naturally. Furthermore Linux was dropped from the name a long time ago

@probonopd
Copy link

probonopd commented Apr 11, 2020

Ah, I thought the "L" in "L Multimedia Studio" stood for "Linux"... perhaps it's the "Libre Music Mastering Studio" now. Anyhow, looking forward to it.

@PhysSong
Copy link
Member

FYI, #3975 is a good start point to support Linux VSTs(not to be confused with LV2) as well as macOS VSTs. I was playing with the code for a while and confirmed it's possible to modify it to support Linux VSTs. However, I need to get some time to organize and test the code.

@probonopd
Copy link

probonopd commented Apr 12, 2020

In the meantime, would you be interested in making an AppImage that would include WINE out of the box @tresf? A lot of progress has been made lately when it comes to bundling WINE as an AppImage.

@tresf
Copy link
Member

tresf commented Apr 12, 2020

Wine should be obtained from official sources. Some of the more complex VSTs require modifying the environment. Doing this on an AppImage is a nightmare. Furthermore, our current stance is to obtain gigantic plugins separately (such as Carla). Wine won't be bundled if i have anything to do with it.

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

Successfully merging a pull request may close this issue.