XXHighEnd - The Ultra HighEnd Audio Player
January 19, 2017, 02:09:08 pm *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Dec. 31, 2012 : XXHighEnd + Phasure NOS1 DAC receive 6moons Blue Moon Award !
** "Lonely at the very top" **
Search current board structure only !!  
   Home   Help Search Login Register  
Pages: 1 2 3 4 5 6 7 8 [9] 10
 on: January 11, 2017, 05:31:55 pm 
Started by manisandher - Last post by manisandher
Peter, do you think has anything to do with using a Remote Desktop Connection? Sliding the UAC slider up seems to have worked (it's still there after the reboot). But what about my rights management?


 on: January 11, 2017, 05:29:12 pm 
Started by manisandher - Last post by PeterSt
On Tidal and MQA :
I don't think that an MQA encoder will exist for 16/44.1 - only higher (like 24/88.2 and beyond).
This means that no 16/44.1 will be replaced by MQA versions.


 on: January 11, 2017, 05:26:39 pm 
Started by manisandher - Last post by PeterSt

I've just checked the XX folder and I have UACUp.tss in there (not .tst).

This is not right;
You might run this RunThisFirst.bat one other time to check and be sure, but this renames that file to its .tst counterpart. If that does not work you have no write rights to that folder or something. And if that is so it is my gues that XXHighEnd will have troubles right from its start, all over.



PS: XXHighEnd can start without Audio Device just the same. But Activation will be a bit problematic. evil

 on: January 11, 2017, 05:20:46 pm 
Started by manisandher - Last post by manisandher
Nah... the audio device isn't the problem. I've got the Audioquest working and XX still won't launch.


 on: January 11, 2017, 05:13:12 pm 
Started by manisandher - Last post by manisandher
OK, I think I've found the culprit. The mobo in my music server has no integrated audio device. I've been using an old Audioquest USB DAC just for the purposes of launching XX. For some reason, this is now not being recognised correctly by the mobo - it appears in Device Manager but not in Manage Audio Devices. So as far as XX is concerned, there are no audio devices. I have no idea what has suddenly caused this - the Audioquest USB DAC has been working perfectly in the music server for ages, and I've just tried it in another PC and it works fine.

Oh well, I'll probably just stick a sound card in the music server at some point...


 on: January 11, 2017, 04:31:49 pm 
Started by manisandher - Last post by manisandher
Hi Peter, thanks. I actually tried launching XX before running the RunThisFirst file, but it wouldn't launch. That's when I thought I needed to run RunThisFirst.

In any event, I've just put the UAC slider up and rebooted. XX is still not launching.

I've just checked the XX folder and I have UACUp.tss in there (not .tst).

Any ideas what I should try?

(BTW, this really isn't a big deal - I was thinking of cancelling my Tidal subscription anyway, especially if they replace all 16/44.1 with MQA.)


 on: January 11, 2017, 03:57:31 pm 
Started by manisandher - Last post by PeterSt
Hi Mani,

At this moment I may have the feeling that I need combinations (permutations) which are beyond my capabilities of thinking over. I mean, reading your issue on this matter, it far sought can be so that this RunThisFirst thing is not "allowed" to be performed on the PC where all has already been arranged for. So if I'd allow you to freely do this, in any combination you like yourself, BUT when being in Normal OS first (I understand ... small problem if you are not at this moment) :

Your UAC will be "down" because of the previous XXHighEnd install (like 2.06). Consider this the culprit which I did not anticipate (not even sure, but say I never thought of that state). So, slide it up one step and reboot.

Assumed you ran that RunThisFirst, then in your XX folder a UACUp.tst exists and this file is checked against, meaning that when it exists, the lot assumes you're in normal UAC (up) operation (and can run apps). But this really must be so, and in your case it was not when you created that file (you ran the RunThisFirst but maybe shouldn't have).
Notice : when you find a UACUp.tss file in there, it means that UACUp.tst does not exist (and the .tss file is not checked against).

At this moment you need not to worry about the contrary situation : UACP.tss must exist together with the UAC Down (put in that state by XXHighEnd because manually that can't be done - thus slider down does not mean down at all).

WARNING : If you are in MinOS DO NOT mangle with the UAC slider, or your OS will be rendered useless forever. This most probably also means that when in MinOS you will not be able to start XXHighEnd. Remedy : re-install 2.06(a); this should normally start; with that, go to Normal OS (this is allowed, never mind you're demo).

If something is not clear because of too many typos or too much of Dutch, let me know.


 on: January 11, 2017, 03:30:11 pm 
Started by manisandher - Last post by manisandher
Hi Peter, Happy New Year!

I've just installed 2.07 onto my music PC [edit: I meant audio PC] and also onto my server (for use with Tidal), using the upgrade patch in both instances. The former worked with no issues whatsoever (I'll post about the SQ later), but I have an issue with latter.

Trying to launch XX, I get no response at all, except a second or so of the windows 10 loading blue circle.

I then decided to load the full 2.07 onto the music server. But I'm getting the same result - a second or so of the blue circle then nothing.

Do I need to do something more than simply double-clicking the 'RunThisFirst' file? Any other thoughts?


 on: January 11, 2017, 08:57:09 am 
Started by Nick - Last post by PeterSt
Hi guys, thank you for the responses.

Stanley, the BIOS settings in the Stealth are for the majority the same as layed out for the "XXHighEnd PC". The Stealth has many more settings, but they remained untouched (were not explored or were regarded wackey by me for the processor we use (this was confirmed by ASRock).


 on: January 10, 2017, 11:36:14 pm 
Started by Nick - Last post by Robocop
Unless you have the new Stealth, Bios settings are totally in your hands especially regarding individual hardware. I've been using the old XXHE computer Bios settings but my computer only has 4 cores, 8 threads.

In the light of changing Bios settings I hope I've solved a problem. As a result of the sound being so good I can't not listen to 2.07. I played the latest St Germain - St Germain 24/44, wow detail and bass not heard before. In fact probably need to rework my subs now.


Pages: 1 2 3 4 5 6 7 8 [9] 10
Powered by MySQL Powered by PHP Powered by SMF 1.1 RC2 | SMF © 2001-2005, Lewis Media Valid XHTML 1.0! Valid CSS!
Page created in 0.42 seconds with 15 queries.