Open rludwig21 opened 5 years ago
Hi, I've had similar issue on chrome, but in my case it was not an issue of Url, but of response headers. Basically on chrome the pause/seek functionality works only if request for file response contains "accept-ranges: bytes". For Edge (I did not test this on firefox) it works event without this header. Anyhow for me it is not a problem (I'm streaming my own files) but maybe check if those headers are correct in your case.
@humulustom How to add accept-range:bytes to the response header
Well it depends on what you are doing. This is a response header, so it should be set by the server you request the audio/file from - so if you control the server, you should add such header to responses there, but also implement proper "range" request handling (see for example this). If you send requests to a third party, then there is little you can do, aside perhaps from some proxy, middleware or other hacks, but I don't specialize in frontend/js so can't really suggest anything from the top of my head.
Works fine in Edge, Firefox but not Chrome (Current version). When using a Url that does not end in ".mp3" the Seek and Pause then Play jump back to zero restarting the audio...
Example: Using the Player Example just replace Player.js with this Player.js
"Html5: false" corrects the issue but then its a full download...