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
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?
Trying to figure out if this is a server-issue or a MX-player issue.
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?