[Bug 53486] foobar2000.exe with foo_out_upnp breaks sending audio stream to another upnp renderer after a short period of time

WineHQ Bugzilla wine-bugs at winehq.org
Thu Aug 4 10:57:04 CDT 2022


https://bugs.winehq.org/show_bug.cgi?id=53486

--- Comment #3 from Pawel <pavlos.audiofreak at gmail.com> ---
I have applied this patch to the "master" version 7.14. 
Shortly: it works. 
20 minutes of continuous stream sending and playing audio on the renderer side.
No breaks, hangups or hiccups.

The "forcing STATUS_ALERTED" has appeared only once, briefly after the
beginning of the first track. Never appeared again, even though I have cycled
several times the playlist containing about 20 mins in 3 tracks.
The log line says as follows:

server/sock.c:3586:req_send_socket:forcing STATUS_ALERTED (errno=0)

Please note, that errno will always be zero, because you assign it to zero just
before the fprintf output statement. When I comment out the line 3575 "errno =
0;" of ./server/sock.c the log line says as follows:

server/sock.c:3586:req_send_socket:forcing STATUS_ALERTED (errno=115)

I have restarted the foobar for several times and the errno always returns 115.

Next, after getting rid of the "once" variable and letting the fprintf
statement to execute unconditionally, it usually (but no always) returns
errno=115, what happens every 10 to 50 seconds. Other values are 22, 13 or 107.

Full output log after playing the playlist of 3 tracks is in the attachment -
please note beginnings of tracks, marked by me.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.



More information about the wine-bugs mailing list