XXHighEnd

So:

- Windows 8.  (Still won't run on Windows 10, correct?)

- I initially installed to a RAMDisk, but then got the message my activation wouldn't last if done on a RAMDisk.  I then installed on the internal SSD and activated that.

- After that I copied the 2.01 folder to the RAMDisk (leaving the SSD installation in place) and tried to run the copied version from RAMDisk.  But I got little error messages about the DAC used previously not being the one selected currently (not so), and the XXHighEnd in the title bar flipped back from red (activated) to blue (not).  So I went back to running from the SSD.

- These are the two problems that are now occurring when I run from the SSD, as well as I can remember while not at home (too late last night to write this then): (1) When trying to play minimized OS and Unattended, the OS logs off to the Login screen.  (2) When trying to play, if I remember correctly, with minimized OS but not Unattended, the UI shows the track playing, but there is no sound, and when I stop XXHE I get an OS message that the sound device (driver?) has been deactivated, and do I want to troubleshoot it?  This is with kernel streaming selected.

- Best to blow everything up and install again?  (Though I'd like not to lose the activation.)  Or something short of that?

Hahaha


It does over here (tbh since yesterday) but if Windows 8 is giving you troubles - not for you, Not yet. :) :)

So Jud, all I see or think to recognize is that you are using W8 for the first time;
First culprit I see is that you are running Windows Defender and it is that what signs you off. I must look up the topic which tells about how to shut off Defender, which is not necessary for some W8 versions, but for few it is (and for W8.1 it always is).


Strange. But with Defender being actively monitoring and knowing what I do with all the (services) sh*t, maybe nothing is strange.




It is highly unlikely that this is "not so". Now combine the two ... ;) (but put in the correct sequence)

Idea :
When you're in Normal OS Mode you have selected a Sound Device which is WDM (WASAPI) and which is not available in Minimized OS Mode because you set WASAPI to shut off. Now your sound device will be a different one and it is not your DAC. So you hear nothing.

I think easiest (least unsure hassle) / fastest will be to start all over. That is, when currently you are not activated, of which you are afraid you will lose that.
ahum
So :


:nea:
If you are still activated when running from the SSD, it will only be a matter of having your copy procedure right, which I guess you have not ? What about the copying being done from a wrong (source) location ?

Peter

Hi Jud - I put the Defender stuff in a small Tutorial :

Windows 8 Tutorials - Shut off Windows Defender (http://www.phasure.com/index.php?topic=3222.0).

Regards,
Peter

- Actually it's not nearly my first XXHE install on Win 8.  More like the 5th (but this one has its own folder - within the XXHE directory - as instructed).  I have had Defender shut off since I first installed Win 8.  Will re-check....

- I always select kernel streaming when doing the initial settings on install, so XXHE should not have been sending messages related to the selection of WASAPI.

- Strange about the copy procedure.  Waited until the SSD installation was activated and just copied the whole 2.01 folder to the XXHE directory on RAMDisk.  Anything special to do besides that?

- Don't mind losing the activation so much, just didn't want to bother you with the refund process.  But as I'll probably just be blowing everything up anyway, I think, unless the sound quality is a complete and utter disaster, that I might prefer to make the next installation on Win 10.  I've always disliked 8, and only kept it around for XXHE.  Anything special regarding installing on 10?  Is it best to install on SSD and copy to RAMDisk, or vice versa?  And anything special about copying, or just copy and paste the whole folder?

Jud,

The refund process is super easy. Less than one minute of work. So please don't be bothered by that. The typing in this post so far already took longer. :)

About the copying :
Maybe you don't copy all of it ? So your XXData also belongs to it, although I'd have to dig whether it can influence (but to be on the safe side I say Yes and anyway I copy it myself as well).

What could be more likely is that it looked like you were activated, but in the end are not. And not because your are color-blind and mix up blue with red, but because the procedure obfuscates (on purpose). Anyway, it will end up in definite-blue when not activated.

The other situation I desribed the other day : "you" mixing up what's started from where. So if you *think* you start from the SSD but meanwhile start from the RAMDisk after all, there you have it. And when the RAMDisk is not arranged for yet (still contains the old version) it van go back and forth really (I experienced that myself abnf figured that only women would find such a thing logical - I could not follow). This is also how the warning came about for Activating on the RAMDisk.
Best is : Move everything out of the way (delete the RAMDisk folders explicitly) and reinstall. And only when all is up and running, create the RAMDisk again.

About the signing off ... I really seriously can't tell when you did not change anything. I (XXHE) don't do anything new in that realm ...
So let's keep in touch about that.
Side note : Shutting off Windows Defender does not help in the situations I know of. Only the procedure I described in that small Tutorial doesn. But if you weren't pestered by this before ... then what. I forgot the process or service name of it (windef or so ? - but recognizable), so you might look for it.

Peter

About the logging off - I did allow Windows Update to install a bunch of updates, and you know no one can screw up a Windows installation like MS itself can.  So it's possible something I switched off got turned back on.

As I mentioned, I've never liked Win 8 as an OS, so I will probably forge on and try to install on the Win 10 preview.  (I'm on the fast update track, so the build changes every week or so.  Should be fun!   :) )

