-
Notifications
You must be signed in to change notification settings - Fork 42
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
Error running example code in readme #66
Comments
Which examples are doing this ? I did check them just the other day. Could you post the full error with stack trace if you got one? That would be very helpful. Thanks! |
hi! sure, this is what I get when pasting the first snippet in the readme file
Thats running |
when I try
Ther's a chance Im messing something up with versions 🤔 |
Ack! You are right: the js side defName and what sclang gives it were why it wouldn't load. I have a fix posted and will do a new release shortly. The sine-wave.js example should not have been included : I was sketching out an idea of how it could/should look. I will clean and test all the examples. That was all done in a hurry last week. Sorry for the |
There will be a new dryadic soon that will dramatically improve how you work with it. I was hoping to get that completed for the 1.0 release |
Nice! I tried changing the code here and there before creating the issue, but it would break other places... |
… of the synth def and the generated compiled name that sclang gives it
There is a new release out. I had unit tested that stuff but no integration tests. I should set up a test that can run all the examples. |
Hello, I installed
supercolliderjs
and tried some of the examples in a js file but when calling it with node I got the following error:SynthDef not in store: 1075206181
Looking a bit into the code, there seems to be a mismatch when saving the synthdef with a readable name and trying to recall it using the assigned server name, I tried hacking around but didn't manage to get it working, I wonder if this is related to some version mismatch (lodash perhaps?).
I ran the examples with node version
v12.8.0
and[email protected]
, also[email protected]
and the error seems to be present in both versions, either thrown as an error or ignored and failing later when trying to access the buffer data.The text was updated successfully, but these errors were encountered: