Otto Rottier

Hi @Jerboas86, you are still assigned this issue. Are you interested in publishing your direct form implementation?

Thanks for digging in! Indeed, AudioParams are treated just like AudioNodes, and are therefore part of the audio graph. Params share the same characteristics as nodes: they feed into other...

I also realize we definitely need to look into 'inactive' audioparams. As you can see from the flame chart, AudioParam 'rendering' takes a lot of time. If we know an...

Hey, no worries. I actually don't really have a plan currently so I never complained about it either. I'll try to come up with a strategy in the linked ticket...

Removing the milestone goal. It would be nice to have, but this can probably go into v2 along with other breaking changes such as variable render quantum size.

Once this is implemented, we can fix the panic that occurs when you add nodes to a closed context, e.g. ``` let context = AudioContext::new(None); context.close(); let delay = context.create_delay(1.);...

Another panic that can be fixed is ```rust let context = AudioContext::new(None); let analyser = context.create_analyser(); context.close(); analyser.get_float_time_domain_data(vec![1.; 128]); ``` This should just return zeroes when the context is paused/closed

I have a branch ready for item 1 at [feature/intmap-for-graph](https://github.com/orottier/web-audio-api-rs/tree/feature/intmap-for-graph) But I will have a look at the other items first before deciding if this is worth the hassle of...

I took a stab at `Avoid the remove and insert calls of the currently processing node.` @b-ma but it's very tricky. We will need a lot of unsafe code to...

I took a new look at intmap: `6b7f11f80a4fe4`. A very slight performance increase but maybe it's just noise. Also `Granular synthesis` seems to regress. I would say, no merge. Next...