And Richard, mind the "Hires Audio" tags to the (right) side of the MQA logo. If they are not there, the decoder does not work on the PC where you search Tidal. So tell me if you see them ...

Peter

Richard,

I don't know what you all did or omitted, but notice that once you've got something running, you must throw out all MQA (so also the search results !), research it, prepare it and then retry.

And if that still does not help, try another PC ...
Sadly is it no different and it is not going to change either.

Peter

Hi all,

Today it is my advice to play as much from Tidal as you can before the service is going out of the air. Or at least it looks like this may be happening forthcoming. Maybe not this month yet, but ...

So start Preparing while you still can.

Peter

OK. Yesterday we were explicitly talking about the eerie good SQ we have here now with btw by now and each day a different perception from it. But I imagine that this is because it is all so fragile and on the verge of being completely real. Hence, all what deviates from that makes it unreal and very noticable for that reason. I also have the idea that my system won't do any more with less than an hour of "breaking in" for the day. After that, all can go to infinity. There's just no way things can sound bad after that period of playing.

Q1 = 30x40
Q3,4,5 = 1,1,1
SFS = 9.0 ()
ClockRes = 15
Core 3-5
No OSD Text
Coverart Wallpaper  in use
(NOS1 Driver = 16ms)

About the SFS = 9.0 : well, I just finally set it to that because 8.0 did not satisfy me and 10.x is too much of it (highs). I did not want to have the 9.0 because you can't (yet) but I did it after all. And now I seem to be overly satisfied. Anyway, anything close to 9.0 may not matter - I don't know (did not try).

About the change each day :
For me surely this is about the operating of my ears or maybe mood (not sure about this latter, but we know this matters too and although my mood is almost always good, gradations of it exist).
The last days I very deliberately did nothing about the "hardware" as such, when I found it to be less that the day before. So I have adopted the situation about mood and ears. And indeed, the next day all can be "100%" again. But it is difficult because this breaking in which is required each day is something to "bite through" instead of letting it destroy your mood and arrive in a downwards going circle.

When writing the above I feel like I just described how voodoo operates. And maybe it just all is a state of mind. Well, then I don't care. And you suit yourselves, haha.

I hope we're having fun !
Peter

Hey ...

Each time I go for something else than Q3,4,5 = 1,1,1 for me the sound is too gray. But mind you, this is all rtelated to the Lush. So with 1,1,1 there's more sparkle and the Lush requires that (for me). Maybe not with each and every other setting, but then I did not find those ...

Peter

Hi,

I think I have at least one very good reason : You leave the Audio PC in a state of XXEngine3.exe not running (this one keeps the memory allocated). So for example, when you receive an error because of sample rate mismatch ("Device can't play" and the like) and then think "oh well, let's call it a day", then tomorrow the contiguous memory required will have been eaten.

More situations of this may exist, like you killing Engine3 yourself (the Blue Led) or ... change the SFS. This latter is quite harmless because when playback starts XXEngine3 is killed and right after that (0.1 sec) restarted, but when you are low on memory right in between it can be eaten.

Btw, after the new Crack Detect procedure Engine3 is also killed.

People must know that it is the Max SFS which is rejected at some stage. Not the SFS itself. So the Max SFS reserves the memory ...

Peter

Johan, Joachim, this is VERY strange.
May it help ... my Audio PC runs for weeks and weeks without reboot and is used every day with (on estimate) 10 starts of Playback.

Do more people suffer from this ?

Thanks,
Peter

Hi Johan,

What is your Max SFS set to ?

Regards,
Peter

Arggh, I forgot to test this yesterday.

Hi All,

Day before yesterday I found that SFS=10.0 could be disturbing in really lesser compressed albums. Think Beatles (no Remaster). Too much highs in related to something missing right under that (lower highs ?) with a still very profounding mid. So say that this shows a gap above the mid.

Then I changed to 10.1 (because of someone proposing that - I forgot who, but thanks) and thought it was an improvement. Then changed to 10.2 and again found that working very well and I left it at that. Not sure whether there really was a difference between 10.1 and 10.2. But 10.0 really was too much of highs.
Yesterday I was happy with this 10.2 throughout.

It occurs to me that this is so much "on limits" that I can very much imagine that this can not work out the same on so differing systems as a whole, which most of us must have.

What keeps on occurring is how good the drums are. So much differentiation between everything (I am not talking cymbals).

Peter

Richard ... or install the NOS1 driver and connect your NOS1(a/G3).
If it is a Windows 10 then you will first need to shut off the Driver Siging (in XXHighEnd's settings).

Quite a useless remark :
On a side note (or not) I myself am unsure about how the "48" setting in the Sound Device can be related. OK, surely you won't be able to play (88.2 or 96) but why the Decoding (or MQA detection at first) would fail on this ...
But hard to try for me just the same.

Peter

Juan, you won't believe it, but I just had it myself ...
Why now ? why you now too ? ... no idea yet.

That Postcard(1).jpg file is the background picture I assigned myself to the background in XXHighEnd and which gets copied along with an install.

Preceeding that message I got a "disk full" or something like that, knowing that I loaded two more large albums in the Playlist Area and pressed Play for Unattended. So nothing strange to me that such a thing next happens.

I deleted nothing but let XXHighEnd do it's (deletion) job by starting and quitting. Now all plays again without hurdles.
See you in 30 minutes.

Let me know if it happens again. I will do so too.
Peter

Juan,

The (1) in it indicates that it came from an email.
Did you look at the JPG ? I mean what picture was in it ?
(if not, don't attempt to, because of ... virus ...)

Best regards,
Peter

Hi Juan,

Looks more like a virus, or a virus scanner to me (I know, both are a bit opposite). But that NOT assumed :

Did you check your Max SFS setting ? I found mine on 2850 yesterday and this does not really look right. It may consume all the memory and this is what you are thinking of to begin with (I don't know how, but ... ).

Postcard(1).jpg does not exist from over here. Only if you put it in there yourself. So maybe check whether it really exists.

The first message you showed I have never seen but very theoretically could spring from DEP (Data Execution Protection) - notice that Google shows me no proof of that.

It can be hardware too, I think.

Best regards,
Peter

So ... Yesterday I tried some huge combination buffer settings and thought it was quite fine. But technically not because of unsynchronized activities at the end of a track etc. (instead of the next track beginning, the last buffer of the previous track played again and more anomalies), but anyway it played. This was also my mistake to do, because now I did not like SFS = 8.00 any more. Also not 8.80 (worse I'd say).
Then I went back to my formerly chosen 10 ...

So right in the first second I notice it again. There is something (very) special with 10.00 going on. It is in the sense where I left off a track with 8.80 (paused) and proceeded with it where it left off, with 10.00, I couldn't even recognize it as the same track.
Highs seem to be infinitely more but also of explicit good quality (at some stage I measured and saw I was playing at 94dBSPL with is fairly loud ).

Don't ask me why this is.

As I reported a few days ago, I already noticed this. But now it was with the 705.6 Low filter (few days ago it was the High(est)).

Peter