Russ

Yes that would work (sort of), but you will not get the full bit resolution doing that.

great white

3545b?

Have I been away that long? I'm still using 3538m!

I'm using an old audigy 4 card with xp, is there any advantage to updating to 3545?

I don't want to loose UFX or Pro FX either if I update..........

Cheers

SGProd

(Realized this was not the appropriate place for my post - Started a new thread - SG)

caballo

Is 3545b version improved for 10k1 models in comparation with 3539 version ?

I don't see the difference... Mine SB0220 run ok with the two versions

Lex Nahumury

done;
NEW: ProFx (3538) Update Incl. MX6 and AC97

wrobelpl

Thanks,
but still doesn't work with over 2GB RAM

weenerdog

thank you for the profx update

djsubject

how do i remove the older pro kx plugins so i can run the new ones?

thanks in advance

Subz

weenerdog

djsubject:

from the download page (download)

Delete any previous ProFx.kxl file!
Unzip and register the new ProFx.kxl file.
Restart kxmixer, clear the DSP and reload saved DSP setups if any.

You can verify that you are using the correct ProFx version
by opening the "Info" of one of the ProFx plugins.
The "Engine" field should display the current version.

djsubject

this is where i get stuck,

where would this .kxl file be?



Subz

Russ

You really do not have to delete it, just register the new version (the instructions do not really apply to the bundled version of ProFx).

The bundled version is part of kxfxpack.kxl, kxfxlib.kxl, and kxfxadc.kxl in the Windows\System32 directory (and you would not want to delete those files (except for maybe kxfxadc.kxl), as you would lose more than just ProFx).

LyyNx

when you double click on the file (.kxl ) it kxmixer registers it's location and uses it from there. at least that's what i experience. so, the file is wherever you put it when you downloaded it originally

djsubject

Ahhh, thats what happened last time

i registered from desktop, all was well, then i deleted the file & it stopped working,

thanks for the help!!

Subz

lawrence_lan

windows server 2008 ,6GB RAM NO problem !!

dawkorn

Ive Been enjoying the kx drivers for Multi-Track ASIO Recording for 5 plus years now (thank you Eugene and the KX Family!)

24bit input working at 10.67ms, 4 stereo channels simultaneously

I've tested version 3545b drivers in effort to get a recently installed Audigy 2 ZS to function in "24BIT" for Multi-track ASIO.

System Spec: P4 2.4ghz, 1.5gig ram, Audigy 2 ZS, SBlive 5.1 (CT4830)
3545b drivers, Using UFX .39 and New ProFX 3.09 for 3545

Target - Record multiple 24bit ASIO sources from the two SPDIF IN's on the Audigy2 ZS,

using 2 inputs simultaneously in 24bit,
cd_SPDIF IN and AD_EXT SPDIF IN
----------------------------
Observations:

1. SRC 00/01 - Using SRC on 00/01 blasts noise on 00 channel only when activating "input monitoring" or 00/01 as wave input, no solution yet.

SRC 02/03 - Used by default for Soundfont/Cubase Metronome (router), so not recordable (if using metronome)

that Leaves two discrete stereo pairs for recording, 4/5 and 6/7.

2. Previous Cubase multi-track Project, with Mixed 16bit and 24bit files, project set to 24bit 8+8 / Default

5.33ms works with crackles, unusable
8ms - unusable

SUCCESS at 10.67ms - ONLY WORKING SETTING so far, with occasional crackles on OUTPUT ONLY - USABLE - no crackles on audio input

16ms - Crashes Cubase, input buffer error
21.33ms - input buffer error
32ms - input buffer error / crash
42.67 - input buffer error

Typical error -
"Error creating input buffer#2: error = (size)=16384)
GetLastError()=2

Unknown error

Retry?
---------------------------------------
Mostly same results for blank 24bit new project with imported 24bit single file.

Similar Results with input buffer errors using Reaper at 24bit.
---------------------------------------

Driver when set to 16bit/48khz stable - no apparent glitches.

Feedback welcome

Maddogg6

Hmm - 2 devices?? - you are either;
1) using both cards as a 'master/slave' config (1 card is the selected ASIO device, other card acts as either a send/receive or pre-amp or submix for the selected device)
2) using Cubase 4 SX thats *supposed* to support multiple ASIO devices, but I have heard of troubles with that
3) using ASIO4ALL - in which you are actually using kX's WDM interface.

Please clarify your configuration. And maybe state what version of Cubase you are using.

Russ

@dawkorn

(in addtional to what Maddogg6 asked)
What Operating System (Vista?) and what DSP config?

dawkorn

the SBlive 5.1 (CT4830) is sitting idle right now, it is NOT being used for "card to card pinout" inputs. I just left it in the computer for now!

I am only testing with the Audigy2 ZS, but I did try the SBlive 5.1 (CT4830) and it worked fine with the new drivers.

My OS is XP Media Edition with SP3.

Regarding Multiple "ASIO" interfaces -
I have a second pc running a Electric Piano vsti....it is a Celeron 2.8ghz box. That box runs the electric piano, and its passing its audio via its SBLive SPDIF out, thru coaxial cable, to the SPDIF in on the Audigy2 ZS. That is working perfectly, simultaneously using midi passing from the 2.4 to the celeron to trigger.

I have tried using two audio apps on the same box (the 2.4) using asio4all but it glitches too much due to latency/two apps running simultaneously.....there are no glitches using a second box sending SPDIF out.

I have not gotten as far as jumping internal wires from card to card to get additional inputs (as I really only need 2-4 ins at a time) and Im achieving that by using the two SPDIF Ins as mentioned previously.

I may try to use aux_in for additional analog ins and will post if I achieve that at some point.

Maddogg6

I2S only applies to the analog inputs of a Audigy Drive (That IO box that fits in to a Drive Bay on the fron of a PC - and makes your card An A2ZS 'Platinum' - and would thus be referred to as 'Aux2') - the 'aux in' you are likely referring to (the connector on the edge of the sound card its self) is an AC97 based input - and with ProFx:ADC you can access 2 ac97 inputs discretely (Line In & Aux or CD In & Aux, or what ever)
This is only possible on your A2ZS because of the AC97-2 (aka UDA) codec on that card.

*do not* connect an analog audio source to the I2S pins of the AUD_EX header.

Russ

Sorry, I meant the config that is giving you problems. That config does not show anything connected to ASIO 0/1 or 2/3 (for recording), so it is not possible to determine if there might be a problem with the config itself (i.e. that is preventing you from being able to use 0/1/2/3 for recording). Additionally, although the plugin labeling is descriptive as to the audio sources, it does not indicate which FxBusses are being used by some of the plugins, nor how the mixers (MX6/MX8) are configured (and it would also be helpful to know which and how the inputs/outputs are being used in Cubase).

As for the errors (error creating input buffer, etc), as far as I can tell, kX has a max input buffer size of somewhere around 32,768 bytes. 16 bit is using 4 bytes per sample, and 24 bit is using 8 bytes per sample.

So for just one channel at 16 ms:
(16 bit) 768 samples * 4 bytes = 3072 bytes --- 32,768 / 3072 = 10 channels max
(24 bit) 768 samples * 8 bytes = 6144 bytes --- 32,768 / 6144 = 5 channels max

So for all 8 channels (24 bit), 10.67 ms would seem to be the max possible latency setting, which is in line with your observations.
512 samples * 8 bytes * 8 channels = 32,768 bytes.

BTW: The above is with 10k2 cards only (and it may not be exactly right, as it is just based on observations (but I think it is close enough to be able to figure out how many channels you will be able to use under each setting)).

starkwong1

This build is just the same as any builds greater than 3540, it cause serious sound distortion when I play movies using analog output (SB0222 on Windows Vista SP1, 2GB RAM, sound output on channel 4/5).

dawkorn

New Tests:

Using the Audigy 2 ZS in 24bit 8+8 mode at 10.67ms:

for a total of 4 stereo pairs, or 8 mono channels

Using ADC (and UDA), success with 2 discreet analog stereo channels using

Line In from mini jack
Aux_In from AD_EXT on card

and

