On Mon, 17 Dec 2001, Jaroslav Kysela wrote: > > k = card number, l = device number and m = subdevice number. In my case k = > > 0 and l = 0 (for the PCM device). When I use m = 0, the front channel is > > addressed. I tried a couple of other subdevice numbers, but I only got the > > front channel. Is there a possibility to address the rear channel is this way? > > No and Anders doesn't follow the name semantics for the open functions. > Every program must allow to pass any device name otherwise the user is > restricted to use selected configurations only. Simply, it's not a problem > of ALSA but the given application.
I would be delighted if someone could tell me what the name semantics are. In BruteFIR I only want to be as close to the hardware as possible, meaning that if you have a sound card that has only two channels, you can open only two channels, not four or eight, even if ALSA-lib allows it. The software was initially designed for building embedded convolution solutions (advanced hifi equipment) with well suited sound hardware and reasonable low latency (this is still the main goal), and less as a sound application for a workstation other than for development, therefore the software modes has been kept away from the user. However, ALSA support is isolated to an external module of just 500 lines of code, so incorporating proper support for software modes would not hurt anyone, so I guess I should do it. But, then I need to know about these semantics, could you tell me where to search? aplay.c as always? /Anders Torger _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
