XXHighEnd

Hi Peter

I had this problem last night, for the first time in years.  Here's the rundown:

• -2.07
• -Minimized OS
• -Unattended
• -Ignore my sig settings.  I've been running 2.0x close to default settings to attempt better xxHE's reliability (which I'm sorry to report has not been good at all, sorry I've just not had the time to report on it)
• -My normal way of playing is also to select several individual tracks and hit play, via click and ctrl-click or shift-click using a mouse.  This could be important.  And so I was doing this prior to this noise burst incident.
• -I've been running with the start-playing-immediately setting because I've been using the AI filter a lot lately, and this setting is the only workable way of using AI. (AI is often best with an OS DAC.  This contradicts what I've written in the past, sorry, as of this date.  Oh,  and for this reason please keep supporting AI)
• -Loaded a CD of classical music with about 15 tracks (Phillips Sleeping Beauty and full Nutcraker Suite if you have it, CD#2)
• -I selected a single track part way into the CD, hit play.  xx then selected all of the remaining tracks and started playing
• -About three tracks in, in the middle of a track or closer to the end but not the end, super loud burst of noise, louder than playback volume
• -I soiled my pants
• -Luckily I had the remote in my hand and quickly hit mute
• -I then watched xx to see what it did:  It stopped playback all on its own, and came back to attended by itself. 
• -I then rebooted computer, DAC, and unplugged/replugged USB cable on both ends several times and restarted everything else again with no problems.

Oddly, prior to the above incident last night, xx had been running without any problems.  Sadly, this is not the norm.  I normally get all kinds of unreliable behavior, for example, stopping playback after the first track in unattended, hitting play won't start playback (mouse),  the dreaded "This error should not happen please restart xxHighEnd,"  which keeps popping up as I try to shut xx down and interferes even with shutting it down because it closes the UI, etc.  But not last night.  Instead, I got the noise burst.

Hi Charlie,

Thank you very much for this extensive report.

You did not change Q or SFS settings recently ?

Did you find that message with "24 bit Crack Detect" on your screen somewhere, after playback had stopped ? If not, it is very probable that it was your DAC (or interface to it).

Let's also keep in mind that those who announced themselves (in this topic) have the issue with 2.08 or 2.09 and not prior to that (like 2.07). And even that possibly is not the reason because for me it is far more likely that it is the changed SFS (and more) settings people use since 2.08.

The reliability issues you have ... what to say. First off, there is totally nothing instable whatsoever. BUT, you use AI and it is for a reason I want to deprecate that. The way it works it just "unworkable" no matter you think it is. For example, you start playback, the conversion starts under the hood but you press Stop already. That conversion keeps on running though and when pressing play again, nothing will work any more. It is just an example of so many more problems in that (AI) area.
The least you should teach yourself is stopping the sound engine (Engine3.exe) before playback, which you can do by clicking at the blue led in the right hand border (it will go dark after that).

Kind regards and sorry about your pants !
Peter

Hi Peter,

No I wasn't using AI last night at all. 
Further answers below:



Much less for 2.07.  I tried leaving defaults as much as possible.  For example, I left Q1 at 14/1.  I didn't touch SFS.  But I did set "start playback".


No.  That is possible.  But it doesn't happen with HQplayer, which I use more frequently than xx now, due to the reliability issues.  Also, JRiver is flawless as well. 


I think my SFS is like 150 or 120.  Whatever the default is.


Yes I do that.  I use Kill as my stop button once xx starts acting up.  In fact, I was going to ask for a setting "stop button unloads xxEngine3.exe".  Possible? 
Otherwise it is a pain because the kill button is so far away and I use a logitech keyboard with a trackpad; quite painstaking to move long distances and back.

If others are not experiencing problems on a nightly basis then it must be something I'm doing or some settings combination.  It could be my PC.  But I doubt it.  It is an xxHighEnd PC spec PC.  Plus, I'm only getting back to xx now.  I've been using mostly HQPlayer for months without a single problem. 

So it is probably how I use xx in combination with my settings.  Or it could also be how xx interacts with my Wyred 4 Sound DAC in KS mode.  I wonder if going away from KS will restore reliability.   Hmmm,  for HQplayer I use ASIO I think.

I'm part of the problem because I've not asked for help.  Very little time these days.  Deep down,  xx is my favorite player.  I'd love to get back to it fully.  Today I installed 2.09.   


All clean now!

Thanks Peter,

Charlie

(I moved this to a separate topic)

Charlie - a short and quite useless response just because I can't make up any longer (and correct me if I am wrong) :

I don't see how your responses to mine are relevant - but it is difficult to really see (through). You start out with "No, I wasn't using AI last night at all". This suggests that I stipulated that AI is causing the noise. I did not anywhere.

I do claim that AI is unusable for stability reasons, but you seem to avoid just that - or like to ignore it which is human.
You did not explain about "stability issues" outside of AI. I just can not make up what you are talking about now. This includes :


Of course it doesn't because the message is from XXHighEnd. But in the end you respond to me telling about the DAC being a possible cause and *then* you say this ? now all is beyond me because it happened to you ONE time in a million years and besides all you are in the middle of a topic which is about 2.08/2.09 so you can't be talkin about the same issue anyway, if there is one anyway. :) (but say there is one).


It doesn't look good that you don't know this. And the default is whatever you set it to yourself (could be 3 years back).
For a new, fresh install the default is 2.00 I think (maybe 4.00, depending on how it was for 2.07 vs 2.08 or 2.09).


Not really in combination with the Straight Contiguous Memory setting.


I use a tablet and drop my finger on the led.  :)


Good thinking. HQPlayer does not support KS. But your descriptions too much lead to "inherently XXHighEnd" and a few pilot errors. But "pilot error" is easy to say for someone like me who just "knows" what not to do. Just saying !

Kind regards,
Peter