Jump to content

Problems With Live TV Recordings Stopping Early


Recommended Posts

Posted
On 2/28/2026 at 10:01 AM, iON22 said:

BTW...it is still happening. For example, yesterday scheduled recording of 30min news broadcast at 5:30pm recorded fine. Another scheduled 30 min news broadcast at 10pm only recorded for 2mins.

I am wondering;

  1. Is it possible that the rate of the download stream is being reduced (due to network traffic or IP Provider throttling) causing Emby to think the stream has dropped?
  2. Is there any thought of changing the Emby recording algorithm to have it reconnect immediately if the stream is interrupted. Even if there were interruptions in the recording at least it would be 'more' complete.

Thanks for your persistence on this.

@iON22we already do this, but the remote server hosting the content sends back the 555 error on the retry:

2025-12-13 01:13:52.192 Info SharedHttpPipelineSource: Opening SharedHttpPipelineSource Live stream from Http-http://host4/x_path1_x/x_path5_x/x_path13_x/x_path14_x
2025-12-13 01:13:52.192 Info HttpClient: GET http://host4/x_path1_x/x_path5_x/x_path13_x/x_path14_x
2025-12-13 01:13:52.289 Info HttpClient: Http response 555 from http://host4/x_path1_x/x_path5_x/x_path13_x/x_path14_x after 97ms. Headers Access-Control-Allow-Origin=*, Date=Sat, 13 Dec 2025 06:13:53 GMT, Server=Apache2, Transfer-Encoding=chunked
2025-12-13 01:13:52.290 Error SharedHttpPipelineSource: Give up retries copying live stream http://host4/x_path1_x/x_path5_x/x_path13_x/x_path14_x No more retries allowed.

So that's what we need to know, is why they're sending it back.

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...