Nice library. The landing page needs some more work. The "features" section contains just keywords that are not explained. I'd like a sentence explaining each feature: what it does and when/why it is useful. For example, at first I didn't understand what "Auto Mute" meant. That was until I played a sound while I switched to another tab, which made the sound stop. When would one want to use auto mute? To me it felt unnatural/unwanted, almost like a bug. Explain why Web Audio API is used when available. What will not work (if applicable) when using the HTML5 Audio fallback? In what kind of web applications would I want to use Waud.js? Games?
Waud.js: Web audio library
11–20 of 26 posts
Re: Waud.js: Web audio library
#12Re: Waud.js: Web audio library
#13What is going on, why on earth are we now encoding audio in base64? It's gone beyond getting angry, now I'm just sad for the state of this whole schlamassel.
The only reason for encoding audio in base64 is to reduce the number of requests which in turn reduces the loading time. It's an alternative to audio sprites. Useful when you have a lot of audio files to load.
Hey Adi the link to API Docs seems broken.
Re: Waud.js: Web audio library
#14Earlier quoted context omitted.
The only reason for encoding audio in base64 is to reduce the number of requests which in turn reduces the loading time. It's an alternative to audio sprites. Useful when you have a lot of audio files to load.
Hey Adi the link to API Docs seems broken. http://www.waudjs.com/docs/
Working link: http://www.waudjs.com/api/
Re: Waud.js: Web audio library
#15Nice library. The landing page needs some more work. The "features" section contains just keywords that are not explained. I'd like a sentence explaining each feature: what it does and when/why it is useful. For example, at first I didn't understand what "Auto Mute" meant. That was until I played a sound while I switched to another tab, which made the sound stop. When would one want to use auto mute? To me it felt un…
Thanks for the feedback. Will try and improve the home page. Auto mute can be helpful in cases like watching a video in one tab and if you don't want audio from another tab interfering, on devices when you press home button or when you receive a call, playing 2 games in 2 tabs, etc. Just there if you need it. Everything will work exactly the same way whether the browser supports web audio api or not. That's the aim anyway and if it doesn't its a bug. Definitely useful for games and any web apps that needs audio playback.
Re: Waud.js: Web audio library
#16strikingly similar to WAD - https://github.com/rserota/wad
Re: Waud.js: Web audio library
#17Earlier quoted context omitted.
Even recording audio?
Web Audio API is all about playback. The media capture API can tackle recording, and it works on mobile: http://simpl.info/mediacapture/
I thought that only works for video? Wouldn't you want navigator.getUserMedia for audio only?
Re: Waud.js: Web audio library
#18API docs link is a 404. But I'm looking to try this. Have you worked around with any of the audio playback changes (onlick vs. ontouchend vs onmouseup) in iOS 9/10? I'm curious what "audio unlock" on iOS means.
Re: Waud.js: Web audio library
#19Earlier quoted context omitted.
Web Audio API is all about playback. The media capture API can tackle recording, and it works on mobile: http://simpl.info/mediacapture/
I thought that only works for video? Wouldn't you want navigator.getUserMedia for audio only?
Right, and on iOS, it just leaves the browser and opens the video recording app.
Unless something has changed, getUserMedia still doesn't work on Chrome/Android or iOS/Safari yet.
Re: Waud.js: Web audio library
#20Earlier quoted context omitted.
I thought that only works for video? Wouldn't you want navigator.getUserMedia for audio only?
Right, and on iOS, it just leaves the browser and opens the video recording app. Unless something has changed, getUserMedia still doesn't work on Chrome/Android or iOS/Safari yet.
I believe you're correct - the state of audio recording on the web via browser is still awful. We are just finishing an investigation at work on my team, and find that we cannot avoid the use of Flash to record for IE/Edge/Safari...our only saving grace is that this app is mainly intended for desktop use.
I wish mobile browser vendors didn't avoid this problem - I get that they're all prioriizing different things, but the state of audio/video recording & playback is abysmal.