"All the time" and "Quite frequently" sound like a bit too much for me, but I do use GIG and SFZ to some extent, along with WAV samples.
This is worrisome because Carla is all I have for now.
I have this 'ls16' you speak of, but Carla won't find it. Running it on the command line is one of the most difficult things I have tried to do on Linux bar compiling a kernel.
Code: Select all
usage: /usr/lib/dssi/ls16/ls16_gui <osc url> <plugin dllname> <plugin label> <user-friendly id>
I don't believe there is any hope I will ever understand people who think that I'll even know what an 'osc url' is much less remember this or that one 'osc url' whenever I want to run an application... or a sampler.
The only other sampler I have is for Windows and it only plays WAV files.
The sampling life is not very easy in Linux Land.
Look for ghostess in your repo. It will open ls16 as a plugin from the command line and gives you the gui as well.
you can do something like
$ ghostess ls16-dssi.so
and it will open to a small popup with a button marked UI. Press this and the magnificent interface that is LS16 will open.
Ghostess assumes your folder containing dssi's is in the usual places.
I have given up on carla for the linuxsampler problems and the restriction of one instrument per plugin. (no matter how many midi channels it has carla plays them all at once, so it's one midi channel per strip/plugin instance as far as i can tell and with experimenting). It's fine for those users who might have 10 or twelve single instruments on separate tracks, but for us folk who use herds of instrument articulations per instrument Carla is not designed to cater for that workflow.
A) Reaper with linuxsampler instances as plugins, saved as Reaper presets. You need to build these one at a time, as Fantasia and Qsampler will not open for each plugin instance selected by track. They'll only allow you to edit the first instance. So if you go down this path, you'll add a track to Reaper, add linuxsampler as a vst plugin, open Fantasia/Qsampler, add your instruments to each midi channel, save the track as an fx preset first, then as a Reaper track preset. When you've done this, you shut Fantasia/Qsampler down (i opened them in a terminal), then remove the track.
Wash, rinse, repeat. Be patient. It does work, and Reaper does remember what you've done. Best of all, there are actions for switching channels in Reaper, and i utilize the 16 pads on the top of my MPK88 to switch channels to the articulation i want for the track/instrument selected. As an example, i have two tracks for my 1st violins because i have more than 16 articulations.
You can also build midi instrument maps in linuxsampler as use these in your plugin instances. Then switch artics using programme changes. Repear will also faithfully record keyswitch data, if your gig is multi instrument.
I have over 178 Reaper presets created this way, and linuxsampler runs just fine even with all of them loaded. (My box has 64GB of ram)
B) Lately, Muse has improved further, and i have Muse3 installed as a backup. Muse does DSSI by default, BUT, ls16 will not save any instruments you have loaded in an instance. (Tim says DSSI doesn't do this, if i understood him correctly).
However, you can use LV2 quite successfully, using the same patient building process i described above.
I hope Tim finds a way around the saving preset DSSI conundrum, because it would be a lot easier to open the LS16 UI in Muse, per instance, load the instruments, and save them as a preset.
Hope this helps.
p.s. I have a lot of gig libraries, including some big orchestral sets. They're still as valid as anything else, and linuxsampler gives us the chance to keep using them. The samples are the same recordings, yes? I have a couple of Kontakt libs, but i've given up on them for their vehement anti-linux stance, and the sometimes yes sometimes no nature of using Wine. It was worth leaving all this stress behind, imho.
I respectfully urge anyone still using gig files to continue to do so. One day we'll have a proper plugin UI (LV2 and VST) for the mighty Linuxsampler, and all the effort i described above will diminish to something normal.
If i could code, and i'm no spring chicken, it'd be done already, and we'd all be swimming in Vegan Cream and Strawberries.