W10 strange driver behavior

[michaeljeger]

Not sure if the title really describes what is going on.
So I installed W10 and 2.02 and all seems to work.

However, when I boot up windows before I start XXHighend the first time after reboot, Windows does not recognize the NOS1a at all.
In the control panel I see the device but the sampling rate is changing randomly 2-3 times per second.
Then when I start XXHighend and try to play something for the first time after reboot, I might get the error "Cannot set sampling rate". It usually takes 2-3 tries until I get playback.
After that, Windows also recoginzes the NOS1a and this crazy ample rate switching stops even if I quit XXHighend.

Anyone observed the same behavior?
I tried both drivers 1.04 and 1.03, no difference.

Thanks, Michael

[Gerard]

Yeh i have the same problem  sometimes. 

[PeterSt]

Hi Michael,

Which W10 build are you using ?

Regards,
Peter

[michaeljeger]

Hi Peter

I just installed the recommended build 10074 (German version 64bit).

Regards, Michael

[PeterSt]

In that case ... I don't know.

I can (very far away) imagine something like first installing 1.03 (which will install but isn't officially made for the job I'd say) and after that you install 1.04 (which avoids all officialities (the Signing)). In combination now it is W10 which messes up because it is *known* to not support any driver yet, actually.

But if this scenario is to lead to something, then Gerard must have installed 1.03 at first as well.
I sure did not and I also never saw the problem. That is, I am not going to look after a boot whether the NOS1a is recognized, but at least I never saw a problem with Playback not working unless attempted several times etc. It just works fine over here ...

Peter

[Gerard]

My attempt was first the 1.04 driver version but after that 1.03.

[michaeljeger]

I also tried 1.04 first and then when this strange sample rate changing occurred, I installed 1.03.

But 1.03 did not help to solve that.

Best, Michael

[PeterSt]

It looks like we are lucky that it works in the first place ?

Most heard complaint about Windows 10 is "no sound".

Ok, thanks,
Peter

[BertD]

It just works fine over here ...

I have installed 1.04 from the beginning and everything is fine here as well (so far).

Bert

[Scroobius]

As posted before I cannot install driver 1.04 and in 3 times I have installed W10 (different disks each time) I tried to load 1.04 before 1.03. I use 1.03 which works fine - I don't (except maybe some odd stuff have 48KHz material).

I also tried 1.04 first and then when this strange sample rate changing occurred, I installed 1.03.

But 1.03 did not help to solve that.

The first two times I installed 1.03 I had the same problem Michael had where the speaker symbol on the taskbar flickers and when you open the XX Nos driver panel the sample rate is randomly varying between different sample rates. But that has not happened on the last install so no problem now.

Paul

[PeterSt]

Hi Paul,

I use 1.03 which works fine - I don't (except maybe some odd stuff have 48KHz material).

So you don't.
Okay. Ehm ... what ?
use ?

And if so, what about that Driver103.tss ?



Peter

[michaeljeger]

Paul, what do you mean with the "last install"?
Did you do several Win10 installs?

Regards, Michael

[Scroobius]

And if so, what about that Driver103.tss ?

eerrmm!!! well yes I did make that change but I assumed it was to do with the varying sample rate problem - particularly as that problem disappeared after I made the change. I just checked and all sample rates play fine.

So no problem!!!!

[Scroobius]

Paul, what do you mean with the "last install"?
Did you do several Win10 installs?

Yes I wont bore you with the details but involved problems with hardware including a DVD writer that turned out to be failing and is now in the bin. Anyway everything is OK now.

Paul

[michaeljeger]

Well the problem for me only occurs after a reboot.
Once XXHighEnd is running and playing, the sample rate problem is solved until the next reboot.

Michael

[PeterSt]

Michael,

This switching can happen in different scenarios. The only scenario I can think of is that the switching happens between the last set (previous boot session) sampling rate for the base oscillator (44.1 / 48) and the other one. Uhm, an example will be more clear : Like you see it switching between 352800 and 384000 only and nothing else.

Is this so, or do you see something else ("random" is also an answer).

Thanks,
Peter

[Scroobius]

Like you see it switching between 352800 and 384000 only and nothing else.

Is this so, or do you see something else ("random" is also an answer).

