You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for this very useful app, I've found it really convenient when messing around with live audio streams in Termux!
The TCP connection isn't closed properly after pressing the Stop button, it stays alive until the app is explicitly stopped from the recent apps screen. This usually isn't noticeable when streaming from PulseAudio, since that allows multiple connections, but in the windows server it could prevent reconnecting after stopping the stream.
How to reproduce:
Open pavucontrol -t 2 (the Recording tab)
Open the app and connect to the stream
Press stop and play repeatedly
Multiple Simple client entries appear
Force-close the app. This should disconnect all of them
Device info:
Huawei Mate 20 Pro with Emui 12 (Android 10)
Simple Protocol Player 0.5.8.0
I'm pretty sure this is caused by the following line only being executed when an Exception is caught, but not when exiting normally by setting running to false.
Thanks for this very useful app, I've found it really convenient when messing around with live audio streams in Termux!
The TCP connection isn't closed properly after pressing the Stop button, it stays alive until the app is explicitly stopped from the recent apps screen. This usually isn't noticeable when streaming from PulseAudio, since that allows multiple connections, but in the windows server it could prevent reconnecting after stopping the stream.
How to reproduce:
pavucontrol -t 2
(the Recording tab)Simple client
entries appearDevice info:
Huawei Mate 20 Pro with Emui 12 (Android 10)
Simple Protocol Player 0.5.8.0
I'm pretty sure this is caused by the following line only being executed when an Exception is caught, but not when exiting normally by setting
running
to false.SimpleProtocolPlayer/src/main/java/com/kaytat/simpleprotocolplayer/NetworkReadThread.java
Line 164 in 8345ab8
The text was updated successfully, but these errors were encountered: