bruor 43 Posted September 24, 2024 Posted September 24, 2024 I'm using emby with IPTV and curious about the technical details behind this release note. Any chance you can provide some specifics of what the issue/behavior was and what about it was addressed?
Luke 42078 Posted September 24, 2024 Posted September 24, 2024 Hi, it is a charge to the ffmpeg command line based on user feedback.
bruor 43 Posted September 24, 2024 Author Posted September 24, 2024 Ok thanks, looks like you dropped the "-reconnect 1" My provider is impacted by this ffmpeg functionality: https://trac.ffmpeg.org/ticket/6423 My provider starts throwing 401 errors when the token embedded in the redirect URL expires. I assume I could modify the params ffmpeg tries to reconnect for to be more specific and exclude 401 errors. However, is restarting the the feed from the original URL something that Emby can handle? If ffmpeg exits because it encounters a 401, does the emby server or client have any mechanism in to reattempt to tune to that channel URL again before giving up and throwing an error on screen for the user?
Luke 42078 Posted September 25, 2024 Posted September 25, 2024 54 minutes ago, bruor said: Ok thanks, looks like you dropped the "-reconnect 1" My provider is impacted by this ffmpeg functionality: https://trac.ffmpeg.org/ticket/6423 My provider starts throwing 401 errors when the token embedded in the redirect URL expires. I assume I could modify the params ffmpeg tries to reconnect for to be more specific and exclude 401 errors. However, is restarting the the feed from the original URL something that Emby can handle? If ffmpeg exits because it encounters a 401, does the emby server or client have any mechanism in to reattempt to tune to that channel URL again before giving up and throwing an error on screen for the user? Looking at this ticket: Quote However, if the input URL passed on the commandline return a http code 302 and a redirect URL, the subsequent reconnections happen on the redirect URL and not the original URL input URL. I think the problem is there is no way for ffmpeg to know how to handle this. I bet you if they change it there will be reports from others that need it how it is now.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now