Audigy RX works

[trex2000]

I can confirm that the audigy RX card (the pci express one) works with 3552. The card is recognized as a 'generic card'.

I've tested only analog outputs 5.1 and the optical one, all of them are working.

[trex2000]

Will keep this updated when I will be able to test the other features. I could no get SPDIF passthough to work over optical output yet.

[AwkwardAardvark]

Thanks trex2000! Which operating system are you using?

[trex2000]

Windows 10 64 bit

[trex2000]

As expected, there is no Wave Out HQ, as it does not have the P16V chip anymore (it has P17V, if I recall, but it's not recognized)

[trex2000]

So far, I've tested the SPDIF output, that works, but could not get AC3/DTS passthrough to work. The analog outputs are also working There is no Wave HQ, but I've read somwhere that is does not have the P16V chip, it has the P17V, that could be the reason. I've used the 3552, not the 3553. I did not have issues with cracking, even with the default buffer values.

Mainboard: MSI H270 Tomahawk and I5-6600K CPU, Windows 10 64 bit.

[pachuco]

I am having trouble installing driver with Audigy RX. The installer detects the RX, installs, asks me to reboot. Upon reboot, kmixer says device not detected.

In device manager:

• Device name: kX 10k2.5 Audio (3553) - Generic
• Issue: Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)

And indeed, it is missing from system folder. Attempting to "update" device by pointing it to driver location(kx.cat/inf/sys) fails, as it does not locate driver it needs.

The OS is XP SP3 x86 The driver is v3553.

Edit, attempting to install via "Add New Hardware/I Have Disk" gets around the problem, but not for long as BSOD in kx.sys happens.

[pachuco]

I am not sure how the planets aligned, but after kx.sys found its way into system folder, the driver was able to install itself after telling it to "Update Driver, Install Automatically". Now it works.

Painful experience, would not do again.

[ITzTravelInTime]

I have added audigy rx full support in my own fork if you want to check it out.

[pachuco]

I have added audigy rx full support in my own fork if you want to check it out.

How does this driver like PAE and addresses above 4gb?

[ITzTravelInTime]

How does this driver like PAE and addresses above 4gb?

I just added support for the sound card model and a little workaround to get all inputs/outputs working by threating the card like an audigy 4.

The hardware being 32 bit pci (used trought a pcie bridge) is limited to addresses within 4gb and the driver itself (at least on macOS) can't allocate buffers above the 2gb mark.

So for PAE i think the situation is unchanged: the driver just relies on the os to be able to allocate the dma buffers below the 2gb or 4gb mark. This is a solution that allows all 10kx sound cards to work using the same code for buffer allocation.

EDIT: i am working only on the macOS driver, so i don't know about the windows-spcecific stuff. I mostly made a fork supporting both modern macOS and powerpc macs running OS X (that required some reworks of stuff like io port access or dma buffer access)

[pachuco]

Ok, I bit the bullet and reinstalled Audigy Rx. Can I has xp x86 win driver?

Edit: actually, hang on, I have WDDK. I'm gonna get off me bumarse and try compile myself.

[ITzTravelInTime]

For windows xp there are official drivers you can use.

[pachuco]

Official Creative drivers?

Some issues:

• Not as fun as kx drivers. But hey, they have hardware EAX. But hey, who bloody care, soft-oal exist!
• They very much hate PAE with addresses above 4gb(kernel patched).
• If you leave application playing overnight(background music or simply forgot to close), you find sound does not work in morning until you stop said app. That smells a lot like an int32_t sample counter overflowing at 44.1 khz.
• The kx drivers weren't amazingly stable either, but eh, give try for shits and giggles, at least they have fun features.

[pachuco]

I guess you could say the dma engine on these cards is too smarts for its own good, regarding PAE.

[ITzTravelInTime]

For the Mac part the driver uses some kernel api (designed for this) to allocate memory just in the first 2gb of address space, it’s done just for the dma buffers, all the other allocations are made in the standard way (always using the appropriate kernel api to respect the kernel coding and memory management conventions). And as far as I am aware the Mac port is not displaying the playback issue you mentioned. Btw the windows driver should work only at 48khz as far as I know. While we hacked together a way to have arbitrary sample rates (up to 192 kHz) on the Mac driver.