Hi Johan,


Yeah, you read that from my post today, but possibly you misread that. I said : I recall that 4GB ever back was the minimum and probably this was with Vista or even XP.
It is by no means valid today. I just don't know.


Can you please qualify that ?
I mean, I don't know about "stops" as such without any error message. I also don't know about crashes which go without error message. And all I actually do know is that I use the same OS install(s) as you do (RAM-OS Disk) and that the really only reason for playback to stop is the "Crack Detect" tripping, which is too tight for 2.09 (will be wider in 2.10).
... But I use another PC ... Important ? to some extent of course Yes, but it would only be of real importance if a 100 people would jump in and tell they have the same issue.

Something else - and I suggested that recently - is that the Core Appointment can do wonders. What is required in which environment is beyond me though (I just am not able to know it).

Anyway ... by no means this is a message of "it is you and you must be doing something wrong". The contrary; I only try to indicate that all can be fine as it is, but with which settings it goes "off" I can't tell. Again, if a few more people would be able to confirm this, it would be far more easy to look in "a" direction. And I am here to work things out ...

Regards,
Peter

PS: To be complete, what I do know from the RAM-OS Disk is that the W8 install is not stable really. 10074 is also "so-so" by now, but doable. From the others I see no issues myself, nor do I hear from them.

Telstar,

There is nothing buggy, let alone very buggy. But you have too few memory or imply settings that eat it. Remember, the SFS.

Outside of that, I don't think many people will use Windows 10 on an older (to very older) machine, so maybe we don't even know the implications of that. What I recall is that 4GB is the very minimum, but this is from x years back and possibly Vista or even XP.

When you are out of memory, anything can happen, and it *will* per definition look super buggy because of all the random errors occurring because of it.

So how much memory do you have in there ?

Peter

OK David ... Interesting ...

Thank you kindly for letting me know,
Peter

Hey All,

I didn't tell it right away, but for more than a week now I have my SFS at 5.19 (the .19 fraction is by now the explicit left over from any first who dialed that in) and I'd have to say that from the start of this setting up to now it is the most "pleasing of everything" I ever had (for settings). All as snappy as can be, no harsness anywhere, no idea of wrong cymbal colours ... etc. All good. And the mid-detail is crazy. All flies around through all corners of the room in very holographic fashion ... not-normal.

For those who missed the general idea of the consistency of "crucial" to this sound settings :

SFS thus now at 5.19.
Q3,4,5=1
ClockRes= 15
No OSD Text (Wallpaper Coverart is active)
Core Appointment 3-5 (for any 6 core (hyperthreaded) processor this will be OK)
And for those with a NOS1a/G3 : NOS1 Control Panel buffer size = 16ms.

Regards,
Peter

Hi Jack,

You did engage that "No Driver Signing" in XXHighEnd's Settings and rebooted, right ?

And don't click that button more than once for the boot session; set once to your desired setting - reboot right after that.
Full procedure :

1. Go to Settings - Output Section.
2. Click Refresh button next to the "Driver Signing" text.
3. When it shows "Drivers need not be signed", click Change.
4. Reboot.
5. If you like, after the Reboot, check whether it is now as desired by means of #2. If OK, no further clicking in there ...

I don't think you have the RAM-OS Disk, but for those who have : don't do this while in the RAM boot. Instead boot to the BASE OS.
Also, the installing of the Driver itself has to be done in Normal OS (where the Driver Signing thing is set does not matter).

After the matter, the Driver Signing state can be left as it is (no need to change it back to "Drivers must be Signed".

Let me know how you fare ...
Peter

Yeah, well - when for the firtst time.


Was sent by drone. So yes, plane wrapper. And all the way by 9V battery. I hope there's some left in it for calibrating the DC-Offset because it goes by the same battery.


I suppose you can't hold on to that forever, Jack. I know, your NOS1a/G3 is blue, but even if you lick it hard, it is no pill.


See below. Wears on the left side.


You can say that. After we j'd off the old stuff and pushed in the new *and* moved over the glockenspiel, we discovered that in the very far back we replaced a chip. And this same chip is the one we now sustain on the new B'ASS board. So we move it over. But we never thought about your special situation until some "bollocks !" was floating about because I managed to think about it. This was before inhaling those beers. Afterwards I forgot about it again. This is how I now write it down. Anyway, it kept us busy tweaking for a full day, never seeing what could be wrong, except for that all B'ASS boards we tried seemed to get killed after a few seconds. Never saw such a thing before. But really no wonder because that old chip ran on 2.5V. The new one on 5V, so the old did not last long.
Well, Jack, I already told you the little story by email and I suppose we'll never forget this special one.

OK, it is clear that I thought to be funny too with a clashier response, but no way I can get passed that Child in Time, supersede on the Jumping Jack Flash which I recall from the same era and ego, and trying to Get Satisfaction screaming around I couldn't. Those were the days.

I hope you like it with my remark that I couldn't have a slighest clue myself, after all these upgrades.

Peter

I have the biggest smile on my face.
I just wanted to respond quickly just after reading this. I think I will give a stylish response later.

It may happen that at the start of Playback, a message like this one pops up :

Attempts: 11 Current CPU% level of process 4.89341. Continue ?”


If this message appears (quite) consistently at the start of Playback, either your system is "generally slow" (read : not on par) or the Mixed memory type is selected in XXHighEnd Settings (in the Memory section).
Set that to either Mixed Contiguous or Straight Contiguous and it should help avoid the message.

Notice that what ever is being done in Normal OS Mode (which is the normal Operating System mode as presented by Windows) is inherently way more slow than when having booted into Minimized OS.

If the message won't go away, consider the deactivate (blue) the "Include Garbage Collect" setting. This will not be optimal for the best SQ, but it thus will avoid the "situation" hence message.

Yes Arvind, that will matter !
Not that I ever heard of it, but surely enough many people brought forward this issue as you did today, but you are the only one of which I could tell that it couldn't be the PC.

If I only remember it for the next time ...

Thanks and enjoy again !
Peter

Hello Arvind,

OK, Good !

In Settings (Memory section) there's something like "Garbage collect". Flip the state of that and the message won't appear.
If you did that previously as well, it is plainly that and solved. If you're sure you never touched it, try to imagine what has changed since the previous 14393.0 "install". Notice the size I referred to yeaterday.

And btw, if this happens once a day this is not a problem at all. Or, if it happens one time just after a boot, also no problem. But otherwise it shouldn't be there "continuously" or otherwise I will tell you to get an "on par" PC. But as you know, you already have that ...
So maybe something was changed.

Best regards,
Peter

Yes. But take care that the name becomes "original" again (remove the "- Copy").


Yes. And also check whether you have XXHighEnd 2.09 in there. If not, your copy is from earlier on and you'd need to upgrade it with the UpgradePatch file (paste over, etc.).

Maybe you deleted it so save space. It was originally there (it is for everybody).


Of course it is !

... so you are lucky and nothing is really the matter. However, your 14393.0 got corrupted. This means copy back the "- Copy" version.
Test that briefly at first and then don't forget to expand it. First look at the size of the current (corrupted) 14393.0 so you can make it the same.

Still questions ? just ask ...

Peter

Ah yes, that test was actually first. Please do.

The XXHighEnd version should not be related.