XXHighEnd

First of all, XXHighEnd 2.11a is the best music software so far.

I am running into a problem. I have not yet activated but XXHighEnd always shut down by itself and pop up the message:

"ActiveX Control "....." cannot be instantiated because the current thread is not in a single-threaded apartment."

I am using Windows Server 2019 Core mode with AO3.

Your response will be highly appreciated.

Hey there vhs,

Well, not that I knew about this error, but it will only occur because of the demo version "quitting". So between 6 minutes and 30 minutes or so, the demo version shuts down automatically, and apparently there something goes wrong now. But it would have quitted anyway ...

Thank you very much for mentioning this and of course I am going to look into it !
Peter

Thx Peter

I guess I find the culprit of that ActiveX error message.

As I am using dual Xeon Scalable 4214 (12cores) of my music server, I adjusted the CPU Affinities of "XXHighEnd.exe" & "XXEngine3.exe" to Core 24-47, which were 12 cores in total.

After I readjusted the CPU Affinities of the above two processes to Core 24-43, which were 10 cores in total, ActiveX error message had never popped up again.

Cheers.

 

Interesting ...

I don't think you can tweak like that because XXHighEnd does similar itself. Additionally I never took into account 2 processors in the sense of the total core count emerging by that. I mean, 12 + 12 would be 24 and 24 cores are not supported as far as I recall (I could look into the program - haha). So for example, 12 would be supported, 16 would be, 20 would be, 28 would be, 32 would be, 40 would be. But not 24 because I never saw a(n interesting) processor with 24 cores.
I would not think that things error out because of this (but apparently it can ?) but at least SQ would not be as intended (processor tasks would overlap / be mixed while all should be dedicated (no taskswitching implied)).


I think it is good to know (as said) that XXHighEnd does these things itself, and that possibly this implies anomaly because of the two levels this now occurs. Thus, you do this by means of TaskManager, and XXHighEnd does this internally. I'd say this will overrule but ... how will this unroll the stack ? Think of you quitting XXHighEnd and all nicely being undone (this really is so). But if XXHighEnd bails out because of demo-end time, then I am not so sure. It could be a too hard-quit falling back to ? ... Your settings ? ... I just never thought about this. And thus :

Interesting ...


PS: And thinking some more ... The Demo version does not allow explicit Core Appointment (see the according field in Settings for that), BUT one scenario is set anyway. It can well be that at "bailing out" this is not sufficiently taken into account. "If Demo then Don't reset Appointments because no User Settings applied". And this all in the midst of quitting playback right where it is (doing its job), which is different from you stopping playback where all is reset (mind you, for the whole system, not only the two XX executables). So yea, the bailing out with playback going on may not do even anything about resetting Affinities ... (call that a bug).

Thx Peter for your explanation.

Yes it is indeed interesting.

I am using Process Lasso (PL) as well......

Without using PL to force the CPU affinities of "XXHighEnd.exe" & "XXEngine3.exe", these two processes will be automatically assigned to CPU 2-39 and CPU 0-1, respectively.

Cheers

@vhs

Looks to me you are coming from JPlay environment. For your info, licensed XXHE will do all Windows optimizations (probably more) without need of Process Lasso (PL), Audiophile Optimizer (AO) and Fidelizer Pro (FP). Simply press 'Minimize OS' and XXHE will do all that is needed for perfect PC audio reproduction. Server 2019 is variation of W10 where some services/processes are not activated. If I remember well, even Kernel Streaming is not started or even not installed at all.

Brgds,
George

Thx George

I used HQP and Jriver in WS2019 Core mode with AO3 & PL.

Currently I am auditing XXHighEnd, IMHO, it is better than HQP (with or without upsampling) and Jriver......

I am going to get the license of XXHighEnd within a couple of days.....

Cheers

Hi there George - thank you.
Kernel streaming surely is installed. Without that no sound.
You probably were thinking of WASAPI.

Kind regards,
Peter

Hi Peter,
No, it was problem with KS on WServer 2019 Core mode installation however it seems to be one of options in Audiophile Optimizer: 'to install Kernel Streaming and Media Player Support or not'. Never tried AO myself but read abt KS problem on another forum :smile:. Sure, without KS @vhs would not have sound at all :smile:

Hi George,

Yes.. there is an option in AO to install KS in ws2019 core mode....... but I choose not to install.....I am using dCS ASIO as output....for Jriver and HQP

btw, I activated XXHighEnd last nite...and thank you so much for Peter's prompt response.....

XXHighEnd is the best music software in Windows environment I have ever used so far....


Cheers