RIV@NVX

Hi, I have a couple of questions:
1) What is the difference between EMU10k2 and EMU10k2.5?
2) Is EMU10k2.5 introduced with Audigy2 or later? According to kx.inf, it is used only by Audigy 2 and Audigy 4 Value cards (is it the CA0108-IAT then?), but Wikipedia claims 10k2.5 is Audigy2 chip.
3) What are the labels on those chips? I noticed CA10300-IAT LF, CA0102-IAT, CA0100-IAF CA0108-IAT (there is also CA0103 and CA0106 but they aren't 10k2 chips at all).
I think it's:
CA0100-IAF - Audigy
CA0102-IAT - Audigy 2
CA10300-IAT LF - Audigy 4
CA0108-IAT - Audigy 2 Value and Audigy 4 Value
Are there any other that I'm missing?
4) What do E-Mu cards use? I believe that there is a difference between revisions, that first revision uses CA10300-IAT LF and second one CA0108-IAT, is that correct?
5) Is Alice2 codename of CA0102-IAT chip and Alice3 of CA0108-IAT? I took that from ALSA source, but I'm not entirely sure if that's correct, can anyone confirm?
6) Is there any difference between CA10300-IAT LF and CA0102-IAT?
I would be grateful for any help here, and hope someone can answer this.

__________________
-- Vedran

Max M.

1. The latter has a cousin of p16v integrated.
2. Later. Wikipedia is wrong here (see 3.)
3.
CA0100 - A1, "Emu <1st rev>" ("Emu1212" etc.)
CA0102 - A2, A2ZS, A4Pro
CA0108 - A2V, (probably also later rev. of A4Pro)
CA0109 - AZSNB (?)
CA1030 - A4, A4V, "Emu <2nd rev>" ("Emu1212 PCI" etc.)

CA0100, CA0102 -> 10k2
CA0108, CA1030 -> 10k2.5

4. See 3.
5. I don't know.
6. See 3. and 1.

__________________

RIV@NVX

Thanks for your answer, that clarifies a lot of things. One more question - is there any known difference between CA0100 and CA0102? Because it seems weird to me that E-mu used older model when newer one was available by the time they released first series of their cards.

__________________
-- Vedran

RIV@NVX

I have one more question: if I recall correctly, Eugene once said that 10k1/10k2 can be reclocked to work at 44.1K. That's basically what Xilinx does on E-MU cards.
However, I saw that you can use 44.1K with ASIO on Live! (that is, no p16v). Does that mean that DSP gets reclocked in that case? If yes, how is that possible? If no, how come that it doesn't introduce latency?

__________________
-- Vedran

Eugene Gavrilov

yes, Max is almost correct:

ca0100: original audigy (DEV_ID ix 0x0004)
--
ca0102: audigy2 - this is actually a slightly modified ca0100 + p16v (ca0151), two separate chips on the same card (DEV_ID is 0x0004, and CHIP_REVISION is 4)
this is also found on a4 pro, if I'm not mistaken (sb0380), but not on a4 value
the first card released with this chip was sb0240
--
ca0108: a2 value, a4 value, DEV_ID is 0x0008, subsys should be >=0x1000: p16v is replaced with p17v, integrated on the main chip. first card was sb0400
--
ca0109: audigy2 zs notebook (codename 'tina') used for e-mu cardbus cards as well. this is a kind of ca0108 - there's also tina2, but I'm not sure about the difference
(DEV_ID is 0x0008, subsys should be >=0x2000)
this chip is with p17v integrated
first card was sb0530 - a2zsnb - I have one
--
ca0106 is p17 stand-alone chip, not compatible with kX (audigy se and a value)
--
there are at least two more chips - ca1020 and ca1030, but I'm not sure about their differences - pls consult with PKWORLD Компьютерный звук (in russian)
it seems ca1020 is just a version of regular ca0102 and it is found on sb0380 a4 pro
ca1030 seems to be a version of ca0108
--
alice2 is just 10k2 : )
alice3 is p16v+10k2
--
my version of 1212m 2nd generation has CA10300-IAT LF, subsys is 0x4004, dev_id 0x0008, chip_rev=0
(perhaps any ca10300 has subsys >=0x4000)
--
1st generation e-DSP cards had dev_id=0x0004, that is, it was either 'audigy' (ca0100) or 'audigy2' (ca0102), but not 'a2 value' (ca0108) chip
--
2nd generation e-dsp cardbus has subsys>=0x4200, dev_id=0x0008
--
from kX point of view, ca0100 and ca0102 are very different (p16v, Wave HQ etc.)
ca0102 and ca0108 are different, too, because ca0108 has 10k2.5 and p17v
kX does not support p17V found on ca0108, ca0109
--

E.

Eugene Gavrilov

as for 44100 support:

kx supports 44100 for playback only on any 10kx card, because the card itself performs SRC on the fly

any 10k2 chip -theoretically- can handle 44.1 as its main frequency -instead- of 48000, but this requires a separate clock generator, which is absent on most 10k2 cards
it seems that this clock generator is present on a2value and a4value, and is also used for e-dsp cards

10k2 chip has a special bit - 'use 44.1kHz baud rate' - bit 19 of the HCFG register (0x14), since 1999 : )

E.

JGSF

If I got it right, 1st generation E-DSP cards have a p16v chip and the latter ones a p17v?

85181542

KX_EMU10KX.DeviceDesc01="kX 10k1 Audio ("3545") - Model APS"
; 10k1-based cards ("Lives")
KX_EMU10KX.DeviceDesc02="kX 10k1 Audio ("3545") - Model CT4670 Value"
KX_EMU10KX.DeviceDesc03="kX 10k1 Audio ("3545") - Model CT4620"
KX_EMU10KX.DeviceDesc04="kX 10k1 Audio ("3545") - Model CT4780 Value"
KX_EMU10KX.DeviceDesc05="kX 10k1 Audio ("3545") - Model PCI512 CT4790"
KX_EMU10KX.DeviceDesc06="kX 10k1 Audio ("3545") - Model SB0040/CT1140 Value"
KX_EMU10KX.DeviceDesc07="kX 10k1 Audio ("3545") - Model CT4830 Value"
KX_EMU10KX.DeviceDesc08="kX 10k1 Audio ("3545") - Model CT4832 Value"
KX_EMU10KX.DeviceDesc09="kX 10k1 Audio ("3545") - Model CT4870 Value"
KX_EMU10KX.DeviceDesc10="kX 10k1 Audio ("3545") - Model CT4872"
KX_EMU10KX.DeviceDesc11="kX 10k1 Audio ("3545") - Model PCI256 CT4890"
KX_EMU10KX.DeviceDesc12="kX 10k1 Audio ("3545") - Model PCI256 CT4891"
KX_EMU10KX.DeviceDesc13="kX 10k1 Audio ("3545") - Model M002/M003"
KX_EMU10KX.DeviceDesc14="kX 10k1 Audio ("3545") - Model CT4831 Value"
KX_EMU10KX.DeviceDesc15="kX 10k1 Audio ("3545") - Model CT4871 Value"
KX_EMU10KX.DeviceDesc16="kX 10k1 Audio ("3545") - Model PCI256 CT4893"
KX_EMU10KX.DeviceDesc17="kX 10k1 Audio ("3545") - Model CT0060"
KX_EMU10KX.DeviceDesc18="kX 10k1 Audio ("3545") - Model CT4760"
KX_EMU10KX.DeviceDesc19="kX 10k1 Audio ("3545") - Model PCI512 CT4750"
KX_EMU10KX.DeviceDesc20="kX 10k1 Audio ("3545") - Model CT4850 Value"
KX_EMU10KX.DeviceDesc21="kX 10k1 Audio ("3545") - 5.1 Model SB0060"
KX_EMU10KX.DeviceDesc22="kX 10k1 Audio ("3545") - 5.1 Model SB0100"
KX_EMU10KX.DeviceDesc23="kX 10k1 Audio ("3545") - Motherboard Model (DXW)"
KX_EMU10KX.DeviceDesc24="kX 10k1 Audio ("3545") - 5.1 Model SB0102"
KX_EMU10KX.DeviceDesc25="kX 10k1 Audio ("3545") - 5.1 Model SB0222"
KX_EMU10KX.DeviceDesc33="kX 10k1 Audio ("3545") - 5.1 Model SB0228"
KX_EMU10KX.DeviceDesc32="kX 10k1 Audio ("3545") - 5.1 Model SB0220"
KX_EMU10KX.DeviceDesc26="kX 10k1 Audio ("3545") - Model CT0061"
KX_EMU10KX.DeviceDesc27="kX 10k1 Audio ("3545") - 5.1 Model SB0101 Value"
KX_EMU10KX.DeviceDesc28="kX 10k1 Audio ("3545") - 5.1 Model SB0103"
KX_EMU10KX.DeviceDesc29="kX 10k1 Audio ("3545") - 5.1 Model SB0105"
KX_EMU10KX.DeviceDesc30="kX 10k1 Audio ("3545") - 5.1 Model SB0221"
KX_EMU10KX.DeviceDesc31="kX 10k1 Audio ("3545") - Model PCI512 SB0150"
KX_EMU10KX.DeviceDesc34="kX 10k1 Audio ("3545") - Model SB0229"
; 10k2-based cards ("Audigy")
KX_EMU10KX.DeviceDesc50="kX 10k2 Audio ("3545") - Model SBxxxx"
KX_EMU10KX.DeviceDesc51="kX 10k2 Audio ("3545") - Model CT4820"
KX_EMU10KX.DeviceDesc52="kX 10k2 Audio ("3545") - Model CT0070"
KX_EMU10KX.DeviceDesc53="kX 10k2 Audio ("3545") - Model CT0072"
KX_EMU10KX.DeviceDesc54="kX 10k2 Audio ("3545") - Model SB0090"
KX_EMU10KX.DeviceDesc55="kX 10k2 Audio ("3545") - Model SB0162"
KX_EMU10KX.DeviceDesc56="kX 10k2 Audio ("3545") - Model SB0092"
KX_EMU10KX.DeviceDesc57="kX 10k2 Audio ("3545") - Model SB0161"
KX_EMU10KX.DeviceDesc58="kX 10k2 Audio ("3545") - Model SB0192"
KX_EMU10KX.DeviceDesc59="kX 10k2 Audio ("3545") - Model SB0191"
KX_EMU10KX.DeviceDesc60="kX 10k2 Audio ("3545") - Model SB0091"
KX_EMU10KX.DeviceDesc61="kX 10k2 Audio ("3545") - Model SB0095"
KX_EMU10KX.DeviceDesc62="kX 10k2 Audio ("3545") - Model SB0230"
KX_EMU10KX.DeviceDesc63="kX 10k2 Audio ("3545") - Model SB0231"
KX_EMU10KX.DeviceDesc64="kX 10k2 Audio ("3545") - Model SB0232"
KX_EMU10KX.DeviceDesc65="kX 10k2 Audio ("3545") - Model SB0238"
; 10k2-based cards ("Audigy2")
KX_EMU10KX.DeviceDesc80="kX 10k2 Audio ("3545") - Model SB0240"
KX_EMU10KX.DeviceDesc81="kX 10k2 Audio ("3545") - Model SB0243"
KX_EMU10KX.DeviceDesc82="kX 10k2 Audio ("3545") - Model SB0242"
KX_EMU10KX.DeviceDesc83="kX 10k2 Audio ("3545") - Model SB0280"
KX_EMU10KX.DeviceDesc86="kX 10k2 Audio ("3545") - Model SB0245"
KX_EMU10KX.DeviceDesc84="kX 10k2 Audio ("3545") - Model SB0244"
KX_EMU10KX.DeviceDesc85="kX 10k2 Audio ("3545") - Model SB0320"
KX_EMU10KX.DeviceDesc87="kX 10k2 Audio ("3545") - Model SB0249"
KX_EMU10KX.DeviceDesc88="kX 10k2 Audio ("3545") - Model SB0246"
; 10k2-based cards ("Audigy2 ZS", "Audigy4 PRO")
KX_EMU10KX.DeviceDesc90="kX 10k2 Audio ("3545") - Model SB0360"
KX_EMU10KX.DeviceDesc91="kX 10k2 Audio ("3545") - Model SB0350"
KX_EMU10KX.DeviceDesc92="kX 10k2 Audio ("3545") - Model SB0352"
KX_EMU10KX.DeviceDesc93="kX 10k2 Audio ("3545") - Model SB0380"
KX_EMU10KX.DeviceDesc94="kX 10k2 Audio ("3545") - Model SB0350b"
KX_EMU10KX.DeviceDesc95="kX 10k2 Audio ("3545") - Model SB0350/SB0355"
KX_EMU10KX.DeviceDesc96="kX 10k2 Audio ("3545") - Model SB0350/SB0359"
; 10k2-based a2 value, a4 value cards & zs notebook
KX_EMU10KX.DeviceDesc100="kX 10k2.5 Audio ("3545") - Model SB0400"
KX_EMU10KX.DeviceDesc101="kX 10k2.5 Audio ("3545") - Model SB0530 NB"
KX_EMU10KX.DeviceDesc102="kX 10k2.5 Audio ("3545") - Model SB0610"
KX_EMU10KX.DeviceDesc103="kX 10k2.5 Audio ("3545") - Model SB-1000?"
KX_EMU10KX.DeviceDesc104="kX 10k2.5 Audio ("3545") - Model SB-1022?"
KX_EMU10KX.DeviceDesc105="kX 10k2.5 Audio ("3545") - Model SB-2021? NB"
KX_EMU10KX.DeviceDesc106="kX 10k2.5 Audio ("3545") - Model SB-1101? SA"
; E-DSP cards
KX_EMU10KX.DeviceDesc110="kX 10k2 Audio ("3545") - Model E-1010 EM8810"
KX_EMU10KX.DeviceDesc111="kX 10k2 Audio ("3545") - Model E-0404"
KX_EMU10KX.DeviceDesc112="kX 10k2 Audio ("3545") - Model E-1010 4003?"
; E-DSP m cards
KX_EMU10KX.DeviceDesc120="kX 10k2.5 Audio ("3545") - Model E-0404 PCI"
KX_EMU10KX.DeviceDesc121="kX 10k2.5 Audio ("3545") - Model E-1010 4003?"
KX_EMU10KX.DeviceDesc122="kX 10k2.5 Audio ("3545") - Model E-02 EM8950"
KX_EMU10KX.DeviceDesc123="kX 10k2.5 Audio ("3545") - Model E-1010 EM8960"
KX_EMU10KX.DeviceDesc1000="kX 10k1 Audio ("3545") - Generic"
KX_EMU10KX.DeviceDesc1001="kX 10k2 Audio ("3545") - Generic"
KX_EMU10KX.DeviceDesc1002="kX 10k2.5 Audio ("3545") - Generic"

RIV@NVX

I have 1212m (first generation with FireWire port) and it has no p16v on board, or at least I can't find it. But I'm pretty sure it isn't there since E-Mu used CA0100 on first generation (which according to Eugene doesn't support p16v), because really old cards had "Audigy" (instead of "Audigy2") written on chip.
Also, E-Mu cards handle samplerates differently (Xilinx and stuff).

Also, I would like to thank everyone for their responses, I'm really glad we clarified some of it.

Regarding CA10300 and CA10200 - these _could_ be unleaded versions.

__________________
-- Vedran

RIV@NVX

Is alice3 then also 10k2.5?

Could be. Bit there are also cards which have such subsystem but aren't CA10300-based - e.g. first E-mu generation has 0x400n; specifically, 1212m has 0x4001.

Hmm, this is very interesting. ALSA doesn't differ CA0100 and CA0102 (it basically has two routines - ca0102 and ca0108, and every card is supported using one of those two). I wonder what would happen if I played to HQ device on first Audigy which doesn't have p16v on board.
Since I don't have any Audigy card around, I might give 1212m a try with this, if someone can confirm that there is no p16v there.

BTW, can anyone show me how that p16v thing looks like? Here is the picture:
http://img236.imageshack.us/img236/5307/audigy2wg0.jpg

__________________
-- Vedran

Maddogg6

Most of this thread goes way over my head... but I see this...
The CA0151 is 2nd chip below the CD SPDIF connector on the top of the card.

RIV@NVX

Oh! Now I know what to look for.

Some more highres images:
http://www.ixbt.com/proaudio/emu/040...-full-size.jpg (old revision (I believe) 0404)
This thing above Xilinx _might_ be p16v.
http://images31.fotosik.pl/10/5135b2a060180b0a.jpg (old revision 0202)
http://descr.mpc.ru/descr/33613/i/6.jpg (new 0202)
http://descr.mpc.ru/descr/33613/i/4.jpg (new 1010)
I can't find old 1010 anywhere, I will take a couple of pictures of my card ASAP. I just can't get to it right now.
Anyone can confirm lack or existence of p16v on old E-mu cards?

One more question - does that mean that if a card has p16v, then it must have CA0102 too since p16v wouldn't work with CA0100?

__________________
-- Vedran

Maddogg6

Well - I think that quote answers that question also....

Which I read as:
The CA0102 has the P16V included with the CA0100...
In other words... a CA0102 is a CA0100 + P16V in one chip, that *used* to be 2 separate chips in older cards. With that said - my best guess is that - adding a P16V (CA0151) to a CA0102 - would be a redundancy - now, if it can, or cannot work, is likely not so simple - possibly the redundant P16V could just add a second Wave HQ device to the PC...??? But of course I can only speculate. And again, its a bit over my head.

