Jump to content

direct plays take forever to load


pr3dict

Recommended Posts

pr3dict

Yeah that last log file was from http:8096 and I am using chrome on windows 10. Version 72.0.3626.109 (Official Build) (64-bit)

Link to comment
Share on other sites

If you're behind a reverse proxy, make sure it's configured to preserve all http request headers, including range request headers, or something like this may happen.

Link to comment
Share on other sites

pr3dict

If you're behind a reverse proxy, make sure it's configured to preserve all http request headers, including range request headers, or something like this may happen.

 

When I'm on the same network and I connect directly (bypassing the reverse proxy) using the android or iOS app on my iphone/androd it still loads slowly. I remember you bringing up that for some reason it's trying to load the entire file first before playing or something?

Link to comment
Share on other sites

pr3dict

also I noticed you combined the threads I made... The live TV issue is something different entirely. I can't even load the guide or view the channels without my server coming to a halt.

 

I don't think the direct play issue is related. 

Link to comment
Share on other sites

 I remember you bringing up that for some reason it's trying to load the entire file first before playing or something?

 

Right that's what it looks like and that's not normal.  You're saying it does eventually play?

Link to comment
Share on other sites

The next question would be what is your file system that the media is stored on? I wonder if perhaps when we open the file handles, they are not seekable for whatever reason, thus preventing the server from being able to send back file ranges.

Link to comment
Share on other sites

pr3dict

Right that's what it looks like and that's not normal.  You're saying it does eventually play?

 

It does eventually play... The larger remux's that I have that are 30gb each or so take a significantly longer amount of time. Sometimes 2 minutes+.

 

The next question would be what is your file system that the media is stored on? I wonder if perhaps when we open the file handles, they are not seekable for whatever reason, thus preventing the server from being able to send back file ranges.

 

I'm all about putting on my sherlock holmes hat and finally getting to the bottom of this...

 

I'm using a drive pool. So all of the individual drives 4TB are ext4 but the pool that runs on top of it is MergerFS. The filesystem reports as fuse.mergerfs.

 

https://github.com/trapexit/mergerfs

 

I just remembered that emby is connected to the storage server via nfs. All the clients connect to the storage server via SMB. 

Edited by pr3dict
Link to comment
Share on other sites

Yea that sounds suspicious to me. It's so many layers of translation involved that support for various features are probably getting lost along the way.

 

As a test, can you try setting up a small test library on the same drive the server is installed on? Assuming that's not also part of that pool.

Link to comment
Share on other sites

pr3dict

Real quick. Before I go Frankenstein my setup... Can you explain how the file descriptors work? Is this on the actual video file thats stored on my storage server, or is it where the metadata is stored? Who needs to access it, the emby server or the client?

Link to comment
Share on other sites

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...