Ah OK Tore. No probleml not at all !
Peter

Hi Anthony,

Of course I am no Tidal expert, but how do we apply that link ? For sure not in XXHighEnd. Give it to Google Chrome brings nothing (but the Tidal Player in Chrome). And in the Tidal Desktop Player I wouldn't know how to apply it ...

Thanks,
Peter

Hi,

Some times I don't understand what's going on, on Tidal;
I have been trying and looking for 20 minutes what could be wrong with XXHighEnd that this album gives no result at all, and then I very coincidentally saw it in the Tidal player, used the Share link from there, which bring this :

https://tidal.com/album/78350437

And that one just works.
So Tore, does your link still work for you ? Does this new link also work for you ?

Regards,
Peter

Dear all,

To my surprise, this morning I found that the code which generates the Activation Emails, is not working any more. And so far I can not find the reason.

Below you see the PayPal screen with at the bottom a "Terug naar Webwinkel", in English something like "Back to Web Store", and this unsollicited change is already not a best because if you don't click that, nothing *proceeds* to a next required screen. This is the other screen you see below. That one shows your Activation Code, BUT, the guide how to apply it will never be sent to you (this is the now lacking email). And you can't do without it ...

This all means :
a. that you must copy - paste your Activation Code from the webpage you will receive after clicking "Return to Web Store".
b. that you must wait for me to see the payment coming in, which shows your email address;
c. and which contains sufficient data for me to manually create the Activation Email for you.

Also, let me apologise to those who could copy-paste the Activation Code all right, but who 100% sure ran into problems with Activation because nothing told you how to do that (the lacking email).

Regards,
Peter

Haha, thank you Paul.
It seems that everybody says the same, but everybody finds an opportunity to mention this in between lines in some topic. So you are the first with a topic about it.

Cheers,
Peter

Phew Juan ! you sure managed to make that a small thriller.

I think you can count me in for speaker (re)placement. Sort of.
What I found was that something was inaccurate while I could not find the reason why. So eventually I started thinking that possibly the speakers were not aligned to the cm and thus I changed things with measure in my hand.
From here I noticed a difference and also small improvement but after a month or so I still felt dissatisfied. Then I grabbed the IR measure meter I just have and did it really to my best capabilities, on the mm accurate.
And now I am happy again (I did this last step maybe 3 months ago).

So Juan, it is that you mention this and that it gives me a reason for my own somehow degraded situation, at first. Somewhere this started to happen to me, but with me weekly applying changes, it went unnoticed when exactly - and thus by what.

Thank you for sharing !
(and holding on )
Peter

Hi David - Thank you for your suggestions.

Your mentioned (too quick turn around) could only (theoretically) be related to Unattended; in Attended it's just track per track anyway.

It almost definitely is related to the new Volume (change) setup. And for example, with the really small SFS (like 0.1) the volume change itself hardly works and sound most of the time just stops (as I recall it).

It looks like possibly Ramesh as a way to mimick it. So I seriously hope he can !

Thank you all,
Peter

What I noticed myself yesterday at changing the volume after the GUI has been brought up (Unattended Playback commencing), was that clearly I ended up in another part of the track (maybe only 1 second further or earlier, but not "adjacent" as should). So this already looks dangerous to me ...

Peter

Hi Ramesh,


Can you eleborate on this please ?
So supposed the first track is automatically selected (is it ?), select it "again" would un-select it.

Thanks,
Peter

Ramesh, did you all these years play Attendedly so regularly ?

Peter

Hi Arjan,

Maybe it is not the best idea to cange the volume by means of XXHighEnd in that (Unattended) fashion. So if it happens you you like that only, then we can bet it is that (for your situation). Also, this is never tested of course. Also not by me and as you actually just told, when I'd try 10 times of course nothing goes wrong. So it should be used by a 100 people each day 20 times, and then we'd have a nice test base. But I am afraid you are the only one ...

Regards,
Peter

Hi Stanley,

Boot into the BASE of the OS you want to apply the 2.08 Upgrade patch to, and pase it over the c:\XXHighEnd\2.xx folder. In there unrar it.

When all set, boot back into the RAM OS again.

I am not even sure whether WinRAR is on that OS. I'd think it is. But if not : WinRAR.

Regards,
Peter

Joel, I think I may have a better response :

If you are now using another interface (and it looks like it), select the Kernel Streaming driver for it (KS: prefixed). Now you won't have the WASAPI message because you are not using WASAPI (WDM). This would even be better because SQ is better from Kernel Streaming (which your other interface does not offer).

Peter

Robert,

That other night I just changed the SFS to somewhat higher without having in mind to what exactly. Day before yesterday I found that I had set the SFS to 1.80 (so apparently I doubled it). This is also good for the volume change (hardly any stutter with this SFS setting) but it wasn't about that for me. A more friendly sound it was about (mostly related to MQA) and I think it helps for that.

Thank you for the feeback on the Oppo.
You could try to stop 16/44.1 playback, kill the Sound Engine (click blue led in the right hand border), select the 24/96 etc. and start playback.
This re-engages the DAC in a somewhat different way and it could be interesting to know whether this makes a difference (now no ticking).

Also revisit your own observation with the first track vs the second. You may have a different opinion on that now, which could be helpful, also to me.

Regards,
Peter

Hi Joel,

I think you're copying the last bit of a two-part message, the first part telling you the Clock Resolution internally is set to something else you denoted yourself (Clock Resolution is a setting you'll find at the bottom in the main screen under [ Q ]).

The message is harmless and can be avoided (about that, see the message itself). It is not related to no sound, as long as you click it away or avoid it (see message). Or set the Clock Resolution to the smallest mumber yourself.

The message can originate from WASAPI itself but only in more rare circumstances. It is more likely that something else hogs the Clock Resolution (setting) which is legitimate (just like XXHighEnd does it) but not convenient for our audio (because it is a SQ parameter).
With the notice you may have a Chinese programmed XMOS driver at hand, I would blame that right away (now the driver can more easily obtain its speed like 768 over USB). But don't let that disturb you - or at least not now.

The short message is : this is not related to not getting sound.

At each attempt in such a situation (of trying to squeeze out sound) kill the Sound Engine first (click lit blue led in the right hand border).

Best regards,
Peter