After XX PC won't go to sleep anymore, until reboot

[andy74]

A little update.

I made a simple app to use wasapi exclusive.
And made couple of simple tests.
Closing wasapi gracefully and exiting the app without closing wasapi correctly.

in 100% it showed that PC won't sleep as expected if you exit the app not closing wasapi properly.
and PC goes to sleep if you start and stop playing, exit and start app correctly closing wasapi.

[PeterSt]

Ok, so there must be a difference between a Playlist ending by itself on one side, and let XXHighEnd indirectly stop XXEngine3 on the other.

Thank you Andrey, I will look into this immediately ! (but there should be no difference ...)

[PeterSt]

Andrey, you are right !!

What I never saw was that the thread loading the tracks had become leading in determining whether playback has to end, and that this thread initiated a (startup of XXHighEnd and) shutdown of XXEngine3, that thread never being able to close down WASAPI objects properly. At the time I created this I never saw the difference, and later I never thought of this anymore. So indeed XXEngine3 can quit at two places, one of them being from within that thread, which just isn't allowed. I just solved that.

Another kind of problem is, that nowadays some 100 of situations exists that a quit is initiated from within that thread, althouh these are all error situations (except for playback has to stop because end of Playlist). I can theoretically solve them all the same, but I will be unable to test them. Most of them are theoretical situations anyway, but either way they just cannot be tested. And, because the only normal way which is there (and which is the one I just solved) has a return which is under my control, while all of the others may just jump out of the blue, I think I can do nothing else than leave those others as they are. They *are* real error situations (like format not supported), and in most (of not all) of cases, WASAPI won't be initiated anyway.

Andrey, good job !!
Peter