I didn't have the proper ears for anything, yesterday.
It's a bit of a psychological thing as well, because while I couldn't find my sound, I noticed that the settings (of XXHighEnd) were not as how I expected them to be, so I probably too soon set them to what I thought they should be, for the worse (relative to day before yesterday).

On a side note, I can't figure out how that happened. So the settings I found yesterday are a combination of settings I definitely used somewhat longer ago, but with having the Audio PC (Stealth III) rebooted regularly (say about daily), the settings always being nicely saved to the SSD, on Sunday (day before yesterday) I rebooted too, but this time in "hard" fashion because I couldn't connect to it because of something I did wrongly on Saturday night. So Sunday afternoon the settings were not saved with for result it got hold of older settings ? I wouldn't know how it did that, but it did.
The settings are auto-saved each day, also to permanent storage once the RAM-OS is normally shut down. So I set myself to the task of finding out when actually these settings we saved in "old" fashion for the first time.

As you can imagine this confuses highly. I don't know about you, but for me such settings are an evolution of relative judgments and findings. And if suddenly this has reverted to something you don't know, then you are, well, confused. Had I been listening to these settings for one day more ? two days ? a week ?? This unknown alone is sufficient to be without ears. And that happened to me yesterday.

Peter

PS: Below we can see how there's a gap between the 9th and the 13th of May (Sunday). So the Mach III has been running for 4 days from of the 9th, until I had to hard reboot it and it couldn't save the settings files to permanent storage of the lacking days. But these are the saved settings, which doesn't readily tell what I used after any boot up. Anyway, the file of May 13 should contain the wrong settings already, which settings are a copy of the real settings used when XXHighEnd was started the first time after the reboot, Sunday afternoon, 1:38pm. It seems logic that the settings of the 9th were used (loaded) at that moment. Btw, it resembles my (previous post) mentioned "4 days" of burn in of the newly built PSU. So after the 4th day suddenly all "snapped in". Yeah, but with different settings than the 3 days prior to that ...

Remember ...
(and I don't like to repeat everything a dozen times, OK ?)


I recall you said something about an additional LAN card. If possible, go for that. Way way more easy and always secure.

No go for it !
Peter

I wanted to tell yesterday but I forgot I suppose :
There is no such "procedure" as observing whether the Audio PC sees the other end.

- Obtain IP address from the Audio PC (IPConfig);
- Enter that IP Address in the RDP Client (your Mini) (please don't be ignorant with PC Names);
- Connect (log in).

It is as simple as that (the OS on the Audio PC is prepared for this), but only when at first the Audio PC is in Normal OS Mode and when not connected via a router (with possible firewall issues).

The fact that no led lits doesn't tell a thing in this case. When there is no connection there is also no led (I noticed that myself). Of course the Ethernet cable must be OK.

On another note : a bridge in the Audio PC never brought me the solution. However, maybe in combination with the topic I linked to from RMalits - I never tried it any more after having that "knowledge").

Maybe it helps that I tell that close to 100% of people use the connection how I advised it (thus one Ethernet port in the Audio PC). It would be true that the Music Server PC requires two Ethernet ports in "convenient" circumstances. So, the inconvenient way is both via the router and it is there where RMalits' topic applies for sure.

Best regards,
Peter

Michael,

The shortest Ethernet can do is 160 meters (and that is from gear from 30 years ago). So it can't be the length.
Btw, you could test the cable by connecting your Mini to it, I suppose ?


That depends. For normal RAM-OS Disk situations (they are sold separately just the same) this is not the case. For dedicated installs like yours it depends on whether I think of it. Point is : the Audio PC is regarded not to be connected to te Internet at any time (it can of course, but there you go with problems - not today then tomorrow).
Because your "install" took quite many hurdles, I did the install many times. So actually I don't know. But apparently I did.

Regards,
Peter

Hi all - time for a small update.

The 10/20 processor must be in for 10 days now and I must say that I feel I have it fully "under control" now. Of course it can be so that by now I forgot the sound of the 16/32 processor, but there's now so much more interesting in the music than what I recall from my Mach II "era" that by now I would definitely stay with the 10/20 if I could only choose that one (and my Mach II).

Two main matters happened which made this work really well now :

1. For this processor I changed a few things to the PSU (to be honest it has become a whole new PCB so it better fits the case in the mean time). Will post a photo later, if it means anything to you anyway.
This PSU required some break in of 4 days. At least this is what noticed. This was completed 3 days ago.

2. The somewhat more "grey-ish" sound (say a bit more slow) compared to the crazy 16/32 regarding the highs, could be tamed by putting back the buffer in the NOS1's Driver Control Panel from 16ms to 4ms. So yeah, what experience all can do (didn't I use that 4ms for "years" until the recent long Q1 setting method). So in combination it brings more sparkle for this setup - the sparkle I missed since the 16/32 went out (to Michael).

