Yes.  Will do.  (though I'll have to install irfanview on that machine and it is not on the network anymore)

And I'll change SFS MAX from 72 to 12 in case I want to play with numbers <12.

Perhaps premature to report, but last night I had no problems with SFS=2 and Mixed Memory (not mixed contiguous).

Thanks 

Peter, is this also true of my Vista version 0.9z-8f?

Thanks Peter.  I will try it.

I had no idea that SFS=60 was not possible and that I should keep it under 12 for 4Gig of memory @32bits. (I presume "not possible" means "not reliably possible.")  In all of this, I'd like to point out that the defaults for xx have gone from checking to unchecking "Include Garbage Collect."   Should I try checking it back on?

New data point: Like a fool, a week or two ago I attached the ground lead of my o'scope to a place on my amps that caused one monoblock to blow and I had to replace an output MOSFET and degauss my output transformer.   When something like this happens, all is up in the air.  It's like starting all over again.
And so I tried new xx settings.  I tried SFS=2 (thanks boleary who championed this, i think it was boleary) and got brave with straight continuous and it "works" now in that I don't get the dreaded "lower SFS or reboot message."   SFS=2 also sounds great, and for now I'll say better than SFS=60. 

So I'm already at SFS<12.  But with the above settings, I still get the "Unattended mode behaving like AB" skips in the middle of a track to the next track.

Next I will try Mixed Memory.

Thanks,  I will check out the spindown time.  I thought that I had no spindown time on any disk.   I'm almost sure they stay on 24/7 if I leave the machine on.

I'm still trying to find a way to repeat the error at will.  It happens almost every night, or several times per night.  Some nights it does not happen at all.

New idea: I wonder if this has something to do with it.  I sometimes get a vary small popup box that says "out of memory".   Usually I just click okay and ignore it.   Maybe it was something to do with this.   I have 4Gig of memory,  effectively 3Gig because of 32 bit OS.

Very frustrating problem.

I'm also back to no PE and no ArcPredict, just 2x interpolationas in my sig.   Makes no difference.   

I'm using SFS = 60.   Maybe I should try something smaller.   But I like the smoothness of 60.

Oops!   Sorry for the delay in response. 

No, in my case I never actually hit the stop button.   But the song / track stops playing and xxHE almost instantly starts playing the next song / track.   Sometimes it's hard tell that it made the jump to the next track, when the music is similar depending on the passage.

The stopping of this thread is similar to that of the other thread if the stops occur mid-track.

[ C ] Does not appear to help.  I thought so for a while. 

What does seem to help is to kill xxEngine.exe.  But that does not always cure for the rest of the listening session as I once thought it did.

Seems quite random.

Rebooting seems to help too, but is also not a complete cure.

I'm thinking that this may relate to this problem, still unsolved:

http://www.phasure.com/index.php?topic=2367.msg24576#msg24576

I bares some resemblance.  One difference is that the stopping is not exactly = hitting the stop button.  Instead, it stops and continues to the next song.

Sorry, that was a bad example.  Here's what sounds best with my 192K DAC, cables, amps, speakers...

Source	Output rate
44	2x
48	2x
88	2x
96	1x
176	1x
192	1x

...and there's no way to get it.

I don't know what you mean by "more complex situations" because a table like JR's covers all situations; and if not you can add more columns for like PE etc.

You may not need fx for deciding on 1x 2x 4x 8x 16x.  Fx can still be used for other things like gain control.

Not to mention that people with 96K DACs may need something like this:

Source	Output rate
44	2x
48	1x
88	1x
96	1x
176	0.5x
192	0.5x

And it's so easy to specify with a simple table.

Why not do a table like JRiver for specifying interpolation rates.   Something like this.

Source	Output rate
44	2x
96	2x
176	1x
192	1x

Without this, there is no way to enjoy top sound quality for each type of source material when playing back tracks of different sampling rates (as in random playback from Nice Stuff directory) without playback stopping with a sample rate change warning for 176 and 192K tracks.

Last night I didn't have this problem for the first time.  I didn't try extensively, but I did try a few tracks of different sampling rates and bit depths in a row.

It appears 0.9z-8 (version 8 for vista) solves this problem! 

Thanks and I'll report if this is not so.

Juan

Above, did you mean 8ms or 8KB?

This worked!  Many Thanks Peter!

 Sounding great too

Juan

If I choose Q1F=2, I blue screen in ancient Vista.  I've not reported this because a) vista, and b) old settings sound great.  I reserve bug reports only to those things I prioritize as essential for a joyful experience.

Yes, I've been living with this for longer than a month.  But one kill of Engine3 solves it for the rest of the night.   It's funny, I run into this problem only near the beginning of a session (new boot). 

I did not try [ C ] because immediately after you posted

Besides, there is no [ C ] while unattended (or I don't know what you mean).


For 44.1 I use 2x PE ArcPredict, and for High resolution I use a mix of that and nothing.  Sometimes I just set 2x PE ArcPredict and set fx to "on" , which does nothing I guess for HighRes materal.  (not quite sure)