SourceBuffer's also look promising
this setup also allows me to have native clients just use plain UDP sockets. which seems cool.
I've also gotten complaints about the delay/rtt being too high. but I've no idea on how to debug that since it's a giant black box. I've also noticed that sometimes the client can't catch up, so there's a delay of 30s. which is stupid
the current setup -works- but I have to depend on the server to e.g. mute a client. since I've not found a way yet to see which stream is which. the server knows which streams belong to who. but there's no identifier client side.
all of this shouldn't be a big performance hit either. because the MediaStream already uses opus, and I'll be using the native API's to encode and decode them. I could also optionally premix the received audio frames.
this _should_ work. but I'm going to lose all "benefits" of an RTC MediaStream. which I haven't encountered yet. this allows me to timestamp and put other metadata (like, who this is from) on audio frames, and drop them on will, and detect lag!
and sending those over a RTCDataChannel to the SFU, on client when received, wrap it in an ogg container again, decode, and queue sample with an ScriptProcessorNode or AudioWorklet on an AudioContext object.
"Screaming into the void has never been so much fun!"
Meanwhile http://abuse.im is coming along fine. currently it's just a blank page, and you just have to trust you're not alone in the server
It's only natural the next chat app is going to be called abuse
"Note: As of the August 29 2014 Web Audio API spec publication, this feature has been marked as deprecated, and is soon to be replaced by AudioWorklet."
> AudioWorklet is not implemented in Firefox
"Out-Of-Scope for http://v.next"
what the hell man
WebAudio is uhh, weird. e.g. a NoiseGate (mute stream when sound is below n dB), would be really helpful, somebody in 2014 also thought so: https://github.com/WebAudio/web-audio-api/commit/77323cf07a408fb490efaad3d738b19ca3fe2ee3
I am cri
I am building a WebRTC app, and jesus. this spec is 5 years old and somehow still immature? (my IS_CHROME hacks so far: https://gist.github.com/the-eater/6d5a3625fa0ffe7e66ce90011f72794d)
but damn, the stuff you can do with it is pretty awesome.
Most likely talking about programming or music. maybe both.
Jack of all trades, master of one
[toots may originate from twitter]
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!