XXHighEnd

Hi Peter!

I`m ready to test W10 build 10586 with XX 2.04
But it is not posible to play music, i get this message:
Failed to set sample rate

The settings are the same as yours with XX 2.03, that has been working fine here with XX 2.03

Tore

Tore !

... I have no idea and I'm afraid I can only point you to the obvious things like "did you select the proper sound device" ... but it is really toooo obvious.

Which 10586 version do you have there ? So 10586.xx ... ?

Peter

I was just thinking ... :yes:
Maybe it matters when you set the Buffer Size of the NOS1 Control Panel to 4ms.

Otherwise I vaguely recall that the message can occur when the SFS is set too low - but in some rare occasion. And do notice that 10586 can't have an as low SFS as W8 or 10074; 0.20 is doable though.

Peter

As it happens I had this error yesterday.

I  normally play without upsampling in XXHE, ie slider fully left. Mostly I play 44K but yesterday I put a 96K recording in playlist and got the Failed to set sample rate error. I could see it set the output sample rate to 48K. Moved upsampling slider one step to right and it played OK, 96K in and 96K out.

Its a while since I've played any hires recordings but I think in earlier versions of XXHE it worked OK without needing to manually set the slider.

Colin

Peter,

W10 is build 10586,36
Buffer Size of the NOS1 Control Panel is always 4ms here
It does not help with higher SFS


Tore

Colin, that depends on the input possibilities of your DAC. For example, it if can take 96KHz only and you put in 96KHz and upsample that 2x, then the output to your DAC will be 192KHz. And not it can't take that for input (that assumed).

Use the fx button (engage) to actually set the output rate fixed instead of the number of upsampling times. Well, sort of as it is always hard to explain. Play with it and you will see.

Regards,
Peter

Tore,

It is not coincidentally what Colin is talking about ? that you put in a Hires which doesn't take 16x upsampling for your poor DAC ? (haha)

Is the Driver running properly ? The NOS1 Control Panel must show in the bottom "Streaming is up and running". Maybe it isn't ?

Peter

Streaming is up and running,
and the sound device is the right one

Tore

Happy New Year!   :NY02:

I have to go out now!


Tore

Happy New Year, Tore !

I think I may know the reason :
You went to MinOs and only there connected your NOS1a for the first time. That would be the typical situation that all seems fine whatever you look at, but still no sound is produced. In that case, boot into Normal OS (NOS1a connected), try it, and go back to MinOS after that.

Regards,
Peter

First time i tested was in Normal OS: failed to set sample rate
Then i was testing in MinOS: Same result
Back to NormalOS: Same result

And there is nothing on desktop, i have to reboot to get desktop back.
(cntr-alt-delete to find the restart)


Tore

Then I don't know ... sorry ...
So I have to assume it is your 10586.36.

Keep in mind : 10586.0 is the one wich works. All of the others I can't know, unless someone tells about it.

Peter

Maybe Uninstalling and Reinstalling the Driver helps ?

YES, that helped!  Everything is OK now.

Thanks Peter!


Tore

Not here though... I am still running into similar problems with the 1.04b driver.

But only when trying to play unattended.

I can see the driver (opened panel) switching between sample rates which correct visible while playing attended but not when playing unattended. The error message come up...

The panel sticks to 96.000 or 88.200 depending on the track (wav, flac, MP3 all the same)

At some point XX didn't start anymore, at all.

Turned the PC off (reboot didn't do anything useful) resulting in huge BANG :o through the speakers and again while booting...

Good to know that my speakers can handle such spikes well, a lot better than me!  :heat:

It did do the trick though... all seems to work normal now?

Next update will be for the long future, hopefully 10586.0 will stick for a very long time!

Now let's see what the Intona will bring when it has arrived and burned in properly.

Bert

Bert, of course that didn't do any tricks. All you implied was DC Offset by switching off the PC and which can happen always, can happen for everybody, and always happened when it liked to. For years.
Nothing special in your situation. Oh, possibly you implied a new situation for yourself (as in : not used to) because of the Intona, which isolates (obviously). That can matter. :yes:

The driver seemingly behaving strange right after install is a Windows 10 thing, as Windows 10 is a no-THING (especially when it is about drivers).
But this is all very well known (by now).

Eh, happy listening ?
Peter

Haven't heard this for a very long time... since W10074?


There was nothing changed here besides the Windows update and its related errors during the installation and configuration of XX...

One thing did change directly after the BANG though... the music sounds a whole lot more real now! Not after the update itself where the sound was as used before so there must have been something disturbing... or the system woke up suddenly?


Starting...  :)

Bert

EDIT: There is no Intona in the system here (has not been delivered yet)

Ah, ok.

Bert, usually you can see (hear) the tick or bang coming for the next boot, because it announces itself at the shut down (DC going the wrong direction). That usually is a harmless tick. So when you hear that happening, switch off the speakers until the boot is accomplished (and DC goes back to zero). And easy to check (my story) because the DC Offset will show "off" in the DAC ...

Peter

That is what I am used to have not a big BANG...

DC is stable, every time I checked but perhaps this time it wasn't?

No problem anymore, the harmless tick is back again.  ;)

Bert