Random would best describe what happened for me - "flickering" between different speeds - but the flickering was fast so not easy to see which speeds but looked like quite a few for sure 44.1 was one of them. Also and perhaps understandably that seemed to give rise to error messages as XX would not always start up. But after a few attempts XX would run OK and then and thereafter the flickering stopped until the next reboot.

[BertD]

Perhaps 2ms for the driver in combination with your PC is a bit too fast?

Perhaps not related though... 

Bert

[PeterSt]

Maybe this is off topic, maybe not, but I just rebooted (into Normal OS) anyway, so I thought to have a look, XXHighEnd never fired up for this session. All normal.
Well, not all, because the 16ms of buffer where the driver install defaulted to (I reported about that) - and which was set to 4ms by me back at the time ... now is at 16ms again ?

Peter

[CoenP]

Hi,

I've got the same driver "problems" here. Installed the old 1.03 first on win10 10074 and ran into the next things with an unactivated v2.02:

1) driver does not see the NOS1a after the driver installation reboot, another reboot is nesseccary to see the dac in the driver control panel. Actually i dont know if this is installation related since I ran into this twice.

2) first play after executing xxhe2.02 gives a "buffer overflow" error, restart the track and everything plays fine

3)  saw the flipping of the samplerate, but no big deal to me

4) the nos 1.04 driver will not install. "Preparation failed" error no matter what I try.

Probably all known stuff, just sharing to provide support for the courageous that dare to wander onto the win10 path.

Greets, Coen

[michaeljeger]

One thing I want to add here using Windows 10.

The only player that is working is XXHighEnd.

The windows sound does not work at all.

When I go to the sound settings in Windows, I cannot play any sound.

Sound currently works in XXHighend but nowhere else.

Regards, Michael

[PeterSt]

Coen, did you apply that (not) Driver Signing stuff ?

Peter

[CoenP]

Coen, did you apply that (not) Driver Signing stuff ?

Peter

Hi Peter,

I don't think so. The instructions say that you may have to do something, but I cannot figure out what. Googleing did not bring any useful answers.

regards, Coen

[PeterSt]

Hi Coen,

Go to the Release Notes of 2.00 :
XXHighEnd Model 2.00 - New Filters & Extended Remote Control
and in there use ctrl-f to search for :
Driver

I am not 100% confident that it will still work when you first tried without this. So please let me know.

Regards.
Peter

[JohanZ]

Hi Peter,
After reading Coens problem with installing the new driver and Driver assigning stuff, I did an atemp to asign the new driver. Now i have some big problems! No sound and installation problems with this new driver. All was working ok. All the time great sound and latest driver was working ok. It was an atemp to fix this signing stuff. I did this installation in minimized os. Probably this was wrong....Now i have problems to get out minimized os. ...first i have to make a dinner...and read the manual......grrrrrr

Regards Johan

[CoenP]

Thanks Peter,

Changing to "Drivers need not be signed"  via XXHighEnd settings (and not Windows 10 settings...  ) with a reboot in NORMAL OS mode allowed the 1.04 version to install.

I feel sorry for Johan, but hey it could have very well been me not noticing MinOS. I hope you will be able to solve it without a reinstallation of WIN10.

regards, Coen

[JohanZ]

Hi Coen,
Finally i succeeded to reboot in normal mode and reinstalled the 1.04 driver. So xxhe is working with sound.

Regards johan

[PeterSt]

but hey it could have very well been me not noticing MinOS.

Haha Coen, yes, that happened to me quite a number of times.

Good that it is all working for you both, now.

Regards,
Peter

[PeterSt]

...first i have to make a dinner...

That's what I need to do as well quite often.

and read the manual......grrrrrr

Even that ...

[JohanZ]

......grrrrrr

[CoenP]

Hmmm,

Started the PC and no NOS1a in the driver panel appeared. Rebooted and it appeared again.
Saw the sample rate moving along all rates in a loop.
After starting XX and playing a track and the error message "failed to set sample rate" appeared. After two tries the music started playing. Imho this is about "catching" the right sample rate in the loop.

Now the music played, but shoot me I think it sounded pretty cr*p compared to the other day. Also later in the track there seem to be hiccups in the music. I also saw some kernel streaming errors.

I reinstalled the 1.04 driver, rebooted and the driver showed the last sample rate without looping to others sample rate. Sound seems still improvable and I experienced some hiccups (and errors). I wonder what happens in one of the next boots.

regards, Coen

p.s. the was in normal OS mode still.

 

[christoffe]

Hi Coen,

a couple of weeks ago I tried W10-10074 and installed the driver 1.03 and faced the same problem ( sample rate moving along all rates in a loop and never stops). The installation of 1.04 failed on that build.

With build 10240 the driver 1.04 installation suceeded and is  stable as a rock.

Joachim

[michaeljeger]

I installed the 1.04 driver as well.
However, the samplerate cycling persists until I start playback in XXHighend.
Sometimes playback needs to be restarted several times until things work.

Also as mentioned before, Windows sound does not work with either driver, so for the time being, XXHighend is the only player I can use under Windows 10 (build 10074).

Hopefully, we all soon know if the current Win10 build is also as good in SQ as the 10074 build so we can potentially switch to a regular Win10 version.

 

[CoenP]

thanks for the replies,

I just booted again and no NOS1 present in the driver panel. Replugging the USB does not make a difference.

Does this all work when at Min OS?

regards, Coen

[PeterSt]

Coen, did you "re-mangle" with that Driver Signing field ?
What is the status of it now ? ONLY APPLY THE REFRESH (go further and you will be changing the status at the next reboot).

Take it that if you don't have this reliably working in Normal OS that I don't see how it will work for the better in MinOS.
But then I don't have problems with it anyway (and by now I did quite some installs (different PC's and different NOS1a's)).

Let me know.
Peter

[CoenP]

Hi Peter,

No messing around with the "driver needs not be signed". I wouldn't dare!

Rebooted four times just only checking if the NOS1 was in the panel. NOS1 was there each time. I also did a reboot after playing some tracks in XXHE, no problem either.

Much better SQ returned so this was no imagination.

Don't know what causes the NOS1 not to appear in the panel or mess with the sound, let's hope it stays this way. Maybe my previous installs of 1.03 and 1.04 messed the OS up under the hood or something. Whatever.

regards, Coen

[HaraldN]

Hi Coen,

a couple of weeks ago I tried W10-10074 and installed the driver 1.03 and faced the same problem ( sample rate moving along all rates in a loop and never stops). The installation of 1.04 failed on that build.

With build 10240 the driver 1.04 installation suceeded and is  stable as a rock.

Joachim

Hmmm,

Started the PC and no NOS1a in the driver panel appeared. Rebooted and it appeared again.
Saw the sample rate moving along all rates in a loop.
After starting XX and playing a track and the error message "failed to set sample rate" appeared. After two tries the music started playing. Imho this is about "catching" the right sample rate in the loop.

Now the music played, but shoot me I think it sounded pretty cr*p compared to the other day. Also later in the track there seem to be hiccups in the music. I also saw some kernel streaming errors.

regards, Coen

p.s. the was in normal OS mode still.

I faced the same problem then i installed Win10 - 10074.
My solution:  Onboard HD Audio must be enabled in bios during installation of Win10 - 10074.

I first installed 10074 with Onboard HD Audio disabled in bios. No audio driver active. After installing the Phasure usb-driver I got the same problems as quoted above.

After several attempts i tried to enable the Onboard HD Audio in the bios. I then installed 10074. Standard audio drivers  for audio was automatically installed. After this i installed the Phasure usb-driver and all worked fine.

Maybe there must be an audiodriver up and working in 10074 before the Phasure USB-driver can be properly installed?

Harald

[PeterSt]

Hey Harald,

Very coincidentally I just saw this happening myself at someone's PC;

So you see this "looping" and when you next choose a(nother) buffer size, it stops and all is fine.

Peter

[acg]

Hey Harald,

Very coincidentally I just saw this happening myself at someone's PC;

So you see this "looping" and when you next choose a(nother) buffer size, it stops and all is fine.

Peter

For me I it stopped when I went into MinOS.  Drove me half nuts before then...but I had not turned off driver signing for that installation so perhaps that had something to do with it as well.

[PeterSt]

In the particular case I just experienced, Driver Signing was Off.

One thing to be complete : I reinstalled the Driver because it had stopped working (Streaming prepared but Not Running). And then I experienced this behavior (after replugging the NOS1a).

This was NormalOS and W10-10565.

Peter