[Syan25]

How well do you find that the high impedance headphones at 600 ohms run on the D100? I still have mark 1 and I am thinking of buying a T1? What do you think?

 

[liamstrain]

I have no problems at all with my Beyer 880/600, and AKG Sextetts on the D100 Mk 1. 

 

[Syan25]

Sweet!

 

[Syan25]

BTW - DId you ever test the AES/EBU function? I am wondering if you had any comments on that? 

 

[liamstrain]

Nope - unfortunately, I have not. Not had any need for how I'm using it.

 

[punit]

Recently purchased a used D100 for my bedroom system. Very good value & sound for the money. Has a quite decent amp too.

 

[Soundsgoodtome]

Does anyone know where to get drivers for the MK1 D100? I want to update my drivers and possibly revert from a newer one that the computer picked up automatically via windows update. With the current driver (that says Yulong Audio) it only allows 44/48/96 in 24-bit. Doesn't go up to 88, 176, 192 nor does it do 16-bit, although that's less of a  problem. It used to when I first got the unit.

 

[Soundsgoodtome]

  Does anyone know where to get drivers for the MK1 D100? I want to update my drivers and possibly revert from a newer one that the computer picked up automatically via windows update. With the current driver (that says Yulong Audio) it only allows 44/48/96 in 24-bit. Doesn't go up to 88, 176, 192 nor does it do 16-bit, although that's less of a  problem. It used to when I first got the unit.

Bump! Anyone have an old driver handy for the MK1?

I think Yulong purposely supplied the latest Windows update drivers to cap the D100 MK1 so people would upgrade but that's just speculation.. If so, that's scandalous.

 

[project86]

No that's a limitation of the USB chipset in the device, not the driver. The Tenor chipset is showing it's age by now. A lot of people just use their playback software to convert the other hi res formats to 24/96.

 

[Soundsgoodtome]

Certainly something is up, even 16bit has been taken off the list of compatible rates.

I've only got 24 bit in 44/48/96 listed in compatibility under properties.

No that's a limitation of the USB chipset in the device, not the driver. The Tenor chipset is showing it's age by now. A lot of people just use their playback software to convert the other hi res formats to 24/96.

 

[project86]

Well that's odd. What happens if you try to play a standard 16/44.1 file? 

 

[Soundsgoodtome]

  Well that's odd. What happens if you try to play a standard 16/44.1 file? 

It plays it and the display shows 44.1 but I think Foobar is putting out 24-bit (under settings). I will try using Windows Media Player to play some 16/44 flacs tonight and get back to you.

 

[Soundsgoodtome]

  Well that's odd. What happens if you try to play a standard 16/44.1 file? 

Finally got around to messing with it. I changed the output of Foobar to run 16-bit and played 16/44 FLACs, I get a message it's unsupported. I think an older driver for the USB will fix this.. except I don't know where to get one tagged Yulong or maybe one that's for this USB chip?

 

[project86]

I lost the plot here - do you have the original D100 with the TI TAS1020B USB chip? Or the mkII with the Tenor TE7022 chip? Either way, it should work without drivers and should support 16 bit or 24 bit.

 

[Soundsgoodtome]

  I lost the plot here - do you have the original D100 with the TI TAS1020B USB chip? Or the mkII with the Tenor TE7022 chip? Either way, it should work without drivers and should support 16 bit or 24 bit.

I have the D100 MK1 with the TAS1020B. However drivers in sound properties (W7) only shows 24-bit in 44/48/88/96. Reason I think it's the drivers is because previously the Yulong had a different name or a generic USB chip under sound properties. After windows update or however Windows got the Yulong audio driver automatically, I'm only seeing 24bit and Foobar errors out when I change the output to 16-bit..?

Edit:
I just tried Spotify which should be in 16-bit but that utilizes Direct Sound. When using direct sound on Foobar, it does however work. So... my guess is the Wasapi is going off of the driver properties which is only showing 24-bit compatible and not 16-bit thus error when changing the output to 16-bit. The problem is in the driver not showing 16-bit as compatible..