Can it be so that somehow you missed a track that was about to play ? So, all what I see is that your mentioned (to come up) "I'll come running back to you" was the one lastly playing, to be followed by "Lucky Bounce" from another album, and that one is 24/96 ...
Not quite. The last track that sounded like music was 6 - "Just for you" by Sam Cooke. Therefore, if the log file shows that the last song playing was 9 - "I'll come running back to you", then it was probably a reversed byte order or some strangeness. Actually, I don't doubt that the data for the loud gaussian-like noise was "I'll come running back to you", it just didn't sound like music.
Otherwise, I'm not quite sure what you mean by "Can it be so that somehow you missed a track that was about to play ?" above. If you mean that xxHE skipped "I'll come running back to you" and instead went directly ahead to the 24/96 "Lucky Bounce" from another album, then I understand what you mean but I didn't select that. I didn't have time to manually do anything before the big bang.
On the "24/88.2 running into 24/96", that happens here all the time. Maybe not every night, because generally that happens with random playback, but surely at least several times per night with random playback. Still, I will concentrate on that.
(speaking of random playback, where can I find an explanation of what "First selected, then per n tracks" does?)
Question : What causes you Clock Resolution to be set at 1ms under the hood ? (you switched off the forthcoming of the message about this)
Nothing I ran. This just starts to happen after a while. killing engine3.exe sometimes solves it, but sometimes memory is left in a less than perfect way after killing engine3.