Yesterday I ended the listening session first with Autobahn (Kraftwerk) and of course everybody is allowed to call me crazy to play this "music" in the first place. But mind you, because it is so blatantly stupid - 20 minutes long, it really has to have something or otherwise indeed it is "nothing" as such. So might you don't know, those (simple) synthesizers together with the simplicity can just spellbound you. But it has to work.
earlier on I told about the mid detail of this 10/20 setup. But what mid-detail I actually mean here ? well, how a lower keyed synthesizer can be sparkling (shattering) in the lower frequencies because of its on/off sound. Yesterday I heard things in that 20 minute track I never ever heard one bit of before. When it happened the first time we both looked at each other and equally said "huh ??!".
It was not even me who said that the PSU must be broken in now, she also referring to a "hey, but the other day this Autobahn did not work much, right ?". Correct, I even shut it off preliminary.

Talking about spellbound ... when Autobahn was finished there was a bit of time left before dinner would be ready and I thought "oh wait, if Autobahn sounds so mighty good suddenly, what would In-a-gadda-da-vida do ?". And yes, nothing worked out better than that if it was for the return to the atmosphere of dark basements with (fish)netting against the ceiling, an LP shimmering while playing this 17 minute track with the xth Iron Butterfly drummer because they all died of the too long drum solo (who ever made up that story for this few minutes of real solo I don't know, but I am sure that I believed everything at the age of 12).

---

If I feel like it, tonight will be important because I plan to move my USB cable (ending at the input of my NOS1a/G3) to the Stealth II (yes, that is still running from its 8++weeks RAM boot). Part of the plan is that I will try to tell you as accurately as possible the difference between the sound of the (2640v4 - 10/20) Stealth II and the 10/20 Stealth III. I will (honestly) do that too if the Steath II sounds better of some sort. But I would not count on that.

More later. Kind regards,
Peter

Hi Robert,

FWIW (!) : You are talking about the same forum where nobody hears a difference in anything, differences can't even exist while matters you refer to are crucial. Somehow.
To me this seems not to combine at all.

Anyway this is not new of course so maybe we are not talking about the same thing and (kind of) software.

If we look at this from a mere technical perspective and/but also in relation to hoe XXHighEnd achieves her goals (with many contributions of yourself) then all minute things happening in there will be thrown out with one big blast. So to give a virtual number : say that XXHE improves SQ by technical means with 0.1% then the means you are referring to will degrade SQ by 10%. IOW, you must completely forget that such software (also hardware) will be able to sustain the SQ you are used to and chose for yourself (by settings etc.). However :

It is one large mixed bag of apples and oranges because we are talking about completely different kinds of "sound improvement". I mean, say that XXHE is able to more accurately reproduce the music then what is it worth that the time alignment of two speaker drivers are so-so and can be improved upon by some means which debunks the usage of XXHE all right, but which is an improvement in itself. I mean, I did not compare ...
(but I even can't if we're talking about time alignment because my speakers have that inherently arranged for (it can only be destroyed).

There is so, so much more to say about this, ... undoable.
But an example for you could be that the Orelo MKII speakers makes used of DSP only for the bass (under 240Hz or so) because I explicitly only allowed it for that frequency range, which is all related to the sampling speed possible of such DSP hardware and how otherwise the higher frequencies would be destructive for our fine DACs to begin with. Or, how for example Dirac (possibly you refer to that) allows for a (recording) sampling rate of 192KHz max while your DAC already outputs 384 and mine 768) and while *also* not even more than 20KHz is output by that software. Conclusion of only the latter : forget Hires.

Only pure in-software (which Dirac is too) solutions have a theoretical chance (because there's actually no sampling rate in order), but the first thing that incurs for is a D/A converter per channel. So if you have two speakers and Bass + Mid/High then this is 4 D/A channels (and 4 amplifiers). You have Bass + Mid + High ? then 6.

The (preliminary ?) conclusion is that you can only make it worse with relatively low money and with high money there isn't even a good solution (but it could be made - even by yourself with creativity - don't ask as I am not that creative, haha).

Dirac would be the only one which works with XXHighEnd and the sound is ... .... .
(I tried it).
Maybe my standards are too high ?

Kind regards,
Peter

Thank you very much Arvind.

OK Michael, I am afraid that by the time you're back behind the keyboard, we didn't communicate much today. So in case you still have 14393.0 running for real (and by my means of observing please), this topic could help you : A secure way to prevent Windows 10 , updates on the audio PC. Please keep in mind that this is only one of them / the possibilities and it is not exactly your situation, but it may give you some pointers. I think it is also a good idea to read the sequence of things to do once more (Install Guide "addendum") plus my today's first post. All is quite exact untill you blindly know what to do - it just is so for the moment. We just don't want to mess up (which is relatively easy).

Kind regards,
Peter

PS: That link I gave is not to leave you be with it but to leave you with something for the day.

OK, first things first now.


?

Peter

And ... Your 14393.0 could be upgraded to whatever you don't want.
Does XXHighEnd still show 14393.0 in the main screen after pressing Clear ?

You-do-not-want to connect the Audio PC to the internet.
But I think you just did.

Juan,

Strange question : do you have the problem (can't make a connection any more) in the first place ?
I mean, I don't have that Group Policy setting either ... in 14393.0.


Now I don't know what you are referring to, but means applied via the Group Policy Editor usually (or most often) won't let apply themselves via Registry changes. Read : they are a combination of appliances (at the same time) with special rigths required. IOW, I don't recall many tweaks which usually require GPEdit that don't need special (API) functions and most often it is a lot of work to get them going.

N.b.: In a Home version we can't even perform GPEdit (it isn't there).

RDPW is such a (very smart) program and all it does it allow RDP where it normally is not allowed. It is in there but not allowed. We need to pay more first.

Peter

Juan, maybe the opposite;
If you engage that Multi User option (this is an option in there somewhere IIRC), then now people can log into your PC and you wouldn't even notice.
Quite smart eh, for vulnerability.
Ahum.

Peter

Michael,

Something else is that you told me that you were able to boot from RAM. OK. But now knowing that you didn't arrange for the RDP connection, this is quite not what the install guide tells you for the sequence of matters. So it is quite possible that now you are in all of the wrong modes where nothing will install and nothing is persistent either (RAM).

Boot into Normal OS, BASE. If you are in MinOS RAM right now :
- Boot into the BASE version.
- Boot into Normal OS.
Now you are in normal OS BASE.

Peter

OK, I see that Anthony did point it out for sure. But the mistake on your side is made very easily because both main entries I refer to look mighty much similar.

Juan,

I didn't look at the Policy screen(s) myself, but I know there are two main parts in there. One for "system" or something and one for "users" (or something). Are you sure you investigated both parts ? (not that I saw ths advised to you, but that's why I do it now ). Maybe I am not even right with it, but ... please investigate it.

Regards,
Peter