cardfasad.blogg.se - Xxhighend vs hqplayer

#XXHIGHEND VS HQPLAYER UPDATE#
#XXHIGHEND VS HQPLAYER WINDOWS 10#
#XXHIGHEND VS HQPLAYER SOFTWARE#
#XXHIGHEND VS HQPLAYER PC#

I am stuck at '20% sound degradation' with Bughead WAV file: William Walton, Viola Concerto with Nils Mönkemeyer, 2 Vivo e molto preciso. OK, I compared Bughead 8.59 with XXHighEnd 2.07. If you've used a similar version I'm definitely going to check out XXHighend.ĭoes JPlay and AO feature in your systems? I'm using Nontallion 7.80 on a Kaby Lake i7 processor and find the sound fantastic. Just so I can compare, which version of Bughead are you running? You know it when you hear it – very intuitive – so I tend not to be too analytical about it. I prefer the Lampi for DSD and the Audio Aéro for PCM.įor me, good sound makes me forget that I am listening to gear. However, thanks to XXHighEnd and WTFPlay I rediscovered my old Audio Aéro Prestige Signature DAC + Audiophilleo 1. JRiver Media Center (large footprint great database!)īefore, I upconverted everything to DSD256 into my Lampizator DAC with an Amanero board. HQPlayer (upconverting to DSD, great algorithms, but large footprint is noticeable in sound) Bug head (very cumbersome and unreliable in my setup) APlayer (works well with foo_dsd_asio for upconverting to DSD256) Of course this a subjective snapshot, based on my own setup. I have used the following, grouped in 3 SQ groups. So how does XXHighend sound in comparison to the other players (please list them) that you've used? The processes/threads went down from 27/450 to 25/375 when playing with XX in unattended mode.

#XXHIGHEND VS HQPLAYER PC#

In the meantime I am playing from RAM disks (one for the player and one for the music – very easy to setup with XX) with the PC optimized with FP/AO/PL. So I will stick with WS2016 and wait for that. The good news is that the developer has promised to make this work in the next release which is due in September. Alas, it appears that 'Minimize OS' does not work yet with Server 2016. Maybe I will purchase a license (€72) and find out. So what I am wondering is whether the 'minimize OS' option can be used before using another (DSD capable) player. One disadvantage for me is that XXHighEnd only PCM only, and no DSD.

#XXHIGHEND VS HQPLAYER WINDOWS 10#

Windows 10 as his SW strips the OS anyway. Somewhere on the XXHighEnd forum the developer states that there is no no benefit in choosing Windows Server over f.i. There is also an option 'minimize OS' which does exactly that before hitting play, and is supposed to optimize even further however, this is only available in a licensed version. In my case the numbers of processes/threads went down to 27/450. Upon hitting play in so called 'unattended mode', the player shuts down many unneeded processes (which takes about 1 minute).

#XXHIGHEND VS HQPLAYER SOFTWARE#

This is an impressive piece of software that may incorporate all and more than AO + FP + PL do together. Under Windows Server 2016 with GUI I installed the demo version of XXHighEnd, the audio player. Just tried another optimization approach: Since I've been chastised elsewhere for posting in threads that 'aren't mine', I will not post further and ask any user with questions to create a new thread. Why? Because Process Lasso is continually tuned for the latest hardware and software in the Windows ecosystem. It occurred to me that all you guys who never open the GUI, never get updates, and you *need* updates.

#XXHIGHEND VS HQPLAYER UPDATE#

Basically it is a page fault that would have been hard, but a cache allowed it to avoid referencing the disk.Īlthough this thread is NOT about Process Lasso, I want to note that I am adding a new updater to Process Lasso to let it update in core mode.

Now, there are also 'soft' page faults which matter a little less. This causes a hard page fault, resulting in a big performance penalty. A hard page fault is when a process accesses virtual memory that is not in RAM, but instead sitting in your page file (swapped out). I saw that mentioned earlier, and just wanted to note that metric should be pretty much ignored. One thing I would like to say is that while you *should* concern yourself with the number of threads open (which relate to processes, as they are contained in processes), the number of *handles* open on a system is never going to impact much.