Playback start broken on v3
See original GitHub issueHi, I found the following issue.
Background: Version 2 and Version 3 of fluid player use exactly the same source files for video playback.
Expected behavior: Clicking on play starts video playback. This is true for v2, but not for v3.
Actual behavior:
v3 doesn’t start the playback at all, instead the following issues are reported in the web console:
[SourceBufferSink] SourceBuffer append failed "InvalidStateError: Failed to execute 'appendBuffer' on 'SourceBuffer': This SourceBuffer has been removed from the parent media source."
Can be tested here:
- Working v2: https://majamee.000webhostapp.com/player/fluid-player.html
- Not-working v3: https://majamee.000webhostapp.com/player/fluid-player-v3.html
I would appreciate, if you could have a look at it, especially as the video files are untouched and shared between the two versions.
Thanks & BR, majamee
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Playback won't start
When I go to start playback, it acts like it's playing, ... 3. Drag them to your desktop 4. Restart Finale and you...
Read more >View playback not working - Cameras
I had a card in my Cam 2, but took it out. It now records events, but playback starts and at 2 to...
Read more >Playback User Guide
3. Building a Setlist. Add a Song. Add Song Menu. Load a Setlist ... Start Pad with Song: Toggle ON to have the...
Read more >"Continue Playback" not working on 3.0.11
Re: "Continue Playback" not working on 3.0.11 ... As an initial troubleshooting step open vlc and go to Tools ---> Preferences (or hit...
Read more >I found a temporary/work-around fix for video playback on ...
Connect to the Camera using the Wyze app · Tap the "View Playback" button · Scrub to video snippet you would like to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The issue has been identified - dash.js comes with a “feature” called autoCreate - it would attach to all video sources automatically once loaded to a page. Incidentally, Fluid Player always attaches it’s own instances of dash.js to the sources when necessary. This double loading of dash causes race conditions and thus the player breaks.
Fix will be released with v3.0.1.
This should now be fixed with the latest release.