I figured there was some technical aspect that made it more than just adding a hook in REAPER's code, and was really just razzing since there were already two posts here asking for LV2 support.

As for using wrappers, I already have Carla installed and it can load LV2 plugins, but the crux of the biscuit is that the only reason I would want to use LV2 plugins is because they are native Linux, and using a wrapper blows that reason up for me.

I've yet to see an lv2 plugin present a modern preset handling system
in any linux daw. And lacking any coding knowledge, have read that
lv2 is as much of a gui coding nightmare as windows vst, I believe
mentioned in the early days of Abique porting Podolski and Zebra2
to linux.

Being an adopted child, I find the whole 'native' semantic
far less important than many linux devotees.
I value who changed my diapers, who deployed the gause and bandaids,
who taught me how to drive, and who bought me a first guitar and amp,
far more than names, titles and legalities.

I suspect unless one has access to some music-friendly
open-source native linux SOC, and the SOC chip manufacturer
produces said chip/mobo etc on manufacturing machines
also running on native linux chips, that 'native linux'
will always be a unicorn in knights armour, and that
people will shorten their life with blood-pressure raising
labeling regimens and conflicts, that divide more often
than conquer, while diverting man-hours away from the studio.

I use the best and/or most enjoyable tools I can get my
grubby hands on, and almost always in a linux environment.
Not because Torvalds and Stallman are saints, not because
Gates and Jobs are devils, but because of filesystems,
utilities, desktop management, portability,
system flexibility... being able to choose
which size nuts and bolts to use, and how tight they fit.

There, I stirred the pot a little, and the ladle is ready
for steadier hands ...winkety wink wink
Cheers

I don't change my SR within a project in all the years working with audio.
It could be marked as "experimental" and with a big hint about this behaviour.

I've run REAPER at 24/44 for more than ten years and never ever changed it. Somewhere around the year 2000 when I was using Sonar I switched from 16/44 to 24/44, but even that change was not a SR change.

Wrapped plugins, whether VST or LV2 are simply not as efficient since they are passing their data through an extra layer of code.

Code is not plywood. Most people won't even notice speed differences,
and wrapper efficency keeps improving. Plus we're not
bulldozing a behemoth like win-10 or Catalina back and forth
with some bloated expensive daw.

LinuxSampler is indeed a good example of native linux efficiency.
But it's quirky, lacks dozens of how-2 video guides, and competes with industry leaders like Kontakt and SampleTank
(with their own quirkyness when used in linux) which provide
sounds, and 3rd-party sounds are myriad.

I doubt audible examples of speed lags
among wrapped or wined plugins even exist.
It's usually player skillz, hardware availability,
or poor latency configs that need help.

Diva will pummel a weak cpu, and never caring a whit about the OS.
Cheers

I doubt audible examples of speed lags
among wrapped or wined plugins even exist.

I have projects that were created in REAPER for Windows that will not play without artifacts because of so many bridged plugins. In Windows those same projects with 100+ VST FX will play without issue running 24/44 @ 64 samples latency, but not in Linux at any buffer size because 100+ instances of bridged Windows plugins is a noticable strain.

Once I started replacing my Windows plugins with native Linux plugins, I started seeing the same kind of performance I was used to seeing on the same machine in Windows.

That said, there are still some Windows plugins like Kontakt that I use every bit as much bridged in Linux as I used them in Windows. Same for Superior Drummer. Nothing native Linux has the complexity of mic bleeds and midi control for a pad kit that Superior has.

All my audio plugins are now 100% native Linux, but for a few VSTi instruments I still used bridged Windows plugins.

I like to have a system that's less likely to have something that I rely upon suddenly not work or just generally be less predictable. That's why I'm currently not using bridging of any kind. I'm not saying bridging should inherently be considered unreliable, but it is one more layer in which possible issues can arise. Factor into that how the various Linux distros are maintained (including dependencies), and that the bridging for LV2 is done by third party developers on a volunteer (or donation-based) basis.

