redocneXk released - Realtime 5.1 ac3 Encoder

Russ · Nov 24, 2008, 05:44 PM

I do not know, I just threw that out there as a guess, I doubt that the game would disable it at the OS level. There is a DirectSound wrapper that allows you to tweak some of the DirectSound options, you could play around with that and see if it makes any difference (I doubt it will help, but...).
DirectSound Control Home

tecnoworld · Nov 24, 2008, 06:23 PM

thank you, but I just found a hidden feature. There is a file called dare.ini, in which a line is called "DISABLE_OPTIMISATION". This is equal to TRUE by default; simply put it to FALSE and the game will use 3D acceleration! At that point, just load redocnexk and...5.1 dolby digital live is a reality!

WOW

I simply LOVE redocnexk

Toth · Dec 31, 2008, 05:03 PM

I just discovered this program and I am using it with kxdrivers on my old audigy 2(SB0240 10k2), and I am outputting by pass through on my AL888 onboard optical connection.

I tried the GUI first, but I seem to get this weird stuttering (something I have seen mention of here and there on the threads). Its not there constantly, but its there often enough to be pretty distracting. I have messed with the ASIO frequency (I think) and tried 2.0ms,4.0ms,30ms, but with no real effect.

I then tried the console version in hopes that may be part of it (seemed to get that from reading the threads), but everytime I try to run it, it starts up and then blue screens with a message about kx.sys and a nonpageable section of memory marked as pageable. I have tried both 5.10.00.3538 and 5.10.00.3541 with the same effects.

Any help would be apperciated.

Tril · Dec 31, 2008, 05:48 PM

The GUI version never worked properly so the stuttering is unavoidable on that version.

The console version should work fine on Audigy 2. I've never encountered the blue screen that you are talking about so I would not know how to fix the problem. Sorry for not being able to be more helpful. It's just a guess but maybe it starts with the wrong parameters. If it works a bit with the GUI version, it should not crash like that with the console version.

Toth · Dec 31, 2008, 06:08 PM

Quote:

Originally Posted by Tril

The GUI version never worked properly so the stuttering is unavoidable on that version.

The console version should work fine on Audigy 2. I've never encountered the blue screen that you are talking about so I would not know how to fix the problem. Sorry for not being able to be more helpful. It's just a guess but maybe it starts with the wrong parameters. If it works a bit with the GUI version, it should not crash like that with the console version.

Thanks for the quick reply. So I got the console version working... apparently it doesn't like 5.10.00.3538 or 5.10.00.3541 with redocnexk on my machine. I tried going all the way back to .3534f and was finally able to get it working without a crash

.

However, even with the console version I am getting stuttering/clipping. I can see the dolby digital light on my receiver blink when it happens. Any parameters to mess with? EDIT: I figured out how to get the ASIO control panel (I am dumb)... let me see if messing with that fixes it now that I am running the console version.

mause · Jan 15, 2009, 09:43 AM

Quote:

Originally Posted by Toth

Thanks for the quick reply. So I got the console version working... apparently it doesn't like 5.10.00.3538 or 5.10.00.3541 with redocnexk on my machine. I tried going all the way back to .3534f and was finally able to get it working without a crash

.

However, even with the console version I am getting stuttering/clipping. I can see the dolby digital light on my receiver blink when it happens. Any parameters to mess with? EDIT: I figured out how to get the ASIO control panel (I am dumb)... let me see if messing with that fixes it now that I am running the console version.

I have the same issues with stuttering with the console version. I tried every combination's of option and the only thing that change something is the -l options, that when i use with 4 the audio works OK for +/- 5 minutes, then starts stuttering again. Any one can help me?

Specs of my system: C2Q 6600, 4Gb ram, Geforce 8800GS SLI, Sound Blaster Audigy 2 ZS.

hollowgr4m · Jan 20, 2009, 04:51 AM

hey guys, i've been having a problem with redocneXk, basically it works fine while it's running and sounds great, but occasionally when i close the command version (or click stop encoding on the GUI version) my pc freezes and i need to restart. It doesn't happen every time, but if i want to make it happen i usually can by opening and closing the program a lot, eventually it will crash. Obviously i that isn't the only time it happens, it can happen the first time i close it. So there seems to be a problem when encoding stops.

The only other info i can give is some error reports i've had, i think they are mainly due to the GUI version, as there is sometimes an error without a crash when i click stop encoding with that. I have also had a "system has recovered from a serious error" message a couple of times, with a 0x000000D1 stop code, and usually it will lead me to a microsoft site saying my audio driver has a problem. I've installed a fresh XP on a test drive to see what would happen and i have the same problem.

All drivers are updated
I'm using XP32 SP3 with an Audigy 2 ZS platinum pro

Here are some of the messages.

Faulting application redocnexk.exe, version 2.0.5.0, faulting module user32.dll, version 5.1.2600.5512, fault address 0x00031bc4.

