Closed agrathwohl closed 3 years ago
Experiments conducted today yielded some important insights.
We are able to load the waveform and begin audio playback almost immediately, when:
assets/peaks
dir via fetch()
.backend: MediaElementWebAudio
instantiation option for WaveSurfer.Currently, this also breaks background visualizations as they are currently implemented. The move is probably to:
post
and playlist
layouts work without any visualizer code.post
layouts, implement improved WaveSurfer code in a new include, _includes/wavesurfer.html
. This code should load peaks data from the local assets dir and use backend: MediaElementWebAudio
for now. (Later, make it dynamically and intelligently build out the WaveSurfer config based on context from the post/playlist metadata.)Fixed in a big way in commit d85fe181170853236aaa3687987b8a10078c577f
When the MP3 located at
post.stream_url
is 20+ minutes in duration, load times become unacceptable.We need to get more information on this phenomenon:
AudioBuffer
do the trick instead?