Re: [Linuxsampler-devel] [ANNOUNCE] QSampler 0.0.1 released!

[Rui N. C. <rn...@rn...>]

Mark,

>
>>>2) I'm gettting the left channel only on the version of LS
>>>on your web site. [...]
>>
>> Please try one of yesterday's, [...] (http://www.rncbc.org/ls).
>
> All fixed. Much better. Volume slider actually works very nicely in real
> time. I can trigger a note with a long decay and then raise and lower
> volume. Seems to work nicely. (What about a pan control?) ;-)
>

Unfortunately there's no way to have such a pan control by current LSCP
command interface, nor it's in the v.07 protocol draft. Meanwhile, it's
also assuming that sampler channels are stereo, which might not always be
true.

Perhaps in some other way, as audio channel routing becomes effective, it
could include individual volume per audio mix channel. That could be handy
in implemeting a pan control. Suggestion: extending SET CHANNEL
AUDIO_OUTPUT_CHANNEL command with an additional gain/attenuation
coefficient?

>
> I think Benno is right. It's the large gigs that never load for me. The
> small ones do what you say - sometimes don't load the first time then
> load fine the second time.
>

Yeah. Something in the lines of Benno proposition might be the definitive
solution. That is, the LOAD INSTRUMENT command returning an incremental
status instead of blocking until it's complete, which is annoying to say
the least, even if you set the timeout value too high, making the GUI
quite unresponsive while the file is being loaded by the server.

Let's see what comes about this. votes++ on the incremental load protocol :)

>
> OK, so with the current versions things are working a bit better. Volume
> control works great. S/V count is a bit better.
>
> Enhancement request - a command line option to make default channel
> audio connection with Alsa or Jack for this instance of QS.
>
> qsampler -a {alsa:jack}
>

Again, that will be OK when LSCP implementation get's over it. The
abstract device driver model which is in the latest draft might come to
the rescue.

Meanwhile, you can take advantage of qjackctl's active patchbay feature
for just exactly what you want. Let me show you how:

1. Setup a QS/LS session the way you want, the way you play and hear some
notes, of course. That includes the MIDI source program (e.g. vkeybd). By
this time you'll still have to connect all the ALSA and JACK ports
manually, probably using qjackctl's Connections facility.

2. When you have everything working as you like, open up the Patchbay
window from qjackctl. Press the "New" button and answer "Yes" to the
snapshot question.

3. Hopefully, you'll get a model of all current ALSA and JACK connections.
Edit them as you please in such a way that you end only with the
LinuxSampler connections you want.

3. Save to a pachbay definition file (it's plain xml).

4. Activate the patchbay.

5. That's it. From now on, provided you're running qjackctl, the active
patchbay will be kind of persistent. Whenever LinuxSampler's JACK/ALSA
clients shows up, the respective connections get wired up automagically :)

Hope you enjoy it.

Cheers.
-- 
rncbc aka Rui Nuno Capela
rn...@rn...