When providing preloaded peaks with MediaElement, the peaks are overwritten once the track loads entirely
See original GitHub issueI’m using wavesurfer.js 2.0.0-beta01, MediaElement
as a backend, and providing preloaded peaks.
When the track starts playing, the provided peaks are shown OK. But after the whole track gets downloaded, peaks generated by wavesurfer.js are shown over preloaded peaks.
I replicated the issue here: https://codepen.io/newjurgen/pen/KqvYxO (the track is around 20MBs, it can take a little while to load).
How can I prevent this behaviour?
Thanks for making wavesurfer.js.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5
Top Results From Across the Web
tools/metrics/histograms/histograms_xml/others ... - Google Git
Tracks the status of token loads from disk by Chrome OS Account Manager, for. a given user. This is recorded only once per...
Read more >Contents at a Glance - Springer
resource and the first one that succeeds will be the resource chosen for the <media> element. If none succeeds, the media element load...
Read more >Testdome merge names - Caritas Castellaneta
Next, provide the commit message for the changes. Track FedEx shipments with one of the convenient tools below. Write a Python function that...
Read more >OppiaMobile Documentation - Read the Docs
Since users who are registered but not actively using the app will put little or no load on the server. 2. There will...
Read more >macromedia® - FTP Directory Listing
provides these links only as a convenience, and the inclusion of the link ... 3 Choose a Preload option to define how cast...
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
@thijstriemstra it’s actually set to true in version 2 by default. pr #1159 to set default to false
I solved the issue by adding a parameter when initializing:
forceDecode: false
. I thought this parameter defaults tofalse
? Looking at this code, it truly looks so: https://github.com/katspaugh/wavesurfer.js/blob/master/src/wavesurfer.js. But somehow theforceDecode
gets the valuetrue
, even when leaving it out when initializing. Not sure how this happens, looks like a bug.