Answer the question
In order to leave comments, you need to log in
Which technology to use for web player: Web Audio API vs HTML5 Audio?
Good day to all :)
We are writing a small site for the company, where you will need to play music. The UI-constitution of the player is approximately the same as that of the VK player: there is a list of tracks to be played, and there is also a simple controller (start, stop, next, prev, shuffle, volume). A distinctive feature of the player from VKshnogo - there should be a frequency filter (equalizer) with 6 positions, which are controlled by simple sliders, as well as visualization of the data being played (spectrum). After playing a track, the next one down the list starts playing. Preload, of course, should be.
We started to embed the standard web audio api, but faced the problem that, given the specifics of the player, the mechanism for working with time and switching is really not suitable (of course, it can be configured, but there will be a lot of dancing with a tambourine).
To what extent would it be a correct decision to delegate application control (clicks, timings) to the audio tag and its api, and the data visualization and equalizer parts to the Web Audio Api using the audio tag, like MediaElementAudioSourceNode ?
Thank you!
Answer the question
In order to leave comments, you need to log in
About visualization
www.schillmania.com/projects/soundmanager2/demo/36...
I'm not sure about the possibility of implementing this item, study the documentation, perhaps this also exists.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question