XXHighEnd - The Ultra HighEnd Audio Player
October 16, 2018, 02:43:21 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: September 16, 2018, 05:52:10 am 
Started by Shreekant Somany - Last post by Shreekant Somany
When I rip a cd or convert a track from flat to wav. And when I open the file in xxl I inevitably get ._ 01 ....  how can I avoid this. I have attached a screen shot.
Iam using dB power amp and my comp is Mac Pro.

 on: September 15, 2018, 07:01:21 am 
Started by Robert - Last post by Robert
 Yes only have 4 cores, 3/4 sounds the best. I was meaning SFS and balanced settings primarily. Although I should retry the core settings.

Bios settings have a large effect on the sound something I'd forgotten. I have been running Bios update default settings for 3 weeks and didn't notice till Peter's Disable Crack comment. Its interesting how one can get use to a sound quite easily and not realise some things are not optimised.

Yes I'm miles away from the new Stealth MKIII still better than a laptop.


 on: September 15, 2018, 06:31:39 am 
Started by Robert - Last post by briefremarks

Looking at you signature I see you are using Scheme 3-4; Peter has 3-5.


 on: September 14, 2018, 11:35:54 pm 
Started by Robert - Last post by Robert
As a result of a recent Bios update and resetting, disabling Bios settings, more than I have ever been brave to try, the subsequent sound with Peters current XX settings is amazing. I also prefer Disable Cracks off sound wise.

Lush 2 is on the horizon perhaps a Xmas present. 


 on: September 10, 2018, 12:20:35 pm 
Started by Robert - Last post by PeterSt
Thank you, Colin.


 on: September 10, 2018, 08:20:08 am 
Started by Robert - Last post by coliny
Hi Peter

Its:- Custom Filter 352800 low (NOS)

It happens on peaks in music. Also on 0dB sine test tone, switch your amps off first if you try this.

Not particularly a problem, I posted this in case others are using 0dB & get cracks.


 on: September 09, 2018, 01:25:58 pm 
Started by Robert - Last post by PeterSt

Hmm ... that would be a filter anomaly. Not that I am going to solve that instantly, but with which filter does that happen ?
If you don't know for sure any more I rather learn that. Happy

Regards and thanks,

 on: September 09, 2018, 11:09:42 am 
Started by Robert - Last post by coliny
I got Crack Detect occurring recently but discovered my volume was 0dB in XXHE. Went back to my normal -3dB and no more Crack.
0dB with upsampling filters can cause Cracks, I think it was mentioned on the forum a while ago.


 on: September 09, 2018, 10:17:01 am 
Started by Robert - Last post by PeterSt
Robert - Interesting ...

I would say that the Crack Detect setting is unable to influence sound (quality), but if I read what you just wrote ... : scratching

The Balanced Load at 18 is a "tricked" one. All under 43 is. Maybe you recall that ever back under 43 was not allowed because it did nothing. Until that changed and I recall it was about Windows 10 or some Build of it. It allows the processor to be tuned all the way to about 0Hz frequency BUT one has to check what happens for reality responses, because it can be too slow. For example, 430Hz is still workable, but one step lower (which goes by several steps in the Balanced Load because one step does nothing) that ending up at 300Hz and the PC becomes unresponsive and what I recall ... erroneous.
Point is also that this depends on the processor.

The combination with the Nervous Rate is almost even more interesting (for your description) because it tells how fast the processor adapts to a "more speed" request. Thus, if it runs too slow (notice : while it runs at an about fixed speed anyway), the Nervous Rate tells how often to look to adjust the speed. Think in terms of 1ms vs 1000ms (mentioned figures are not absolute) with the idea that 1000ms is equal to "never" (in the terms of this domain) - and which is not meant to let error the system, but to let it behave in steady fashion instead of being "wild" en nervous.
This gets complex when we see that the numerous other tasks in the system (which can be 1000s) also need their "time slice" and while they are being kept out of the door (because the system does not respons fast enough) in the end the OS itself may fail on accomplishing whatever it is.

Summarized, it looks like you, Robert, are able to let the OS error, possibly up to the sense of not being able to process complete audio words and a few bits are chopped off, *because* an other process on the same thread (so to speak) received priority and it has to continue. Example of this in general, is the audio not being allowed to speed down. This can be solved by the system to keep track of the speed but chop off complete samples, while more internally and detail, also bits can be shopped off. Both are as illegal, although the skipping of samples would be acceptbale, as long as it isn't about charachters in a Word document.

I must add that shutting off Crack Detect does not help a thing in avoiding the real cracks (because of incomplete audio words or whatever) BUT that the process of checking for Crack Detect is an additional read of the complete stream (though it goes per chunk). Thus one could say that while the processing of the file for that part takes a certain amount of processor cycles, the checking (Crack Detect) for it to be OK takes maybe 10% more. Apart from that possibly influencing SQ to begin with (all processes do) it also requires 10% more of the processor and that just could underwhelm what's necessary.
So if your processor runs at e.g. 500MHz and just can cope, then this "feature" actually requires 550MHz which isn't available. And together with the Nervous rate at a highest number, also not a little bit and at least too late (the system does not detect that the processor must speed up a little).

This is a lot of hoopla and blahblah, but a means of explaining the situation you ran into.


 on: September 09, 2018, 01:31:07 am 
Started by Robert - Last post by Robert
I got so annoyed I had disabled Crack detect, since 12 August post. No problems at all.

Today I noticed you have changed balanced rate and nervous from 18/100 to 35/10.

With 35/10 and Crack detect enabled I have a better sound similar to 18/100 with Crack Detect disabled. Crack detect certainly has a major influence on the sound.

I do wonder that your XXhighend software is probably very stable and unlikely to cause cracks. I have re enabled Crack detect and have yet to experience any problems with it. I recognise that some owners may create a situation that could cause cracks.

I've updated my settings and its all sounding excellent.


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