>1) I understand now that there is no mixer. Yet, I am a bit baffled how then d
>oes ardour (for instance) control this app's output? Couldn't there be a some
>kind of generic mixer app derrived from the way Ardour addresses volume issue
>in this card? Could it be that the app only attenuates the signal sent to the
>output channel while the channel volume always stays constant?
yes, ardour attenuates its output signals. there is no channel volume
control on the hammerfall.
who wants a generic mixer app anyway, and what would it do? you should
perhaps get familiar with jack (jackit.sf.net) which is the one
framework where such a thing would make sense.
>2) If this is an app-specific thing, is it still possible to use apps which ha
>ve multi-channel capability, but have not been designed with RME Hammerfall in
> mind to utilize it? How about every-day use (i.e. desktop sounds and trivial
>stuff like that)? Also, is it possible to write sound to the soundcard's chann
>els just by addressing a specific /dev/dsp (or whatever its name is) device (i
>.e. aplay or cmixplay etc.)?
this can be done, but its not trivial. things that use /dev/dsp
directly will not work unless they are forced to load libaoss using
the LD_PRELOAD "hack". thats because the devices accessed via /dev/dsp
are necessarily only able to use code in the kernel; the ALSA code in the
kernel faithfully emulates the exact h/w capabilities of all ALSA
supported cards. since the hammerfall does not offer a way to use less
than the full channel count, only supports 24-in-32 bit samples and
uses non-interleaved format, regular, naive linux apps cannot work
with it in this way.
however, naive ALSA apps plus OSS apps that are forced to load libaoss
will find their access goes via alsa-lib, which is capable of supporting
pretty much any configuration the program or user wants. under these
circumstances then, they will work.
there are no /dev/dspN devices associated with subsets of the
Hammerfall channels, but ~/.asoundrc can be used to define ALSA PCM
devices that correspond to such subsets. again, naive ALSA apps plus
OSS apps that are forced to preload libaoss can use these definitions;
OSS apps that are run "naked" will not be able to.
>3) Jeremmy has mentioned that there is something called asoundrc file. What do
> I do with it? Where do I store it? Is there a way to have it set system-wide?
> Could you please give me the example file (i.e. one you use) so I can go from
> there and tailor it according my needs?
that is beyond the scope of this reply. its a generic ALSA question
that requires a generic ALSA answer, and i don't have the time right
now to answer it.
>4) How do I go about changing the setting of sync being ADAT1 to INTERNAL? I h
>ave tried changing it in the asound.stat, but it gets overwritten every time a
>lsasound is restarted, which makes me believe it is done elsewhere? I would gr
>eatly appreciate as detailed syntax as possible.:-)
"N" is the card ID for your hammerfall:
alsactl -f foo store N
emacs foo
... change the ADAT1 input source setting ...
... save the file ...
alsactl -f foo restore N
asound.stat should contain the new setup the next time you shutdown
ALSA cleanly. alternatively, edit that file by hand.
>5) What do I need to put in the ardourrc file, or whatever file is responsible
> for that (and where to store it system-wide) in order to use Ardour with my H
>ammerfall? BTW -- I finally got Ardour compiled from the yesterday's CVS and i
>t is looking very nice so far :-) Could you please provide me with your possib
>ly example-file? Thanks you!
no, because if you got ardour from yesterday's CVS its incomplete, and
ardour has nothing to do with audio h/w anymore. it uses jack for that.
ardour is currently 95% finished with "jackification", but the version
in CVS right now is still a little problematic. it should be ready in
a day or two.
jack simply takes an ALSA PCM device name (as specified in your
asoundrc file):
jack -d whatever ...
i repeat: ardour contains no code relating to ALSA or audio h/w anymore.
--p
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
