![]() *limitations (I've found so far, and because I don't know Rust): trickier to read file metadata (so I've made the new one organize around files/folder names), trickier to put in the tray, and I believe impossible to make the player the default program. The two major things I have left (which I had in my previous player) are the "randomize/linear", add lyrics, and hopefully fix the limitations. I might semi-open-source it at some point (code-readable and compile your own, or pay $4-10 for the binary) but here is the direction I'm taking so far: It does have some major/minor limitations compared to Electron*, but also 10MB (which can apparently be reduced even further) vs 200MB and a pretty nice dev experience makes it worth it for me. I actually started with Electron and raw HTML+CSS+JS, but at some point I discovered Tauri+React and switched over and now I'm very happy programming there. Yes, it’s theme-able audio controller !Īnd of course, I added a custom shortcode attribute for allowing split channels ! I did not include all WaveSurfer-js attributes, but this one was highly desired.No, but I want a more "minimal" one from what I'm seeing. To allow further customization, I put all necessary CSS classes, so that everyone can make and share his own theme. I created a global settings page, for controlling global aspect of the plugin and allow a deeper integration with the theme, and waveforms colors can be overriden locally with shortcode attributes. Safe deactivation: if you deactivate the plugin, your shortcode will fallback to the WordPress default audio player.It supports every audio format supported by WordPress (wav, ogg, mp3, m4a).You still have the default player in the Visual Editor (not just shortcode).I decided to override the default audio shortcode. ![]() It was clear that the HTML output should be handled the WordPress way: with shortcodes. The second step was to integrate it with WordPress. In resume, that was countless hour of struggling for small details on CodePen. The difficulty was to make it work with several player on the same page, and to retrieve audio infos once files were loaded, which happend before wavesurfer-js initlization. The safari browser will download the entire audio file. X-Raym play button does not change from Play to Pause automatically. So that was the first step: creating buttons that could control the audio element according to certain output. player no longer works or displays when woocommerce/contact form 7 active. But it needed an controller (play, pause, stop buttons etc), because the standard audio player (depending of the browser) was output below the waveform, and so, two progress bar from different size were visible, which is a bit distracting. The HTML initialization render was pretty basic: it just detect audio element and replace it by a waveform, according to certain parameter. Well ok so we have split channels, we basic have HTML initialization… Now it needed to be WordPress friendly. So I write another feature request, and once month later (one month ago), the feature was ready ! Indeed, it is not possible to modify a jQuery script from a post content, so I needed a way to put the infos in standard HTML format, and a way to transform this markup into the WaveSurfer-JS player. This may be powerful in some cases, but for integrating within a WordPress post, it needed HTML initialization. Indeed, all settings, including path to the audio files, needed to be coded in jQuery. That’s was very promising, but it was not enough to be usable for me. It was maybe the first multiple-channels waveform web audio player available. About one year later, the feature was integrated. More, it was pretty customizable, and modular… two things I really like in a software.Īs soon as I found it, I write a feature request for having multiple channel capabilities. I searched for this type of player a certain amount of time, until I found WaveSurfer-JS, a free open source jQuery plugin by katspaugh capable of embedding audio while displaying it’s waveform on a web page. Also, having to upload the sounds on a third-party platforms can be not desired, especially if you already have a lot of sounds uploaded on your website and that you don’t wont to upload them elsewhere, and if you want to stay independent. If I want to make a tutorial about 5.1 panning, having only one waveform is not that useful. These are both great players but they lack something: multiple channels display. That’s why I instantly liked SoundCloud player, and later, the Hearthis.at player. But finding this on the web is pretty rare. It is especially useful for audio tutorials, or podcasts, e-learning etc… It allows quick search in audio sections which is especially useful in these circumstances.Īudio waveforms preview is very common in sound processing softwares and in every Digital Audio Workstation. I always loved waveform display for showing audio content. EDIT : WaveSurfer-WP Premium Add-On, featuring cache system for waveforms and interactive markers system, is out!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |