bobo1on1

Yes but lets say someone has a sblive 5.1, ac3 passthrough is currently not supported on that card, one could still use the asio outputs and send the ac3 stream out another soundcard that does support ac3 passthrough.
Since directsound is used for ac3 this should be no problem at all.

dj_stick

IIRC: soundstorm capalbe nVidia boards would work with is

__________________

ParaLMo

@Trill & Russ



Ok,



sorry that I forgot to mention the special thing, that without redocneXk, there's no S/PDIF output at all, using the kx driver!

So, of course, there's no Passthru on any of the S/PDIFs, but with Creative drivers it works fine.

(I tried every S/PDIF Port and every S/PDIF Setting in the kx Mixer!)
After starting redocneXk the AC3-Passthru Logo appears, at bottom right of the screen, and I have AC3 2.0 at one of the S/PDIFs.

(Don't know the S/PDIF'S correct number, because it's allway active, and no setting can change the active S/PDIF out, neither the version of redocneXk, nor the S/PDIF0-2 Setting in kX's Mixer)

Yes, the Audigy 4 (nonpro) card is a real cheap bitch, it only offers S/PDIF 0, S/PDIF 1and S/PDIF 2, there's no S/PDIF , and there's NO AUD_EXT at all, there's no S/PDIF onboard, there's just a 4 contact jack at the rear plate, containing this 3 S/PDIFs.

Russ

What AC3 logo do you mean? Do you mean on your receiver? It definitely sounds like there is some issue with kX and your card (or maybe your receiver), but I cannot be sure. Did you see the AC3 decode popup message from kX (you should not have when using AC3 passthru)?

You should perform some extensive testing to try and determine what is and isn't working.
i.e.
With kX AC3 passthru off, try playing normal sounds and see if you hear them (on the digital out).

Play some AC3 source (again not using redocneXk), with kX AC3 passthru off (software should be set to use SPDIF so that it does not decode it.). kX should decode it, and you should hear the front channels on the digital output. If you have analog speakers (or headphones), you could connect them to the analog outputs, and you should hear the individual channels.

Set kX AC3 passthru to SPDIF 0, and play the AC3 source (again, not using redocneXk, and using the same setting in the software as before), and this time you should get an AC3 signal at your receiver, and hear all 6 channels.

Try to note if/when you see the AC3 decode popup message from kX during your testing.

<edit>
I did not know that there was also an AC3 Pass-thru popup message from kX, as it is currently not supported for my card, but I did mange to see it when playing around with some of the AC3 passthru plugins, so I am guessing that is what you were talking about.

Russ

I figured that is what you meant, but it wasn't clear in your previous message. I agree that could/would be useful, but I am not sure what issues there might be with adding that option to redocneXk (i.e. I am not sure if/how the sample rate comes into play here), so we will have wait to see what Tril says about it.

Tril

It can be easily done. WaveOut (or DirectSound) is used. A different device needs to be chosen when opening the audio output device for playback. It's that simple. I can add (and I'll do it as soon as possible) another switch to choose the ouput device.

bobo1on1, it's your suggestion. Do you need it?

bobo1on1

Personally I don't need it anymore since I'll be receiving a second hand audigy within a day or so.

But people with a sblive still need it if they want 5.1 over spdif, and it should be relatively easy to add.

Maddogg6

I was thinking maybe if redocne used same SPDIF port as what set in mixer for AC3 passthru (for the device selected WITH redocne) - I guess this makes sense to me for easy 'setup'. Id think most will use same port as the AC3 passthru??

or a command line switch - for future-proof compatability.. ??

For instance a switch could be added:
-0x62 (if I have an audigy)
-0x23 (if I have a Live)

Then if those address' change for some reason (ie re-mapped by driver, if thats even a remote chance??) - no redocne code changes would be needed. No need to detect the card model either. But probably more confusing/complicated to setup.

Im not sure if the info in the IO assignments are driver or hardware.

Just babbling suggestions/points of view.

bobo1on1

I have now received my second hand audigy, my Onkyo receiver is still connected to the spdif out of my onboard soundmax since the spdif cable I made has a cinch connector at each end, I have to make a jack -> cinch cable.

So I set the default soundcard in windows to my soundmax, started redocneXk, set the default soundcard back to my audigy and guess what, works great!

Tril

New version released. See the link in the first post.

Changelog
----------
version 1.02
- Slight modification to the DirectSound code.
- Changed an incorrect error message.
- Added the -o switch.
- Decided not to compile and not provide SSE/SSE2 executables because they are not faster. That's because only the main program and not the encoder was compiled using SSE/SSE2 optimizations.
I added what bobo1on1 suggested. You can now choose to which audio device you send the encoded audio.

fl00d

hmmm when I try to run this program a popup appears making some reference to an adobe sound driver running in half duplex mode, and then it crashes. I don't understand - I followed all the instructions properly, with the exception of using surrounder+ as when its double clicked, the window that opens has no buttons or sliders. (I've resorted to using just 'surrounder' that seems to work.)

One other thing; I can access the asio control panel in an app like cubase, but when referred to in instructions here, how is it accessed?

Cheers for any solutions forthcoming...

Maddogg6

You need to specify the correct output device with a command line switch.

The adobe is default because (I assume) its alphabetically first in the list of available ASIO devices. - look at the redocne readme on what switch to use - I looked and the '-d' is used to select the output device.

Edited:

Russ

Right click in kxmixer, or from the kx icon in the system tray, and choose: 'Settings' -> 'Asio Control Panel'

fl00d

command line switch?
I see the references in the read me, but not how to implement them.

How do I determine what device number the kX asio driver is?

(btw, thanks russ, got it.)

Russ

@Tril,
Where is version 1.02?
The link in the first post is still version 1.01.

Maddogg6

Ok - make a shortcut to redocne - then edit that shortcut properties...
in the 'TARGET' add - after the quotes - a '-d X'.

the X = the ASIO device

for me X = 3 - so on my system the KX ASIO device is the 4th ASIO device (count 0-3 = 4 counts)

So on my system:
"C:\redocneXk_v1.01\redocneXk.exe" -d 3

Uses KX ASIO as the device

It seems to me theres an easy way to see all the avalable devices on your system - but I cant remember where I seen it.

I just tried 1 then 2 then 3 - and seen in redocne screen that KX ASIO was selected and DIDNT crash.

@Trill:

I just noticed - with 3538J (and the latest redocne) I NOW get a 'AC3 DECODE' popup if AC3 passthru is turned off - otherwise 'AC3 Pssthru' pops up.

Previously neither ever popped up before.

Russ

The registry key: HKEY_LOCAL_MACHINE\SOFTWARE\ASIO should show all the ASIO devices. I have only kX ASIO installed so I am not sure how it would look with multiple ASIO drivers, but I would guess that they would be listed in the device order (i.e. first one would be device 0, etc).

Russ

Did you have "On Screen Display enabled" (under kX settings) unchecked before?

Maddogg6

Hmm - on mine

NO KEY says KX there - KX IS mentioned as device under Premeire Elements key.
So I dont think that this is a reliable way...

My memory is of a DOS/Command Prompt box showing them.
For some reason - I thought redocne would show a list if no device was selected - or a switch would show the list - or something like that. Im 99% certain it was shown in a dos box somehow...

Maddogg6

I have always had all that stuff enebaled/checked - as I have a MM keyboard also and thats #2 of KX settings changes I make. (after adding a GM SF)

Im pretty certain I have those settings the same as before - I like seeing the notifications - as I used headphones to auto-mute speakers also. Remote IR enabled - KX Splash OFF.

Oh - now Im 100%


My guitar processor is SPDIF and I always (well, there were 1 or 2 times it didnt) seen that notification - and if 1 was on - they all were.

Russ

Hmm, that is strange, I am pretty sure that they should all be listed there (i.e. a subkey of that key) in alphabetical order.

Maddogg6

OOpps - wrong one..


BUT - its still not reliable -

1) KX ASIO is listed 8 times
2) the 3rd one in that list is NOT KX...

(That key is too big to post )

Russ

Like I said I have only KX ASIO installed, so mine is failry clean. The only ones that are valid would be ones that have a valid CLSID (you will notice that the extra kX entries do not have a CLSID or Description). If kX is device #3 for you, I would guess that it would be the 4th one (but maybe not). That is generally how software would enumerate the ASIO drivers (although it might be wrapped up into a nice little function call, the function just enumerates the registry keys).

Tril

radiocolonel.it is hosting redocneXk. He told me he uploaded version 1.02 but he must have made a mistake somewhere. I'll contact him and he'll fix it.

Maddogg6

Ahh - ok - but others like me who didnt run driver cleaner will probably have multiple KX ASIO entries.. - and YES - it IS the 4th one in the list WITH a CLSID set.

I wish I could remember how I seen the list of devices that are valid... - before, its how I discovered which device to use.

Russ

Ok, just thought I should let you know that it wasn't there.

Russ

I would guess that any ASIO host software would show them all (and probably in order).

fl00d

Maddog, thanks for the 'how to'; I am now making some progress.

Everything is working now, except I have the rapid stuttering problem described by a couple of people earlier in this thread.
The AC3 5.1 signal is being recognised by my reciever, but it too flickers in sync with the choppy sound.

I got the same symptom with kX driver 35 37, but updated to ensure I was on the same page as you guys. Unfortunately, under 35 38i, the problem is even more pronounced, and for all my fiddling with latencies in the asio control panel, testing basic setups with wave generator to the ASIO inputs on epilogue, I still have the same problem.

If I quit the redocnexk_v1.01 driver, sound still works, however now its accompanied with a buzzing sound.

Also worth mentioning, is that under 35 38i, cubase now crashes when it comes to initializing kX ASIO as part of booting up. So Im assuming theres an issue with the ASIO driver included with 35 38i.

35 37 drivers were removed properly with driver cleaner.

I have an Audigy platinum and am connecting to my 5.1 reciever via an optic connecter (same as spdif right..? just different cable?)

I'm almost ready to give up for the time being

Maddogg6

Yes - optical on frontpanel is SPDIF - just a different cable.

Sorry - I cant help with sputtering/buzzing

Other than maybe try different modes on the unit your sending SPDIF to..

Some may have sample rate settings - or DTS or what ever...

Also, you may want to try different SYNC METHODS in the KX ASIO control panel.

Russ

Try setting the latency to like 16 ms, and the format to 16 Bit /48 kHz [8+8]. If that works good then try lower latencies.