Q 4/0/0/0/0 has always been my favourite. i also dont like to move Q1/4 to anything else but 0 (i call Q0 the first).
Appointment Scheme 3 - works well on dual cores.

Your signature says 14/15/15/0/0.
I said to try 4/0/0/0/0 because the other Q can make the sound too smooth, less realistic. Q0=4 is my favourite, but 14 is also very good. If the comparison was this, no need to do another one.

Please try with Q settings= 4/0/0/0/0 and report back. Once I tried XMPlay and found it very similar to Foobar.

Yes, exactly.
But this happens with any player i use when i stop or pause a track. It's some bug in the quartet asio drivers.

Jriver sounds more or less like Foobar or any other wasapi player under vista.
Moreover Jriver volume control doesnt work (because it stupidly change the windows volume which is disabled when u use wasapi/kernel mode).

Yep, i never touch invert.

I called it error because the program crash with a red window and no sound (loud PRRRRRRR in my case thanks to the cr*ppy drivers). Next time it happens i'll write down what it says. I dont think it is always the same error, though. I'll take the logs as well.

The random errors that dont happen frequently are the hardest to catch and to solve, i agree, but are also the most annoying to me because they give a feeling of instability, unreliability of the software. I used vista since RC, I know what that means

I change volume normally at the beginning of a track to adjust it to my desired level (somebody called me a volume freak, i take that as a compliment since I'm able to spot 0.3db changes).
Also, I have "start xxhe during conversion" disabled.


I think that it has to do with the ASIO router and the timing (latency). It messes with something in xxhe ONLY with the volume change.
I cannot do without until a XO is implemented in xxhe


Thanks.
But no hurry, just really curious how the error is triggered. I thought you had forgotten bout it.

Hi Peter,

Sorry for the tone of my last post. I think there has been a huge misunderstanding from both parties.


I didnt use the mousewheel, i dragged the mouse to move the slider. I have always done like this to change the volume.


I thought it was clear
The thing about the mousewheel was a suggestion, it wasnt and it's not related to the crash.


copy and paste mistake, sorry.


This is what i do to change the volume:
With the MOUSE pointer i went on the volume slider of the ATTENDED window and moved the mouse to change it from -15 to -10.5.
Or to a different step. Higher or lower crashes anyway some times.
Is the description clear and precise now? I dont know what else to say to explain it


I copied everything beause from the logs I sent you with email (another misunderstanding with the error gone, it just didnt happen the next day, didnt mean it was gone) thought they werent enough to show the issue.

What does this mean? "because then it worked"?
In the logs i sent you the crash error happened two times. I guess it doesnt show.

It is RANDOM and happens like 1/10 of the times when i'm changing volume.


OK, i'm posting here. But I think i explained it several times Once more:
With the MOUSE pointer i went on the volume slider of the ATTENDED window and changed i.e. from -15 to -10.5. Pof!

Since last week, I haven't had the pleasure to listen to much music since then. Yesterday i had a couple hours and got the error again.
What I can say more is that I think it didnt happen with x- versions. and I think is due to timing/latency. If you fix the "change volume several times in one second" bug, MAYBE also my issue will be gone. Not sure if u did

Besides, I still have the start menu logo to disappear bug. I dont care much anymore since i have the bar hidden on the music pc, just FYI.

XX and X3: you mean the .dat files?
Version is y-3 +3a exe.

In the attached zip are ALL the files which have date of yesterday at about the time of the crash (except the wallpaper).

PS: underclocking makes no sense (u would have taken a slwer and chaeper cpu), but undervolting, if your motherboard allows it can save a few more watts.
Why? Because i can.

I have an E5300 dual core 4G of ram and W7 x64 Home premium. The machine is powerful enough to do real time filtering and crossover. And green to use like 10W.
So, both goals can be accomplished I highly recommend this kind of setup.

Did I? Dammit.
I have lots of things on my head and I'm listening to less music that O wanted. And that relaxes me...

Note that I use the mouse to change the TINY volume slider and that I hold it until i read the number i want on the left.
For the errors themselves, i'll post screens and logs later tonight.

I must have missed it and now cant find that topic. That's why I made this one

Will play something later this evening and send u the log and as well the conditions which triggers it.

Are the volume change errors fixed? I didnt read about it in the release notes.
Since yesterday is getting worse, basically any change of volume incurs to an error and i have to restart xxhe to be able to play.

I have logs that i can copy or send u.

4/0/0/0/0 always sounds the most right to me.