-
It looks from the readme as if the waveform data can be stored if using My expectation is that the browser would not have to spend time analyzing the audio to generate the waveform if it were available via the If so, is there a similar way to save the waveform data if using an |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
That's right, yes. The idea is to precompute and store the data server-side, which saves time and memory in the browser.
Peaks.js uses waveform-data.js to create the waveform data, but doesn't currently provide a documented way get at the data. Peaks.init(options, function(err, peaks) {
console.log(peaks._waveformData); // private data!
}); |
Beta Was this translation helpful? Give feedback.
-
I know this is undocumented and unsupported, but just in case I'm missing something obvious.. if I store the Here's what it looks like: I tried serializing the |
Beta Was this translation helpful? Give feedback.
-
For future readers, here's what I did to get this working:
|
Beta Was this translation helpful? Give feedback.
For future readers, here's what I did to get this working: