Autoplay?

Currently no,
unless some very particular case (a user triggered pop up for eg)
it is not that a user-friendly thing,

• 5 Reasons Your Website Should NEVER Autoplay Sound! – Web Propelled
• Autoplay is bad for all users | Punkchip

I’m pretty sure it could be coded in some ways but I don’t really want currently to spend my free time for coding a feature not that appreciated by the end users ??
(thing is it would require some researches to make this feature doable, to prevent multiple files to play together, to trigger the sound only when page is loaded, to update buttons accordingly, etc…).

Hoping it is not a critical feature for your project !

Thanks, I appreciate the advice but, yes, that’s one of those special cases ??

Since, you’re overwriting the original [audio] shortcode it would only make sense to keep all original features (from the user’s perspective anyway). Otherwise, if I have some special rules somewhere with regard to autoplay or say, preloading, all that is lost, as soon as wavesurfer is activated. Just my two cents.

It’s not critical for my project but desirable. The main issue, however, is not being able to cache the waveforms as images. What I like about your plugin is that it has a small footprint but loading the waveforms each time somewhat diminishes that advantage. I’m presently benchmarking a commercial plugin that does waveform caching, autopaly and more but it has a much larger footprint, so I’ll need to do some more tests.

Don’t get me wrong, though. You did a great job with that plugin, just giving you my feedback.

The main idea behind overriding the main audio shortcode is to

• make the player backward compatible with post that were posted before the plugin activation
• having the regular player in post editing view
• having clean uninstall

so, having all default audio shortcode attributes accessible was (and is) not the priority. That said, it would indeed make sense to have it, but as you can see, it was not the main idea.

I also admit that having a way to have cache peak would be nice to prevent full audio loading at page load.
But this would require a mot lot works that it may look as it needs:

• creating a way to generate cache for new imported audio files
• creating a way to recreate peaks files for older audio files in library
• creating a way to recreate peaks for post that links to external audio
• creating a way to regenerate peaks if the media (the user could update/replace the media), even if it is an external audio file
• creating a way to store these peaks on the server
• creating a way to delete them when the plugin is uninstall
• creating a way to load this peaks at page load
• find a way to encode the peaks in a first place
• prevent audio loading at page load (this could be actually the easiest part, but it is still something to consider)

As you can see, this is way more than it could be done for a free un-sponsored plugin, considering the way that I have no idea how to make all this.
Alternative plugins like ZoomSounds (premium, 681 sales at 8$) doesn’t provide this either.

Note that the source code is open source. Anyone is free to modify the code, and to propose pull requests, including you, especially if you have experience in audio player ??

I keep in mind your ideas, but I can’t have plans for these at this moment.

Thanks for your ideas and support anyway, it is appreciated, and I’m glad you can see how it could be even better !

PS : Don’t hesitate to leave a comment to showcase your plugin when it will be ready, I’m sure it can interest users that would need autoplay and caching just like you proposed.

That’s not my plugin ?? I’m merely trying it out before deciding which one to use on some of my sites. WavePlayer

Oh that plugin is surprising,
it does handle peak files cache and…
… it is based on the same script as mine plugin, wavesurfer-js !

I definitely have to take a look.
I don’t want to reinvent the wheel.