Jud, I forgot to tell :
W10 will be supported in 2.02 if all is right. But maybe later (depends on possibly other emergency updates needing to be around first).
So at this moment (2.01) W10 can not work because it is not recognized (and all sorts of authorizations fail).


The fun is that I think it sounds better. :yes:
But I can't compare really yet because it is all SUPER buggy and MinOS is a challenge still, plus Unattended with Services Shut off kills the LAN and more and all sorts of things which should not happen.
One thing very nicely works this time though : Reverting to a Restore Point while in MinOS and nothing works otherwise any more. :heat:

Peter

Last night I blew away the prior installs and reinstalled clean.  There are still two bugs remaining (not those I mentioned yesterday, but others I considered minor in a relative sense so I didn't bring them up):

- Minimized OS, unattended: Starts fine but within ten seconds the volume stops completely.  Since there's no UI I don't know whether it's stopped playing or is still playing but no volume.

- Minimized OS, unattended off: This is perfectly OK until I try playing unattended for the first time.  Then all subsequent attempts to play with the UI showing prior to a reboot don't work.  Playback won't start, and there is an odd thing going on with the UI where there's a sort of black "phantom loading progress bar" that progresses from left to right near the top of the XXHE UI.

So that's where I am now, unable to use 2.01 in minOS unattended.

Doh ... And I just have been working on that issue exactly the same but in W10. And I already couldn't imagine how it would be W10 related, already because I saw similar before.
But odd : I solved that. Ehm, thus not really.

This is about the OSD Running Time; deactivate the "as bar". You can leave on the Running Time itself. Now you can play (sound doesn't stop either). And after this works you can set the As Bar to On again, if you want. And then it works.

Beats me as much as it just did you. :swoon:

Peter

Thanks Peter, that worked, though things are not completely bug free.  A couple of times playback stopped in the middle of songs, and another couple of times playback wouldn't start when unattended.  Also, unlike what you found, as soon as I put the "As Bar" back on it cuts out after 10 seconds again.  But most of the time it works, and I've got it running from a RAMdisk now.

Wondering whether the custom filter is mainly for people with NOS1/1a and Orelos....

Since I have larger fonts set, the UI is pretty bad, with text overrunning many fields.  I will have to adjust that.

Does 2.01 work at least somewhat now on Win10?

Hi Jud, can you show me a picture of that ?


No, why ? But it would be best for NOS DACs because all is super "fragile" (tuning is very precise and the slightest interference will kill what I put in there (about the phase stuff and such)).


Nope, not at all. So no need to try ...

Peter

Yes, will do later.



Was thinking it might help with, e.g., DSP for bass or something.  Both the DACs I have are delta-sigma, so no PCM upsampling but the result would be run through a modulator.  I imagine that qualifies as "the slightest interference."  ;)

XXHE screenshot attached.

Ah ...

What about setting the Scaling smaller ?
If you set ity to 1.7 it will be the same as it was (1.186).

Peter

Will that affect Remote, or different settings?

Actually - This *is* set to 1.7, I just checked.

So I tried 1.5.  Everything looks exactly the same, no change at all.

:oops:
You are correct about the 1.7. The old one was 1.4.

But no difference at all ? hmm ...

Hi Jud,

I wondered ... are you (still) able to mimic this at will ? If so, how ?
I saw it myself but for the life of me I can let it happen any more. It is as if this happens right after an install only. At least that is where it happened to me and I recall something like having problems with it after each boot.

Of course I now like to solve it, but ...

Peter

Hi Peter -

I'll check tonight if I have time, otherwise in the next couple of days.

Answer unfortunately is still yes.  As bar on, sound cuts out in ~10-12 seconds.  Off, it stays on as long as I like.