linuxsampler-devel

[Linuxsampler-devel] example script generates errors

[Markus W. K. <kr...@ko...>]

Hi there developers,

I tried to use the example script from your homepage, thzat explains how to connect LinuxSampler automatically to Jack. Following options of your script
generates errors in Qsampler, because Qsampler cannot find the output:

SET AUDIO_OUTPUT_CHANNEL_PARAMETER 0 0 JACK_BINDINGS='alsa_pcm:playback_1'
SET AUDIO_OUTPUT_CHANNEL_PARAMETER 0 1 JACK_BINDINGS='alsa_pcm:playback_2'

I changed the "alsa_pcm:playback_1" to "system:playback_1" and similar *_2

Please patch this into your script for others, would be nice.

I am working on Debian-Sid with Jack, ALSA, LinuxSampler, Frescobaldi, Renoise and some Softsynths and Effects.


Greetings!

Markus3000 aka Musix


-----
Musix-Blog - Über meine Kompositionen - http://www.musix-de.blogspot.com
Musix-Wiki - Den Computer zum Komponieren einrichten - http://www.musix-wiki.org

Klavierunterricht in Köln - http://www.koelnklassik.de/klavierunterricht.htm

Markus W. Kropp
Buchholzstr. 36
51061 Köln
Tel.:0221-4719703

kr...@ko...

Re: [Linuxsampler-devel] example script generates errors

[Christian S. <sch...@li...>]

On Wednesday 14 March 2012 11:36:57 Markus W. Kropp wrote:
> I tried to use the example script from your homepage, thzat explains how to
> connect LinuxSampler automatically to Jack. Following options of your
> script generates errors in Qsampler, because Qsampler cannot find the
> output:
> 
> SET AUDIO_OUTPUT_CHANNEL_PARAMETER 0 0 JACK_BINDINGS='alsa_pcm:playback_1'
> SET AUDIO_OUTPUT_CHANNEL_PARAMETER 0 1 JACK_BINDINGS='alsa_pcm:playback_2'
> 
> I changed the "alsa_pcm:playback_1" to "system:playback_1" and similar *_2
> 
> Please patch this into your script for others, would be nice.

Yes, you are right, the main client name is now "system" on JACK2 / jackdmp. 
But how is it with JACK1? Isn't that still using the old name "alsa_pcm"?

CU
Christian