recloudstream
audio keeps playing after exiting the video, and that of the previous episode on clicking next ep
Steps to reproduce
(on tv)
- play an episode
- Exit or click on next episode
- Wait for the error to show up followed by the audio of the episode which was playing
Expected behavior
The previous video as well as auido should stop playing
Actual behavior
Audio keeps playing
Cloudstream version and commit hash
4.1.1
Android version
Android 10
Logcat
Unable to get logcat to phone through tv
Other details
https://discord.com/channels/737724143126052974/1136191575152668692
Acknowledgements
- [X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
- [X] I have written a short but informative title.
- [X] I have updated the app to pre-release version Latest.
- [X] If related to a provider, I have checked the site and it works, but not the app.
- [X] I will fill out all of the requested information in this form.
@fire-light42 @LagradOst @Blatzar sorry for direct ping here, but any idea what causes this? This is one of the most annoying issues on TV that I have ever seen, about 90% of the time this happens, unless instead of clicking the next EP button, you fast-forward to the very end of the video, that seems to be the only way this is fixed. If you exit the video, and gave autoplay next EP on it continually plays the previous episode audio with no way of fixing without force stopping the app. I have tried to look into this but can not find anything on it. It happens on FireTV, as well as Google TV, and very often. I can not get Logcat from TV either.
Again sorry for the direct ping, but this is the most annoying issue that now instead of playing on TV directly I mostly just cast from my phone to TV which isn't as good. I just hope we can find some way to fix it...
P.S. A couple times I actually had to unplug my Fire TV to fix this as it was just qucker than going back into the app, but sometimes it still plays when you exit the app to go back to home screen, and even pressing the power button to the TV didn't actually stop it, which is more of an OS issue but just goes to show how deadlocked you can get when audio doesn't stop playing. It can get frustrating. A side issue is on Google TV sometimes it gets stuck in some PiP window without being able to re-enter the app, which can be just as annoying. PiP on Google TV doesn't seem the most efficient, and probably doesn't have to much use if it doesn't work much anyway. But that doesn't happen as often and isn't as annoying as the audio issue.
just adding some more insights it's probably caused because the tv is too weak, this could be due to low amount of ram, storage or just a bad processor the error it shows is remote error for some reason the easiest fix is to close and open the app again one of the ways I fixed it was that i realised that my tv was too weak and I'll have to lower my standards a little basically i configured it so that it will play 720p by default (not that it makes much difference I mostly use the crunchyroll source and it's top notch quality even at 720p) and by reducing the buffer size to 40mbs, if your tv is decent enough just the buffer setting should work
@fire-light42 @LagradOst @Blatzar sorry for direct ping here, but any idea what causes this?
No clue, it is a known bug, but completely impossible to replicate in emulator, phone or google TV. I suspect it is a Fire TV exclusive thing. I have tried to fix it multiple times without success. I have no idea what causes it or how to fix it, I have not found anything similar on exoplayer/media github.
It would be wonderful if you took a look, this issue is simply too weird and its hard to test any fixes without direct access to a device this happens on.
No clue, it is a known bug, but completely impossible to replicate in emulator, phone or google TV. I suspect it is a Fire TV exclusive thing. I have tried to fix it multiple times without success. I have no idea what causes it or how to fix it, I have not found anything similar on exoplayer/media github.
It would be wonderful if you took a look, this issue is simply too weird and its hard to test any fixes without direct access to a device this happens on.
what if it is related to the ffmpeg audio thing
No clue, it is a known bug, but completely impossible to replicate in emulator, phone or google TV. I suspect it is a Fire TV exclusive thing. I have tried to fix it multiple times without success. I have no idea what causes it or how to fix it, I have not found anything similar on exoplayer/media github. It would be wonderful if you took a look, this issue is simply too weird and its hard to test any fixes without direct access to a device this happens on.
what if it is related to the ffmpeg audio thing
@LagradOst
That's a really good thought. I enabled some ADB testing on my Fire TV yesterday trying to fix this to no avail either, but FFmpeg is a great thought for potential cause. Although I do remember it happening on Google TV at least a couple times awhile ago, it happened on my phone before also, but hasn't for those in months. On phone it was easier to solve by closing the app easier though, on TV it sure is a pain. And on phone I think it was an OS issue with PiP, IE it was technically playing in PiP, but the PiP player was somehow hidden offscreen. That may have been what happened on Google TV also. But Fire TV is a much different and consistent issue that is quite the pain to deal with. And then of course when you really want to reproduce it becomes hard to reproduce but when you don't want it to happen, it happens consistently, so it is quite hard to debug also.
