-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to prevent react-howler from creating a new instance of the same song while the previous one is still playing when updating the seek? #133
Comments
Hi @barackm, Can you include the rest of your component's code or, better yet, reproduce in a simple, stripped-down, example and include that code? My hunch is that you're accidentally creating a new instance of react-howler somewhere or some state's not getting updated like you're expecting. |
faced the same problem, I'm sure it's related to this goldfire/howler.js#1163 |
Could be caused by a song that's not fully loaded. Since you're buffering the song (assuming the file is very large). This kind of error occurs when you try to load a part of the song that's not loaded yet. |
I'm having the same issue. Is there a way to prevent this issue? |
also facing this issue :(( |
Having the same problem.. |
I am trying to create an audio player, I have been following the documentation here for the full control example,
However, when I try to update the seek of the player with my range input, the same song starts playing from the beginning while the previous one is still playing.
Here are the methods I use to manage the player seek
The text was updated successfully, but these errors were encountered: