Quote:
|
Originally Posted by mirko2
1. why does the manual mention 16 buses but the router displays 32 buses (0-63)? For example, in the default setup, the E routing of the voice Wav 0/1 is connected to bus 63. Why, what is bus 63? In the DSP window, only 0-31 are visible. Is 63 the equivalent of "not used"?
|
SBLive (10K1 chip) has 32 mono busses, Audigy (10K2) has 64.
FXBuss 2 gives access to 32-63
The busses can be used like effect sends on a physial mixer (mixing console/desk ) for the various sources. Except, you also choose the output with it also. (on a mixer theres dedicated outputs, in KX you assign what 'pin' the signal is sent to -
for instance:
Wave0/1 is set up to send to the FXBuss 0/1 pins (2 monos, making it stereo) and 13/14 is the stereo send to the FXMix which allows you to add reverb and chorus to that.
Quote:
|
2. If the Wave 0/1 stream is selected in the router, the right side shows the routings A-H for this stream. Is it implicit that A is left and B is right and C is left and D is right and so on?
|
In the KX Router
If you click on the '0' (or any of the A-H sends) - a pop out will allow you to change the pin that signal will appear at.
Quote:
|
3. There are volume sliders for all routings of the Wave 0/1 stream (except for routing a/b, but that's explained in the manual with internal use for panning). But I don't get any sliders for the routings of stream Wave 4/5, 6/7 etc. Why is that?
|
*I think* its because the 'X Routing' will manage the record sends (in KX Mixer.. if you remove XRouting from the DSP - the KX Mixer looses the vol sliders for wav recording (master and wave 01/ 2/3, 4/5, 6/7) in the recording screen.
If you adjust Sends A/B in the KX router also, it could get really confusing, you need to do too many adjustments to make recording work. ??
I could be wrong, but thats my opinion/guess. XRouting is a bit counter intuitive (IMHO) and its name makes no implication to its purpose.
Also back to FX Buss, I look at it like this... The FX Buss plug-in/module - is NOT a plug in per se like a delay or reverb is - but represents, and gives interface to, the DSP's internal routings ability much like the Prolog and Epilog give access to the physical (and virtual - ASIO) ins and outs. To me, they should be called something more 'mixer like' as Ive never seen a 'prolog' on a phyical mixer (those are programming terms as far as I recall/seen) - Phyical & Virtual ins/outs - would have been more 'musician' friendly.