SPDIF In from AD_EXT
SPDIF CD_In from AD_EXT

Again, the 4 stereo pairs would only record at 10.67ms without glitching or crashing

To confirm what Russ said regarding the "input latency errors", I discovered that by limiting the audio app to only a single STEREO input, I could select up to 21ms without a driver crash, so that seems to gain driver stability.

I Did not test reducing the number of Output channels active, so it would be interesting to see if its a combination of both reduction of input and output channels that contributes to increased low latency responsiveness.

I performed the same tests using the same project running in 16bit, no crashes.
Also tested the SBLive Card using ASIO and no crashes with it at 16bit.
-------------------------------------------------------------

Questions I still have are:

1. Is it confirmed that in ASIO 24bit mode, mic in/line in and (Line In and Aux_In from AD_EXT on card) are actually receiving IN/encoding at full 24bit, or are they being reduced to 16bit by passing thru the ADC?

(the physical analog codecs are 24bit in/Out, right?)

Path is: ADC - gainHQ - MX6 - epilog

2.Regarding "SPDIF In from AD_EXT and SPDIF CD_In from AD_EXT" if both are receiving

24bit signal, and their path is:

SRC - gainHQ - MX6 - Epilog

Are they retaining 24bit?

3. Once these signals pass from ADC or source to MX8 and epilog front speakers, am I hearing them at 24bit or they are reduced to 16bit?

4. is there now any difference between the stereo in WaveHQ 24bit signal and the ASIO Inputs set to 24bit?

5. Lastly, considering a "max input buffer size of somewhere around 32,768 bytes", will this always be a issue for 24bit mode or might there be a workaround?

Russ

The new 24 bit stuff is not really about the physical inputs/outputs (they will be mostly the same as with previous versions of kX), it is really about the path between OS and DSP (i.e. ASIO recording/playback and WDM Kernel Streaming).

See details from from 3544a released - BETA

dawkorn

Russ,

Thank you for your previous posts and the link to "3544a released - BETA"...... reading that section cleared up many of the questions I had.

Russ

Your welcome

BTW: The DSP is 32 bit, but anything you do to the signal in the DSP modifies the signal in some way, so when you ask if such and such config is retaining 24 bit (or when talking about analog sources), I am not really sure what you are asking (i.e. if you modify the signal in some way, it is not going to be bit accurate, but the processing is 32 bit).

As for the physical I/O's, that is going to depend on the card model and the capabilities of the specific I/O. If you search the forum, I think you may find some posts from Max M. that talks about the physical I/O's (IIRC, they are 24 bit with A2 card models).

Also, that value of 32,768 bytes may not be correct (I suspect it is actually double that), it was just a guess based on observations (from the error messages, etc (which BTW, is basically just telling you that you have selected too high of a latency setting for too many channels)), but I mentioned it because it seems to work (i.e. ratio is probably the same) with the previous calculations to determine how many channels you will be able to use.

<edit>
I just saw your edit in the Bug Reports thread. A feedback loop is a definite possibility... This is why I asked for details about the specific DSP config (and host setup) that you were using when you were getting the noise from ASIO 0/1. In any case, just try to be sure that you are not recording the output of the host to a track that is also being monitored, and you should be OK.
</edit>

wrobelpl

The problem with over 2GB RAM memory is Vista. After I moved back to XP there is not a problem )

kovetm

This tool, please, when a new full-version drivers?

Andreotti

I would gif up my right arm to continue this project (I am a leftie, so...), so to speak.
What can i do to support this? I am a professional Delphi programmer with a lot of DX and driver experience. I use this driver for years now. Let me know and I will do it!
I don't give a f**k about skins or language, just about quality of this excellent driver.

enpy

Still problems with 4GB RAM.
Vista SP1 & Audigy Platinum

dtr

Yes, there are still problems with 4gb and vista32. For example when I use Ableton live, there are alot of clicks (like vinyl). Clicks and glitches presents both on DS and ASIO. But in Ds there are harder to detect them
About clicks, it`s not only vista + 4gb problem, it`s vista + kx problem. I tried in different configurations (amd, intel), and different vista builds (business SP1, enterprise SP1)