Thank you very much, Colin.
I currently can not test that anymore because all has been realised / finished by now months ago. But because there's a huge make-over for the search engine for Tidal, I can not upgrade without finishing that. The mere point is : it is difficult to cope with the sh*t Tidal throws at us, because if they keep on changing, I better wait until they finished their changes (if ever).

Anecdotal : More than 10 years ago I stopped the support for Amazon (which was used for obtaining coverart) because they kept on changing things, leaving the developer with a week of work each 6 months or so. With Tidal it is worse because Tidal just "does" it without notification and without documentation. Unbelievable but true.
Modern times, I suppose.

Kind regards,
Peter

Seriously ?!
Wow, I don't think we ever payed attention to that. But we will from of now !

Thank you, Robert.
Peter

Yes, this surely (and obviously) makes a difference.
Very well found !

Peter

Hi Robert,


I assume you know that this is the maximum temperature before the processor will throttle down. If all is right, it should never reach that.


Not at all. It is made to be like that.

What you noticed about the first switch is correct; that is (indeed) for emergency, like being in the BIOS for a long time (that implies running at max) or just having all cool when you are not playing (theoretically it is better for the longevity). Using the switch (down) almost explicitly implies bad sound because of (electrical) oscillation of fans.

Best regards,
Peter

Hey Muni - Welcome then !
(finally ;-)

In the picture below I tried to catch all in one screenshot.
It starts with the F button (see where the mouse is). Next see the Filter Designer screen for what to select for "Low". Notice, however, that you ask for "8x" so probably you want to select the "Low" filter two lines down.

The 8x is set by the little slider you see left of the blue "352800". Prior to that, take care that this section of XXHighEnd is visible by means of the [1] button you see in the top; slide it sufficiently to the right.

I think that is all ! (if you have more questions, please open a new topic for it so we can find it back later more easily).
Your Lush^3 is due Tuesday.

Kind regards,
Peter

Paul, because in that case only, Services are shut down. As said, (try to) omit that and my guess is that it will be fine. Easy to try, but it starts in Normal OS mode to set it. And this with this notice that without changes at first, in Normal OS it may happen just the same. If it does, it is easier for you to test.
Please keep in mind that shutting off Services in Normal OS takes quite a while (1-2 minutes after pressing Play for Unattended).

If I'd know how to solve it, I would obviously do it right away.

Best regards,
Peter

PS: You said the fix is to restart XXHighEnd. Thus, Quit by crossing away and restart, right ? Could you try what you see below (when XXHighEnd already is on screen) ? Notice that this will need a real keyboard, but if it works, I can incorporate that in the XXOSK screen.

Hi Robert,

Not necessary to be alarmed because it will keep it under control. Btw notice that the means you use to observe the temperatures will let rise the temperatures just the same.

Point is : with the extra fan power (2nd switch) the sound may deteriorate a little. Will that be noticeable - maybe not. I have it down as well.
If you "mangled" with the other settings (set to 1 and set to 0) and you recognize it is since then, then I would restore those to how it was (they have fairly high impact).
See my settings below which are good to go.

The main culprit could be the Balanced Load set too high (see mine at 62), but notice that when you bring up XXHighEnd after playback, the normally cooling feature - never mind playing - will not be active. Thus, you may test all with XXHighEnd crossed away again (then cooling is again active) and leave it like that when not playing.
This way you can't see temperatures, but you might see the light not coming on now.

I have that light always in sight and I think it is a good habit.

Kind regards,
Peter

For your understanding ...

The sheer fact that you shut off services in the Audio PC may mean that the other PC (the one communicating over RDC to the Audio PC) is not able to detect the properties of the screen (size) at the other end correctly. This is the only thing which comes to my mind because indeed, XXHighEnd is obviously not running on that controlling PC.

I am pretty sure (no guarantee) that if you don't shut off services (the more the better the chance) that all stays in-tact. But what to do with that.
I can't tell how this could be made more comfortable for you because I don't see / have the problem. So what it seems to come down to is that with the help of Google you start to recognize your situation and from there may "tweak". Regarding that in itself ... it probably won't bring a solution because what XXHighEnd does in the Audio PC is a kind of killing the communication. This is intentional (better SQ).

Not using RDC is a kind of solution, but in the end probably not because it requires an active video card. This is present in the Mach III but (I'd say) for most it is not present at all and then the other "remote connection" means won't work.

Peter

What do you mean ?

Paul, to be honest I has a similar experience the other day. But I thought it was coincidence (I actually still think it was).

Peter

(yes, I must upload the "solved" search issues with Tidal, but one nasty thing holds back (plus the lack of time).)

Fr a program which runs on an OTHER PC ?
hahaha
No.
This has to be some compatibility issue between Windows versions. You know, such screens which warn you that something is out-dated ... (but which we all accept).

Please Google the issue and try to solve it. I can't do that myself ... (as I don't have the problem). I know the question seems odd, but ...

Peter

Thank you, Paul.

Interesting. Do you perhaps have any idea yourself what could be the difference between this laptop and the other PC's not showing the issue ? W10 version ?

... Which brings me to the oddity of you telling about the issue as you did all right - even showing it per photograph ... but this is your remote ! So this is not where XXHighEnd plays at all - right ?
This makes it a sort of RDC issue of which I am not sure whether it is under your control in the first place. Anyway, now knowing this, can you think further a bit ?

Also ... referring to the topic Anthony linked to ... are you used to seeing Scrollbars ? I don't mean "today" per se, but always before ? If Yes, it is a good indication that your settings of the RDC client (the remote) have never been right. But today it starts to bother because of (for example !) a not-equal resolution between the client and the host(-capabilities).

Regards,
Peter

Anthony, I now see that that topic ended in you not understanding something. Hence it never was worked out.

Please notice (Paul too) : This can only be about the DPI setting of Windows, as I never have any problem with this whatsoever, BUT I also never set that DPI setting different than 100%. Still all should be able to cope ...

Peter

Hmm ... Still it has been made such that all should be able to cope. So maybe at some stage something sneaked in that undermines it now.

Paul, or Anthony, can you give me a DPI (Windows) setting on one hand, and the Scale Factor of XXHighEnd on the other ?
Also, at which native resolution of the display is this ?

Best regards,
Peter