XXHighEnd

Just to share an experience with possible sq benefits.

I was in search of a solution to usb3 related dropouts and fiddled around with processorscemes and playbackpriorities. This afternoon after a fresh boot i found myself having better than usual sq, but no special setting occurred to me. Another break-in leap of the NOS?

It occurred to me that the processorloading also was different than usual with a single sfs loading peak in the second core, where it is usually in the first core with the driver (as long as that lasts). Running again through the settings I discovered that I left 'Not Switch during Playback' in the processorsettings on. Disabling this feature restored the processor loading and warped me back in sq. Sq returned after putting it back on.

Oh and even the sfs peak is now distrubuted over all cores it still sounds -imho much- better with the setting on than off...

Maybe this does something for your sq too.

Happy listening,

Regards, Coen

Thanks Coen. I think I made this for people with drop out problems, but I wonder whether I ever anounced that it is in there. At least I never used it myself.

It is not completely clear to me how the "SFS peaks" did not spread, then did, and then stayed after switching back. Can you please elaborate a bit ?

Thanks,
Peter

Peter,

When I start with playing Wavs, the peak stays in one core. The PC has to have some extra load when starting a new track to "spread" the peak. A shure bet for switching over to all cores is playing a FLAC file. There are other causes too.
After this switch all cores remain active on SFS peaks (no revert to single core peaks).

I attatched two recent screendumps of my processorload (note: "not switch during playback" is on otherwise the peak would have been in the first core).

Something that caught my eye was that at the loading of the very first track after a reboot, the first peak is in the first core. Next ones are in the second core.

I like the sound best when spread over all cores (shortest duration of the peak, but at 100% cpu).

Does this help?

regards, Coen

Hi Coen - Yes, I understand now.
Btw, it is a known phenomenon that at a first activity things are different. But looking at your description I'd almost say that this must be a problem on my side ...

Peter

I've been experimenting a lot with xx settings to get a better grasp on what they do to the sound of my system.

Being back on engine 3 with considerably lower sfs, I found a very nice sounding combination, still with the abovementioned 'Not switch during playback' feature on.
What immediately occurred to me was that the sfs peak in the first core was very low and that the processor load indicated something like 58% on the sfs peaks. With the 'not switch...' feature disabled, the peaks are back on 100% again, that is a max peak in all cores.
Also the sound changes from focussed and clear to warm and fuzzier. I tend to prefer the first (with the feature on).

Imho this is an important feature for sq, at least on my system.

Regards, Coen

Aha ... And so customers start to know more than me.
If you would have kept it a secret of course, of which I'm glad you didn't. :)

But I can imagine we just don't know this, because first everybody started to use KS instead of WASAPI, and only then the SFS was introduced. Let alone that someone ever tried that "not switch" feature, of which I hardly know myself it is in there. Hmm ...
(but I have it on ("not switch") since you mentioned it)

Thanks !
Peter

Hi Coen,

I am also seeing the same effect on the CPU as you have. However I havent been able to notice a difference in SQ in my system at least.

In any case I am keeping this feature switched on, less load on the CPU anyway.

Arvind

Hi Arvind,

Thank you for trying. Not hearing a difference is valuable information as well!

regards, Coen