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?)



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.

Here are the remainder of the recent log files from that session / date code.

And to confirm, no my system never BSODs.  The last time was when you introduced Q1factor and I tried Q1factor=2 and got a huge crack followed immediately be the BSOD.  This was for sure with SFS=60 on Vista. 

Thanks so much for being attentive to this.  Much appreciated.  We xxHE users are in a bind: Other players we've tried are unplayable / frustrating in comparison, and so if xxHE becomes frustrating for any reason, then there is only frustration left.

I also have the x3 and x3pb if you need them.

No problem with song length, at least apparently.  And not so fun anymore.  This time the problem is big loud gaussian noise, not music, going to only or mostly the left channel.

EXPLANATION
After randomly selecting HiRez tracks using the randomize function (first then n) and after playing for a while, say one hour, it was too many Sam Cooke tracks in a row and so I hit alt-x while track 6 - "Just for you" was playing and also coming close to the end of that track,  xxHE came up as expected, than while transitioning to track 9 - "Ill come Running back to you", instead of that track I got very loud / ear damaging / and if for a long time perhaps tweeter damaging gaussian or thermal noise like RANDOM fullscale data going out through the left channel.

Instantly I hit mute on DAC first thing, even before I clicked on Stop in xxHE; then I saved the log files;  then I told the OS to restart.  And while shutting down, I got the blue screen of death, luckily while DAC was muted.  The BSOD probably happened as the OS sent audio data out to the DAC.

Not fun.  We are into potential ear and tweeter damaging territory and so please check the code carefully and perhaps do some testing of your own.  I won't be able to test this all alone...  as these are new and expensive speakers we're talking about (and not to mention irreplaceable ears).

Later in the night, very late, I turned the volume down on the DAC, way down, and attempted to repeat the problem and it did not repeat.  Perhaps I entered alt-x too soon in the song and should have waited for the last minute or 30 sec (perhaps while the next track is loading is where the problem can be repeated).   ...or this could have to do with "vista can't do SFS=60" and I have it set to 60 per your last request.

So far so good.  Three hours tonight, with mixture of resolutions, and ending with all hiRes for about 1hr.  That's not definitive, but it's a good start.   Keeping fingers crossed.

The only anomaly I encountered you already know about, and that is that alt-e, followed sometime later by an alt-p, did not continue from the same song, and instead started from the top of the playlist.  But that's another problem and minor in comparison.

Also not new with this version are some messages I've been getting since about z83a ...everytime I hit alt-c from Unattended the pointers set up correctly in Nice Stuff, but I get two messages.  One is something like "91: Object could not be set to instance of an object: c:xdata,"  and a second one about c:xdata but I don't remember.   Perhaps this is due to logging?   Still alt-c works.

In any case, thanks for this big step forward!

Fantastic!  Thanks.      I'll try it right now  (keeping the volume low at first and keeping my finger near the DAC's mute button!).

Ahhhh,  this is great news.  Some progress somewhere.  Thanks.

To summarize the best procedure for gathering log files, it's best to hit alt-x and then click on Stop (not alt-s), and then send ONE extra xx file.

One last point I'd like to make is that in these examples the files were hiRes;  but it has also happened on 16/44.1 material, which I admit is strange.  Strange because if it is a miscalculation based on assuming 44.1/16 when it is really 24/88 or 24/96,  then what is being assumed when the source material is 16/44?   ..mp3?

The previous was the repost you asked for.

This is for a new instance from tonight.  The song is track "07 What a little more rain" by artist Sara K, but actually the disc was Chesky's Greatest Audiophile Recordings or similar (not labeled as Sara K).

Here are the two prior.

Otherwise, did you answer my question about the proper keystrokes or mouse clicks for obtaining these log files?   Because I am running unattended, I have to hit alt-x and alt-s.  Does the order matter?  Then do I quit xxHE?   Obviously, I didn't do it right or I wouldn't have to be redoing it now.

Here you go with 'd.  The song that played short was Santana Abraxas, track 1 Singing Winds and Crying Beasts.   (@ 24/88.2)

The track list was from random selection from the Nice Stuff gallery.  (Which has in interesting "feature/bug" which I may mention at some point in another thread.)

There are two XX files because both were very recent and I wasn't sure which one was right.  I think the one to look at first is XX-20130326-214814.log.

For next time, when this happens,  To copy the log files I have to alt-x, alt-s.  Should I then quit xxHE?, and then go looking for the log files?   ..or do I just keep xxHE loaded?

That sounds right, I remember that now, sort of.  The funny thing is that I also remember intending to load the entire list again, and I remember waiting a long time and it starting after the wait.   But as I said, I also remember selecting only the Beck album.   If that's what the log shows, that's probably correct.   Perhaps I did both (started it three times, why not?). 

This might help:  If I selected only the Beck album, then that was with the mouse cursor with click and Ctrl-click like I usually do and with the entire list still up there.  The tracks that followed and were unselected started with Bonnie Raitte, also hiRes but might have been 96k.

I'll try 09.z-8-3d now.

No.  Both were 88.2/24

I purposely had queued up albums of mixed rates.  Never touched anything and just hit play.   That playlist made it beyond Bonnie Raitte and into 16/44.1 material with no problems.  But i was very uncharacteristically listening in the background while working on an electronics project...  and I thought, wow, that Beck album is very good, I'll listen tonight intently like I usually do from my listening chair.  Then l finally made it to my listening chair to really listen and that's when I started playing with the mouse cursor and such, and restarted the entire playlist, now at higher volume levels.   And as you can see, it only took to track 2 for the problem to happen.

I agree that it is a lucky coincidence that I played it twice.

BTW, I'm using 4x arcPreduct and PE.

But it seems that the problem happens more often when I start stopping and restarting as I did above.   I normally select portions of an album with click and Ctrl-click.

Finally, error with logging turned on.

The album playing was Beck - Sea Change.  The track playing was track 2. Paper Tiger.

Attached are the log files.  There are four files in total and two them are XX, the smaller XX is the more recent and MUCH smaller than the other.

Well, if it skips to the next track than this could  be the "behaving like AB" problem, or can be related.  I've never timed it, and in my case it varies for sure, but 4 min is right in the range.

Wow...  2 hours listening and with sfs 60 and logging turned on and so far I could not recreate the problem. 

I'd say that it must have something to do with whatever or one of the changes you made for z83a.

And, btw, now sfs=60 is sounding better than sfs=2.  Smoother, still detailed, and much better soundstage and far fewer ticks.  Go figure.