Hi Alexander, > This is documented at > http://www.alsa-project.org/alsa-doc/alsa-lib/group___p_c_m.html#ga64fa40b556374dabe40d4874242fee19 > > By "forced channel conversion" they mean the "route" ALSA plugin. See > how it is done in /usr/share/alsa/cards/ICE1712.conf , which is > similar to your use case. Specifically, they try to upscale everything > to 10 channels, because this is what this hardware supports directly. Yes, I know. I have no conviction whether it actually effects 'plug' plugin or not. And I don't know PulseAudio always uses it when doing snd_pcm_open(). > By "forced channel conversion" they mean the "route" ALSA plugin. See > how it is done in /usr/share/alsa/cards/ICE1712.conf , which is > similar to your use case. Specifically, they try to upscale everything > to 10 channels, because this is what this hardware supports directly. Here I have a question because I know little about the devices. (I should post this question to alsa-devel but this is good opportunity for me to get information from you.) My drivers, 'snd-fireworks/snd-bebob/snd-oxfw' totally supports 80-90 devices. Each device has different combination between channels/rates. Can I write configuration to cover such variation? For example, let me assume there are four models which 'snd-bebob' can support: (regend: 44.1/48.0/88.2/96.0/176.4/192.0) For playback: Model_A: 2ch/2ch/2ch/2ch/2ch/2ch Model_B: 12ch/12ch/10ch/10ch/4ch/4ch Model_C: 16ch/16ch/8ch/6ch/4ch/2ch Model_D: 34ch/34ch/34ch/34ch/20ch/20ch For capture: Model_A: 2ch/2ch/2ch/2ch/2ch/2ch Model_B: 8ch/8ch/6ch/6ch/2ch/2ch Model_C: 34ch/34ch/34ch/18ch/18ch/18ch Model_D: 40ch/40ch/30ch/30ch/20ch/20ch And 'Model_D' changes its channel formation according to internal setting: For playback: Model_d: 12ch/12ch/12ch/12ch/10ch/10ch For capture: Model_d: 20ch/20ch/15ch/15ch/10ch/10ch Can I write a configuration file to cover them for 'pcm.front'? Thanks Takashi Sakamoto o-takashi at sakamocchi.jp
