16-channel recording w/ LAYLA, ALSA, JACK, ARDOUR

16-channel recording w/ LAYLA, ALSA, JACK, ARDOUR

[Lance Blisters]

I bought a Layla24 and Cardbus adaptor.  Works beatifully with ALSA/JACK/ARDOUR up to 8 channels.  However, the soundcard presents the 8 analog channels as device 0 and 8 digital channels as device 1.  JACK will only open one device at a time.  So in order to record 16 channels with Ardour, I apparently need to create a virtual ALSA device combining the two LAYLA subdevices.

Has anyone solved this problem for this device?  I know ".asoundrc" and 
"multi" and company, but that is far from a complete answer - what
I really need is an actual functional .asoundrc.

Please CC me, as I had to drop off the list about five years ago due to
bandwidth limitations.

Thanks,

  -geoff


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: 16-channel recording w/ LAYLA, ALSA, JACK, ARDOUR

[Lee Revell]

On Wed, 2006-04-12 at 13:09 -0700, Lance Blisters wrote:
> I bought a Layla24 and Cardbus adaptor.  Works beatifully with ALSA/JACK/ARDOUR up to 8 channels.  However, the soundcard presents the 8 analog channels as device 0 and 8 digital channels as device 1.  JACK will only open one device at a time.  So in order to record 16 channels with Ardour, I apparently need to create a virtual ALSA device combining the two LAYLA subdevices.
> 
> Has anyone solved this problem for this device?  I know ".asoundrc" and 
> "multi" and company, but that is far from a complete answer - what
> I really need is an actual functional .asoundrc.
> 
> Please CC me, as I had to drop off the list about five years ago due to
> bandwidth limitations.

Maybe someone can explain why this .asoundrc does not work, AFAICT it
should.  The error is:

ALSA lib conf.c:1592:(snd_config_load1)_toplevel_:606:27:Unexpected char
ALSA lib conf.c:2837:(snd_config_hook_load)/root/.asoundrc may be old or
corrupted consider to remove or fix it

Character 27 is either the '1' or the newline.

The analog device is "hw:0,0" and digital "hw:0,1", right?

# .asoundrc for layla 
#
# Create virtual devices out of multipls subdevices
# JACK will need MMAP_COMPLEX support to use this. 

pcm.multi_capture {
	type multi
	slaves.a.pcm hw:0,0
	slaves.a.channels 8
	slaves.b.pcm hw:0,1
	slaves.b.channels 8

# First 8 channels of first soundcard (capture)
	bindings.0.slave a
	bindings.0.channel 0
	bindings.1.slave a
	bindings.1.channel 1
	bindings.2.slave a
	bindings.2.channel 2
	bindings.3.slave a
	bindings.3.channel 3
	bindings.4.slave a
	bindings.4.channel 4
	bindings.5.slave a
	bindings.5.channel 5
	bindings.6.slave a
	bindings.6.channel 6
	bindings.7.slave a
	bindings.7.channel 7
    
# First 8 channels of second soundcard (capture)
	bindings.8.slave b
	bindings.8.channel 0
	bindings.9.slave b
	bindings.9.channel 1
	bindings.10.slave b
	bindings.10.channel 2
	bindings.11.slave b
	bindings.11.channel 3
	bindings.12.slave b
	bindings.12.channel 4
	bindings.13.slave b
	bindings.13.channel 5
	bindings.14.slave b
	bindings.14.channel 6
	bindings.15.slave b
	bindings.15.channel 7

}

ctl.multi_capture {
	type hw
	card 0
}

