XXHighEnd

1) In w10 when I set the Time pref.index to "Stable"in the Base and reboot to RAM it does not remain as set. When Refresh is clicked it flashes error.
How do I make the time pref. remain "stable"

2) nervous rate setting suggested is 100 for the stealth comp. I do not have the stealth comp, but I'am using the settings of stealth. should I keep the nervous rate as 1 or 100.

Hi Shreekant,

First an easy answer ...


Let's first off say that the 100 runs a bit cooler. However, although this seems Stealth related, it isn't. This is merely about how often the system adjust things, thinking about processor (cycle) speed. Thus, the lower the number, the faster the system adapts to "the" situation of the moment. This could sound better.
On the other hand, the more often the system adjusts, the more "nervously" all could sound, because the sound changes all the time (like 1000s of times per second). When the other end of the extreme is taken, and adjustment takes place in once per second or so only, a. the system is too late with a required adjustment and could be "squeezed" somewhere while b. the sound is more consistent. Of course a. and b. conflict to some degree at least, however, when all is hogged for SQ with Q3,4,5 to 1, what's squeezed should be the other processes (not sound related) in the system.

And so we have another "nest" of related settings without clear result in advance, and which you may find out yourself when you have some spare time.  :)

I always use 100 with the Stealth, but I also don't try anything else. I use Q3,4,5 at 1 because it sounds better (more clear, more crispy).

Regards,
Peter

I think you don't know that, because it requires a Refresh first and :


... so how can you tell ?

It is a bit sad that I don't recognize any error there and certainly not a "flashing error" as you describe it. However, I assume it is a matter of speak (flashing would be something which briefly shows) and that you can make a screenshot of the error ?
So I'll wait for that - without that I really can't tell what this is about. OK ?

Kind regards,
Peter

A couple of months ago I did exhaustive testing of my settings trying to figure out a particular issue. I found that setting the nervous rate to 1 was a significant SQ improvment. At 100 there was a glare to the sound. At 1 the sound is much more relaxed and neutral sounding.  YMMV.

One other thing about setting the nervous rate to 1: you must reset it every time you reboot because it automatically reverts to 100 after a reboot. Peter said he'd address that bug in the next release. Though it would be great if a patch could be created so it could fix the bug in other versions. I'm currently using 2.06.  :)

Hi Brian - Yes, thank you, I already forgot about that. Notice though that it was/is not related to the OS session but to the XXHighEnd session.


Peter

Peter, not sure what you mean above: I didn't mean to relate the issue to the "OS session." In all XX versions after 2.05, regardless of the OS being used, if you set the nervous rate to 1, it is not saved upon a shut down. When you again boot up the nervous rate automatically reverts to 100. Once I set it back to 1 it stays at that value throughout the entire XX 2.06 session. So you can stop and restart tracks and the value remains one. (With 2.05 it reverts to 100 every time you stop/restart a new track.)

My suggestion is for a patch that will allow one to save the nervous rate to 1 upon a shut down for all versions of XX after 2.05. I'm currently most satisfied using 2.06.  It's no big deal but sometimes I forget to set it to 1 after booting the pc and it takes a few minutes to remember why the sound is off, and I'm only getting older....... :)

Hi Brian - It is no big deal at all. But in the topic I linked to (via my post in there) you "claimed" that. And today you did the same by means of :


I know, you guys call switching on a light bulb also "reboot", but nobody will understand. So in case you meant to "reboot" XXHighEnd, outside of the US we restart it. Haha.


This is completely correct. But also irrelevant because you didn't even switch off the light (you imply here not to quit XXHighEnd).


But then this again is beyond me. And I am pretty sure that at least that you didn't want to say. But if so after all, I need to know more.
Anyway now I am dizzy of inconsistency. :wacko2:

Peter :old:

Thats weird, am just asking if a patch can be developed to fix the problem in versions 2.06 thru 2.09.

Hi Shreekant,


Do you have problems with this ? If Yes ... is maybe the error really "flashing" by as such ? (appearing and quickly disappearing)

Peter

Nah, that is not possible. Or at least I wouldn't know how to ...