XXHighEnd

Interrupt Mechanism out of order; Notify XXHighEnd development (Restart Playback)

I am reporting as commanded by XX-6. Guess what I did to engender this command. Trackus Interruptus.

-Chris

Tell me ...
(if that was a question)

The answer was right there. Trackus interruptus--a play on... ok nevermind, not fair.

I interrupted the track; tried to stop a track and start another. Tried it several times, always the same message. Happens right when stopping the track.

-Chris

Ah, so not at starting, but at stopping eh ?
Hmm ...

Yup.

Edit: Let me add to this already lengthy post. I'm using AntiImage for the first time (if that matters) because the Audio-GD only does 96 and 192.

Is that with Attended or Unattended ? (not that I see the real difference).

Well, what happens if you don't use any filtering at all ?
(I think I wouldn't apply filtering in your case).

Attended. OS minimized.

Interrupt problem remains with AntiImage off.

If I want to upsample, the track won't play without AntiImage on.
 

Ah, that thing.

Ok, thanks.

When you have some spare time, can you please post the XX, X3 and X3PB log files from the moment the message is on the screen ?
Please restart XXHighEnd just before that, so the log files will be more clean. Before quitting XXHighEnd maybe also use Off to stop the Audio Engine. Notice though : exactly this latter may incur for everything being ok. If that happens, just press Stop, and Play again. Then the message should occur again (if it happens "always"). Ok ?

Shouldn't you be sleeping ?

PS: I think I said something strange about the Play - Stop sequence for when it doesn't happen the first time. I mean, since it happens when you Stop ...

I'll send the logs eventually. It's a bit of a pain to do anything other than listen to music with that computer.

-Chris

Hi Peter.
count me in.  I have the same issue here.
Comes when pressing play.  I have to first push stop then play to avoid it.  Tricky that the message comes behind xx-window  ;) took a little while to figure out the first time. :)
I do not use minimize OS.  setup is pretty much standard.

But sound is awesome :)

Jan

After starting up with my NOS1 USB I got those anoying messages too.
But they disapeared after I did the following:
Reboot PC.
Starting to use "minimize OS".
Adopted some clock and memory settings, essentially those in Peters signatur.

Thank you Jan. Still strange, but good to hear from as many as possible that this can happen.

But ...


This puzzles me a little. So what are you saying ? that pressing Play *without* Stop causes the message ? If that is so ... I guess I never thought of people doing that (although it should work anyway .. but regarding this ... hmm.)

Please let me know !
Peter

Well just to add to the confusion, or lack there of, my interrupt error has miraculously corrected itself. In other words, it don't happen no more. Don't ask. Alright go ahead. I don't know.

Really! I can't think of anything I've changed, certainly nothing that should effect such a change. I run pretty standard settings.

-Chris

But I do by know. :yes:

It goes wrong when the Thread Priority is set to "Nothing".
So people, change that into an explicit value, and for 0.9z-6 it will be okay.

Will be solved for the next version.
Peter

Yup, yessir, you do know by now.

I did change the priority to not "Nothing" a few days back after reading someone's comment about something or other in another thread. Thank-you whomever, even though it wasn't your intention to solve my flacus interruptus.

-Chris