XXHighEnd

Peter,

The other day I hooked up another USB DAC to my xxhighend win7 pc, to compare it to your nos1a.

I never succeeded in getting it to make any sounds, which was a bit of a disapppointment.

The real problem is, that the XXhighend drive has changed from "kernel streaming" to "pcmrenderer"

I have the distinct feeling that it sounds a lot less open, and as a side-effect, I can not use Jriver anymore to watch a movie, because it only "sees" the "kernel streaming" driver which isn't working anymore....

Any idea what I can do to fix this?

Thanks,

Henk

Henk, hmm ... no real idea at this moment ...

So you say that when you drop down the list of Audio Devices in XXHighEnd, no KS: device is visible any more ?

If that is what you say, what happens if you uninstall the driver, reboot (never mind if no question for reboot appears) and reinstall it ?

Let me know,
Peter

Hi Peter,

Yes, I do have a KS driver, so I have sound from xxhighend.

The thing is:
Up until last weekend the driver was called:
KS: Phasure NOS1 Out 4.0 [Kernel Streaming]

and now it is called (even before re-installing!):
KS: Phasure NOS1 Out 4.0 >> #pcmrenderer_01_04

The problem I have is that Jriver, which I use for watching movies, can only see:
KS: Phasure NOS1 Out 4.0 [Kernel Streaming]
So Jriver doesn't work anymore....

Off course I immediately tried re-installing the "Phasure_NOS1_v1.0.3_768_setupproduction" driver, but that didn't help.

As soon as the weather allows (it's too hot now) I'm going to try and reinstall Jriver, maybe then it will recognize the "pcmrenderer" driver?.

The question is though: How can this happen, and is there any difference between:
KS: Phasure NOS1 Out 4.0 [Kernel Streaming]
and
KS: Phasure NOS1 Out 4.0 >> #pcmrenderer_01_04

????

Henk,

By now I forgot a bit how, but since Windows 7 the name of the Driver as how the software (like XXHighEnd) sees it, can be changed by the user. This means that software can do it as well. And this latter implies (??) that this other DAC you tried might have changed it. That is, its driver.

A wild guess of course ...

And no, I never ever heard of such a thing.

Peter

Henk, I just looked, and when you choose the Properties of an audio device, you can just change the name of it in the first field. See below at the mouse pointer.

For a Kernel Streaming Device this would be the same, weren't it that they won't show up in this list with Audio Devices to begin with.
Read : you did not do that; software can have done it though.

I was just going to suggest to scan the Registry for this and change it back (tedious !! because it will be in MANY places). Then I though : what about going back to a Restore Point from the moment all was fine ?
That should work ...

Peter

Peter,

Thanks for the suggestions:)

I already did most of the stuff you suggested (except for the registry thing)

- I reinstalled Jriver. didn't help
- I went back to a previous restore point. I made a small mistake here, don't  remember exactly what I've done, but I had sound for a brief while.
- then I restored an older Jriver library, including settings.

I'm not exactly shure what fixed the problem, but now everything is fine.

Thanks again,

Henk

Henk,

You operate 2 pc's. With pc 1 (at your desk) you control pc 2 (audio pc) with remote desktop.
We discussed that you might put the music files on pc 1 (server) in stead of on the audio pc.

But why don't you use pc 1 for playing movies and keep the audio pc exclusively for music?

Maybe you told me already, but then I forgot  :dntknw:

Regards,
Stanley