XXHighEnd

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.

Hi Telstar,

I am sorry (maybe :)) but I didn't change anything. Why ? I asked you questions about this (other topic) but you never responded.
Maybe you can find it yourself, paste it in here, so we can work it out.

If something is not in the Release Notes, it has not been done (well, that's how it should be).

I have no problems with the volume whatsoever. But then I use it how it should (as explained elsewhere), which may not be what you do. Again, you didn't respond or explain.

Thanks,
Peter

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.

All of yesterday I was using volume and don't recall ever having errors doing so.  Hope it works out for you Telstar
edit
I do go real slow. (AHK) push alt U/alt D ...wait for vol to change... then push again.

Hahaha, almost correct ! You can't find the "topic" because it was posted in the middle of another one, which ... you just did again. I mean, it was me creating this as s "topic" for you (and myself :yes:), which only indicates the relative importance of specific problems being in their own topics.

http://www.phasure.com/index.php?topic=82.0 :)

Anyway, if you can describe what you do, I will try to solve it. That's about time anwyay (because it is not fool proof at this moment ... not calling you that fool of course :secret:).

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.

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

Hi Telstar,

I can't be sure what is going on with you, but to me you seem to be more and more confusing.

I TOLD you not to use that mousewheel. Or did I not ? Or did I tell you I fixed that ?
Instead you again create a post for it (which now has become this thread). Next I ask you for the details :


and next I receive nothing. Oh yes, I received an email with in there that you were not able to let it go wrong anymore.


That may be so, but see my last sentence. I obviously did not look in the log files because you said you couldn't let it go wrong (leaving me in wonder what to do with those log files then).
Did I maybe read it all wrongly ? perhaps, and in that case I am very sorry. But why sending me emails about this is in the first place ?
Here is your topic about it !

Then I recall - previous to this topic - you started this subject two times earlier, with similar result.


I don't think you listened much to what I said as many times about it. If you do this in one go (and it was YOU who suggested how to use it : at letting the mouse button go it will be effective) there is no problem. Well, I don't see you write anything special, with my conclusion that you did not work according this "prescription". So, I aksed you what you exactly do, and with this answer I cannot do anything.

What are you up to, besides bombarding me with the same from many angles, BUT now leave out this which you did mention in the PM :


At last that looks like important information. Why leave it out now, and instead come up with some less nice sentences and the wrong smileys ?

Btw, your log files indeed show "something"; I'm not sure yet whether I can make anything of it. Right now I'm not even sure I WANT to make something of it. Not without your very precise description of what you do. In here please. :)

Thanks.



PS : For the next time : The log files are those in the TemporaryData folder (subfolder of your current XX folder). But of course I've got them now too as part of the larger set you posted.

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.

Of course this by itself is clear. But the (or my) point is that this looks too simple. I use it countless times per day and never see a problem ? I know though, I shouldn't be using it right at the end of a track. Or, do it when a previous one is "pending" so to say. Thus, as said before, there sure are ways to let it go wrong, and it sure is time to solve it. But now, what is it what lets it go wrong with you ?

Ok, I'll have a look in those log files, and see whether I have questions from there.
One thing is clear : something must be solved. :)

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 Telstar,

I could have told it a few days ago already (when I examined the log files), but this is not related to "volume change" as such, but more generally the manipulation of the cache. The Volume Change needs that though, so to you it will appear as "volume change" going wrong.
Instead it can (or will) happen at any situation that allows a change to the playback settings, like changing the Invert settings (there aren't many more of these).

Unfortunately this is very tough to solve because it completely depends on the situation which happened "in the past", like in your case playing a couple of tracks, change the volume of one, play another couple, and change it again. I mean, it is sheer undoable to copy this (because each test may take an hour) so it must be solved in theory. I can also tell you that this particular thing happened to me two times in 4 weeks of time which (ok for me) is a reason by itself not to dive into it. Also please note it is exactly this I have been working on for over a month to get, well, right(ish).

With this I don't say it won't be solved, but I myself need loads of (log file) data in order to be able to (hopefully) see the line in it. So, if it happens to you don't hesitate to post the log files of it, and the more I have of them, the better it will be.

One thing though : At least the last time this happened to you, you got a rather normal and clear message about it which reads :
Unexpected situation at Remote Command; Playback must stop
If you just tell this, it saves me 90 minutes of looking for something you could have spent 5 seconds on (just tell it). So I not only want to know exactly what one does, but also exactly what one sees. In addition to that, I don't see the reason in describing such a thing as "an error", while an error has a description.

Ok ?
Thanks !
Peter

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

Like a constant repeat of the last buffer contents you mean ?

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.

Now it happened again, on my other computer, without Console and all that rerouting stuff.

It is a "remote command" error as the last time. The interesting thing is that is on a different PC without anything between xxhe and the OS.

Ok, thanks for the log files !

But it is not related to PCs or anything. Just a general bug. Not related to volume either. Remember ?
Thanks,
Peter

I had the suspicion that my setup with Console, etc made it more commoin (>50% of the times)
Now I think is much more common with the 4x arc upsampling on. I got it another 3 times in a short time.

Oh, I just wanted to ask additionally : how may times did you have it since the previous time (post) ?

Me 1x (at using a Volume change approx. 10-15x per day)

But please keep in mind not to use it when it's still "busy" with the previous one (OSD time is yellow or white), or at track boundaries; I wanted to solve *that* for 0.9y-4 but left it for -5 afterall. :)

Btw, *if* you post one log file only, the XX is the most important. :yes:
Thanks again.
Peter

I would say close to 50% of the times that I use the volume. Never in any other case. I occasionally have a XXHE stopped working crash, but thats rare.


I never do that (and i'm still using only attended).


Fixed, I added the XX log.

Now, i'm in touch with SIMS support and hope they fix the asio drivers so i can get rid of that buffering issue. If you have some tip for me how to explain them the last fractions of second that is repeted endlessly when i pause or stop the music, it would be really helpful. Now i'm gonna record that, lol :)

Lil update.
I've been monitoring these errors. 100% are the "remote" type. They mostly happens at the beginning of a new track, when i change the volume to "normalize" it to the desired level. Even if i wait like 10s, it still occurs. In the middle of a track it doesnt seem to happen.

Ah, that is a god thing to know. And yes, you obviously use it in the beginning of a track (me too btw).

My count is still at 1, so trying to let it happen and solve it from there is a no-go. Maybe I can tweak it. I mean, I know it is going to happen, which is why you get the nice message in the first place (if I let it go without message things really go wrong).
I will try to do *something* in the tweak area.

But then the music stops (accompanied by the P-P-P buffer bug that Infrasonic is looking at).
I mean is not just the error window :)

This is solved for the next version (0.9y-5).

All has been setup completely different, and it can't happen anymore.
:heat:

 :clapping: :clapping: :clapping:

Actually no. In y-06 I still got it :(