FORUMS
Remove All Ads from XDA

Correct handling of HTTP streams (header)

6 posts
Thanks Meter: 0
 
By largie, Junior Member on 5th February 2018, 10:34 AM
Post Reply Email Thread
Hi, thank you for MX player.
Used it for years, simply a great product

I'm currently working on a http-server project and it streams to a lot of media-players.
My server works perfectly with for instance Kodi and alot of other streamers.

I wonder how MX player handles seeks in a HTTP-stream?

My server sends the header to MX player: Accept-Ranges: bytes
MX sends to me: Range: bytes=0-
My server then with correct headers:
Content-Range: bytes 0-10561452647/10561452647
Content-Length: 10561452648

If I seek in MX the next GET-request for the file does not contain the: Range: bytes=x-
With information above MX should have what is needed to request for instance 50% in the stream?
Range: bytes=5280726324-

Trying to figure out if this is a server-issue or a MX-player issue.
Any tips?

Edit:
I have investigated further and found MX seeks perfectly when using the HW+ or SW decoder.
The seek does not work when you are using the HW-decoder.

Does anyone know if this is a bug or restriction in the decoder?
 
 
6th February 2018, 03:21 AM |#2  
Recognized Contributor
Thanks Meter: 4,107
 
More
Quote:
Originally Posted by largie

Hi, thank you for MX player.
Used it for years, simply a great product

I'm currently working on a http-server project and it streams to a lot of media-players.
My server works perfectly with for instance Kodi and alot of other streamers.

I wonder how MX player handles seeks in a HTTP-stream?

My server sends the header to MX player: Accept-Ranges: bytes
MX sends to me: Range: bytes=0-
My server then with correct headers:
Content-Range: bytes 0-10561452647/10561452647
Content-Length: 10561452648

If I seek in MX the next GET-request for the file does not contain the: Range: bytes=x-
With information above MX should have what is needed to request for instance 50% in the stream?
Range: bytes=5280726324-

Trying to figure out if this is a server-issue or a MX-player issue.
Any tips?

Edit:
I have investigated further and found MX seeks perfectly when using the HW+ or SW decoder.
The seek does not work when you are using the HW-decoder.

Does anyone know if this is a bug or restriction in the decoder?

HI,

HW+ & SW are MX Player's own implementations. Whereas HW decoder is just a wrapper for android mediaplayer API. So, MX ony has basic controls. If any errors on it, generally it's from the mediaplayer implementation on the device itsellf.

Some old android versions do not support seeking of ts videos. Not sure is it the case of yours.
We can understand it better if you can provide a bug report which is colllected immediately after the issue (from MX's help menu)
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes