W A R N I N G !


W A R N I N G !

This page is full of non-facts and bullsh!t, (just like the internet and especially forums and other blogs), please do not believe entirely without exercising your intellect. Any resemblance to real things in reality is purely coincidental. You are free to interpret/misinterpret the content however you like, most likely for entertainment, but in no case is the text written on this blog the absolute truth. The blog owner and Blogger are not responsible for any misunderstanding of ASCII characters as facts. *cough* As I was saying, you are free to interpret however you like. *cough*

Saturday, May 29, 2010

EAX5 via DS3D GX on HT Omega Claro (or other CMI8788 cards) using Xonar driver

Introduction

The AV100 and AV200 processors found on Asus's Xonar line of sound cards are known to be C-Media's CMI8788. Even Asus's drivers say so:


Naturally, at least one person would eventually make use of that fact to install Xonar's drivers on other CMI8788-based cards to get software-emulated EAX5 found on Xonar's drivers.

There are at least two methods to install a driver not meant for the device, I'll touch on one that works (in enabling EAX for non-Xonar cards), and one that didn't.

Changing the subsystem ID in the driver .ini/.inf files

It didn't work, so I won't go into details.

The driver installs, but does not work - Xonar Audio Center does not run, digital out works or doesn't depending on whether you had installed the soundcard's original drivers previously, analog out not tested, no DS3D GX.


Changing the card's subsystem ID in EEPROM

If DS3D GX is enabled through Xonar Audio Center, then that center must be made to work (it has no ini/inf that can be edited). The other method to disguise a card as something else is changing its device and subsystem ID.

Fortunately due to the apparent frequent failure of EEPROM of Xonar series of cards people wrote a EEPROM writer for it:

Xonar EEPROM Failure - AlsaProject

When run the program gives you a list of device IDs with their respective cards' names to write to your card's EEPROM, including Razer Barracuda AC-1.

If your card is PCI, choose a PCI card; if it is PCI-E, choose a PCI-E card.

Asus's naming system - PCI-E versions of the cards have an X at the end of their name - DX, D2X, STX, only exception is HDAV1.3 which is a PCI-E card, with the PCI version being HDAV1.3 Slim

This is where you need to trial-and-error - not all, if any, of the Xonar drivers/IDs work with your card's analog out, digital out worked for me in all cases I tried.

For HT Omega Claro, the one that works is Xonar D1.

After changing EEPROM:


Testing if DS3D GX/EAX5 is working

First there is the above program to tell you what features the card has.

Secondly you can run games that are known to crash with Xonar's DS3D GX (a lot), if your card now crashes the game, congratulations, you have managed to recreate the DS3D GX crashing games part on your card.

Any other suggestions on testing EAX5 functionality are welcome.

2 comments:

Hapi said...

hello... hapi blogging... have a nice day! just visiting here....

Connor Ness said...

I know this is an extremely old post, but I used this utility on my HT Omega Claro II. As it turns out, my card's device ID is not an available option in the utility, so I could not use it to revert back to the old ID. Luckily, the author of the tool made the source code available, and I was able to simply add a single line to it and recompile (from within an XP VM, as the original compiler would not run on my 64-bit 7 installation). My modified version of the application was able to successfully restore the device ID on my claro II, and it's back to factory default. If anyone came across this post and wishes to use the utility to make use of GX, or has already changed the ID and can't revert back, let me know and I can provide you with my source and EXE