Skip to main content
Topic: WASAPI shared output (foo_out_wasapis) (Read 16580 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: WASAPI shared output (foo_out_wasapis)

Reply #75
Every time my computer went to sleep while I paused a playback, it shows the popup when wake up:

Quote
WASAPI (shared) PlayThread error: Received event to fill buffer but IAudioClient::GetCurrentPadding reported the buffer stayed full during <number> ms of retrying

Is it possible to permanently hide the popup? It's very annoying.

Re: WASAPI shared output (foo_out_wasapis)

Reply #76
New version released with hopefully proper support for power events. The playback thread should no longer die from power events and if you don't manually pause the playback the component should handle it for you.

Re: WASAPI shared output (foo_out_wasapis)

Reply #77
I'm sorry but I'm still getting error
Quote
Unrecoverable playback error: WASAPI playback thread terminated: Received event to fill buffer but IAudioClient::GetCurrentPadding reported the buffer stayed full during 1010 ms of retrying
I'm using foo_out_wasapis 0.6.9. All I'm doing is 1) play a music. 2) put to sleep. 3) immediately wakeup. 4) observe error.

Re: WASAPI shared output (foo_out_wasapis)

Reply #78
I'll attach a test version that prints to console some status info. Could you tell what it prints when you test that scenario again.

Edit: I must have been lucky when testing the change on my laptop. I just tried with my desktop and replicated the issue. I reset the sleep flag in a stupid position. Replaced the attachment with hopefully working version. If it fails I'd appreciate the console output. If it works I'll release a proper version with the change.

Edit 2: Obsolete attachment removed.

Re: WASAPI shared output (foo_out_wasapis)

Reply #79
Thank you for help. The test version has the same error message. Here is the print from console:
Quote
WASAPI shared: machine going to sleep
WASAPI shared: playback paused by sleep
WASAPI shared: sleep flag reset
WASAPI shared: sleep flag:0
WASAPI (shared) PlayThread error: Received event to fill buffer but IAudioClient::GetCurrentPadding reported the buffer stayed full during 1015 ms of retrying
Unrecoverable playback error: WASAPI playback thread terminated: Received event to fill buffer but IAudioClient::GetCurrentPadding reported the buffer stayed full during 1015 ms of retrying
WASAPI shared: playback resumed after sleep
WASAPI shared: power broadcast: 7, 0

If you need me to test more versions, feel free to shoot me PM. You can upload file to something like Firefox Send.

BTW, my OS is Windows 10 build 2004. foobar2000 ver 1.5.4.

Re: WASAPI shared output (foo_out_wasapis)

Reply #80
Did you notice the edit and update to the test version?

Re: WASAPI shared output (foo_out_wasapis)

Reply #81
Yes. When I download, I saw the "Edit" paragraph. Also just tested again. Although the two lines swapped, the issue persists.
Quote
WASAPI shared: playback resumed after sleep
WASAPI shared: power broadcast: 7, 0

Re: WASAPI shared output (foo_out_wasapis)

Reply #82
Thanks to testing help from @CrendKing I released a new version that should finally handle standby correctly. On my laptop it was OK to just reopen playback chain immediately after waking from standby but proper handling required waiting for the OS to signal that machine has woken up.

Re: WASAPI shared output (foo_out_wasapis)

Reply #83
Another power event you could look in to or comment on.
Output = HDMI monitor (which has also sound)
track is paused (e,g, long podcast) after a while the screen is put on stand-by.
After waking up the screen foobar2000 shows an "unrecoverable playback error WASAPI".

Is that avoidable?
In theory, there is no difference between theory and practice. In practice there is.


Re: WASAPI shared output (foo_out_wasapis)

Reply #85
Yes, that is on (by default).
Not that it matters. The HDMI device disappears anyway when it switches off.
In theory, there is no difference between theory and practice. In practice there is.

Re: WASAPI shared output (foo_out_wasapis)

Reply #86
Error should be gone with the just released 0.6.11 version.

Re: WASAPI shared output (foo_out_wasapis)

Reply #87
Wow, I'm impressed. Thanks, it works.
In theory, there is no difference between theory and practice. In practice there is.

Re: WASAPI shared output (foo_out_wasapis)

Reply #88
From foobar v1.6 change log "Default output mode is now WASAPI shared"

Does that mean that there is no need to have it installed on v1.6?
foobar2000 plays music

Re: WASAPI shared output (foo_out_wasapis)

Reply #89
Different implementations. It would certainly be good if as many people as possible would help test the native mode in foobar2000. I don't know if the built-in output uses lockless design or how its mixer compares to mine. For example at the moment my output is the only one that allows you to play the 10 channel audio sample from this thread. But my component will be obsolete soon. The new smooth fade options for output implements identical methods as my component to remove glitches when playback is adjusted.

Re: WASAPI shared output (foo_out_wasapis)

Reply #90
Thanks for clarification.
foobar2000 plays music

 
SimplePortal 1.0.0 RC1 © 2008-2020