How to configure Sitala Drum Sampler as Reaper VST

[Adamastor]

I'm running Reaper 5.9 and I'm trying to install Sitala Drum Sampler https://decomposer.de/sitala/ as a VST. However, running the installation .deb from the site I get a standalone Sitala installation which I then have to route to Reaper and route it back for playback.

How do I install or configure Sitala as a VST as is used in this video? https://www.youtube.com/watch?v=wdqTwMx0a5c

[jelloman]

The VST .dll file is in c:\Program Files\Steinberg\VSTPlugins

Make sure REAPER has that file location in it's plugin manager and rescan...

[Adamastor]

Thanks, but this is Reaper for Linux, and this VST is installed via dpkg, not Wine, so there are no dll's.

[lilith93]

Just copy the file libsitala.so into your /home/yourname/.vst folder and rescan plugins in Reaper. You also might want to copy the drum kits there.

[Adamastor]

Originally Posted by lilith93

Just copy the file libsitala.so into your /home/yourname/.vst folder and rescan plugins in Reaper. You also might want to copy the drum kits there.

You beauty! Thanks a ton.

[TonE]

Is there shortcircuit 1.1.2 for linux as well?

[Xenakios]

Originally Posted by TonE

Is there shortcircuit 1.1.2 for linux as well?

Nope, it was never ported to Mac or Linux by the developer.

[4duhwinnn]

Originally Posted by TonE

Is there shortcircuit 1.1.2 for linux as well?

shortcircuit likely would run with a modern wine installed,
and the plugin .dll wrapped by LinVst plugin wrapper, so it looks like
a native linux vst.so

Google linvst, the install/use guide is in the
page texts, and it's not rocket science.
Cheers

[scotchi]

Originally Posted by lilith93

Just copy the file libsitala.so into your /home/yourname/.vst folder and rescan plugins in Reaper.

That is *not* the correct way of doing things. The correct way is to add `/usr/lib/lxvst` (which some Linux hosts include by default) to your VST search path in Reaper.

[4duhwinnn]

A big part of linux is shedding elderly 'correct ways',
and using new or better ways. Using .vst instead of
some root permissioned folder from 2006, is more convenient
to musicians, while sysadmins may love or need /usr/xyz.

U-he chose .vst, so it's good enough for me too.
Cheers

[scotchi]

Originally Posted by 4duhwinnn

A big part of linux is shedding elderly 'correct ways'...

First, I created the package in question. It expects the drum kits to be under /usr. If you move them, it won't work anymore.

Second, there's nothing new about putting things in your home directory, though (a) that only makes them available for that user (usually not a problem) and (b) means you can't upgrade them using the package manager (which is a problem).

Ardour and other hosts that are packaged by the distribution tend to expect plugins in `/usr/lib/lxvst`, so configuring Reaper to look there too is reasonable.

[bulevardi]

Works like a charm!

Although I also have put my other plugins already in my home/username/vst folder.

So putting that extra vst into that folder is handy... to have them together.
Of course you can let Reaper search that usr/lib/lxvst folder, handy, although for me there's only one vst inside that folder, and that's the Sitala drum sampler.

[Primeval Mudd]

Originally Posted by scotchi

That is *not* the correct way of doing things. The correct way is to add `/usr/lib/lxvst` (which some Linux hosts include by default) to your VST search path in Reaper.

Aha!

Yet another vst folder to add to the ever increasing collection.

Still, can't complain, it's an awesome plugin.

[Primeval Mudd]

Originally Posted by bulevardi

Works like a charm!

Although I also have put my other plugins already in my home/username/vst folder.

So putting that extra vst into that folder is handy... to have them together.
Of course you can let Reaper search that usr/lib/lxvst folder, handy, although for me there's only one vst inside that folder, and that's the Sitala drum sampler.

I wish the plugins would put themselves in subfolders in the existing ladspa/lv2/vst folders rather than being antisocial and setting up on their own.

This is a list of the plugin folders that have popped up on my computer:

usr/lib/:

• bristol
• calf
• ladspa
• lv2
• lxvst (one plugin)
• plugins
• vst
• vst3

usr/share:

• bristol
• calf
• helm
• ladspa

Home:

• .vst (one plugin)
• .vst3 (one plugin - the same one as .vst)

[Pre34]

Had no problem installing Sitala, but now I have two problems:

1. I like it and prefer it and want to use it.
2. I can't use it because it keeps randomly creating new tracks every time I reopen a Reaper project, any project.

[audiojunkie]

If you are an Arch based user (Arch, EndeavourOS, Manjaro, etc), it is worth considering to use the Debtap script. That way you can install the file with Pacman and uninstall it cleanly when you no longer want it installed. Furthermore, dependencies are managed for you!

[audiojunkie]

Originally Posted by 4duhwinnn

A big part of linux is shedding elderly 'correct ways',
and using new or better ways. Using .vst instead of
some root permissioned folder from 2006, is more convenient
to musicians, while sysadmins may love or need /usr/xyz.

U-he chose .vst, so it's good enough for me too.
Cheers

I don't know if I would go quite so far with this. The "elderly 'correct ways'" were put in place for a reason to minimize problems with Linux and create a documented standard of sorts. I still think the elderly ways and ideas are important.

However, at the same time, I think the idea of Linux being only for scientists and developers is out of date. Things are now simplified enough that anyone can use Linux. And, I think it is important that we document and publish the easiest ways of doing things so that more people can enjoy the benefits of Linux.

An example of an old way that I think is no longer necessary, is JACK. It's nice to have (I still think it's nice to have), but as long as there are DAWs that host plugins, JACK is no longer really needed, and a DAW that hosts plugins doesn't need to share audio with other programs--thus ALSA is a perfectly fine solution, and JACK doesn't need to scare off new users. We should be teaching newcomers about how to set up with ALSA--later they can learn JACK functionality if they want.

An example of knowing the old ways is greater independence and flexibility--for example the benefit of knowing how to custom compile software and kernels, and how to manually tune a distro for low latency makes it so that anyone can do nearly anything with nearly any distro. It's beneficial and useful. However, not needed for everyone.

The whole Linux idea of "Do one thing and do it well" still has merit today--especially when having the ability to pipe the output of one app into the input of another--really beneficial.

So, I think a better way of looking at things is that the old ways are still important and beneficial for those who want to dig and understand and grow further with the world of Linux, but certainly not as necessary as it used to be.

One part of the elderly thinking that needs to be changed and we can all do our part to help with, is the old thinking that Linux is hard and difficult and scary, and Linux users are science nerds who lack the social skills and desire to help newcomers out. That's a perception we all need to work to change.

EDIT: That said, I'm all-in for better ways. If developers like Uhe start to use an easier path, and it becomes a common standard, I'm all for it. My point is just that the old ways were there for a reason and still have value.

[PMan]

The reason for the "elderly ways" of putting plugins in /usr/lib/vst was to make the plugin available to all of the users on the machine.

Plugins located in /home/<username>/.vst are only available to that user.

If there are two users on a machine, Jack and Jill, Jack can use plugins in /usr/lib/vst and /home/jack/.vst. Jack can't use plugins located in /home/jill/.vst. Jill can use plugins in /usr/lib/vst and /home/jill/.vst, but not /home/jack/.vst.

Not saying one way is more correct than another, they serve different functions. I *prefer* /home/<username>/.vst because I'm the only user who needs to access the plugins.

To each their own.

[norbury brook]

as a new linux user I came across this issue on day one fo my journey. I couldn't copy .so files into the /usr/lib/vst directory as I didn't have permissions. The only way I ended up doing it was to create a home/user/VSTplugins folder and add that to the reaper path, which of course worked perfectly.

Most computer users of windows/OSX are used to GUI's so the command line is scary to them. Having to manually build packages etc and change permissions just to install a plugin that is drag and drop in OSX or a double click in windows would put off anyone who want's to experiment quickly to see what linux is about.


Most musicians/photographers historically use OSX/mac computers because they're 'artistic' types and have no idea at all about technology/etc they want simplicity and ease of use. I was always thought of as unusual and nerdy because I started building my own computers and I used windows. I did this after actually researching native audio/DAW's and realised ASIO direct monitoring was the only way to work natively back then and Core audio didn't have this. So unless you were on protools TDM you had to deal with latency.


Even after all this I still found Linix a PIA to get working as well as windows or OSX.

After many years I tried again recently and I'm pleased to say things are much better


M

[GtrGeorge]

Not sure why/....but I downloaded it. Rescanned my VST plug-ins in Reaper and it isnt seen.
I powered down. Rebooted Reaper...still nothing.
Did they STOP making Sitala downloadable???

GtrGeorge

2/5/2023 uses a PC with Win10 and Reaper 5.9, with SSD and plenty of RAM

[Glennbo]

Originally Posted by GtrGeorge

Not sure why/....but I downloaded it. Rescanned my VST plug-ins in Reaper and it isnt seen.
I powered down. Rebooted Reaper...still nothing.
Did they STOP making Sitala downloadable???

GtrGeorge

2/5/2023 uses a PC with Win10 and Reaper 5.9, with SSD and plenty of RAM

I just downloaded the 64 bit Windows version, and it seemed to download okay. I'm running Linux though and already have the native Linux version installed and working, so I didn't see if it would install using WINE.

[foersu]

Originally Posted by lilith93

Just copy the file libsitala.so into your /home/yourname/.vst folder and rescan plugins in Reaper. You also might want to copy the drum kits there.

I am a little bit late with my question (I am really new to Reaper) but: where do I find the file libsitala.co?

Cheers.

[Primeval Mudd]

Originally Posted by foersu

I am a little bit late with my question (I am really new to Reaper) but: where do I find the file libsitala.co?

Cheers.

Hi foersu,

Sitala creates a new LXVST folder in lib, where the the vst, vst3, LV2 etc folders are, and pops itself in there.

I moved it to a regular .vst folder and it seems to be working OK from there.

Do you know how to find the standard vst/lv2/vst3 etc folders?

[foersu]

Hi,

I just added /usr/lib/lxvst in REAPER (thanks Axel!).
It works ok and I decided not to move it to another directory.

Thanks a lot for your answer and explanation.

Cheers!