seek no longer works in 2.1.0

[smakinson]

Updating to 2.1.0 causes seek(position) to no longer work. It always plays from the start. If I revert to 2.0.15 it works again. I am using html5: true and format: ['mp3']. Setting the html5PoolSize to 0 did not resolve the issue. I have the same result in chrome & safari.

[goldfire]

Can you provide sample code demonstrating the issue?

[smakinson]

Sure. If I switch between 2.0.15 and 2.1.0 in the pen I get different results when I press seek.

https://codepen.io/smakinson/pen/maPRNe

[ardeois]

I've got the same issue and found the problem.
See #1102

[ardeois]

@smakinson If you change your codepen howler version to my branch it should work. Can you confirm?

https://cdn.jsdelivr.net/gh/ardeois/howler.js@610ed0c02f07680fd4e73a87cc6ebed8ab273188/dist/howler.min.js

[smakinson]

@ardeois Looks like that fixes it!

[paulrosen]

I think you can also pass the id back in when calling play the second time:

var howl = new Howl(...);
...
var id = howl.play();
...
howl.pause();
...
howl.play(id); // will not start back at beginning.

[ardeois]

Good point, it should work. However it looks to me like a workaround on a regression

[goldfire]

This should now be fixed with d22ddcf.

[smakinson]

Thank you for addressing this so quickly!

[stevenleeg]

Has this issue come back again? I'm noticing calls to seek always causing the playhead to reset to 0 in v2.1.2 with html5 set to true.

[Mani7TAM]

I am also facing this seek issue in chrome and opera using version 2.1.2. But working without issues in firefox.

[tsukinose81]

Version 2.2.3 also has this problem. It works normally in firefox

[JoshKasap]

I found the url that you get your audio file from needs to include the response header Accept-Ranges: bytes in order for the seek and duration counters to work properly in chrome.

IDK how you do this using other languages but for cold fusion you need to add <cfheader name="Accept-Ranges" value="bytes"> to the top of page that returns the audio file.

For more context that might help people.
In my case the url I provided to howler was not a direct path to an audio file but instead a path to a page that would accept certain url parameters which would in turn be used to search a db and return the file. So I just needed to add the Accept-Ranges: bytes header to the top of this page that returned the audio file. Hopefully this information can be used to help determine the solution to this issue in more commonly used languages.

[serious-angel]

Accept-Ranges: bytes

That was it! The same exact issue: from direct path to a custom reference - missing header.

Holy smokes... You are a hero... Ha! Thank you very much! Hurray!

Please have a pleasant time and stay safe! ✨