but there does seem to be some room for interpretations with that quote...??

RIV@NVX

Definitly, and I think you didn't interpret it right. Because CA0102 cards _have_ separate CA0151 chip: http://img236.imageshack.us/img236/5307/audigy2wg0.jpg
CA0100 cards don't have p16v chip at all. I checked - my 1212m doesn't have it either. It probably uses CA0100 then, as I read somewhere at some point. Or maybe...

That brings me to another question (kinda related to my first question): can CA0102 exist on a card without accompanying p16v?

__________________
-- Vedran

Maddogg6

Yes, you seem to be correct - I didnt even look at the BIG chips # (CA0102) before...

Max M.

RIV@NVX
It can (btw., but what's the idea with all that?) - there's simply no diff. between 100 and 102 beyond the p16v access stuff (registers/IO)

Yes, sure, i can. The E-mu cards simply do not use this p1xv stuff.
(Same for new revisions - the choice of the CA1030 had just a manufacturing motive there - not a functionality/features one).

E
Here i should stress that i don't think the 10k2(.5) is ever reclocked to 44.1 within A2V/A4 cards - from what i've seen they support "true" 44.1k only through their p17v channels (and their 10k2 is still always @48). While E-mu cards do support 44.1 through 10k2 reclocking.

__________________

Eugene Gavrilov

p16v: this is quite easy to check: open device manager and check IO space for the device. also, kX Mixer will report if you have p16v chip (Wave HQ device)..

Eugene Gavrilov

Could be. Bit there are also cards which have such subsystem but aren't CA10300-based - e.g. first E-mu generation has 0x400n; specifically, 1212m has 0x4001.

yes, 0x400x is related to device=0x0008

Hmm, this is very interesting. ALSA doesn't differ CA0100 and CA0102 (it basically has two routines - ca0102 and ca0108, and every card is supported using one of those two).

kX doesn't as well. these are identical chips from 10kx engine's point of view

I wonder what would happen if I played to HQ device on first Audigy which doesn't have p16v on board.
Since I don't have any Audigy card around, I might give 1212m a try with this, if someone can confirm that there is no p16v there.

the p16v chip is accessible via additional register IO space. this IO space is located in PCI IO space and thus is very easy to detect. if you see wavehq device, then it is supported on your card. if you don't see - then it is not : )

BTW, can anyone show me how that p16v thing looks like? Here is the picture:

ca0151 is p16v

ca0102 is just a different version of ca0100 which supports external p16v module

E.

chipwizme

If i replace the 24.576MHz crystal with a 22.050MHz (or something close), how should i modify the ALSA source to initialize the card correctly? My plan was to find every write to HCFG and add 0x00080000 to the written value. What exactly does flipping this bit do in terms of functionality? Does the DSP clock itself from a different pin altogether, and/or does something else happen? In my mind, the fact that this has to be explicitly asserted suggests that the DSP is capable of switching between two crystals, which further implies that there's an unused pin where I can connect an ADDITIONAL crystal. Any thoughts?

cjrcl

Have a look at here:

/linux/sound/pci/emu10k1/emu10k1_main.c

and here:

alsa-driver sourcecode, sound_2pci_2emu10k1_2emu10k1__main_8c-source.html, 1.0.22.1+dfsg-0ubuntu3

/* Tested by James@superbug.co.uk 20-3-2007. */
1436 {.vendor = 0x1102, .device = 0x0004, .subsystem = 0x40021102,
1437 .driver = "Audigy2", .name = "E-mu 0404 [MAEM8850]",
1438 .id = "EMU0404",
1439 .emu10k2_chip = 1,
1440 .ca0102_chip = 1,
1441 .spk71 = 1,
1442 .emu_model = EMU_MODEL_EMU0404}, /* EMU 0404 */
1443 /* Note that all E-mu cards require kernel 2.6 or newer. */
1444 {.vendor = 0x1102, .device = 0x0008,
1445 .driver = "Audigy2", .name = "SB Audigy 2 Value [Unknown]",
1446 .id = "Audigy2",
1447 .emu10k2_chip = 1,
1448 .ca0108_chip = 1,
1449 .ac97_chip = 1} ,
1450 /* Tested by James@superbug.co.uk 3rd July 2005 */
1451 {.vendor = 0x1102, .device = 0x0004, .subsystem = 0x20071102,
1452 .driver = "Audigy2", .name = "SB Audigy 4 PRO [SB0380]",
1453 .id = "Audigy2",
1454 .emu10k2_chip = 1,
1455 .ca0102_chip = 1,
1456 .ca0151_chip = 1,
1457 .spk71 = 1,
1458 .spdif_bug = 1,
1459 .ac97_chip = 1} ,

It is obvious that Audigy 4 Pro uses ca0102 with the acompany of ca0151 while E-MU 0404 has a ca0102 in its solitude. So ca0102 can function without ca0151 and those E-MU cards have to reclock 10k2 inorder to output in 44.1 kHz.

BTW I found:
ca0102 (Audigy 2) is an upgrade of ca0100 (Audigy 1) aiming to support a seperate ca0151;
ca0108 (Audigy 2 Value) is a combination of ca0102 and ca0151 but is a "value" version;
ca10200 (Audigy 4 Pro) is the unleaded successor to ca0102 while ca10300 (Audigy 4) is ca0108's counterpart.

cjrcl

I finally got an evidence here (E-MU 1212m PCI) in favor of my conjecture that the 1st generation of the E-DSP cards feature ca0100 (not ca0102, even though ALSA & KX treat them with no discrimination) while the 2nd generation of these cards use ca0108 or ca10300 (which are apparently smaller than their predecessor) instead.

The 1st gen E-MU 1212m with 4 crystal oscillators on board may surprisingly do SRC via the XILINX chip as the 1st gen E-MU 0404 which has only 1 crystal oscillator.

Max M.

I guess you mix up "SRC" and "reclocking"

And that's what I wrote here.
Though I still don't understand the purpose of this digging - why care what revision of the chip Emu cards have if this does not affect any functionality in any way?

__________________

cjrcl

[Quote]I guess you mix up "SRC" and "reclocking"[Quote]

Thank you. I googled and found there are some distinctions between them. In the past posts I actually alluded "SRC".

It is the price that aroused my curiosity. In the market 8852 is touted as much better than 8850 and estimated at a 40% higher price. However, I do not agree with those sellers.

Max M.

Ah, it's a market - prices are made of anything but the actual value
(Though I don't mean either revision is better or they are equal - they could improve something else (analog parts for example) after all. I honestly don't know).

__________________

Max M.

OK, either way, I just thought it may be not so clear through the thread with all of those acronims and engineering slang. So let me summarize it (to reduce confusion when someone finds the thread in 100 years :).

Set of facts A.

1. All revision changes to 10k2 chips since ca100 are made around p16v/p17v derivatives (see "p16v/p17v" description in the end).
2. E-mu "EDSP" soundcards (whatever 10k2 revision they have) do not use any p16v/p17v functionality (they simply don't need to - as the base ca100-based Emu design already provides more advanced functionality than any p16v/p17v does - see below).


Set of facts B.

1. "EDPS" cards (with native drivers, not kX) provide:

a. 24bit 44.1/48kHz playback/recording* with advanced routing and effects
b. 24bit 96...192kHz playback/recording with advanced routing but without effects

2. Audigy 2 family cards (i.e. A2...A4, with native drivers) provide:

a. 16bit 48kHz playback/recording with advanced routing and effects
b. 24bit 44.1...192(?)kHz playback/recording without any routing or effects

* - here "playback/recording" means "true" "bit-perfect" playback/recording without any sample-rate conversion or downquantizing (except 44.1...192kHz mode of A2..A4 cards - where "bit-perfect" support can vary between models).

---

What is "p16v/p17v"?
Basically, it's an audio controller with 8 playback and 2 (or 8) recording channels (with no processing/routing), supporting 24bit/44.1...96(192)kHz (not necessary bit-perfect). Creative used this controller for a wide range of their soundcards for various purposes.
For example:
a. As a core controller in SBLive24(aka "Live7.1")/AudigySE soundcards.
b. As a bonus/addon/kludge controller in A2..A4 family of soundcards (to add 24bit/96kHz support).

__________________