It's not always loading especially, if you select the precise waveform instead of synthetic one (which looks exactly the same under any song).
If you click play before it's completely loaded (which 99.9% of people will do because you need to wait so long for it to load), then it might not load at all, and remain invisible, even after track change.
Only on Windows Chrome 83.0.4103.116 (Official Build) (64-bit)
In order to display the dynamic soundwave, we must preload the MP3 file first. We wont preload it till the user has clicked play because it would slowdown the page for people who have not / dont want to click play.
If you want to display a soundwave faster, we recommend to use the synthetic waveform which is a fake soundwave but the result is quiet great.
If you want to preload soundwave, we use Wavesurfer.js https://wavesurfer-js.org/ for the library..I think there is a technic to preload the soundwave in the server backend but we never used it because it would require custom setup on each server..If you want to use that technic, you will have to check directly with wavesurfer im afraid.
We strongly recommend synthetic soundwave over the dynamic soundwave if you have any preloading issues or mp3 bigger than 2mb.
hi, the problem there is that it's not always loading even after you click play. Sometimes, it loads, other times it won't load at all, especially during automatic track change. Also, clicking play button doesn't update it often. Are you planning to fix this? Thank you.
Could you try something for me? Please deactivate all your plugins except our mp3 player then see if the issue persists. If not, please reactivate your plugins one by one and see which plugin can cause the conflict.
Thank you! I have cleared all the console errors, and then I removed all plugins, but the errors from your plugin still being shown all the time in chrome. It happens when I click play, but then the "play" icon doesn't change to the "pause". The track still however plays, and then these errors start showing up:
iron-audioplayer.js?ver=2.1:177 Uncaught TypeError: Cannot read property 'list' of null at iron-audioplayer.js?ver=2.1:177 at 00.wavesurfer.min.js?ver=2.1:4 at Array.forEach (<anonymous>) at Object.fireEvent (00.wavesurfer.min.js?ver=2.1:4) at 00.wavesurfer.min.js?ver=2.1:4 at 00.wavesurfer.min.js?ver=2.1:4 at Array.forEach (<anonymous>) at Object.fireEvent (00.wavesurfer.min.js?ver=2.1:4) at b (00.wavesurfer.min.js?ver=2.1:4) at 00.wavesurfer.min.js?ver=2.1:4
I can see the error too. However, the error with our code is included in a file that has been generated by a cache plugin or fireewall or something like that. the file is not a file from the plugin (the code is tho). see screernshot: https://d.pr/i/cjZaxw
Please deactivate your cache plugin or cache server-level app and see if you have same issue. Perhaps you can avoid to minify our file somehow since its already minified.
my apologies! I have disabled the caching plugin, and the error still exists, but this time it's iron-audioplayer.js?ver=2.1:177. Could you please verify now? Thank you, and I'm sorry about the caching plugin
In order for the error to appear you kinda have to keep on changing songs. Sometimes it's the first song, and other times, it's 5th or even latter etc.. It's not always showing error right away, so if you don't see it, then try changing songs until it pops up.
my apologies again! I've deleted all the cache. Now it should load directly.
here on the screenshot you can see it took a few clicks for the error to appear. Sometimes, it takes just one click, sometimes several song changes, but it will inevitably appear:
It looks like the play/pause button works now. great.
Despite you might see some js warning in the console if you click too fast on the tracks, I cant seems to reproduce front-end issue where the play/pause button does not work?
Indeed, now the error doesn't appear so often anymore. It happens, but very rarely now. The only exception that can somtetimes happen now is this one: Uncaught (in promise) DOMException: The play() request was interrupted by a call to pause(). https://goo.gl/LdLk22
It's not always loading especially, if you select the precise waveform instead of synthetic one (which looks exactly the same under any song).
If you click play before it's completely loaded (which 99.9% of people will do because you need to wait so long for it to load), then it might not load at all, and remain invisible, even after track change.
Only on Windows Chrome 83.0.4103.116 (Official Build) (64-bit)
https://h-var.com/album/2015-psychectomia/
Hi,
In order to display the dynamic soundwave, we must preload the MP3 file first. We wont preload it till the user has clicked play because it would slowdown the page for people who have not / dont want to click play.
If you want to display a soundwave faster, we recommend to use the synthetic waveform which is a fake soundwave but the result is quiet great.
If you want to preload soundwave, we use Wavesurfer.js https://wavesurfer-js.org/ for the library..I think there is a technic to preload the soundwave in the server backend but we never used it because it would require custom setup on each server..If you want to use that technic, you will have to check directly with wavesurfer im afraid.
We strongly recommend synthetic soundwave over the dynamic soundwave if you have any preloading issues or mp3 bigger than 2mb.
Thanks,
Max from the Sonaar.io Crew
hi, the problem there is that it's not always loading even after you click play. Sometimes, it loads, other times it won't load at all, especially during automatic track change. Also, clicking play button doesn't update it often. Are you planning to fix this? Thank you.
It looks like a JavaScript conflict.
You have a lot of error in your chrome console.
Could you try something for me? Please deactivate all your plugins except our mp3 player then see if the issue persists. If not, please reactivate your plugins one by one and see which plugin can cause the conflict.
Tell me how it goes.
Thanks,
Max from the Sonaar.io Crew
Thank you! I have cleared all the console errors, and then I removed all plugins, but the errors from your plugin still being shown all the time in chrome. It happens when I click play, but then the "play" icon doesn't change to the "pause". The track still however plays, and then these errors start showing up:
iron-audioplayer.js?ver=2.1:177 Uncaught TypeError: Cannot read property 'list' of null
at iron-audioplayer.js?ver=2.1:177
at 00.wavesurfer.min.js?ver=2.1:4
at Array.forEach (<anonymous>)
at Object.fireEvent (00.wavesurfer.min.js?ver=2.1:4)
at 00.wavesurfer.min.js?ver=2.1:4
at 00.wavesurfer.min.js?ver=2.1:4
at Array.forEach (<anonymous>)
at Object.fireEvent (00.wavesurfer.min.js?ver=2.1:4)
at b (00.wavesurfer.min.js?ver=2.1:4)
at 00.wavesurfer.min.js?ver=2.1:4
Thank you so much
Hi,
I can see the error too. However, the error with our code is included in a file that has been generated by a cache plugin or fireewall or something like that. the file is not a file from the plugin (the code is tho). see screernshot: https://d.pr/i/cjZaxw
Please deactivate your cache plugin or cache server-level app and see if you have same issue. Perhaps you can avoid to minify our file somehow since its already minified.
Thanks,
Max from the Sonaar.io Crew
my apologies! I have disabled the caching plugin, and the error still exists, but this time it's iron-audioplayer.js?ver=2.1:177. Could you please verify now? Thank you, and I'm sorry about the caching plugin
In order for the error to appear you kinda have to keep on changing songs. Sometimes it's the first song, and other times, it's 5th or even latter etc.. It's not always showing error right away, so if you don't see it, then try changing songs until it pops up.
Sorry, the error is still comming from file 19C84.JS file. see screenshot https://d.pr/i/Ua0MN7
this file is not one of our file.
Looks like your server or wordpress modify the output of the file which cause the error.
try to disable/remove any cache plugin or optimisation plugin or firewall or CDN.
Thanks,
Max from the Sonaar.io Crew
my apologies again! I've deleted all the cache. Now it should load directly.
here on the screenshot you can see it took a few clicks for the error to appear. Sometimes, it takes just one click, sometimes several song changes, but it will inevitably appear:
https://i.imgur.com/kU52YMB.jpg
Sorry for the cached files again. Could you try once more?
It looks like the play/pause button works now. great.
Despite you might see some js warning in the console if you click too fast on the tracks, I cant seems to reproduce front-end issue where the play/pause button does not work?
Can you tell me what is not working ?
Thanks,
Max from the Sonaar.io Crew
Indeed, now the error doesn't appear so often anymore. It happens, but very rarely now.
The only exception that can somtetimes happen now is this one:
Uncaught (in promise) DOMException: The play() request was interrupted by a call to pause(). https://goo.gl/LdLk22
The error you see is relatively normal.
the play function might be interupted by a call to pause. dont worry about this,.
Thanks,
Max from the Sonaar.io Crew