[monoethylene]

Yeahhh like the HiFace for example and as you ve said they arent cheap. In other threads the digital interface by Audio gd or the v-link by music fidelity (http://www.head-fi.org/forum/thread/537080/musical-fidelity-v-link-usb-spdif) were also recommended but there are a lot of other solutions. At least it has to be capable of playing almost all formats.
 
Personally I am using the Thingee (Blue Circle Audio) beside the HiFace as a D/D converter even though the Thingee is like a passthrough only and doesnt upsamle.
 
I am in the lucky circumstance that I nearly only have 16/44.1 files.
 
It would be really good when you can post the reply of Realtek.

 

[Roseval]

Probably a driver issue: http://yabb.jriver.com/interact/index.php?topic=63546.0

 

[fallsroad]

Quote:

Yeahhh like the HiFace for example and as you ve said they arent cheap. In other threads the digital interface by Audio gd or the v-link by music fidelity (http://www.head-fi.org/forum/thread/537080/musical-fidelity-v-link-usb-spdif) were also recommended but there are a lot of other solutions. At least it has to be capable of playing almost all formats.
 
Personally I am using the Thingee (Blue Circle Audio) beside the HiFace as a D/D converter even though the Thingee is like a passthrough only and doesnt upsamle.
 
I am in the lucky circumstance that I nearly only have 16/44.1 files.
 
It would be really good when you can post the reply of Realtek.

If I hear from Realtek or Asus on this, I will post the reply.

Before spending for a USB to SPDIF converter, I'll wait to see if I can track down the correct PCI module for the internal SPDIF header, and try the coax. Seems the next step, short of a driver problem or other issue that eludes me right now.

Another alternative is to find an audio card that supports all the usual formats including 88.2, and passes the native bit depth and sampling rate of the file through to a digital out (I actually prefer Toslink at this point - it solved a minor, but annoying ground loop problem I had previously) and on to my DAC.

Thing is, I know nothing of sound cards any longer, having used on board for many years now.
 

 

[fallsroad]

Quote:

Probably a driver issue: http://yabb.jriver.com/interact/index.php?topic=63546.0

 
 
Thanks for the link.
 
I'm beginning to think this is the case.
 
I'd still like to find that module just to confirm.
 

 

[Wildstar]

Alternatively, maybe as a stop-gap measure, you can use the SoX resampler for foobar2k.
I use the 'mod' version, where you can specify a list of sampling freqs you want to exclude from conversion.

 

[fallsroad]

Quote:

Alternatively, maybe as a stop-gap measure, you can use the SoX resampler for foobar2k.
I use the 'mod' version, where you can specify a list of sampling freqs you want to exclude from conversion.

Thanks for the link. I'll give this a try as I see how other things shake out.
 
Install like any other Foobar plug in?
 
 
 
 

 

[Wildstar]

Yeah, just put the .dll in the components folder (I'm not sure if it is different in Win7).

 

[fallsroad]

This is definitely a driver issue.
 
Asus had nothing to say but to offer me an RMA. The board isn't broken, so that's a giant waste of time and money.
 
Realtek has not responded to any of my inquiries. They did recently release version R2.60 drivers for their HD Audio codecs, so I dutifully installed it hoping they might have included a fix for limiting their own hardware.
 
During the installation the old driver is uninstalled, the computer must be rebooted, then the new driver is installed.
 
During the restart process I got the little windows notification about New Hardware, driver is being installed. Not paying attention I opened the properties from the generic Windows sound icon in the tray, and lo and behold, 88.2kHz was now an option.
 
Hooray!
 
Then the Realtek installer popped up, automatically finished the driver install, and upon reboot the 88.2 option was gone.
 
IOW, the generic Windows driver recognizes the hardware capability, but Realtek's own driver intentionally disables one of its output modes.
 
The Realtek driver includes all the EQ and sound effects software, but I'm not sure I need that, so I uninstalled all audio drivers and let Windows install its own driver a 2nd time, and now I have 88.2kHz playback capability.
 
I just don't get why a manufacturer would disable a mode advertised as a feature of their product.
 
 

 

[Wildstar]

I just don't get why a manufacturer would disable a mode advertised as a feature of their product.
 

Could be due to system instability (beware of bluescreens), hardware faults or plain lack of testing.
 
 

 

[hohum]

I vaguely remember them removing the 88200Hz option around the time Windows 7 appeared, at which point it was removed from all newer driver versions aswell. I assume it's certification related. R2.25 was the first WHQL W7 driver according to the changelog, so perhaps it's from that point onwards.

 

[fallsroad]

Quote:

Could be due to system instability (beware of bluescreens), hardware faults or plain lack of testing.
 
 

Nothing like that has occurred. 88.2 play without difficulty.
 
If any of those problems are the case they should update the features list for the codec and remove 88.2 capability. A lot more high resolution audio content is becoming available at that sampling rate. If their hardware or drivers really are unstable, they should stop advertising it is a capability you get when you buy a motherboard with the ALC892 on it.

 

[wnmnkh]

Quote:

This is definitely a driver issue.
 
Asus had nothing to say but to offer me an RMA. The board isn't broken, so that's a giant waste of time and money.
 
Realtek has not responded to any of my inquiries. They did recently release version R2.60 drivers for their HD Audio codecs, so I dutifully installed it hoping they might have included a fix for limiting their own hardware.
 
During the installation the old driver is uninstalled, the computer must be rebooted, then the new driver is installed.
 
During the restart process I got the little windows notification about New Hardware, driver is being installed. Not paying attention I opened the properties from the generic Windows sound icon in the tray, and lo and behold, 88.2kHz was now an option.
 
Hooray!
 
Then the Realtek installer popped up, automatically finished the driver install, and upon reboot the 88.2 option was gone.
 
IOW, the generic Windows driver recognizes the hardware capability, but Realtek's own driver intentionally disables one of its output modes.
 
The Realtek driver includes all the EQ and sound effects software, but I'm not sure I need that, so I uninstalled all audio drivers and let Windows install its own driver a 2nd time, and now I have 88.2kHz playback capability.
 
I just don't get why a manufacturer would disable a mode advertised as a feature of their product.
 
 

 
Thank you for this information. My new computer refused to send 88.2 signal. I uninstalled the Realtek driver and forced the windows to use its default driver and it worked.

 

[rhuarc76]

I did try it to uninstalling the realtek drivers and indeed the default Microsoft driver gives an 88.2 kHz option. However when I use foobar2000 with the wasapi driver to playback a 88.2 kHz file (which it was first refusing todo) my receiver is reporting 96 kHz so it seems like the Microsoft driver is doing a sample rate conversion.

 

[sorata98]

I also uninstalled Realtek Driver and let windows intall its generic one, and it's working great! But I also noticed that now the SPDIF output light is always on (the red light). Have this happened to any of you? Could this eventually affect the output?
 

 

[Roseval]

 I noticed this too.
The win driver doesn’t mute the SPDIF but sends ‘silence’
I do think this an asset as the receiver keeps the lock on the incoming SPDIF.
Some receivers are slow in getting the lock so you might miss the first part of the audio.