3538h released

If I could make that damn thing input at 96KHz I would have a definite answer if it outpus at 192KHz or 96KHz...

If somebody has any idea how can I could do that I would be great ...

And, btw, why it would say in SPDIF/I2S Status that PB:192000 ?

When I was playingback at 96KHz it said PB:96000...

 

You can get 96kHz input using HQ device & selecting I2S 1 input in p16v source... Connect your audio input to LineIn on the back of the card...
Make sure, in AC97 page, you have that green button enabled (LineIn to I2S Routing or something)...

 

192 khz, I understand that it would be cool, however I must ask WHY? 96 khz already gives us 48,000 hz per channel (the ear is supposed to hear a little less than half of that) also, the 10k2 chip operates at 48khz so anything above that you are just upsampling right?

 

I have installed the 3537 drivers last week, mainly to have spdif dd 5.1/dts support. (cause i couldnt get it to work for my audigy 1 with the creative drivers)
I noticed there is always a loud short distortion when i start (or stop) sending a dd 5.1/dts signal to my receiver. Is this known and is this going to be fixed in the 3538 drivers? I know for sure this has something to do with the kx drivers, because i now got the creative drivers to work and it doesn't happen with those. I rather want to keep using the kx drivers, but this distortion is really annoying,... always have to turn down the volume, cause i don't want to damage my speakers.

 

the loud distortion is a known issue, and is on the to do list

 

3538g driver allows the Sound Blaster Live 5.1 (SB0220) to use 5.1 speakers!

I'D SAY, IT ALLOWS U TO USE IT AS 6 ch !!! low latency !!! ASIO output !!!


... REAR LEFT / REAR RIGHT (black plug) is seems to be "misrouted" due to sb22x codec version (or bug? IDK) ...
I founded "BLACK PLUG" channel is hiding at kX_out_13 & kX_out_14 Asio Outputs
(experements in REASON 2.5 - 6 ch. output with 4-8-10 ms latency)

BUT

AT SAME ROUTE (13&14) THERE ARE kX FX CHANNELS (DSP section / KX router)
this seems to be REAL BUG for SB22x ...


kXdrv3538g - it's the first time I can use SB220 with more than one SILY stereo output!


850 mHz Spitfire on KT133A 256MB@133 40G@ATA100
with
SB220 aka SoundBlaster Live! 5.1 Digital

kX - Urs S-BLASTER's NEURO-POWER!
Line input FX processing: m2in+m2out is less than 4 ms latency for your DSP!

 

try to use

kx out 13 & kx out 14 outputs
for sl/sr (black) channels ...

for my SB220 @ 3538g it helps

 

Den_VS - please post your SB022x findings in the relevant thread, and keep this thread for general comments/overall performance reports

thank you

 

I usually use a lot of kX windows on my desktop, and they remember their positions on restart, but sometimes they don't. Anyone else having this problem with 3538h?

 

I believe that if you save the driver settings when they are setup like you like them you wont have this problem. I think I have posted something like this before but we need to have snap to windows (if you move an effect close to another effect, within 10 pixels or something it will snap to teh other effect to make things a little easier to orgainize)

 

3538h testing

Done testing, this are the results:

Win2k-SP4 DOES not support 192KHz playback, for any attempt of playback at 192KHz DirectSound displays an initialization error, and the only way I could enable playback it was at 192KHz 16Bitt MCI, but it got resampled to 44.1 by windows, so this will not work on Win2k.

WinXP-no SP, behaves like win2k.

WinXP+SP2, behaves like Win2k3, I get a BSoD when playback at 192KHz/24 or 32bit (16bit I didn't try it), but in cerain conditions:
- when starting playback
- after 1-2 seconds after starting playback
- when stopping playback
- when seeking (exactly when seek occurs)
BSoD: 3 types until now:
1) Saying that someting was wrong and windows shutdown to prevent hardware damage
2) Saying: BAD_POOL_CALLER
3) Saying: IRQ_DRIVER_LESS_OR_EQUAL

This was tested with several of my friends machines, but with the same soundcard, an OEM SB0240 Audigy2.

Eugene, could this be a hardware issue (I mean my Audigy2 being broke on 192KHz output? except 192KHz is solid-rock, no hang ever)?
Can somebodyelse test this and post the results ?

 

This doesn't work on my soundcard ... (model SB0240)

 

make sure the input is coming from AC97 2

 

How do I do that?

 

AC97 2 is DSP source only, for real 96kHz you'll need to select kX HQ device as recording device in your audio application & select I2S 1 as p16v recording source...

adi111p, my SB0240 works well, as i described... Please retry & tell us if you made anything work, were you able to get ANY sound when trying to record like this?

 

forget about 192kHz. don't use it

E>

 

ok, I finally made 96KHz input work: I had to set the recording to 96KHz/16bit (before I used 24 bit and so i didn't get any input), so it is enough for my needs, so I tested the 192KHz output:

192KHz is in fact 96KHz output for some reason, so no 192KHz ever. I think this is why I could get 4 channels at 192KHz working

anyway, for now 96KHz/24bit is ok by me ...

Only one question though: what is the optimal output format: 96KHz/24bit or 96KHz/32bit?

 

32bit is simply 24bit padded to 32 for those applications that don't support pure 24 bit sound - so there is no real difference

 

I did exactly that and couldn't make it work! Actually I tried all of the P16v inputs but none worked. obviously made sure the program used HQ as its rec device. I made sure the green button in the ac97 is on. is there something i'm missing?

 

It worked on my soundcard like this:

First done this:
- set P16V rec source I2S1 (Mixer->Master)
- make sure that Master Recorder Level is maximum in Mixer->Recording
- in Mixer->AC97 made sure the green button in the ac97 is on, and made sure that Line-In volumes are selected and set to 0dB

Then:
Started recording program, but only 16bit recording works, 24 or 32 doesn't.