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
My Swiftfin clients seem to have duplicate streams going fairly regularly. I haven't dug in too much but it appears if an item is paused or stopped during playback, that stream doesn't properly terminate and a new stream is created alongside it. When I look in my Dashboard, it shows the same user, device and content playing twice or in extreme circumstances, up to 5 times. When a new content item starts, this will usually clear the previous streams but this has caused issues with playback due to my poor upload speed provided by my ISP. Thank you for reviewing this!
Application version
1.0.1
Where did you install the app from?
App Store
Device information
Apple TV 4k
OS version
tvOS 17.2
Jellyfin server version
10.8.13
The text was updated successfully, but these errors were encountered:
I am also experiencing this, what makes it worse is that if a user is trying to watch a transcoded stream, suddenly my server is bombarded with multiple transcode streams which obviously places a lot of strain on my CPU's integrated GPU.
Describe the bug
My Swiftfin clients seem to have duplicate streams going fairly regularly. I haven't dug in too much but it appears if an item is paused or stopped during playback, that stream doesn't properly terminate and a new stream is created alongside it. When I look in my Dashboard, it shows the same user, device and content playing twice or in extreme circumstances, up to 5 times. When a new content item starts, this will usually clear the previous streams but this has caused issues with playback due to my poor upload speed provided by my ISP. Thank you for reviewing this!
Application version
1.0.1
Where did you install the app from?
App Store
Device information
Apple TV 4k
OS version
tvOS 17.2
Jellyfin server version
10.8.13
The text was updated successfully, but these errors were encountered: