Output Device keeps changing

[hbrew]

Output Devices in list: Primary Sound Driver, KS:ASUSVAD Wave,  and KS: AMANERO TECHNOLOGY STREAMING.

Used 0.9z-9b until installing 1.186a. I always use minimized OS.

When I select play (unattended or not) it will change from Amanero to the ASUS device and then a couple messages come up. I change to Amanero and it plays. It also does this when I choose next in either mode - Alt-N or the next button in attended mode. It happened on 0.9z-9b but seems more often with 1.186a.

Three days ago I installed the Ramdisk but it was happening before that.

I recently tried different core appointment schemes so thought that may be the cause of more frequent problems. I was using 1-2 for a long time then tried the others and was on 3-5. So I went back to 1-2 -- still happens but perhaps less often when play is pressed still occurs with Alt-N and next button.

In Control Panel I found the ASUS device where I hadn't looked before and disabled it and it dropped from the list. I haven't found where the "Primary Sound Driver" can be disabled. In my HP it was easy to find with Beats or a HP setup.
 
I'm hoping that having only one choice will stop changing the output device (and doesn't select no driver at all).
Will try one more thing: select another field so the last wasn't the output device and see if ALT-N still changes it.

That is where I am (or was) at with this. I saw that other people had similar issues but I didn't see a solution.

Peter's suggestion (elsewhere) to eliminate (disabled when I was in doubt) unnecessary processes/programs seemed to solve these problems. Alt-N works in unattended mode now and was previously consistently deselecting my Amanero device. I've only hit play about four times or so but it was doing this fairly consistently. Eliminating these processes also allowed me to select a clock resolution other than 1ms (can now select 15). This was on Core Scheme of 3-5 that I was using earlier with this problem. So it looks good now. Thanks Peter!

[PeterSt]

For a Kernel Streaming device you'd need to Disable the device in Device Management. That will work.

The fact that it happens is not good. And, taking it that it really changes after you press play (and not when XXHighEnd comes up from Unattended), something should be seriously not right in your PC. But, it is hard to tell what as I ever heard of such a thing.

What you can do for a start is switch on logging (at the bottom in Settings) and cause it to happen. When it happened, grab the newest X3PB log file from the TemporaryData sub folder to your XX folder and post that (as attachment). With that, tell me which device was selected according to you (hence which should play) and which one started playing (should be obvious but by the time I see it maybe nothing is obvious to me).

If your SFS is really low (like under 1) I wouldn't use logging at the same time of playing (can be too hard to cope with) and otherwise notice that the logging influences SQ.

Regards,
Peter

[PeterSt]

I see this in your sig :

(cannot select higher clock);

I suppose you get a message from XXHighEnd similar to "asked for is 5, received was 1.xxx" ?
If so, it is an indication that you have something running in your system which shouldn't. Now suppose this is audio related ... (what about Fidelizer). Possibly it is the cause of today's subject ...

Background info :
Nothing (nothing !) should be hogging the Clock Resolution unless it is actively doing something at the moment (the playback of XXHighEnd is an example). So when something is just sitting there (like a Driver) and it hogs the Clock Resolution (setting) then it is actually destructive (something else now can't use it for the whatever purpose).

If I were you I'd find the cause of this and eliminate it. Or tell me what it is first then we can always see further.
If you have no clue, start with programs / processes which look like "monitoring" processes.

Peter

[acg]

I had this device constantly changing problem on my first install of w10074.  I think that the problem was caused then because I installed the DAC driver (nos1) before I installed XXHE.  When I did install XXHE the problem did not go away and I realised (thanks to Peter) that I had not set the "Require driver signing" checkbox in settings so that the driver did not require signing. As far as I could tell the only solution for me was a new os installation, then install XXHE then install the nos1 driver.  It worked anyway.

Not sure if this is exactly the same problem given different dacs, but perhaps the answer is to uninstall the DAC driver totally (perhaps including registry and other hidden settings), set that button in XXHE and then reinstall the DAC driver.  Might be worth a shot.

Anthony

[PeterSt]

Anthony - thanks.

That was my idea at first glance as well, but this is different - it is about devices changing. What we (NOS1 owners) can experience, is sampling rate changing within the one device.
Am I right ?

So since I now saw this myself at a customer's, this is about looping through all the sampling rate possibilities, continuously.
I will admit though that it looks mighty much the same ...

Peter

[AlainGr]

It happened to me a while ago (under Windows , but not sure about the XXHE version (maybe 1.186a ?). I disabled the other audio peripherals, leaving only the NOS1 in Control Panel.

Maybe a little radical, but...

Alain

[hbrew]

I see this in your sig :

(cannot select higher clock);

I suppose you get a message from XXHighEnd similar to "asked for is 5, received was 1.xxx" ?
If so, it is an indication that you have something running in your system which shouldn't. Now suppose this is audio related ... (what about Fidelizer). Possibly it is the cause of today's subject ...

Background info :
Nothing (nothing !) should be hogging the Clock Resolution unless it is actively doing something at the moment (the playback of XXHighEnd is an example). So when something is just sitting there (like a Driver) and it hogs the Clock Resolution (setting) then it is actually destructive (something else now can't use it for the whatever purpose).

If I were you I'd find the cause of this and eliminate it. Or tell me what it is first then we can always see further.
If you have no clue, start with programs / processes which look like "monitoring" processes.

Peter

Yes on the message and running processes. Disabled  three processes that were starting automatically that obviously weren't needed (Java Update for example) and was then able to select 15. Should have known better.  There are several Windows processes still running but left them. There are many showing stopped.
Thanks!