pcm.multi_playback {
	type multi
	slaves.a.pcm hw:0,0
	slaves.a.channels 8
	slaves.b.pcm hw:0,1
	slaves.b.channels 8

# First 8 channels of first soundcard (playback)
	bindings.0.slave a
	bindings.0.channel 0
	bindings.1.slave a
	bindings.1.channel 1
	bindings.2.slave a
	bindings.2.channel 2
	bindings.3.slave a
	bindings.3.channel 3
	bindings.4.slave a
	bindings.4.channel 4
	bindings.5.slave a
	bindings.5.channel 5
	bindings.6.slave a
	bindings.6.channel 6
	bindings.7.slave a
	bindings.7.channel 7

# First 8 channels of second soundcard (playback)
	bindings.8.slave b
	bindings.8.channel 0
	bindings.9.slave b
	bindings.9.channel 1
	bindings.10.slave b
	bindings.10.channel 2
	bindings.11.slave b
	bindings.11.channel 3
	bindings.12.slave b
	bindings.12.channel 4
	bindings.13.slave b
	bindings.13.channel 5
	bindings.14.slave b
	bindings.14.channel 6
	bindings.15.slave b
	bindings.15.channel 7

}

ctl.multi_playback {
	type hw
	card 0
}






-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: 16-channel recording w/ LAYLA, ALSA, JACK, ARDOUR

[Lee Revell]

On Wed, 2006-04-12 at 16:18 -0400, Lee Revell wrote:
> On Wed, 2006-04-12 at 13:09 -0700, Lance Blisters wrote:
> > I bought a Layla24 and Cardbus adaptor.  Works beatifully with ALSA/JACK/ARDOUR up to 8 channels.  However, the soundcard presents the 8 analog channels as device 0 and 8 digital channels as device 1.  JACK will only open one device at a time.  So in order to record 16 channels with Ardour, I apparently need to create a virtual ALSA device combining the two LAYLA subdevices.
> > 
> > Has anyone solved this problem for this device?  I know ".asoundrc" and 
> > "multi" and company, but that is far from a complete answer - what
> > I really need is an actual functional .asoundrc.
> > 
> > Please CC me, as I had to drop off the list about five years ago due to
> > bandwidth limitations.
> 
> Maybe someone can explain why this .asoundrc does not work, AFAICT it
> should.  The error is:
> 
> ALSA lib conf.c:1592:(snd_config_load1)_toplevel_:606:27:Unexpected char
> ALSA lib conf.c:2837:(snd_config_hook_load)/root/.asoundrc may be old or
> corrupted consider to remove or fix it
> 
> Character 27 is either the '1' or the newline.
> 
> The analog device is "hw:0,0" and digital "hw:0,1", right?
> 
> # .asoundrc for layla 
> #
> # Create virtual devices out of multipls subdevices
> # JACK will need MMAP_COMPLEX support to use this. 
> 
> pcm.multi_capture {
> 	type multi
> 	slaves.a.pcm hw:0,0
> 	slaves.a.channels 8
> 	slaves.b.pcm hw:0,1
> 	slaves.b.channels 8
> 

Can you try replacing "slaves.a.pcm hw:0,0" with:

slaves.a.pcm {
	type hw;
	card 0;
	device 0;
}

etc. ?

> # First 8 channels of first soundcard (capture)
> 	bindings.0.slave a
> 	bindings.0.channel 0
> 	bindings.1.slave a
> 	bindings.1.channel 1
> 	bindings.2.slave a
> 	bindings.2.channel 2
> 	bindings.3.slave a
> 	bindings.3.channel 3
> 	bindings.4.slave a
> 	bindings.4.channel 4
> 	bindings.5.slave a
> 	bindings.5.channel 5
> 	bindings.6.slave a
> 	bindings.6.channel 6
> 	bindings.7.slave a
> 	bindings.7.channel 7
>     
> # First 8 channels of second soundcard (capture)
> 	bindings.8.slave b
> 	bindings.8.channel 0
> 	bindings.9.slave b
> 	bindings.9.channel 1
> 	bindings.10.slave b
> 	bindings.10.channel 2
> 	bindings.11.slave b
> 	bindings.11.channel 3
> 	bindings.12.slave b
> 	bindings.12.channel 4
> 	bindings.13.slave b
> 	bindings.13.channel 5
> 	bindings.14.slave b
> 	bindings.14.channel 6
> 	bindings.15.slave b
> 	bindings.15.channel 7
> 
> }
> 
> ctl.multi_capture {
> 	type hw
> 	card 0
> }
> 
> pcm.multi_playback {
> 	type multi
> 	slaves.a.pcm hw:0,0
> 	slaves.a.channels 8
> 	slaves.b.pcm hw:0,1
> 	slaves.b.channels 8
> 
> # First 8 channels of first soundcard (playback)
> 	bindings.0.slave a
> 	bindings.0.channel 0
> 	bindings.1.slave a
> 	bindings.1.channel 1
> 	bindings.2.slave a
> 	bindings.2.channel 2
> 	bindings.3.slave a
> 	bindings.3.channel 3
> 	bindings.4.slave a
> 	bindings.4.channel 4
> 	bindings.5.slave a
> 	bindings.5.channel 5
> 	bindings.6.slave a
> 	bindings.6.channel 6
> 	bindings.7.slave a
> 	bindings.7.channel 7
> 
> # First 8 channels of second soundcard (playback)
> 	bindings.8.slave b
> 	bindings.8.channel 0
> 	bindings.9.slave b
> 	bindings.9.channel 1
> 	bindings.10.slave b
> 	bindings.10.channel 2
> 	bindings.11.slave b
> 	bindings.11.channel 3
> 	bindings.12.slave b
> 	bindings.12.channel 4
> 	bindings.13.slave b
> 	bindings.13.channel 5
> 	bindings.14.slave b
> 	bindings.14.channel 6
> 	bindings.15.slave b
> 	bindings.15.channel 7
> 
> }
> 
> ctl.multi_playback {
> 	type hw
> 	card 0
> }
> 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-devel
> 



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: 16-channel recording w/ LAYLA, ALSA, JACK, ARDOUR

[Lee Revell]

On Wed, 2006-04-12 at 16:18 -0400, Lee Revell wrote:
> pcm.multi_capture {
> 	type multi
> 	slaves.a.pcm hw:0,0
> 	slaves.a.channels 8
> 	slaves.b.pcm hw:0,1
> 	slaves.b.channels 8

Please disregard last message - try simply surrounding hw:0,0 and hw:0,1
with quotes.

pcm.multi_capture {
	type multi
	slaves.a.pcm "hw:0,0"
	slaves.a.channels 8
	slaves.b.pcm "hw:0,1"
	slaves.b.channels 8

Lee



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: 16-channel recording w/ LAYLA, ALSA, JACK, ARDOUR

[Lance Blisters]

On Wed, Apr 12, 2006 at 05:40:00PM -0400, Lee Revell wrote:
> 
> Please disregard last message - try simply surrounding hw:0,0 and hw:0,1
> with quotes.
> 
> pcm.multi_capture {
> 	type multi
> 	slaves.a.pcm "hw:0,0"
> 	slaves.a.channels 8
> 	slaves.b.pcm "hw:0,1"
> 	slaves.b.channels 8

Quotes don't work.  To get around the parse error, i need
to give a name to the device elsewhere then refer to it by
name.

So for some reason

pcm.multi_capture {
	type multi
	slaves.a.pcm "hw:2,0"
	slaves.a.channels 8
	slaves.b.pcm "hw:2,1"
	slaves.b.channels 8

will fail to parse, but

pcm.layla_analog {
	type hw
	card 2
	device 0
}
pcm.layla_digital {
	type hw
	card 2
	device 1
}
pcm.multi_capture {
        type multi
        slaves.a.pcm layla_analog
        slaves.a.channels 8
        slaves.b.pcm layla_digital
        slaves.b.channels 8

  
will parse OK.  


However, trying to run jack via qjackctl with a 
few simple configs that the LAYLA is capable of yields:

/usr/bin/jackd -R -t5000 -dalsa -dmulti_playback -r44100 -p256 -n2 -P -o2
jackd 0.100.6
loading driver ..
apparent rate = 44100
creating alsa driver ... multi_playback|-|256|2|44100|0|2|nomon|swmeter|-|32bit
configuring for 44100Hz, period = 256 frames, buffer = 2 periods
ALSA: no playback configurations available (Invalid argument)
ALSA: cannot configure playback channel
cannot load driver module alsa


Maybe need to define channels and/or rate in layla_* and/or multi*
but in the past the presence of those has also seemed to cause problems
(even if the definitions are accurate).


Beyond that, the solution you suggest creates two devices, one 
16 channel playback the other 16 channel capture.  The core problem 
is that JACK will only open a single device.  So even if multi_playback
and _capture worked, to the best of my knowledge that would still
not enable me to run ardour in 16 channel duplex.  Wouldn't it require
another layer of asym or something to present it as a single device?
Or can _playback itself be opened duplex?  The definition seems
identical to _capture anyhow....

  -geoff



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: 16-channel recording w/ LAYLA, ALSA, JACK, ARDOUR

[Paul Davis]

On Wed, 2006-04-12 at 20:17 -0700, Lance Blisters wrote:

> ALSA: cannot configure playback channel
> cannot load driver module alsa

i don't believe that "multi" will work without the MMAP_COMPLEX patch to
JACK that has been outstanding for months and months. its available in
the patch tracker at jackit.sf.net if you want to try it; otherwise i
intend to merge it next week or the week after.

> Beyond that, the solution you suggest creates two devices, one 
> 16 channel playback the other 16 channel capture.  The core problem 
> is that JACK will only open a single device.  So even if multi_playback
> and _capture worked, to the best of my knowledge that would still
> not enable me to run ardour in 16 channel duplex.  Wouldn't it require
> another layer of asym or something to present it as a single device?
> Or can _playback itself be opened duplex?  The definition seems
> identical to _capture anyhow....

this command: 

   jackd -d alsa -P hw:0 -C hw:1

opens different devices for capture and playback

--p






-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: 16-channel recording w/ LAYLA, ALSA, JACK, ARDOUR

[Lee Revell]

On Wed, 2006-04-12 at 20:17 -0700, Lance Blisters wrote:
> /usr/bin/jackd -R -t5000 -dalsa -dmulti_playback -r44100 -p256 -n2 -P
> -o2
> jackd 0.100.6 

Why are you using -o2 - you want 16 output channels, not 2 right?

Lee



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: 16-channel recording w/ LAYLA, ALSA, JACK, ARDOUR

[Lance Blisters]

On Wed, Apr 12, 2006 at 11:29:30PM -0400, Paul Davis wrote:
> On Wed, 2006-04-12 at 20:17 -0700, Lance Blisters wrote:
> 
> > ALSA: cannot configure playback channel
> > cannot load driver module alsa
> 
> i don't believe that "multi" will work without the MMAP_COMPLEX patch to
> JACK that has been outstanding for months and months. its available in
> the patch tracker at jackit.sf.net if you want to try it; otherwise i
> intend to merge it next week or the week after.

So the only way to get 16 channels from the LAYLA is via 
MMAP_COMPLEX and multi?

Do you think the above problem is a direct result of lacking
MMAP_COMPLEX functionality, and .asoundrc might be otherwise 
correct?

> this command: 
> 
>    jackd -d alsa -P hw:0 -C hw:1
> 
> opens different devices for capture and playback

Great! I was thrown by the single Interface selection
in qjackctl, and my assumption that different cards
for input and output would present similar drift and
synch problems as outputting to multiple cards.

  -geoff



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: 16-channel recording w/ LAYLA, ALSA, JACK, ARDOUR

[John Rigg]

On Wed, Apr 12, 2006 at 10:39:45PM -0700, Lance Blisters wrote:
> On Wed, Apr 12, 2006 at 11:29:30PM -0400, Paul Davis wrote:
> > On Wed, 2006-04-12 at 20:17 -0700, Lance Blisters wrote:
> > 
> > > ALSA: cannot configure playback channel
> > > cannot load driver module alsa
> > 
> > i don't believe that "multi" will work without the MMAP_COMPLEX patch to
> > JACK that has been outstanding for months and months. its available in
> > the patch tracker at jackit.sf.net if you want to try it; otherwise i
> > intend to merge it next week or the week after.
> 
> So the only way to get 16 channels from the LAYLA is via 
> MMAP_COMPLEX and multi?
> 
> Do you think the above problem is a direct result of lacking
> MMAP_COMPLEX functionality, and .asoundrc might be otherwise 
> correct?
> 
> > this command: 
> > 
> >    jackd -d alsa -P hw:0 -C hw:1
> > 
> > opens different devices for capture and playback
> 
> Great! I was thrown by the single Interface selection
> in qjackctl, and my assumption that different cards
> for input and output would present similar drift and
> synch problems as outputting to multiple cards.

Analog and digital inputs and outputs on the same physical card use the
same word clock even if you have separate virtual devices defined.

Another thing: if you try to use -o2 ALSA doesn't like it.
Anything other than the full number of channels (the default)
doesn't work, which seems to defeat the object of the -o option. Just
leave the -o option out (same applies to -i).

Since your analogue and digital in/outs are different logical devices
you might have to remove the linking code that was added to pcm_multi.c
between alsa-lib versions 1.0.8 and 1.0.9rc1. This broke duplex jackd
operation with multiple cards; it's possible that it affects your
multiple devices too. You might also need MMAP_COMPLEX support in jackd.

John


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: 16-channel recording w/ LAYLA, ALSA, JACK, ARDOUR

[Lance Blisters]

On Wed, Apr 12, 2006 at 11:29:30PM -0400, Paul Davis wrote:
> On Wed, 2006-04-12 at 20:17 -0700, Lance Blisters wrote:
> 
> > ALSA: cannot configure playback channel
> > cannot load driver module alsa
> 
> i don't believe that "multi" will work without the MMAP_COMPLEX patch to
> JACK that has been outstanding for months and months. its available in
> the patch tracker at jackit.sf.net if you want to try it; otherwise i
> intend to merge it next week or the week after.

is this it?

[ 1289682 ] M-Audio Audiophile USB and other byteswapped devices support

i applied it (had to apply memop.c by hand), but

JACK_DRIVER_DIR=./drivers/alsa/.libs/ ./jackd/jackd -R -t5000 -dalsa -dmulti_playback -r44100 -p256 -n2 -P -s
loading driver ..
apparent rate = 44100
creating alsa driver ... multi_playback|-|256|2|44100|0|0|nomon|swmeter|soft-mode|32bit
configuring for 44100Hz, period = 256 frames, buffer = 2 periods
ALSA: no playback configurations available (Invalid argument)
ALSA: cannot configure playback channel
cannot load driver module alsa
zsh: segmentation fault  JACK_DRIVER_DIR=./drivers/alsa/.libs/ ./jackd/jackd -R -t5000 -dalsa  -r44100

the other three patches don't seem relevant.

> this command: 
> 
>    jackd -d alsa -P hw:0 -C hw:1
> 
> opens different devices for capture and playback

glad i was wrong about this.

  -geoff



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: 16-channel recording w/ LAYLA, ALSA, JACK, ARDOUR

[Lee Revell]

On Thu, 2006-04-13 at 20:00 -0700, Lance Blisters wrote:
> 
> is this it?
> 
> [ 1289682 ] M-Audio Audiophile USB and other byteswapped devices
> support
> 

No, it would have MMAP_COMPLEX in the name.  You can probably find it
googling "jack MMAP_COMPLEX patch"

Lee



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: 16-channel recording w/ LAYLA, ALSA, JACK, ARDOUR

[Lance Blisters]

> Another thing: if you try to use -o2 ALSA doesn't like it.
> Anything other than the full number of channels (the default)
> doesn't work, which seems to defeat the object of the -o option. Just
> leave the -o option out (same applies to -i).

I used two channels output because I wanted the simplest test, I
didn't want to conflate it with correctness of input device,
or ability to actually access upper 8 channels.  That config
works with hw:2,0 but not multi_playback.  After your suggestion
I also tried 16 out, and removing -o entirely from the
command line, got the same result:

ALSA: no playback configurations available (Invalid argument)
ALSA: cannot configure playback channel
cannot load driver module alsa

> Since your analogue and digital in/outs are different logical devices
> you might have to remove the linking code that was added to pcm_multi.c
> between alsa-lib versions 1.0.8 and 1.0.9rc1. This broke duplex jackd
> operation with multiple cards; it's possible that it affects your
> multiple devices too. You might also need MMAP_COMPLEX support in jackd.

I have alsa-lib 1.0.10.26 as part of planet-ccrma, and there doesn't seem
to be any suitably old version of alsa-lib in any of my package 
repositories.  If MMAP_COMPLEX doesn't help i'll look into it further.

Is there a way to have ALSA remap the memory, so that it appears to JACK
in one of the supported formats?  Even if there is a performance loss?

If I use as asym or similar to further wrap multi_playback and
_capture as a single virtual device, would this help with
the "duplex jackd operation with multiple cards" problem?

Thanks for the advice.

  -geoff



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: 16-channel recording w/ LAYLA, ALSA, JACK, ARDOUR

[Lance Blisters]

Disregard my question about having ALSA re-map.  I found your
page about solving this problem for the ice1712 which discusses
route plugin.

  -geoff


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: 16-channel recording w/ LAYLA, ALSA, JACK, ARDOUR

[Lance Blisters]

Well, I did have to patch JACK with MMAP_COMPLEX, I did have to
patch alsa-lib pcm_multi.c to enable duplex, I did some more
tests with .asoundrc.  I had to use echomixer to change some of
the settings before i could access the 8 digital outputs even directly.
I also discovered that during testing the LAYLA would get into 
bad states where even simple access no longer worked, and would 
have to reboot to get it working.  My multi declaration couldn't
refer directly to hw:2,0 but rather to a different pcm definition 
which in turn referred to hw:2,0.  I must open all channels of the
multi devices.

Now I have latest JACK from CCRMA in /usr/lib and JACK from CVS
patched for MMAP in a local directory.  I have alsa-lib RPM from
fedora core updates, patched for duplex multi access.  I can run
my patched JACK, and i can open multi_playback and multi_capture
with 16 channels each, JACK runs and reports the rare XRUN.  But
I can't connect from any clients; starting with QJACKCTL yields
"Cannot connect to JACK server as client" and ardour tries to start
its own server then fails because one is already running, then
"Could not connect to JACK server as  "ardour"".  I get the
same JACK connection problem whether using direct card access
or ALSA multi device.

Must be related to permissions / capabilities?  I'm running
everything as root, which works with CCRMA's JACK.  CCRMA doesn't
seem to offer SRPMS anymore, so I can't recreate how it was built.
Maybe some autogen.sh args will yield a compatible JACK?  I
built with and without --enable-capablities and got same results.

  -geoff



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: 16-channel recording w/ LAYLA, ALSA, JACK, ARDOUR

[John Rigg]

On Fri, Apr 14, 2006 at 01:26:32AM -0700, Lance Blisters wrote:
> Now I have latest JACK from CCRMA in /usr/lib and JACK from CVS
> patched for MMAP in a local directory.  I have alsa-lib RPM from
> fedora core updates, patched for duplex multi access.  I can run
> my patched JACK, and i can open multi_playback and multi_capture
> with 16 channels each, JACK runs and reports the rare XRUN.  But
> I can't connect from any clients; starting with QJACKCTL yields
> "Cannot connect to JACK server as client" and ardour tries to start
> its own server then fails because one is already running, then
> "Could not connect to JACK server as  "ardour"".  I get the
> same JACK connection problem whether using direct card access
> or ALSA multi device.

If you have two versions of JACK installed it will cause problems.
Ardour expects to find libjack.so in /usr/lib and will use that instead of
the one in /usr/local/lib. You can make it use the correct one by
removing the packaged version and putting a symlink from
/usr/lib/libjack.so to /usr/local/lib/libjack.so:

ln -s /usr/local/lib/libjack.so /usr/lib/libjack.so

John


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: 16-channel recording w/ LAYLA, ALSA, JACK, ARDOUR

[Lee Revell]

On Fri, 2006-04-14 at 01:26 -0700, Lance Blisters wrote:
> Now I have latest JACK from CCRMA in /usr/lib and JACK from CVS
> patched for MMAP in a local directory.  I have alsa-lib RPM from
> fedora core updates, patched for duplex multi access.  I can run
> my patched JACK, and i can open multi_playback and multi_capture
> with 16 channels each, JACK runs and reports the rare XRUN.  But
> I can't connect from any clients; starting with QJACKCTL yields
> "Cannot connect to JACK server as client" and ardour tries to start
> its own server then fails because one is already running, then
> "Could not connect to JACK server as  "ardour"".  I get the
> same JACK connection problem whether using direct card access
> or ALSA multi device.
> 

The problem is probably that you have 2 different versions of JACK
installed.  This will lead to bizarre behavior.

Lee




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: 16-channel recording w/ LAYLA, ALSA, JACK, ARDOUR

[Giuliano Pochini]

On Fri, 14 Apr 2006, Lance Blisters wrote:

> I also discovered that during testing the LAYLA would get into
> bad states where even simple access no longer worked, and would
> have to reboot to get it working.

Hrm :-/    More details ?


--
Giuliano.


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: 16-channel recording w/ LAYLA, ALSA, JACK, ARDOUR

[Lance Blisters]

> >I also discovered that during testing the LAYLA would get into
> >bad states where even simple access no longer worked, and would
> >have to reboot to get it working.
> 
> Hrm :-/    More details ?

Unfortunately not much at hand.  It was a long, late night in 
which I was trying many permutations of .asoundconf definitions 
and JACK arguments.  When I reached a dead end, I would undo my
changes back to a stable point.  Several times, I would try to
run JACK with the simplest, 2-out direct hw acess config which
had always worked.  On these times, it would fail.  Restarting
the ALSA init script, the LAYLA driver would not load (didn't 
look deep into it, but wasn't listed under /proc/asound/) and 
trying cardctl eject/insert to reload the card and driver would 
hang - at least once, it hung my whole system including mouse 
input and keyboard input and I had to force a hard reboot.  
After a hard or soft reboot, card would come back, and the 
simplest config would work again.

This is using one of the recent CCRMA lowlat kernels on FC4.  I'm 
at my day job now and can't pull up further info but if you have
specific questions I can look into it (might not be till next
weekend, as i'm scrambling with music gigs, day job, travel, and
trying to get the ALSA/JACK/LAYLA setup resolved before a
big public event at a Texas festival next week).

  -geoff



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: 16-channel recording w/ LAYLA, ALSA, JACK, ARDOUR

[Fernando Lopez-Lezcano]

On Fri, 2006-04-14 at 01:26 -0700, Lance Blisters wrote:
> Must be related to permissions / capabilities?  I'm running
> everything as root, which works with CCRMA's JACK.  CCRMA doesn't
> seem to offer SRPMS anymore, so I can't recreate how it was built.
> Maybe some autogen.sh args will yield a compatible JACK? 

SRPMS are always available at:
  http://ccrma.stanford.edu/planetccrma/mirror/all/linux/SRPMS/
-- Fernando




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642