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
I’m not sure if this can be considered a bug, if it’s appropriate for me to report it, or anything else.
The issue is that when I start multiple streams using the Paramount+ plugin, every time an ad starts, Kodi either freezes or even crashes. I’ve tested this on both Debian and Android TV, with the same result.
For example, if I watch a Champions League match and then the post-match show, every single ad causes the application to freeze. Even if I manage to close the stream in time, I have no way of knowing when the ad ends.
So, if I were watching a match, I wouldn’t know when it resumes.
Any ideas on how to fix this (even a workaround)?
I know the problem might be related to InputStream Adaptive, but do you happen to have any suggestions to avoid the freezing?
The text was updated successfully, but these errors were encountered:
Yes, it's the same thing. The problem lies in the switch between the main stream, such as a Serie A match, and the advertisements, which apparently use a different encryption or something else. It would be great to find a way to wait for the main stream to resume (even without watching the ads).
I’m not sure if this can be considered a bug, if it’s appropriate for me to report it, or anything else.
The issue is that when I start multiple streams using the Paramount+ plugin, every time an ad starts, Kodi either freezes or even crashes. I’ve tested this on both Debian and Android TV, with the same result.
For example, if I watch a Champions League match and then the post-match show, every single ad causes the application to freeze. Even if I manage to close the stream in time, I have no way of knowing when the ad ends.
So, if I were watching a match, I wouldn’t know when it resumes.
Any ideas on how to fix this (even a workaround)?
I know the problem might be related to InputStream Adaptive, but do you happen to have any suggestions to avoid the freezing?
The text was updated successfully, but these errors were encountered: