Increase Stream timeout

[Theradioguy 7]

Hey all,

Currently I'm bumping into an issue with the live TV plugin for TVHeadend where I have a couple of streams that take a very long time to start (45-75 seconds), but Wmby will time out before the stream starts.  In the logs I can see the following:

```
Application path: /opt/emby-server/system
    MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: Connection to http://x.x.x.x:9981/stream/channelid/969920332?ticket=xxxx timed out
     ---> System.Threading.Tasks.TaskCanceledException: The request was canceled due to the configured HttpClient.Timeout of 30 seconds elapsing.
     ---> System.TimeoutException: The operation was canceled.
     ---> System.Threading.Tasks.TaskCanceledException: The operation was canceled.
     ---> System.IO.IOException: Unable to read data from the transport connection: Operation canceled.
     ---> System.Net.Sockets.SocketException (125): Operation canceled
       --- End of inner exception stack trace ---
       at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
       at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token)
       at System.Net.Http.HttpConnection.InitialFillAsync(Boolean async)

```

Which makes sense if there is a hard coded timeout of 30 seconds.  I wonder if there is a setting or other way to increase this value so Emby will wait the required amount of time for these particular streams to start.

Thanks!

Edited June 24, 2023 by Theradioguy

[Luke 40077]

Hi, for the next release this has been bumped to 50 seconds. Thanks.

[Theradioguy 7]

Thanks for this, but I wonder if it is possible to get this exposed as a configuration option so it can be user set?  In my case, 50 seconds would be sufficient some of the time, but I have observed these streams taking as long as 75 seconds to start.  Having this as a user-selectable option under some advanced settings menu would allow the specification of a high timeout for some users but would not impact other users.

[Luke 40077]

Hi, yes I would expect this to be configurable in future updates. Thanks.

[Theradioguy 7]

This is great news!  Any idea when this is planned for?

[Luke 40077]

39 minutes ago, Theradioguy said:

This is great news!  Any idea when this is planned for?

I don't have an ETA, sorry.

[Mbiboy 2]

@LukeWas this ever exposed as a user configurable setting?

[Luke 40077]

4 hours ago, Mbiboy said:

@LukeWas this ever exposed as a user configurable setting?

Hi, no, but it's 60 seconds now. Are you saying you need longer than that?

[SPF79 1]

Hi,

I actually require a longer (preferably configurable) timeout, since my libraries are located on a RAID 5 volume (Zyxel NAS) via NFS. EDIT: They spin down for power saving and take about a minute+ for spin-up once a request has come in.

It's also really annoying that reattempts after a timeout are just rejected as a default, especially when trying to play from the home screen.

Any ideas?

Best,

Seb

Edited February 26 by SPF79

[Luke 40077]

10 hours ago, SPF79 said:

Hi,

I actually require a longer (preferably configurable) timeout, since my libraries are located on a RAID 5 volume (Zyxel NAS) via NFS. EDIT: They spin down for power saving and take about a minute+ for spin-up once a request has come in.

It's also really annoying that reattempts after a timeout are just rejected as a default, especially when trying to play from the home screen.

Any ideas?

Best,

Seb

@SPF79OK what you're mentioning is different then what we're discussing here. This topic is about the server connecting to remote hosted live tv.

What you're asking for is a longer timeout in the player, and yes this is possible on some platforms, but unfortunately not all. For example in the web app, the timeout length of the browser video player cannot be controlled, and the length of that timeout will potentially vary amongst browser vendors.

[SPF79 1]

10 hours ago, Luke said:

@SPF79OK what you're mentioning is different then what we're discussing here. This topic is about the server connecting to remote hosted live tv.

What you're asking for is a longer timeout in the player, and yes this is possible on some platforms, but unfortunately not all. For example in the web app, the timeout length of the browser video player cannot be controlled, and the length of that timeout will potentially vary amongst browser vendors.

Cheers for the reply and analysis, Luke.

Sadly, this doesn't get me anywhere. I'm using the Emby Theater M$ store app here. The default "get lost" behaviour after a single timeout and the roughly 30 sec to a timeout are extremely annoying, whereas I cannot see a reason for the former, and would love the latter to be configurable. 

Please forward this. Especially the senseless "refusing to try again"-behaviour. That's rubbish.

Best,

Seb

[Luke 40077]

13 hours ago, SPF79 said:

Cheers for the reply and analysis, Luke.

Sadly, this doesn't get me anywhere. I'm using the Emby Theater M$ store app here. The default "get lost" behaviour after a single timeout and the roughly 30 sec to a timeout are extremely annoying, whereas I cannot see a reason for the former, and would love the latter to be configurable. 

Please forward this. Especially the senseless "refusing to try again"-behaviour. That's rubbish.

Best,

Seb

For most of the installed apps outside of Roku, yes this should be possible.

[SPF79 1]

9 hours ago, Luke said:

For most of the installed apps outside of Roku, yes this should be possible.

How do you mean? Modifying the behaviour as an enduser or you forwarding these issues? :-)

Edited February 28 by SPF79

[Luke 40077]

I mean increasing the timeout in the player. It is not possible in all apps, but it should be in some.

[SPF79 1]

18 minutes ago, Luke said:

I mean increasing the timeout in the player. It is not possible in all apps, but it should be in some.

Ok, I already checked the Emby-folders in my %appdata% (inkl. Local, etc.) for config files. I found some, but without results for any timeouts. Would you mind researching/inquiring a bit and providing a point to start from?

Best,

Seb

[Luke 40077]

20 hours ago, SPF79 said:

Ok, I already checked the Emby-folders in my %appdata% (inkl. Local, etc.) for config files. I found some, but without results for any timeouts. Would you mind researching/inquiring a bit and providing a point to start from?

Best,

Seb

This is something that has to be looked at separately in each individual app. There's nothing on the server you can do to influence this.

[SPF79 1]

8 hours ago, Luke said:

This is something that has to be looked at separately in each individual app. There's nothing on the server you can do to influence this.

Obviously so. I'm sorry to have addressed you in here with this. Let's assume, that I felt as if there should be a major interest of the whole emby community to have reasonable client implementations and hence hoped to encounter sort of a general UHD.

However, I'm an industry manager and realise that accountabilities/responsibilities seldomly (actually never) rest with the original instance that provided a technology.

Thanks for the chat and all the best,

Seb

[Carlo 4552]

On 2/28/2025 at 3:23 AM, Luke said:

I mean increasing the timeout in the player. It is not possible in all apps, but it should be in some.

Instead of having to adjust the timeout in players, could we do this a different way?

Luke perhaps this could be added to the Cinema Into plugin (or forked) as it should have 95% of the needed functionality built in all ready.
It could have a new option "Disk Spinup" function.

Instead of playing trailers or codec intros, in this mode it plays a simple video or two from memory over and over until the disk is ready or the timeout period has expired.
Pretty much like a series of custom intros.