-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Audio Duplication with ReactPlayer in Next.js using --turbo Flag #1895
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
Comments
I have this same issue. Any update? |
Pretty sure this has to do with react strict mode in nextjs. In prod doesn't happen and seems to be temporary fixable with nextjs config change: |
I'm also having the same issue, but for me it's both in an built app and in dev |
same issue here |
Same issue here. The issue occurs only for media files (no embedded players) and only if they are the 1st media to be played (eg. I play first youtube then mp3, no problem, then I reload the page and play directly mp3 -> audio duplicated). |
Yes, this is a major issue for me. I confirm that the there is a duplicate audio issue that exists in NextJs for external media files and ONLY if it is the 1st media to be played. If it is the 1st media to be played, and if it is played after initial load, with playing=true, then there is a duplicate audio stream. |
Current Behavior
When using
ReactPlayer
in a Next.js project with the--turbo
flag enabled, audio is duplicated starting from version2.14
up to2.16
ofreact-player
. The issue does not occur in earlier versions (e.g.,2.13
). This happens when toggling theReactPlayer
component based on state and occurs only the first time after the page loads.Expected Behavior
Audio should play without duplication when
ReactPlayer
is triggered, and the sound should play as expected without overlapping.Steps to Reproduce
--turbo
flag ("dev": "next dev --turbo"
).ReactPlayer
component that streams video from a local or remote source.react-player
versions2.14
-2.16
, the sound is duplicated.Environment
Code Example
The text was updated successfully, but these errors were encountered: