aneng

Hi,

Call me stupid ("Hey Stupid !"), but I can't get my head around the mixer at all.

I want to use my Audigy card to record audio into my sequencer (Tracktion). I have my sound source (usually an electric guitar) plugged into the Audigy's LINE IN socket. I have the input to Tracktion set to "Kx IN 00 + 01". I CAN get audio recorded, BUT - I can ALSO hear the dry signal before it gets anywhere near any VST effects I have lined up in Tracktion. I get the 'wet' signal too, but also the dry (which I don't want !).

If I close down Tracktion, I can still hear the dry signal, so it's not something I've setup wrong in that.

If I play with the mixer, trying to find the source of the dry signal reaching my speakers, I'll eventually find a slider that will mute it, but then I get no audio at all into Tracktion.

I appreciate that some users will want all the extras that the Kx project provides, but for me ALL I want is what I've just described (and of course the low latency for playing VSTi's live). I really have no need for a mixer full of 'TAD', 'ZVideoI2S', 'Aux2' and 'Subwoofer' etc etc, it's just too confusing for me !

I've sat down and read the manual and the help files, but my brain starts to melt when I do, and I'm sat there thinking "Why does it have to be so complex ?!!!

Can anyone tell me if there is anything specific to the Audigy card that needs 'correcting' in Kx (Please, don't make me go into the DSP Routing room !!! - I'm begging you !! )

...or does anyone know of any other drivers that will give me the same low latency as Kx, but without the 'Masters Degree in astro-musicology' requirement ?

Help me Obi-Wans - you're my only hope !

dj_stick

try the kX Getting Started Guide

__________________

Doomsayer

Ok, here's a quick fix. On the AC97 page select Line In as source, and mute all sliders except Gain. These sliders send input directly to your speakers, so that's where the dry signal comes from. On the recording page select AC97 as source and mute all other sources except Master Level. On the Ins&Outs page mute the AC97 slider , since it can also forward dry signal.

Doug W

aneng,

I would guess that a majority of KX users feel pretty much the same as you do at first, then slowly little light bulbs click on.

I have not seen anything else that does what the KX drivers do. So I believe you must finish your training Luke! Go back into the DSP page!

aneng

