Yotam Mann
Yotam Mann
After calling `pause`, i believe you can restart the recording using `start()`.
Closing this here, since it seems like it is mostly about https://github.com/chrisguttandin/standardized-audio-context/issues/996 and not Tone.js. We can update standardized-audio-context if/when there's an update on this
This is actually an issue with the interactive example component, BroadcastChannel isn't used within Tone.js. so moving here as a reminder to take care of it.
This seems like probably has to do with the way that browser's pause javascript execution when a dialog like the print dialog is open. I'm not sure if there's anything...
Another way to do it would be to render the audio file with `Offline`. Create two audio sources, one connected to a lowpass filter and another connected to a highpass...
Just checked, and this works fine for me: ``` const emitter = new Emitter(); emitter.on("test", (arg) => { console.log('emitted', arg) }); emitter.emit("test", 100); ``` Maybe the Tone.Loop is never being...
Emitter events are just on the single Emitter, not global to all Emitters. If you're looking for a global event, i think the way you're doing it looks great!
There's two different clocks going with Tone.js, one is the Transport clock and one is the Web Audio Clock. The time argument of bpm.setValueAtTime is using the Web Audio clock...
From the original post, i think the error is the desired behavior. Instances aren't meant to be interacted with after they've been disposed, so the fact that it throws an...
🙏🏻 @marcelblum and @chrisguttandin