LSP Project

[sadko4u]

Hello all!

I'm new at this forum but very interested in plugin development.
So after some months of work I would like to introduce new plugin package - Linux Studio Plugins Project.
Currently there are only two basic plugin types but the developed framework (especially, UI) allows to create new plugins easier and faster.
So I'm currently aimed to extend the set of plugins in the future.
The current package contains two types of plugins in both LADSPA and LV2 formats:
LSP Phasendetektor - Phase Detector.
LSP Verzögerungsausgleicher - Delay Compensator (Mono, Stereo, X2 Stereo variants).



The demo of plugins: https://youtu.be/j-rNb409GYg
The official web site of the project: http://lsp-plug.in/

Hope you'll enjoy them.
Any ideas and suggestions are welcome.
Thanks.

[sadko4u]

love the idea, but I don't see any public code anywhere.

The tarballs here: https://sourceforge.net/projects/lsp-pl ... es/v1.0.0/ only provide binaries.
The LICENSE file inside reports the license as GPL v2.
As per GPL v2 you must distribute source code if you publish binaries (when requested).

Probably you're right. The main idea is that I'll publish sources under the free license (GPL v2) after I'll collect some donations that will compensate the time I'll spent for development.
If you could offer licensing model, I would be thankful to you.

Perhaps the reverse would be a better idea?
(Releasing source but asking donations for pre-compiled binaries)

Did this ever work for such small projects like mine?

[asbak]

Hi there, thanks for the plugins

I tried the lv2 version on 64bit Linux. The gui's don't work on my system in Carla host or with jalv.gtk
I didn't test the ladspa version

[sadko4u]

Hi there, thanks for the plugins

I tried the lv2 version on 64bit Linux. The gui's don't work on my system in Carla host or with jalv.gtk
I didn't test the ladspa version

Thanks for response! What does the following shell command show (?):

Code: Select all

ldd lsp-plugins-gtk2.so

[sysrqer]

These look very promising. Is there any chance of providing (linux) vsts?

[sadko4u]

These look very promising. Is there any chance of providing (linux) vsts?

Currently I have no experience of LinuxVST development.
If there is only VST SDK needed to develop plugins, then I can try it in the future.

[asbak]

Thanks for response! What does the following shell command show (?):

Code: Select all

ldd lsp-plugins-gtk2.so

I removed them already, but I think (could be wrong, it was late at night) it was hardlinking to a suil library on your system's path somewhere under /home/sadko/
So on your dev box (the one you compiled them) it would work fine because the library is already there, but it would be invalid for other computers.

[asbak]

Currently I have no experience of LinuxVST development.
If there is only VST SDK needed to develop plugins, then I can try it in the future.

Here is a copy of the VSTSDK 2.4 typically used

http://www.dith.it/listing/vst_stuff/

[sadko4u]

Here is a copy of the VSTSDK 2.4 typically used

And what about VST SDK 3.6.5? Do the linux hosts support it?

[tripomatic]

Here is a copy of the VSTSDK 2.4 typically used

And what about VST SDK 3.6.5? Do the linux hosts support it?

I already compiled plugins with SDK 3.6.0 on my system, so 3.6.5 will do also.
In the SDK there is also a 2.x directory. (VST3_SDK/public.sdk/source/vst2.x)

[asbak]

Here is a copy of the VSTSDK 2.4 typically used

And what about VST SDK 3.6.5? Do the linux hosts support it?

A lot of the projects on github still use 2.4 for their plugins, perhaps it's better for backward compatibility purposes. But best to check with a developer.

[sadko4u]

OK, I'll study VST SDK in the nearest future.

[ssj71]

If you could offer licensing model, I would be thankful to you.

It seems you are doing a similar approach to the OpenAV model. OpenAV would announce the project, but would not release any binaries until the source gets released as a result of sufficient donations or time elapsing. They since renounced this system because it can result in a deadlock. (see http://openavproductions.com/openav-rel ... m-the-end/)

However I also employed this system because it does incentivise donations but also guarantees a source release eventually and fits in with GPL. I do use a variation that I release the plugin with a host generated UI first, so anyone can try and use it, but for the custom GUI code I design I use this model. I had a deadlock the first time I employed it simply because there wasn't enough interest. In the 10 months that I did not release my plugins I took the time to work on several other projects that I otherwise would not have. So I actually appreciated the forced break (though I did consider early release, but time ran out before I knew it). The second such fundraiser was successfully funded after a week or so, the dgoal amount was less since it was for a single plugin UI and it was a more wanted plugin. Both fundraising attempts I consider successful. You can read a bit about it here: http://ssj71.github.io/infamousPlugins/donate.html

If you do not use any other GPL code, you can licence it as a non-open source work until the donations are recieved then relicense, but I much prefer everyone use GPL always. I can understand financially why many don't.

[sadko4u]

ssj71, thanks for a comment.
My model is also a variation of the work process you mentioned.
I produce already working binaries (at least, on my distro of Linux) that users may use for free and distribute for free.
If they want to see my plugins in their linux distro, then these must be in most cases adapted to the target distro and built from source code.
I don't promise to do something and collect money for that. I just say: 'here, it's alreay ready to work, try it, use it'.
So I want to get donations only for publishing the already written source code.
It's just the fact that my work was claimed and the time I've spent was properly paid.
When the code becomes published, it can be licensed under any free license users want (probably, GPLv2 is one of the best candidates).

The code of plugins is written from scratch, the examples of how to use LV2 plugin format I've learned mostly from Calf, Invada and x42 plugin packages.
Also x42 helped me to solve some questions in Ardour's Mantis, great thanks to him.
It uses dynamically-linked expat, gtk+ and cairo libraries and lv2 plugin framework.
The build tools I've used were gcc and GNU make.
The OS used to build binaries is openSUSE 13.2.

[sadko4u]

the current license file you mention for the published binaries is GPL v2, but you do not provide source code.

I've already changed licensing for binaries and re-loaded them.