Well, I studied some more in the ways of the force, then got out my light sabre and severed the connections between AC97 Left In0, AC97 Right In1 in the Prolog and In0, In1 in the Xrouting. This was the only way I could kill the dry sound reaching my speakers. (Thanks for your suggestion Doomsayer, but it didn't work for some reason !).

All is fine now - I have what I need, and shall never more venture into the dark side (i.e. the DSP window)

dj_stick

the DSP window is very powerful once you get used to it
http://kb.kxproject.com/guide/dsp.html
http://kb.kxproject.com/dsp

__________________

miguel

If RecL/RecR worked as expected it'd be so easy for newcomers to do basic 2 channel asio recordings. Eugene explained that analog recording was implemented elsewhere, outside of the routing>>epilog connection. There must be a technical reason for that but it complicates things from the user's perspective.

Anything that is given a record level in the recording tab should pass through routing RecL/RecR. Then connecting these to an ASIO pair would give simple 2 channel asio recording controlable from kxmixer's recording tab, just like we do mme recording. Without this it's kind of a waste to have kx mixer.

Andorbal

I just wanted to throw in my two cents here... At first, I thought the driver control panels were VERY confusing, but I realized their power from the get go. So I just kinda played around and read the help files, and actually just today I got that feeling where the lightbulb just turns on and it all makes total sense now! So just give it time. And actually, what helped me most was the "Reinitialize the DSP" menu option, cause then I knew that I could make any change that I wanted and get back to defaults if I botched something up.

Oh, and I must say that this is probably the most impressive piece of free software I've come across! I know that Linux, BSD, OpenOffice, etc. are all free, too, but these drivers make it seem like you're getting a totally new soundcard! Bravo!

Lex Nahumury

Guys, guys,..after reading these posts it once again becomes
clear to me that many users don't realy understand kX's concept and it's operation.

1. The default DSP/xrouter Setup + kXmixer's functionality is for *Generic* soundcard usage only.
It is not meant to solve most task specific musical application "problems".
If you are using kX as a musician, the DSP window and it's plugins are realy all you have to deal with.

Besides some special features, kXMixer is "just" a shell to control the default DSP setup.
KXmixer is great for *generic* usage, but useless for musicians, so forget about it.
It will only confuse you more.
In simple words;
You can (and have to) realize almost everything solely in the DSP window!

2. Besides some AC3 stuff, *Everything* goes through the DSP one way or another!
So if (for example) you want to rec your mic, line, spdif, midi or whatever to an ASIO input
or WINMM, you will and can realize that only in the DSP window.
Simply unload and upload the right DSP-Plugins and draw the right connections.
That's realy all that's to it!

3. Learn to use the ProFX plugins, (or at least get rid of xrouter),
and you will almost never have to use kXmixer-tabs&sliders again.
It's better to work and learn at one place, namely the DSP window.

All those questions like "I can't get my Mic recorded to ASIO" and such
are easely solved by just loading one 'Src' and one 'Asio' plugin from the ProFX menu
without even touching the kXMixer.

At last;
There is no reason to be afraid of the DSP window.
You don't have to write your own effects or something...just draw some lines..

/LeMury

miguel

I hope you're not referring to my post. If so it's you that don't understand what's happening in the default DSP setup.

thomasabarnes

LeMury:

That's an invaluable post! This guy is apparently misinterpreting what you wrote and your generous help to us, and maybe he doesnt even know your most excellent contributions to the KX Project community. Nevertheless, this still goes to show that more documentation would be a great help. And I refer to documentation on how to work with those ProFX plugins and other additional plugins.

Thanks for your posts, they're greatly appreciated! Apparently, some of us need to spend more time messing around in the DSP.

Sincerely, thomasabarnes

__________________

May a song always touch you in a positive way.
SONAR X1D Expanded, Windows 7 Pro 64Bit, MOTU UltraLite MK3, 150 GB HDD, 250 GB HDD, 1 TB x2 HDD 7200 rpm

My Music Production: Top 40, Contemporary Christian, Pop/Rock, Decent Rap, Inspirationals, and Children Songs

Lex Nahumury

Miquel,
>>I hope you're not referring to my post.
Yes, partialy.

>>If so it's you that don't understand what's happening in the default DSP setup.
I'll try to pretend I didnt' read that ok?


thomasabarnes,
>>And I refer to documentation on how to work with those ProFX plugins..
Yes, after I wrote those plugins I'd already started to write a tutorial on their usage,
but I rather spent that time writing new 'kX add-ons'.
Maybe some day. Besides, they are quite easy to use and "self explanatory".

/LeMury

dj_stick

i may write a simple guide on the pro-fx plugins
i *have* written a guide that uses the pro fx plugins
http://kb.kxproject.com/dsp

__________________

Lex Nahumury

>>i may write a simple guide on the pro-fx plugins
Good idea.

>>i *have* written a guide that uses the pro fx plugins
Yep I know. It would be a usefull example to assign a 'Scr' to an AC97 source
to illustrate the ease of source selection without having to open kxmixer ac97 tab.
Maybe also a screeny of an open 'k1lt dialog' etc.

/LeMury

dj_stick

perhaps like a descriptional page like i did for the kXmixer, and then an example of how it is used?

__________________

thomasabarnes

Man you fellows are quick LOL Thanks DJ_Stick.

Hey DJ, wish you could make a DSP tutorial that will allow us to work with Professional programs with surround capabilities (such as Logic, Nuendo, or any future program with Surround audio authoring capabilities) using the ProFX plugins and other addons.

LeMury:

"Besides, they are quite easy to use and "self explanatory"'.
That's easy for you to say, you wrote some of these goodies, but from the view of someone who isnt familiar with them, well, we really dont know what we can do with 'em.


Sincerely, thomasabarnes

__________________

May a song always touch you in a positive way.
SONAR X1D Expanded, Windows 7 Pro 64Bit, MOTU UltraLite MK3, 150 GB HDD, 250 GB HDD, 1 TB x2 HDD 7200 rpm

My Music Production: Top 40, Contemporary Christian, Pop/Rock, Decent Rap, Inspirationals, and Children Songs

dj_stick

i guess he wrote them to be self explanatory, but that's often hard to do - he did a pretty good job

n i'll see what i can do about the guide idea

__________________

thomasabarnes

admk's Sonar and KX Drivers newbee guide uses some of LeMury's plugins, so I have an idea of how useful they are and how great a job he did with them. I'm not putting LeMury down at all. What I'm getting at is to be able to use the ProFX plugins and addons in the DSP in the light of LeMury's comments here:

"Learn to use the ProFX plugins, (or at least get rid of xrouter),
and you will almost never have to use kXmixer-tabs&sliders again.
It's better to work and learn at one place, namely the DSP window."

That is, it may be less confusing to not even have to use the KX Mixer if possible. admk's guide uses instances of src and MX6. It seems the MX6 is like a mixer, and I think admk's DSP setup in his guide is useful and easier to understand than all the items in the default DSP. One thing that I dont know , though, is how to use these and maybe other plugins and addons for work with a surround capable professional program for audio recording. So, if the DSP can be setup with these plugins and addons for 5.1 surround authoring and mixing with a surround program like Logic or Nuendo, it may be easier to work with such a DSP than working with the default DSP setup.

Sincerely, thomasabarnes

__________________

May a song always touch you in a positive way.
SONAR X1D Expanded, Windows 7 Pro 64Bit, MOTU UltraLite MK3, 150 GB HDD, 250 GB HDD, 1 TB x2 HDD 7200 rpm

My Music Production: Top 40, Contemporary Christian, Pop/Rock, Decent Rap, Inspirationals, and Children Songs

dj_stick

using the SRC plugin, connecting the front (fx4/5) rear (fx6/7) and sub/center (fx8/9) to the respective inputs on the epilog (or the profx variants)
that is simplest way i see

__________________

miguel

I'm sorry for raising some defensive spikes out there. Soul's clean now, I'll go positive. This is from an old thread about mixdown with kX dsp fx. Doug W found it helpfull so i'll repost here. It takes a bit of reading but it's satisfying in the end. Thanks Doug W the dsp screen capture is still online !

On a side note, today I use a similar setup but I've added an MX6 (at the time remote midi control was broken...) and uses other LeMury's plugins like the src's etc, so the same setup works for recording too (through mx6)

so here's the pic and here's the explanation:


those red boxes are untranslated VOL modules renamed for making annotations. They consume no dsp resources and are saved with presets, handy to remember what a dsp preset was for.

I started with all default settings for the card (routing, dsp).
In the dsp deleted everything but fxbus, fxmix2, chorus, reverb and epilog.

On the ASIO sequencer, all tracks should normally out to asio 0/1, with necessary eq and/or inline FX. Now different sequencers have different means of creating busses but all have similar funcionality, so investigate your personal choice. So we create six mono busses that out from asio 4 to 9. Now for each track we can send part of the signal to one or more of these buses, then kx will process them, merge them on "FXMix2 (FX return)" and mix them with our sequencer main mix on "Stereo Mix (monitor)". You can rename your busses on the ASIO program to resemble the names of the fx they send to.

You realize i skipped asio 2/3, well that's because it's sent by default to fxbus 2/3 that is used by kx midi synth too. This way fxbus 2/3 will only carry kx synth audio for selective monitoring/recording. You can change all these routings on kXrouter window.

More on kX synth: I kept the default "Fxmix2" and chorus and reverb to keep compatybility with the standard two FX used on midi sequencers. Now on your midi app you can adjust chorus and reverb for the midi instrument. To do that kX uses fxbus 13/14 to send some of the synth audio. Notice I placed a "stereo mix" in front of chorus and reverb. That's to make these two effects avalable to ASIO sends as well. So synth sends and ASIO sends are merged then processed.

You may have noticed that fxbus 4/5 are labeled "2 sends to other kx card(4/5)". They go straight to a spdif out connected to the other kx card (It could be an external guitar FX box or whatever). On the other card you can have a pair of more dsp expensive FX like Max M's uFX reverb and the like, wired similarly to this card. At the bottom you can see a Le mury's "Src(other kx card return)", that is merged with the other FX. Ah, remember that each travel from card to card audio loses about 1dB, so place appropiate stereo gains right after the SRC or PROLOG.

err.. all stereo mixes and "FXMix2 (FX return)" are used as places to merge signals, so keep the faders to 100%. "FXMix2 (FX return)" has two stereo outs, so i wired one for monitoring and the other goes to an ASIO in for when you decide to bounce the whole "MIDI synth + FX return" mess. Or you can record only part of the mess, like "MIDI synth + MIDI synth FX", simply open "FXMix2 (FX return)" and set to 0% as you wish.

One last note, I used all FX as mono send FX, stereo returns. But you can do also in-line FX by setting a track to out to a pair of ASIO channels other than 0/1. This will process the whole track, but you will run out of ASIO cahnnels quickly.

I hope you all reached here, and that it was worthy

EDIT: I just though one might want to substitute "FXMix2 (FX return)" with a more intuitive MX6. still it consumes a bit more dsp and i only use this as a merger, and not as a mixer (remember that we mix DSP FX on the ASIO sequencer adjusting the send amounts for each track or midi instrument)

Lex Nahumury

thomasabarnes,
>>That's easy for you to say, you wrote some of these goodies....
I understand.

Ok, for what it's worth, here's an attempt to explain the DSP's role in kX as simple as possible.
No bits & bytes, hex numbers, db's or an in-depth DSP exercise.
Also it doesn't pretend to be complete nor, for simplicity's sake, entirely accurate.

-----------------------------------------------------------------------------------------------------------
A newbie guide on kX's DSP concept or "How to setup your own DSP" (for musicians)
-----------------------------------------------------------------------------------------------------------
Chapter 1. Basics

(Note: "DSP" refers to kX's 'DSP Window' wich graphicly represents the on-card emu10Kx chip )

Intro:
---------
Sticking to the default 'DSP, xrouter, kX Mixer' combination is good for *Generic-basic*
soundcard operation but not for more dedicated tasks like most musical applications require.
Most advanced kX users never use the 'xrouting' plugin thereby rendering 'kX Mixer's Recording Tab' useless.
Not a bad thing since it's much easier to work solely in the DSP window and never have to touch 'kX Mixer'.
Almost everything done in 'kX Mixer' can also be done right away in the DSP.

Most important "rule" to realize and remember;
"..Everything goes through the DSP..."
Thus (with a few exeptions), every audio signal has to go in or out the DSP
sooner or later, one way or another.

Knowing this, it becomes clear that understanding and operating the DSP is the
most important thing and often the only thing to fully exploit kX's potential
and to setting up your own DSP configuration succesfully.

I/O Plugins:
-------------
Ok, first let's have a look at all those different signals going in and out your soundcard/PC
and how they relate to the DSP.

1.External input signals;
- analog AC97 signals like Mic, Line-In, Aux etc.
- analog (to digital) I2S signals if you have a Live Drive
- digital signals like SPDIF
These signals are coming from the *physical* inputs of your soundcard.
For example, if you want to record from Line-In.
These signals enter the DSP by uploading [Prolog] or [Src].

2.Internal "input" signals;
-Wave/PCM playback
-MIDI Synth playback
-ASIO playback
-AC3 playback
These signals are coming from (are generated by) your PC.
For example, if you playback your sequencer, mediaplayer etc.
These signals enter the DSP by uploading [FXBus] or [Src].
(Note: Wich signal is assigned to what FXBus nr. is controled by the 'kX Router' applet)

3.External outputs;
-analog rear out
-analog front out
-analog center/lfe
-headphones out
-SPDIF out
-digital front, rear, center and lfe out
These are the *physical* outputs of your soundcard.
You can access these outputs by uploading [Epilog] or [k1lt/k2lt].

4.Internal Recording "outputs";
-WINMM recording input
-ASIO recording inputs
These are the "outputs" from wich your PC records signals coming from the DSP.
You can "activate" these outputs by uploading [Epilog] or [k1lt/k2lt + Asio]


(Note: The naming convention of 'inputs' and 'outputs' can be confusing,
but it just depends from wich end of the audio chain you look at a certain 'port')

The above mentioned DSP-plugins are the so called 'I/O Plugins' and therefore the
corner stones of kX's DSP concept.

Let's summerize them;
-[Prolog] - (1) External Physical input signals
-[FXBus] - (2) Internal "input" signals
-[Epilog] - (3) External Physical outputs + (4) Internal Recording "outputs"

The ProFX counterparts;
-[Src] - replaces both (1)Prolog and (2)FXBus
-[k1lt] - replaces the (3)Physical outputs and (4)WINMM Rec on Epilog
-[Asio] - replaces the (4)ASIO recording inputs on Epilog

If you understand points 1 to 4 and that *everything goes through the DSP*,
you should now be able to;
- locate every output
- locate every input
- patch any signal to wherever you want
- run any signal through any DSP effect(s)
- record any signal any way you want
- monitor (hear) any signal any way you want.

(to be continued..?)

/LeMury

seventiespotato

that's right

__________________
B

dj_stick

LeMury, when you have finished that wonderful description, would you like me to add screenshots and put it on the knowledgebase?

__________________

thomasabarnes

Whoa! LeMury and DJ_Stick, give me a while to absorb this info.

Thanks LeMury for putting this together.

Sincerely, thomasabarnes

__________________

May a song always touch you in a positive way.
SONAR X1D Expanded, Windows 7 Pro 64Bit, MOTU UltraLite MK3, 150 GB HDD, 250 GB HDD, 1 TB x2 HDD 7200 rpm

My Music Production: Top 40, Contemporary Christian, Pop/Rock, Decent Rap, Inspirationals, and Children Songs

thomasabarnes

miguel:

Thanks for sharing.

Sincerely, thomasabarnes

__________________

May a song always touch you in a positive way.
SONAR X1D Expanded, Windows 7 Pro 64Bit, MOTU UltraLite MK3, 150 GB HDD, 250 GB HDD, 1 TB x2 HDD 7200 rpm

My Music Production: Top 40, Contemporary Christian, Pop/Rock, Decent Rap, Inspirationals, and Children Songs

Lex Nahumury

Yes, good idea. It should be obvious what and were the screenies should come.
Also fix grammar and spelling errors in the body text please...

/LeMury

thomasabarnes

OK LeMury and DJ_Stick:

I messed around with the DSP and trying to use only the ProFX and addons in there.

I loaded 6 instances of SRC and loaded k2lt (since I have an Audigy model SB 0090). I set the SRC instances up as follows: fxbus 0/1 and name it Wave 0/1, fxbus 4/5 and name it ASIO Front 4/5, fxbus 6/7 and named it ASIO Rear 6/7, fxbus8/9 and named it ASIO Center/LFE, AC97 LineIn and named it Line In, and fxbus 2/3 and named it MIDI.

Now, I connected ASIO Front 4/5 to outs 1 and 2 on k2lt, Asio 6/7 Rear to Outs 9 and 10 on k2lt, ASIO Ceter/LFE to outs 11 and 12 on k2lt. But, when I play a .mp3 in WMP, I dont hear any sound. The SRCs I named ASIO Wave 0/1, Line In, and MIDI are not hooked up yet.

If I add MX6 and connect ASIO Wave 0/1 to the MX6 In1l and In1r (and put a check mark in the Ms and Es, and VU=Main), and then connect the MX6 MainL and MainR to the k2lt outs 1 and 2, I can see the meter of MX6 has a signal, but I dont hear anything. But, if I connect ASIO 4/5 to the MX6 In1l and In1r, and then connect the MX6 MainL and MainR to the k2lt outs 1 and 2, I dont even see a signal in the MX6 meter. I'm trying to use the ProFX and addons to do 5.1 surround audio authoring in a music production program. What do I need to do to get sound from the speakers?

Sincerely, thomasabarnes

__________________

May a song always touch you in a positive way.
SONAR X1D Expanded, Windows 7 Pro 64Bit, MOTU UltraLite MK3, 150 GB HDD, 250 GB HDD, 1 TB x2 HDD 7200 rpm

My Music Production: Top 40, Contemporary Christian, Pop/Rock, Decent Rap, Inspirationals, and Children Songs

Lex Nahumury

thomasabarnes,

Ok, I re-wrote your setup (as you described it) in a more readable fasion like this;
(please check it)

-fxbus 0/1 and name it Wave 0/1,-> (not connected)
-fxbus 4/5 and name it ASIO Front 4/5, -> k2lt 1/2 ->(analog front)
-fxbus 6/7 and named it ASIO Rear 6/7, -> k2lt 9/10 ->(analog rear)
-fxbus8/9 and named it ASIO Center/LFE, -> k2lt 11/12 ->(analog Center/LFE)
-AC97 LineIn and named it Line In,
-fxbus 2/3 and named it MIDI.


>>But, when I play a .mp3 in WMP, I dont hear any sound.
>>The SRCs I named ASIO Wave 0/1, Line In, and MIDI are not hooked up yet.

No, ofcourse you do not hear anything since you did not connect [FXBus 0/1, Wave0/1],
wich carries WMP/MP3 playback by default, to any output!


>>If I add MX6 and connect ASIO Wave 0/1 to the MX6 In1l and In1r
>>(and put a check mark in the Ms and Es, and VU=Main),
>>and then connect the MX6 MainL and MainR to the k2lt outs 1 and 2,
>>I can see the meter of MX6 has a signal, but I dont hear anything.

Ok, it's clear you have a signal coming into MX6, and connected MX6's Main out's to k2lt 1/2.
Now you should hear sound comming from your 'Analog Front' speakers *only*!
I don't know what speaker setup you have, but make sure you listen to the right physical output.
Also check if you did not 'marked' the RECMON on MX6 because this will
swap the MainOut with the RecOut busses. So if the RecBus of MX6 doesn't carry any signal,
you won't hear a thing.


>>But, if I connect ASIO 4/5 to the MX6 In1l and In1r, and then connect the MX6 MainL and MainR
>>to the k2lt outs 1 and 2, I dont even see a signal in the MX6 meter.

If you don't have a signal in MX6's peak meter, then there's simply *no* signal coming out of your [FXBus ASIO4/5].
Check your app's ASIO output assignment and/or check 'kX Router' assignment.
(Btw; using the 'Peak' plugin is a good way to trace down signal "problems")

>>I'm trying to use the ProFX and addons to do 5.1 surround audio authoring in a music production program.
>>What do I need to do to get sound from the speakers?

Most likely not MX6, since it represents a 2-channel (thus stereo) mixing console.
In it's simplest form you could use your first setup namely 3 'Src' instances connected to k2lt.
Assign/setup your app en the 'Src's', then connect them to 'k2lt' accordingly.
In addition, use 3 'Peak' plugins to (test)monitor if you get all signals from your app into the DSP.
(if nothing comes in,..nothing goes out)

Btw; you *do* use a surround spkr set or have all analog surround outputs of your card
wired to some amplification system,..Right?
I mean, if you haven't wired Analog Front output to some speaker system, you won't be able to hear it's output..duh

/LeMury

PS:
The outputs of 'k2lt' are selectable for easier and quicker "wiring".
Make sure you selected the right output.

thomasabarnes

LeMury:

Thanks for your reply! I figured out why I wasnt getting the sound from my speakers, when I was using Wave 0/1 with the MX6 going into k2lt, I didnt factor in the swap speaker feature I was using with the default KX DSP setup. Wave 0/1 works, but I cant get any signal when I connect any of the ASIO SRCs. I read the KX router info in the KX help, but I dont understand what' s wrong.

When I pull up the KX Router and go to ASIO and select KX Out 4, I see on the right, 4, 0, 13, and 14 with sliders. The slider under 4 is up, the rest are down. I would think this is set up right.

When I select KX out 5, I see 5, 0, 13, and 14 with sliders. The slider under 5 is up, the rest are down. I would think this is set up right.

But If I connect any of the SRCs I named ASIO the way I connect the Wave 0/1 into the MX6, I get no signal at all. Can anybody help me trouble shoot this no signal problem?

Yes LeMury, I'm using Creative Inspire 5.1 5300 speakers : ).

"In addition, use 3 'Peak' plugins to (test)monitor if you get all signals from your app into the DSP.
(if nothing comes in,..nothing goes out)."

I have no idea how to use the Peak plugin you mention. I assume you mean the Peak plugin under add plugin/Basic/Peak? Can you say: "Oh for comprehensive documentation." LOL

Whatever may be the case, thanks for your replying thus far.

Sincerely, thomasabarnes

__________________

May a song always touch you in a positive way.
SONAR X1D Expanded, Windows 7 Pro 64Bit, MOTU UltraLite MK3, 150 GB HDD, 250 GB HDD, 1 TB x2 HDD 7200 rpm

My Music Production: Top 40, Contemporary Christian, Pop/Rock, Decent Rap, Inspirationals, and Children Songs

miguel

thomasabarnes, what LeMuri is saying is that mx6 is not suitable for surround mixing, and instead all you should need is to connect each FXbus pair (that's each ASIO pair) to the respective output in a k2lt.

All this just means you use the music program to do the surround mixing/positioning whatever, and just use the dsp to send each ASIO channel to the proper speaker.

So basically, first configure your music software to send each surround channel to a different ASIO channel. That can be something like

FrontLeft/FrontRight >> Asio0/1 (by default goes to FXbus 0/1)
ReartLeft/RearRight >> Asio2/3 (by default goes to FXbus 2/3)
Center/Subwoofer >> Asio4/5 (by default goes to FXbus 4/5)

Now in kX it can be as simple as getting 3 src's, set each to fxbus 0/1, 2/3 and 4/5 and connecting each pair of wires to a k2lt in order. Then configure the k2lt to read

(the folllowing names are an aproximation because I own an APS card and the names have nothing to do with an audigy)

Out 1/2 Front Out
Out 3/4 Rear Out
Out 5/6 Center/SubW, not sure here

now each one of the 6 channels should go to a different speaker and it's your job to do a decent mix!