Faulting application redocnexk.exe, version 2.0.5.0, faulting module ntdll.dll, version 5.1.2600.5512, fault address 0x0001b1fa.

Faulting application redocnexk.exe, version 2.0.5.0, faulting module wdmaud.drv, version 5.1.2600.5512, fault address 0x0000461f.

The last one is the most interesting i think. I have 2 soundcards installed, onboard, which i use for my gaming microphone, and the audigy which i use for everything else. Is it possible there could be a conflict with the wdmaud driver, as this is shared by all audio devices. I haven't yet tried encoding after removing and disabling the onboard sound, but i'm interested in what any of you have to say. I've never had a problem having them both going before, but would redocneXk have an issue with this?

If not i'll be glad to hear any other ideas, thanks.

t0mb0la · Feb 14, 2009, 06:35 PM

I've been trying, repeatedly, over the past few months, to make this work fully.
All the gleaning of these forums and google, and I am still stuck.

Basically, I am missing two channels; namely RL and FR.
Center, FL, RR and LFE channels all work happily.
Both console (v1.10) and GUI (v2.05) versions of redocneXk give me the same result.

I am hoping someone can suggest my next step, before I admit defeat and am forced into buying a Dolby Live Digital card.

The relevent parts of my system are thus:
Windows XP Professional, SP3. Running on a P4 2.4ghz with 1GB ram.
SBLive 5.1 digital (SB0228), driver kX Version: 5, 10, 00, 3545 - debug.
Trust SC-5250 (CMI 8738/8768), driver Dogbert: 1.2.2.0.

The SBLive is used as the ASIO device, the Trust as the output device for redocneXk.

Bottom line, I am two channels short of having this fully working, I'm sure, my digital amp (a JVC TH-L1) illuminates the LEDs for all channels when redocneXk is encoding.

Playing a DTS or AC3 stream from regular sources fills all my speakers with sound accordingly; so redocneXk 'should' be able to as well.

Can anyone suggest what I might try next?

Maddogg6 · Feb 14, 2009, 06:55 PM

Quote:

SBLive 5.1 digital (SB0228), driver kX Version: 5, 10, 00, 3545 - debug.

I think these cards have a bug concerning ASIO - 'ASIO Mapping' (hint: thats something you can search these forums for - and search for 'Russ' as a user - he knows more about it than me)

This is how you normally would find the work around... but it assumes your use for ASIO is for DAW application like Cubase. Im not sure how else to figure out the work around.

kX and Cubase SX

Others here maybe better to help with that... but maybe if you just hear 'no you not going nucking futs' is help enough for now.

Russ · Feb 14, 2009, 07:03 PM

Right, use ASIO pins 4/5/6/7/8/9 on epilog (because 1 and 2 are not used with these cards), and use the GUI version of redocneXk in order to be able to map the channels. Note that sometimes the ASIO mapping will shift (i.e. 4/5/6/7/8/9 might show up as 6/7/8/9/10/11, etc), so you will have to play around with it, but you should be able to get it working.

t0mb0la · Feb 14, 2009, 08:22 PM

Maddogg6, Russ.

Thank you both for your help.
I will try tomorrow with the ASIO mapping, and let you know how I get on.

Best Regards.

t0mb0la · Feb 15, 2009, 09:00 AM

Hey, you guys, outstanding, what more can I say?

Ta very much!!!

I used Reaper to monitor the ASIO pins. With the wave generator driving the pins in kX DSP, it was easy to see the missing audio on pins 1 & 2. Pins 8 and up were similarly fruitless for me.

At the minute, I've had to use the following ASIO mapping on epilog: 0/3/4/5/6/7
and changed the mapping in redocneXk GUI accordingly.

It works very well; CPU hungry of course, but that is to be expected.
I may have to hack a little at the console version of redocneXk; persuade it to use my 'working' ASIOs, as the general concensus seems to be that the GUI version is inferior.
Plus, anything that can save me even a few CPU ticks has to be of benefit.

Regardless, I have this working now; thanks to your invaluable advice.

I salute you.

Russ · Feb 15, 2009, 09:06 AM

Quote:

Originally Posted by t0mb0la

Pins 8 and up were similarly fruitless for me.

You probably have the format in the ASIO Control Panel set to [8+8] instead of [16+16] (which is fine if it works for you).

CraziFuzzy · Feb 16, 2009, 11:15 AM

I've got a question for you guys. Has anyone looked to see what would be required to make a virtual 6-channel sound card driver that could be used as the Redocnexk target? The reason I ask, is there are quite a few super cheap USB sound cards, that support just one stereo output, or one SPDIF output (Turtle Beach Audio Advantage Micro). I currently use an old audigy card, and then output the SPDIF via the Micro, but the audigy card seems pretty silly. Basically, what is required, would be a simple 6-channel virtual sound card driver that did the proper ASIO redirection, so that Redocnexk could be used without the multichannel sound card.