If you think I'm just too picky about this: you might notice a distinct lack of my posts about issues with my audio driver since I use ALSA and not Jack. Adding Jack into the equation means another layer to consider when something doesn't work quite right (ahem ), and I've seen enough posts about it here and on Linuxmusicians to know if I don't need Jack, I'll just skip it. (I don't want to connect a bunch of other audio apps to Reaper, so for the most part I don't use Jack.) Jack is very good, but it means you have to be ready to deal with whatever it requires to work. This is Linux after all, so configuration of the system can be confusing and documentation is fragmented. I also see bad advice given on a regular basis about configuring audio systems in Linux, some of which dates back to previous kernels and just isn't necessary anymore and some of which is just wrong (and/or doesn't take all the variables into consideration).

If LV2 becomes natively supported in Reaper, I'll use it. If not, I probably won't. That's not an ultimatum either. I'd be happy to get LV2 support in Reaper, but I can live without it too.

I have projects that were created in REAPER for Windows that will not play without artifacts because of so many bridged plugins. In Windows those same projects with 100+ VST FX will play without issue running 24/44 @ 64 samples latency, but not in Linux at any buffer size because 100+ instances of bridged Windows plugins is a noticable strain.

Once I started replacing my Windows plugins with native Linux plugins, I started seeing the same kind of performance I was used to seeing on the same machine in Windows.

That said, there are still some Windows plugins like Kontakt that I use every bit as much bridged in Linux as I used them in Windows. Same for Superior Drummer. Nothing native Linux has the complexity of mic bleeds and midi control for a pad kit that Superior has.

All my audio plugins are now 100% native Linux, but for a few VSTi instruments I still used bridged Windows plugins.

In my paltry defence, I did use the phrase 'most people',
and I suspect there are less than a dozen people here who often use
100 vsts in a project. (happy to be wrong, though!)

To your credit, you actually make music,
and without making 'forum noise', and present your experiences
often and clearly, to help those of us in different studio situations/workflows. Bravo!

I should add that your success using Kontakt motivated me
to gain that capability, now enjoying many unique sounds
available in that format. I've replaced Hydrogen samples
with NI samples at times, and renamed the kits. Hoping their
Balinese Gamelan or a competing lib will go on sale someday!

and I suspect there are less than a dozen people here who often use
100 vsts in a project. (happy to be wrong, though!)

I only have a few projects that have that heavy of a load, but it is very normal for me to have 50-60 VSTs in any project.

Quote:

To your credit, you actually make music,
and without making 'forum noise', and present your experiences
often and clearly, to help those of us in different studio situations/workflows. Bravo!

I should add that your success using Kontakt motivated me
to gain that capability, now enjoying many unique sounds
available in that format. I've replaced Hydrogen samples
with NI samples at times, and renamed the kits. Hoping their
Balinese Gamelan or a competing lib will go on sale someday!

Kontakt has worked great on Xubuntu/WINE for over a year now on my machine, and is the primary Windows plugin I do not want to be without. More of my projects use Kontakt than not, but it is always in addition to other real parts, so it's not trying to be all instruments for me.

Since I've gone 100% native Linux on all my audio plugins though, I could work Kontakt a lot harder than I do, and even have a bunch of other Windows instrument VSTi's running at the same time without noticing any drag. It really only shows up when you are bridging a boatload of Windows plugins.

I think Linux is whiping the Llamas ass it is not about coins or Lamborghini's.. i - Love - Linux! as an OS/community *read my lips* my own choice and i think Linux loves me! *did i just say that?*

Linux is my happy/smiley place now, so much to explore, i have no real issues with Windows10 really *speaking for myself* i simply enjoy the world of Linux and enjoy the rewards of, *Shit! i just learned something, it wooorks, its aliiIiive!

When I want to use CALF plugins - I just go to Audacity (as secondary editor... apply them right back into Reaper... works fine. here is a good link for lv2 also https://wiki.linuxaudio.org/apps/all/lv2

In the past, quite a lot of lv2 (and some vst) Linux plugins used gtk.

gtk is the worst for compatibility with hosts.

Even if Reaper had native lv2 support, there is still the gtk incompatibilities problem.

It's a toolkit problem, not a plugin problem.

Ideally, Calf should hopefully convert their plugins from gtk to X11, and Guitarix might do it soon.

They know that there are gtk incompatibilities with some daws.

To convert plugins from gtk to X11 is not an easy thing.

The lv2 (wrapped) gtk plugins (or even gtk vst plugins) have trouble with Bitwig Tracktion/Waveform and Reaper and Ardour and others are ok but maybe not always.

I have had the wrapped Calf and Guitarix lv2 plugins running as vst's with GUI's in Ardour but that can't be done with Reaper because of gtk (It's pretty useless wrapping lv2's as vst's in Ardour but I wanted to see how the gtk enabled modded version (that I did) of the lv2 to vst wrapper performed and it was very good with Calf and Guitarix plugins from what I could tell and had working GUI's)

The lsp plugins started out as gtk but the dev converted them to X11 because of the gtk incompatibilities.

So, the Guitarix lv2 plugins have been ported to X11 and the lv2vst wrapper can run them with GUI's.

The Gtk lv2 plugins like Calf, one way is for them to be run in another process and then their GUI can be embedded into Reaper and I've got Calf plugins running in that way using a modified lv2vst wrapper and a Linux only version of LinVst (no Wine involved).

So, at the moment I can run Guitarix and Calf lv2 plugins with GUI's in Reaper, just like any other Linux vst plugin would.

So, the Guitarix lv2 plugins have been ported to X11 and the lv2vst wrapper can run them with GUI's.

The Gtk lv2 plugins like Calf, one way is for them to be run in another process and then their GUI can be embedded into Reaper and I've got Calf plugins running in that way using a modified lv2vst wrapper and a Linux only version of LinVst (no Wine involved).

So, at the moment I can run Guitarix and Calf lv2 plugins with GUI's in Reaper, just like any other Linux vst plugin would.

Sounds amazing. I really like Calf Plugins. Is everything showing...some plugins have graph in them and they are gone when you use Carla.