No. What this does is completely crazy, but in order to ever understand what I mean you must try it (make a backup first).
Quote
The cool thing is that his environment can support XXHE
No way it can. Maybe I should have made a remark about that in that thread, but actually I don't care. The guy behind it is, say, a kind of commercial for his own product, and I could do that too. But, looking at "The memory player" as he calls it, this is only a thread to the existing one you referred to earlier, and this is IMHO over the back of others. It may be personal that I don't like that.
There is no single one way that XXHighEnd could drive another sound producing kernel because of the way it works. Besides that, think of it : where XX creates an environment for itself (Core Appointment, Priorities) the first it would do is destroy the environment of that "memory player" which it so carefully created for itself. No ... I don't think he ever tried.
Btw, might it be the idea that his player makes the sound of XX work (so, the other way around) ... that would be the very last possible.
On another note, I think what he is doing in the base is right. But also, it is the opposite of what XX presents : the most simple handling for the best sound (anyway that's the idea ). On that matter, please keep in mind that what's happening so far is the provision of tools so we can all find out what's best, later resulting in a "one setting" player (maybe with "tweak" button).
If you look at UnAttended Playback you can see what it is going to lead to : nothing but a wallpaper and only those services running necessary to play sound. You will visually see no difference with what happens today (like all the desktop icons disappearing), but what will be running is near nothing. This "AA memory player" implies similar. But now try and look how it does it. .