>NO one has specifically sent a copy of the file for the Delta 66 that I
>can seem to understand and there seem to be a few diferent versions
>floating about on the mailing lists. (ardour-dev,alsa-dev, and
>alsa-user).
>
>If anyone could help here by sending an asoundrc file configured for a
>similar setup (Delta 44,66,1010 and a domestic card, preferably for ue
>with Ardour as well) or a clear and simple explanation of how to set
>this up for multichannel cards. (if anyone has the appropriate setup for
>a MOTU MTP-AV, ro Midi Express XT then I'll be in 7th heaven) This must
>allow multichannel recording...
there is no special set up *necessary* for any cards at all.
the most important purpose of an asoundrc file is to *name* PCM
devices. hence, the simplest possible asoundrc:
pcm.myname {
type hw
card 0
}
this makes a PCM device available called "myname". its a "hw" type,
meaning that any attempt to use it with parameters unsupported by the
hardware will fail (this is a VERY, VERY important stipulation. you
must understand this - many people have not. if you need to use
parameters that are not supported by the hardware, you need to make it
"type plughw"). this PCM device corresponds to the first installed
ALSA driver (card 0).
the asoundrc file can also name "control" devices too, which provide
ways of manipulating the state of the hardware independently of PCM
stream parameters. some programs (like ardour) require access to named
control devices. so, here is an additional simplest entry for a
control device:
ctl.myothername {
type hw
card 0
}
this makes a control device available called "myothername". its a "hw"
type, which has less implications at this time than for PCM devices,
and it uses the first installed ALSA driver (card 0).
nothing more is *necessary* in an asoundrc file, but a great deal more
is possible. whether you need or want anything extra depends on what
you wish to do.
and to correct another misimpression i think you have: ardour.rc and
asoundrc are not at all equivalent. they do not describe the same
things, they are not read by the same code, they are not related in
any way other than that ardour relies on both of them (though in the
next couple of days, this will no longer be true, since ardour will
talk to JACK, not ALSA).
--p
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
