Max

one caveat is that at least Chromium constantly shows a warning that the cursor is hidden which becomes annoying really quick

is it really necessary to get rid of HTML5 audio though? it can still be used with the web audio API using [`createMediaElementSource()`](https://developer.mozilla.org/en-US/docs/Web/API/AudioContext/createMediaElementSource): https://developers.google.com/web/updates/2012/02/HTML5-audio-and-the-Web-Audio-API-are-BFFs it's so much easier to control...

actually yeah, good point. [wavesurfer.js](https://wavesurfer-js.org/) is one implementation that uses the Web Audio API. seems to be pretty quick as well!

> Do we do something like covers, where waveforms are generated everytime we play a track? Or can we store them somewhere ? I think it would be good to...

> we can only pass strings between Renderer and Main this might be a problem for the caching. as the web audio API would only be available in the browser...

I'm all about quality work, trust me! :) I just don't necessarily think waveforms are best represented vectorially. however, this completely depends on what kind of waveform is desired. I'm...

here's the result of my initial experimentation: https://gist.github.com/bodyflex/e4f6c9ec0fdea9450fd9303dd088b96d select an audio file with the form input to see the waveform and look into the console for some simple statistics. it...

it already measures the durations (console.time wasn't flexible enough for my needs). an mp3 that is a bit short of four minutes long takes ~0.5s to calculate the values and...

what kind of animation do you mean specifically? highlighting the current playback position in the SVG waveform is pretty trivial using masks at least.

I'd say that if it's enabled it should replace the default seek bar. of course then the progress would need to be displayed on the waveform.