Looped sounds can't be addressed after completing their first loop

[rovenko]

When using a looped sound, it's only possible to address the sound (i.e. fade / stop) only when the very first iteration of the loop is being played back.
As soon as the sound goes into the second iteration of the loop, the same control actions stop working.

[rovenko]

Howler's onend Function fires when the sound finishes playing (if it is looping, it'll fire at the end of each loop). The first parameter is the ID of the sound.
redux-sounds, uses "onend" handler that calls this.removeId(id) therefore removing it from the list and making it unavailable.
Given that there's "onstop" - is removeId(id) necessary for "onend"?

[ludgerey]

Any feasible workarounds for this?

Being unable to stop sounds makes this library not applicable for background music.

[rovenko]

Any feasible workarounds for this?

Being unable to stop sounds makes this library not applicable for background music.

I've applied a git patch to to fix it in my local repo.

Simply comment out _this2.removeId(id); and this.removeId(id); in relevant spots in howler_integration.js and it seems to do the trick.

[ludgerey]

@rovenko Thanks for the heads up!

I got it fixed and added a pull request that supports looped sounds.

[GeKorm]

Merged #28. I'll release the fix in a few days, thank you both for the bug report and PR, I really appreciate the help!

[GeKorm]

3.3.0 Published to npm!