XXHighEnd - The Ultra HighEnd Audio Player
March 20, 2018, 08:38:43 pm *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: August 6, 2017 : Phasure Webshop open ! Go to the Shop
Search current board structure only !!  
   Home   Help Search Login Register  
Pages: [1] 2 3 4 5 6 7 8 9 10
 on: March 20, 2018, 08:31:30 pm 
Started by PeterSt - Last post by hudesigns
Hi Peter,
Baby steps form me  Happy
I use Asrock Z97 extreme MB with Windows 10. Could you tell me the above tweaks in BIOS are still relevant. Or you can give me an updated suggestions.

 on: March 20, 2018, 04:40:02 pm 
Started by Nick - Last post by PeterSt
A different question. Is it possible to use remote desktop and Unattended playing?

Hi Zheng,

Sure !
But it depends a bit on how your network is setup. Generally :

- Take care that you activate "Use Remore Desktop" in XXHighEnd Settings (Services section) while in Normal OS (then boot into MinOS).

- Use the IP address of your Audio playing PC and NOT the PC Name.

I think these are the important settings. But crucial for you is just knowing that it can work (you will find the how easily yourself).
Also notice that the RD functionality of each operating system can be used (IOS, OSX, Android).

Lastly, do not forget to use the XXOSK.exe (is in the XX folder) and "know" that it can size to a square plus it can be resized by means of dragging the title bar.

Kind regards,

 on: March 20, 2018, 04:33:33 pm 
Started by Nick - Last post by PeterSt
And what happens internally I also wonder.

You are right. I found that my memory setting was on "Mixed"! Once I put it on "Contiguous", it jumps back to 4.19 unhappy

Indeed it is related to that ...

 on: March 20, 2018, 04:21:53 pm 
Started by Nick - Last post by hudesigns
A different question. Is it possible to use remote desktop and Unattended playing? Currently it is not working for me. Attended playing is fine with remote desktop.


 on: March 20, 2018, 04:16:53 pm 
Started by Nick - Last post by hudesigns
And what happens internally I also wonder.

You are right. I found that my memory setting was on "Mixed"! Once I put it on "Contiguous", it jumps back to 4.19 unhappy

So now I am using "Mixed Contiguous" and 5.19 which seems fine.

 on: March 19, 2018, 04:02:44 pm 
Started by manisandher - Last post by PeterSt
Hello ZH,

Nothing will change on the logos themselves. So yes, if the file is "natively" 192, the 192 logo will show as always.

Unless I messed up of course. swoon

Kind regards and thank you !

 on: March 19, 2018, 03:49:45 pm 
Started by manisandher - Last post by hudesigns
Hi Peter,

Loving MQA playback! I am using 2.09 and all MQA functions seem to be working as designed. The downloaded MQA48 album gets a MQA48 logo on cover art and plays as 48-->48. And likewise MQA96, gets MQA96 logo and plays as 96-->96; MQA192, MQA192 logo, plays as 96-->96. everything is beautiful.

My question is that under the proposed 2.10, are we going see MQA192 logos for MQA192 albums anymore, which is important to me? Because when I playback a MQA192 album, I sometimes use 96-->192 to feed to the DAC and thought I liked the result which is slightly closer to neutral and less edgy. I know it's upsampling but with certain MQA192 albums, it sounds better to my ear.

 on: March 19, 2018, 02:15:50 pm 
Started by manisandher - Last post by PeterSt
When I look into the ID-tags of these flac files, I can see that the tag ORIGINALSAMPLERATE (44100 or 48000) corresponds with the audio property "sample rate", which is always the same for these wELL working MQA tracks.

When I download a MQA96 album, like the Robert Plant album in the emailed log file, with my audio PC, it is like this:
the tag ORIGINALSAMPLERATE has the value 96000, what seems to be correct. But the sample rate of these flac files is 48KHz only. It should be 96KHz too, as I believe.

So Richard, ...

Quote from: PeterSt
You never read those for me. Never adhere your own ideas about matters, or you will end up nowhere with it, OK ?

Apart from the "for me" which should read "from me" (apologies for this confusing line of text because of that), I tried to help you by means of now explicitly making what you thought could be observed in the first place.
So what actually happened is that you gave me the very good idea that no decoder is required to observe the Native (in-MQA) Sampling Rate, which finally avoids all the hassle about the Music Server PC seeing something different from the Audio PC just because on either of both the decoding does not work. So from of 2.10 it will be like this :

- The Hires Audio logo will emerge based on what the ORIGINALSAPLERATE tag in the FLAC file tells us (thus exactly how you looked yourself);

- The actual MQA Decoding will take place during Playback.

Let's try to keep in mind that the MQA Decoding during Playback is depending on two major data parts :
1. The HiRes Audio logo must be present on the Coverart (when no Coverart is present or (made) visible it's an internal thing, but this is rare anyway);
2. The PC where the Playback happens must be able to Decode MQA (and for some PC's this can be a pain and virtually unsolvable unless Windows is freshly installed (not upgraded !)).

Although not easy to see, the change is major. Why and how ?
Well, because the initial enumeration of the MQA albums is not depending on the MQA Decoding any more (it was in 2.09) only one thing can fail from of 2.10 : the decoding suring Playback. This means that we van be 100% guaranteed that if Playback fails to decode MQA, it is the Playback PC not being able to Decode MQA and nothing else.

How to check this unambiguously ? Most easy description (leaving out more possibilities) :
-> Find an album with HiRes Audio logo of 96, take care that your DAC can take 24/96 for input at least, play the file and observe that after decoding - hence when playback commences for real - the input to output in XXHighEnd shows 96000 - 96000 with the little fx button (sits in between inut and output bit rate) activated and the sampling rate slider (sits in between input and output sampling rate) at 2x.

Additionally I could say that each track which has been played once (briefly) or each album which has been Prepared explicitly, will from then on show the input and output as should even without playback. But better don't pay too much attention to this because it may confuse only.

What *is* important further, is that when you have proven that the 96 decodes, any 88.2 or 48 or 192 (native output is 96 max for real anyway) or whatever, will decode too.
It will NEVER happen that a 44.1 or 48 decodes, while 96 etc. does not (which could be your easy mistake to make).

Btw, I'd say that in all cases the MQA logo at the bottom (above the [ G ] button) will testify of MQA decoding. No MQA decoding means that the MQA logo (including green or blue indicator) will not show.

After some consensus (or earlier Happy) I will try to put this in a Tutorial (in the Tutorials section) as well.

Best regards,

 on: March 19, 2018, 11:11:25 am 
Started by hvdh - Last post by PeterSt

I tried every combination I could think of (with a USB stick which I legally and illegally removed) but I just receive nice error messages (from XXHighEnd) that the path is nor available, something wrong with it, etc.
This is from the Library Area and also from the Playlist Area (tracks remain visible but can not be used and again by more than one message I am told).

What I did not (could not) test is your RAM Disk situation.

So I am afraid that if these kind of things go wrong, you need to "repair" your PC. So I tried, but what I can't mimic, can't be solved either. Plus all the error messages already ...


 on: March 19, 2018, 08:58:11 am 
Started by Nick - Last post by PeterSt
My 2.09 seems to stay on 5.19 without any issue!

But maybe not after Unattended playback. And what happens internally I also wonder. But if it stays after Unattended (or maybe just quit and restart XXHighEnd proves the same) then it should work for real. Watch out though : the piece of software arranging for the "even" numbers is explicit (so the even numbers ever back were on purpose) and a little bit buggy. So yes, it can stay by sheer "accident" but if you re-attempt it (change the number back and forth) you may not be able to get there again.


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.033 seconds with 10 queries.