-
-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get basic audio graph compilation working #10
Comments
Alright, this is working, we are producing audio! :D I commented out the nodes we don't support yet so they don't show up in the UI. So far we have knobs, const, sawtooth, sine wave, audioout and add/mul/div/sub. Next I will work on getting delay nodes working, because they gave some special tricky bits. Namely delays make it possible to create loops in the audio graph, so they need to be broken up into two nodes. After that, I will probably look at |
I got the node parameters dialog working at a basic level so we can set knob min/max values and node names. We probably need a better solution for validating the inputs of the form eventually, but it works. Delay nodes are working too. I will start to look at |
The MonoSeq, in its most basic form, is working. It's missing things like being able to transpose patterns during playback and being able to extend and switch patterns, but it plays and highlight the current step. Oh yeah! :) |
I want to get to the point where we can connect a Noise node to an AudioOut and hear some noise. Then I'll work on getting knobs to work along with some basic oscillators. Then after that we can work our way up to more complex nodes like sequencers.
Sequencers are going to require data to flow both ways between the UI and the audio thread. The user will be able to click to turn individual notes/steps on and off. However, the timing logic will be controlled from the audio thread, so the sequencer will need to be able to set its current step from the audio thread.
There are also other nodes like
Scope
which will need to send data back from the audio thread to the UI thread. We might be able to help the performance of that by limiting updates to once every 50ms and keeping the updates fairly granular. There are also dedicated ArrayBuffers IIRC that can be used to send data back without allocating. I'm hoping we won't have to use that because it would add complexity, but we'll just have to see how everything performs once this is more advanced 🤔The text was updated successfully, but these errors were encountered: