[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Protux-devel] alsa updates
From: |
Martin Herren |
Subject: |
Re: [Protux-devel] alsa updates |
Date: |
Sat, 05 Feb 2005 20:24:48 +0100 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040803 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Remon Sijrier wrote:
| Hi all,
Hej,
| Please, if you still have the
|
| | | | | | | | |
ok, i found where it came from:
in my laptop i got an ali5451 sound chip and as far as i can remember
Reinhard has an emu10k1 chip (hit me if i'm wrong)... both chips (and
some others too) have the particularity to do hardware mixing. So they
provide (internally) 32 stereo output channels, which are hardware mixed
to one stereo output...
And in MADM.hh there is (or was for those who just updated to CVS) a line:
static const int MAX_BUSES = 20;
;-)
As probe_devices() found more than 20 busses and kept filling the array
an overflow occured, killing precious data elements like the ntabs in
MD... that's why it contained such a huge number that only | | |
where displayed for miles...
So i set this value to 64 for now... but we still need to add some
checks to probe_devices() to check we are not creating more cards and/or
busses than defined by MAX_CARDS and MAX_BUSES in MADM.hh.
Beside that i fixed a few minor things in MADM, to make multiple cards
detection work. It correctly detects all busses on all 3 cards here now.
So as far as i tested it up to now it works fine... beside the fact that
some parts like the lcd-meters or the out-bus-selection-box are not
designed to hold 34 busses... lol (perhaps i'll post screenshots).
Reinhard, how about you ? does it work for you now (beside the graphical
problem with 32 busses) ?
Now we'll have to find if there is a way to differenciate from a card
having only one physical output bus, but doing hardware mixing and
providing 32 internal busses, from a card having 4 internal busses
mapped to 4 stereo outs...
/Martin
| P.S.
| You'd better have a very good reason to tell me if it still doesn't work
| hehehe
but it's always getting better... and always will ;-)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFCBR2AENZb8plGFLQRAiscAJ46T4S8k2lAYD/SlE3CwCwwX1xsXACfcqjV
HkKiKiaN38EQIkOvjOAO5CM=
=jJ4C
-----END PGP SIGNATURE-----