Thank you so much for your efforts, Stanley.
I recall this situation from quite long ago, and it is not easy to solve on my side. But I will put it on the ToDo list anyway.

Best regards,
Peter

Hi Arvind,

Yes, that should be fairly easy. But the point at this moment is that I already started working on the 16/44.1 MQA issues. So if I undo those changes (where I ran a kind of stuck in) then it should be easy. So maybe I should do that ...

Best regards,
Peter

Hi Stanley,

I have the hunch that this can be related to two the same track names (file names). Thus supposed that both are named

02 - My Favorite Things

(upper and lower case does not matter, and the file extension (WAV/FLAC) also doe not matter)

that things can go wrong.

Could that be the situation ?

Best regards,
Peter

Thank you Stanley !

Pressing Next ... was this with Attended Playback ?

Regards,
Peter

Hi Arvind,

Couldn't that be the same problem as described here :  Playback jumps to next track prematurely ?
The basis for that to be the same, should be an album which is 44.1 or 48 (not higher). Are those of this issue that ?

Best regards,
Peter

Hi Stanley,

It would be good to have an example of subsequent tracks that would copy the behavior; I have very such regularly mixed tracks in the playlist, but never run into the problem you describe. I surely can imagine it, though.

If you rather not take the effort, I am fine with that. But otherwise the example should be very literal, so indeed it would happen over here too.

Kind regards,
Peter

Mani - wow. But are these speakers so sensitive then ?

Keep in touch with that "boring" sound. I mean, this can end up to be literal. I have that quite often (with wrong settings or wrong cables) and then each 6+ minute track starts to sound the same all through. So as soon as that starts to occur, you are on the wrong track.

So the current must be OK. But I wonder what a just a tad to low voltage (is volume output) will do to the sound. Maybe nothing.

Interesting !
Peter

Thank you Arvind. I think that was the known issue. I will hopefully solve this tomorrow.

Regards,
Peter

Arvind,

Is "unpredictable" a new issue ?

Regards,
Peter

Oh Colin, I never even thought of that "solution". Prize of the day ! (make that month).

Don't ask me whether the album sounds worse than normal RedBook. It may ... Maybe someone can check. You would need a local copy for that and a 44.1 which says it is MQA but shows 16 bits (or indeed the 1411 number). Never think that you can Prepare the MQA and next compare with a previously Prepared Redbook, because you will lose the latter (as stated in my previous post).

Regards and thanks !
Peter

Hi Arvind,

Yes, that is what I expect. The problem may very well be this :

Lately, Tidal is converting all the existing normal Redbook albums to MQA. This is as fake as it can be, but it is also not formally supported. Thus, this is not MQA of any good quality at all, and you can see it by them being 16/44.1 and not 24/44.1 (or 24/88.2 or 24/96). Because this is not MQA really, XXHighEnd does not know what to do with it properly. I have been working on it already, but it is a bit of a tough problem. PLUS (mind you !) you just don't want these at all**. OK, so what I have been working on, is that you can see that they are fake (but also that they will play anyway).

**): With the notice that the old RedBook has been removed and they the ID of them is still the same (!!!).

If you re-Prepare these and you had the normal Redbook version from earlier, you will lose that version and it will be replaced by the MQA fake sh*t.

I think that at this moment you will be able to recognize them largely by the label telling 44.1. Thus the album in the picture below with be fake MQA by a vary big chance (but you will only know definitely after you have it in the playlist and will see that it is 16 bits).

Hard to check anyway at this moment, because of that result of one album only, at this moment. Sorry for that ...

Peter

Are these MQA albums (or tracks) ?

Hi Arvind,

So what does *not* work fine then ? what did you actually change to let it work ? (you too said you used copy-paste from Tidal)

Thanks,
Peter

Do you still see the 48GB of memory ?
(like the below shows all my 32GB)

Mani,

Well, a logical reason would be that there's insufficient memory. Thus, just all together (like only one DIMM of 8GB suddenly at work).

Remember that the Max SFS is determining the allocation. So set that small too (or set it to equal the dynamic setting).

- Maybe it is related to one of the other settings you changed ? (and you told to Save (to the SSD) at rebooting ?

- Maybe your SFS is plainly too high ? (try 20 or so)

- Is this the Mach II or Mach III ?

N.b.: I have no idea whether memory can shut itself off for parts of it (like a HDD can do that), and that thus the contiguous memory really is not available.

You could exchange memory (all of it in one go) between your Mach II and Mach III. It is (about) the same and harmless to SQ when interchanged.

Regards,
Peter