XXHighEnd

Yesterday I conected different USB DAC (with different USB design) & when I started play I got message 'asked for clock resolution wasn't met, asked for 15ms, received 0.5ms. OK'd message & play started. Went back to my original DAC and got same problem, whereas previously I could select any clock resolution, now the only selected resolution that does not give the message is 0.5ms.

1.186 W7

Colin,

You will be running some other program that demands a higher resolution. The highest rules.

Let me know if you have no clue.
Peter

Problem was the Centrance driver for the USB DAC http://centrance.com/downloads/ud/

It only works at 0.5ms clock resolution but even when centrance not in memory and different dac connected 0.5ms remains only option, so I think some W7 setting has been made.

Although clicking OK to 'asked for clock resolution wasn't met, asked for 15ms, received 0.5ms' message gets music playing it does not change the value in Settings. So to get back to having the resolution options I select 0.5ms in Settings then close XXHE & reboot. Then I can change resolution to desired value again.

Hope this makes sense.

Colin,

If all is right it can't happen that "something" just sets the Resolution, bails out, and it stays like that. IOW, you just didn't find the "program" doing this.

Question in between : Are you using Minimized OS for this ? And, with Unattended Playback ? If so, I'd say this can't happen, unless something very persistent is in there that won't get killed. This could be tough to observe, because the assignment of the Clock Resolution could be in advance of killing the processes and all.

Otherwise, not only look for processes but also for services.

Notice : In Minimized OS and all shut off, you will find something like 4 services only (when in Unattended Playback), so this makes life more easy. -> Not quite 4 because when you are observing it (TaskManager) another bunch start again. Processes will be around 17.

Peter