Re: [Jack-Devel] Alsa Jack Plugin

On Sat, June 30, 2012 1:22 pm, Salvatore De Paolis wrote:
> We can follow this on the list...
>
> On Sat, 30 Jun 2012 12:29:52 +0200 (CEST)
> "Patrick Shirkey" <[hidden]> wrote:
>
>> Do you have 6 outputs in qjackctl connections window or 2?
>
> I have an M-Audio Delta 1010LT, so basically 10 in / 10 out
>
>>
>> What is the output of these commands:
>>
>>     cat /proc/asound/cards
>>     cat /proc/asound/pcm
>> If the devices are not combined by your driver you might need to
>> configure
>> them with aconf so that you can see them all as a single "virtual"
>> device.
>>
>> Unless you have a professional audio device each output is probably a
>> sepearate alsa device and they need to be combined into a virtual device
>> to show up as one card.
>
> I'm not on that machine right now...
>
>>
>> Otherwise you have to tell jack to use each device seaperately.
>>
>> hw:0,0
>> hw:0,1
>> hw:0,2
>
> Well the device is just one, I think it's more something James guessed in
> the
> thread
>

Your usage is a bit unusual.

It seems like you want to connect certain ports when you start jack?

You don't need to use alsa configuration to achieve that goal. Just tell
qjackctl to store the graph and load it on start.

You can also write a script for that purpose.

And then there are a few other jack session management tools such as
ladish, non, lash, patchage, etc...

However if you are getting only two ports in qjackctl then you have a
problem with your jack setup or card configuration.

It's unclear exactly how many ports you can currently see in qjackctl
connections window...



--
Patrick Shirkey
Boost Hardware Ltd

1341059463.31238_0.ltw:2,a <64900.175.39.33.120.1341059453.squirrel at boosthardware dot com>