19 Jul
2011
19 Jul
'11
9:40 a.m.
well as you guys said, its horrible code...
so i cam to the conclusion that modifing takes to much time and pain...
i think i will write a new one, using osc communication by default...
but that will take some time...
bye
Ck
On 18.07.2011 04:23, Paul Davis wrote:
On Sat, Jul 16, 2011 at 10:02 PM, Reuben
Martin<reuben.m(a)gmail.com> wrote:
On Friday, July 15, 2011 10:05:24 AM Adrian Knoth
wrote:
what i recall (from years and years and years ago) was that the ALSA
control API can handle 3-argument calls (input,output,gain - for
example), which is why amixer and aset can be used to control the hdsp
matrix mixer, but there is no general representation that could be
feasibly used by generic tools. put differently, there is no "concept"
of a matrix mixer anywhere in the ALSA API.
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev On Fri, Jul 15, 2011 at 08:29:23AM +0200,
Christoph Kuhr wrote:
This is something I've never understood: Why is there no generic interface in
the ALSA API for a matrix mixer? For every pro-audio card that comes out the wheel has to
be completely re-
invented just to control the thing. Are the devices with matrix mixers that different
that it prevents them from being wrapped by a common API that any ALSA compliant mixer
can
hook into? And if someone has some hints to do that...
Rewrite hdspmixer, first. It's a horrible mess at the moment, but I'm
sure you'll see in a second. ;) We could use some clean abstraction of
cards, a matrix mixer and especially a rewrite from scratch in GTK/Qt.