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
Panic using seq nodes as inputs to seq nodes #105
Comments
Hi, thanks for posting it! Sometimes we just use the
And sometimes we add a
The
I think if you check the source code here. Inside the How do you think? is there a particular reason you want to layering different seq? Is is related to #101? I am now working on a node called |
I'm working on using Glicol to generate music from DNA, and IIRC what I was trying to do here was have the Javascript code that parses the DNA not have the notes defined in it. So I was using single-element
and then in JS generating something like Regardless, this just came from me misunderstanding how Glicol works so I don't think it's super important to get it to work, especially if things are going to be redone anyways. Not sure what |
@vgel I think |
This causes a panic in the Rust WASM backend:
Various values in
~n: seq X
seem to trigger it. I originally had 440 (not realizingseq
takes midi notes), then dropped it to 60, then realized it was probably trying to double-convert midi, so dropped it to 1 to see if that would still panic, and it did. So at least 440, 60, and 1 will cause it to panic.I think this is a weird thing to try to do given how
seq
actually works (I was playing around trying to figure it out), so I don't know if this panic is that important, but I figured I'd report it in case my judgement was off.Backtrace:
The text was updated successfully, but these errors were encountered: