Anything like Sampletank in Linux?

[Audiojunkie]

Here’s another site that’s quite active:

https://linuxdaw.org/

[Largos]

@Audiojunkie Please don't tell people to install falktx's repository, especially someone new. This could cause problems now due to it not being updated and the artificially inflated version numbers that are used.

@pax-eterna Do not install kxstudio repos and use sfizz vst3 (not lv2) instead of linux sampler for sfz and fluid synth for sf2. Linux sampler is not as capable with sfz as sfizz is. It's main use is if you use the old gig sample format, it's the only thing that'll play that but you've given no indication you have that.

[glowrak guy]

To get much of the typical use of SampleTank, you can combine DecentSampleror SFizzz with Yoshimi synth. Yoshimi provides the 16 part layering capability (and excellent sounds) and DecentSampler/SFizzz can provide the sampled bread+butter sounds, piano, strings, woodwinds, percussion etc.
Cheers

[pax-eterna]

@Audiojunkie Please don't tell people to install falktx's repository, especially someone new. This could cause problems now due to it not being updated and the artificially inflated version numbers that are used.

@pax-eterna Do not install kxstudio repos and use sfizz vst3 (not lv2) instead of linux sampler for sfz and fluid synth for sf2. Linux sampler is not as capable with sfz as sfizz is. It's main use is if you use the old gig sample format, it's the only thing that'll play that but you've given no indication you have that.

woh!! ok thanks for the heads up. Will try to locate sfizz VST3.

Nope, you are correct, no Giga Sample anything

I did install the KX Repos but have not installed anything yet. Now looking at ways to remove it

EDIT: ok seemed to have done that successfully. Used purge in terminal. Re-booted and it all started fine and no issues in Reaper.

[pax-eterna]

coming across the same issues as always when trying to get this sfizz.

Go to website follow the instructions for adding this or that and just get messages like it's not available, or no pgp key or some other arcane messages. Or run this command or that command and get similar responses

It's why I like flatpack - it's more like a simple windows .exe file everything installs automatically!

[Largos]

coming across the same issues as always when trying to get this sfizz.

Go to website follow the instructions for adding this or that and just get messages like it's not available, or no pgp key or some other arcane messages. Or run this command or that command and get similar responses

It's why I like flatpack - it's more like a simple windows .exe file everything installs automatically!

Ok, you say Elementary is based on ubuntu 24.04. So you can download this https://download.opensuse.org/repositor ... _amd64.deb Go to the folder you installed it into, in a terminal and do

Code: Select all

sudo apt install ./sfizz_1.2.3-0_amd64.deb

That should install it.

[Audiojunkie]

@Audiojunkie Please don't tell people to install falktx's repository, especially someone new. This could cause problems now due to it not being updated and the artificially inflated version numbers that are used.

@pax-eterna Do not install kxstudio repos and use sfizz vst3 (not lv2) instead of linux sampler for sfz and fluid synth for sf2. Linux sampler is not as capable with sfz as sfizz is. It's main use is if you use the old gig sample format, it's the only thing that'll play that but you've given no indication you have that.

Nonsense! I completely disagree, Largo. There is nothing wrong with the KXStudio repositories, other than the fact that the plugins aren’t all the latest versions. All of the binaries are compiled on older distros (like all developers do) on purpose (for compatibility’s sake) for any libraries used. Nothing has changed in the ABIs/APIs. The libraries are backwards compatible. If you read the FAQ, it explains the version numbering as well. A user is very unlikely to have any dependency problems, and there should be no problems with the plugin libraries affecting system libraries. It seems you like fear mongering. Either that, or you have some sort of grudge against the KXStudio repositories, without fully understanding why they are the way they are. Again, much of your concerns are explained away in the FAQ. There is not going to be a problem with someone’s distro from using these plugins. I use them and they work flawlessly. I know many others that do too. Please stop trying to scare new users.

[Audiojunkie]

@Audiojunkie Please don't tell people to install falktx's repository, especially someone new. This could cause problems now due to it not being updated and the artificially inflated version numbers that are used.

@pax-eterna Do not install kxstudio repos and use sfizz vst3 (not lv2) instead of linux sampler for sfz and fluid synth for sf2. Linux sampler is not as capable with sfz as sfizz is. It's main use is if you use the old gig sample format, it's the only thing that'll play that but you've given no indication you have that.

woh!! ok thanks for the heads up. Will try to locate sfizz VST3.

Nope, you are correct, no Giga Sample anything

I did install the KX Repos but have not installed anything yet. Now looking at ways to remove it

EDIT: ok seemed to have done that successfully. Used purge in terminal. Re-booted and it all started fine and no issues in Reaper.

There was no need to uninstall the repos. They were fine.

[Largos]

@Audiojunkie Please don't tell people to install falktx's repository, especially someone new. This could cause problems now due to it not being updated and the artificially inflated version numbers that are used.

@pax-eterna Do not install kxstudio repos and use sfizz vst3 (not lv2) instead of linux sampler for sfz and fluid synth for sf2. Linux sampler is not as capable with sfz as sfizz is. It's main use is if you use the old gig sample format, it's the only thing that'll play that but you've given no indication you have that.

Nonsense! I completely disagree, Largo. There is nothing wrong with the KXStudio repositories, other than the fact that the plugins aren’t all the latest versions. All of the binaries are compiled on older distros (like all developers do) on purpose (for compatibility’s sake) for any libraries used. Nothing has changed in the ABIs/APIs. The libraries are backwards compatible. If you read the FAQ, it explains the version numbering as well. A user is very unlikely to have any dependency problems, and there should be no problems with the plugin libraries affecting system libraries. It seems you like fear mongering. Either that, or you have some sort of grudge against the KXStudio repositories, without fully understanding why they are the way they are. Again, much of your concerns are explained away in the FAQ. There is not going to be a problem with someone’s distro from using these plugins. I use them and they work flawlessly. I know many others that do too. Please stop trying to scare new users.

The version of lsp plugins is from october 2023 and that's one of the more recently updated ones. Not only that, the version is older than the one that is included in Ubuntu LTS. So, in essence, the versioning system would have downgraded this user's version of LSP plugins (and other software) and they likely would have not even known. If they had wanted to install a deb file updating to the new version of LSP plugins, they would have had to go through a number of steps unrelated to fixing their original query to fix the versioning issue. These are the kind of problems, I am talking about.

I don't want users to be scared away by unwittingly caused problems. I don't have any grudges against anyone or anything, I've previously used these repos for a long period and I understand them, tyvm. You can talk about FAQ's and extra information but you didn't mention them until after you got someone to install the repos. AFAIK, you didn't even know the FAQ existed, until you were told by falktx last night on mastodon, in your attempt to cause internet drama to protect your forum "reputation".

[Audiojunkie]

@Audiojunkie Please don't tell people to install falktx's repository, especially someone new. This could cause problems now due to it not being updated and the artificially inflated version numbers that are used.

@pax-eterna Do not install kxstudio repos and use sfizz vst3 (not lv2) instead of linux sampler for sfz and fluid synth for sf2. Linux sampler is not as capable with sfz as sfizz is. It's main use is if you use the old gig sample format, it's the only thing that'll play that but you've given no indication you have that.

Nonsense! I completely disagree, Largo. There is nothing wrong with the KXStudio repositories, other than the fact that the plugins aren’t all the latest versions. All of the binaries are compiled on older distros (like all developers do) on purpose (for compatibility’s sake) for any libraries used. Nothing has changed in the ABIs/APIs. The libraries are backwards compatible. If you read the FAQ, it explains the version numbering as well. A user is very unlikely to have any dependency problems, and there should be no problems with the plugin libraries affecting system libraries. It seems you like fear mongering. Either that, or you have some sort of grudge against the KXStudio repositories, without fully understanding why they are the way they are. Again, much of your concerns are explained away in the FAQ. There is not going to be a problem with someone’s distro from using these plugins. I use them and they work flawlessly. I know many others that do too. Please stop trying to scare new users.

The version of lsp plugins is from october 2023 and that's one of the more recently updated ones. Not only that, the version is older than the one that is included in Ubuntu LTS. So, in essence, the versioning system would have downgraded this user's version of LSP plugins (and other software) and they likely would have not even known. If they had wanted to install a deb file updating to the new version of LSP plugins, they would have had to go through a number of steps unrelated to fixing their original query to fix the versioning issue. These are the kind of problems, I am talking about.

I don't want users to be scared away by unwittingly caused problems. I don't have any grudges against anyone or anything, I've previously used these repos for a long period and I understand them, tyvm. You can talk about FAQ's and extra information but you didn't mention them until after you got someone to install the repos. AFAIK, you didn't even know the FAQ existed, until you were told by falktx last night on mastodon, in your attempt to cause internet drama to protect your forum "reputation".

If a program exists in the default repo, they should be installing it from the default repo, before looking for alternative repos. The OP was specifically looking for LinuxSampler.

No one is supposed to be upgrading the same program from multiple sources—especially without uninstalling the original package first. Upgrades for a package should come from the repo. Otherwise, one should uninstall the original package (and the repo) first, before upgrading from a different source. If one does things in the proper way, there will be no problem. However, I agree that the inflated versioning was not the best of practices, and I personally would not have done that if it had been me. But even still, upgrades should come from the repos that the packages are installed from. This is very, very basic Linux rules that everyone, even beginners should know, when using linux. I still maintain that the KXStudio repos are safe—despite the versioning, as long as the user follows the basic rules of installing and upgrading Linux software.

I don’t want any grudges or problems between us either, but surely there must be a more tactful way of going about things than following someone around and telling people to ignore the suggestions given--give an opposing view point if you want, but don't completely discredit the person who was offering the suggestion. I may occasionally make a mistake once in a while (everyone does), but I put thought into my suggestions that I give, and I give the suggestions with the desire to be helpful. Even if you disagree with me, there are less offensive ways to tell people that you disagree with someone’s suggestions.

[pax-eterna]

coming across the same issues as always when trying to get this sfizz.

Go to website follow the instructions for adding this or that and just get messages like it's not available, or no pgp key or some other arcane messages. Or run this command or that command and get similar responses

It's why I like flatpack - it's more like a simple windows .exe file everything installs automatically!

Ok, you say Elementary is based on ubuntu 24.04. So you can download this https://download.opensuse.org/repositor ... _amd64.deb Go to the folder you installed it into, in a terminal and do

Code: Select all

sudo apt install ./sfizz_1.2.3-0_amd64.deb

That should install it.

thanks, tried that and got "E: Unsupported file ./sfizz_1.2.3-0_amd64.deb given on commandline"

EDIT: then I recalled from somewhere I need to do a cd to the folder it was d/l to....did that and it did some processing but ended up with:

"N: Download is performed unsandboxed as root as file '/home/denzoid/Downloads/sfizz_1.2.3-0_amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)"

EDIT 2: I recalled that EOS has an app in the app store called Eddy that runs .deb files! Did that, then had to do a search on exactly where it installed to and then copied that vst3 folder over to my preferred folder on Home. Just opened it in Reaper! Now to get some sounds. I'll follow a similar procedure from now on as it seems to work.
Many thanks to @Audiojunkie and @Largos for all your help!! Even though you had a friendly disagreement, you were both instrumental (haha no pun!) in getting me started. I think I can start moving forward from here to develop a 100% Linux audio production system

When I understand a bit more about how it all works I will revisit the KX repos. At the moment, with the sites and apps mention by AJ, I have lots to go on with

Cheers

[Audiojunkie]

I'm glad you got things working. Just so you know, there are other tools for installing DEB files as well. I like GDEBI:

https://itsfoss.com/gdebi-default-ubunt ... re-center/

[Largos]

If a program exists in the default repo, they should be installing it from the default repo, before looking for alternative repos. The OP was specifically looking for LinuxSampler.

Then maybe you should have linked to the deb file rather than the whole repository.

No one is supposed to be upgrading the same program from multiple sources—especially without uninstalling the original package first. Upgrades for a package should come from the repo. Otherwise, one should uninstall the original package (and the repo) first, before upgrading from a different source. If one does things in the proper way, there will be no problem. However, I agree that the inflated versioning was not the best of practices, and I personally would not have done that if it had been me. But even still, upgrades should come from the repos that the packages are installed from. This is very, very basic Linux rules that everyone, even beginners should know, when using linux.

I didn't see this around "This will make your life much, much easier!!"

I still maintain that the KXStudio repos are safe—despite the versioning, as long as the user follows the basic rules of installing and upgrading Linux software.

I didn't say they were unsafe. I said they could cause problems for the reasons I said. There's no reason to recommend such an outdated repository with a odd and potentially problem causing versioning system, when there are better ways of getting the software. Even just downloading the individual deb files from the same site.

I don’t want any grudges or problems between us either, but surely there must be a more tactful way of going about things than following someone around and telling people to ignore the suggestions given--give an opposing view point if you want, but don't completely discredit the person who was offering the suggestion. I may occasionally make a mistake once in a while (everyone does), but I put thought into my suggestions that I give, and I give the suggestions with the desire to be helpful. Even if you disagree with me, there are less offensive ways to tell people that you disagree with someone’s suggestions.

Your suggestion was stupid and you are a grown up. I'm not going to sugar coat things to protect anyone's internet ego. The only person who discredited you is yourself by going off site and trying to get the repo maintainer to come here and start arguing the toss with me.

[Largos]

"N: Download is performed unsandboxed as root as file '/home/denzoid/Downloads/sfizz_1.2.3-0_amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)"

You can ignore this message. It should have installed anyway.

EDIT 2: I recalled that EOS has an app in the app store called Eddy that runs .deb files! Did that, then had to do a search on exactly where it installed to and then copied that vst3 folder over to my preferred folder on Home. Just opened it in Reaper! Now to get some sounds. I'll follow a similar procedure from now on as it seems to work.

You didn't need to move it. There are standard folders in the system directory that package manager files like deb use to install vst3 and daw's should be set to search these directories for the files. No reason to move it back but just note if in future you use apt to remove sfizz it won't remove the files you moved.
[/quote]

[jmantra623]

Came across this:

https://github.com/pumodi/open-samples