XXHighEnd

Ultimate Audio Playback => XXHighEnd Support => Topic started by: Andre on January 16, 2017, 02:15:38 pm



Title: Error message
Post by: Andre on January 16, 2017, 02:15:38 pm
Hello Peter!
I am trying out a demo version 2.07 on various Windows 64-bit setups.
On windows 7 ultimate and Windows 8.1 Pro I load only one track to check sound quality and effects of different settings of SQ. However after some time (randomly) the playback stops and I got a message that "ActiveX control ... cannot be instantiated because the current thread is not in a single thread apartment".
Windows 10 does not give me such warnings.
Here is a snapshot


Title: Re: Error message
Post by: PeterSt on January 16, 2017, 05:17:21 pm
Hi there Andre,

This can be a bit of a nasty one, hard to debug.

At the bottom in Settings (under the [ S ] button in the top) there's a button for logging. If you switch that on (red), log files will appear in the TemporaryData sub folder to the folder where you have put XXHighEnd.
If you can let this happen again (preferably on Windows 7 because 8.1 sounds like a drag anyway (haha)) and when it happened do nothing else but grab the log files ...

Best is if I only get the newest log files (sort on date/time) starting with XX-, X3- and X3PB-. Hopefully I can see something from there.

On a side note : what always can be a problem is that on one (or more) of the programs running in the beginning (see the "10 or more programs" message which pops up at the start of the install), you did not tell to run it and/or did not tell to "never ask again". But then you must have "forgotton" coincidentally for W7 and W8.1 and have not forgotton for W10 (if W10 asks for anything to run to begin with, because I don't think I have ever seen it myself).
If you think this could be the culprit, throw away the folder you installed XXHighEnd in, and also delete the \Data\ folder. Now reinstall it, in a folder with a now different name (!).

Regards,
Peter


Title: Re: Error message
Post by: nik.d on January 16, 2017, 07:31:45 pm
Hi Peter,

FYI:
I had the same message on W10 with demo version(s) - both, 2.06 and 2.07. It is related to XXHE
automatic shut down after certain period of time. Clicking on message kills XXHE main window.
Kind od semi-automatic shut-down :)

Brgds,
George


Title: Re: Error message
Post by: fralippo on January 16, 2017, 08:03:36 pm
Hi Peter,

FYI:
I had the same message on W10 with demo version(s) - both, 2.06 and 2.07. It is related to XXHE
automatic shut down after certain period of time. Clicking on message kills XXHE main window.
Kind od semi-automatic shut-down :)

Brgds,
George


Same exact experience here!


Title: Re: Error message
Post by: PeterSt on January 17, 2017, 09:34:55 am
Aha !
That is actually the first thing which slipped my mind. But I didn't put it forward because it was too far sought regarding the error itself (which to me implies another message which now can not be displayed, while no message appears in such "demo" situation.
Indeed things changed regarding the possibiity of this error showing up, I think already in 2.05 (but this never has been a public version - only for RAM-OS Disk users).

You both are of a GREAT help !
Andre, no log file needed. And all you need to know is that when this message appears the play time for the session in Demo has expired. But it should quit quietly and not with this error message.

Best regards,
Peter


Title: Re: Error message
Post by: jabbr on May 26, 2017, 07:11:15 pm
I am getting hit with this error frequently ... very frequently ... and I registered XXHE but it has continued.


Title: Re: Error message
Post by: PeterSt on May 27, 2017, 10:02:01 am
Jonathan, then I am afraid you did not follow the activation email precisely.

Go to Settings, RightClick on the Save As button (this button is close to the top), confirm all and re-initiate the Paypal procedure.
Money will be returned right away as part of the usual procedure.

Regards,
Peter


Title: Re: Error message
Post by: jabbr on May 27, 2017, 03:04:30 pm
It was that I only stopped and restarted XXHighEnd *once* after the activation code was entered not twice (in immediate succession)! ... and once the prog crashes the process needs to restart from entering code.