Closed gilfuser closed 7 years ago
I showed this at a class at UDK and some people did also see that result. For others it worked just fine.
What browser are you using (shouldn't matter at all) ?
I didn't yet figure out what it was. I'll use your issue here to track it and solve it.
I see node 1000 did end (there was a notification that it ended) which would happen when there was a mouse up.
Did you see s_new
and n_go
posted when you mousedown ?
If you reload your web page then it starts a new session (you are a new user). The old session will release its notes.
If you edit any files at all then it will restart the webserver and restart supercollider scsynth. Your browser will reconnect to start a new session.
The warnings are nothing important.
Hi Chris. Actually I was one of those in UdK! Well, maybe I was the only one who was not getting this to work because I was the only one using Linux.
I'm using Firefox.
The first time I mousedown I see s_new and n_go, and with mouseup n_end. After that, sometimes I see s_new and n_go when I mousedown again, and sometimes not. I couldn't figure out why I would see them or not.
I realized now that the problem is not in this example specifically. I just tried the server-plus example and I'm getting no sounds from there to. No errors, the nodes being made... it looks like it was working fine.
best regards, Gil
Ah, I was on mobile and didn't see your pic ! Hello gil !
Maybe they are separate problems. You don't hear sounds. I remember there was a Faust error/complaint you had. Is normal supercollider still working ? (from the IDE)
Did you patch the audio (with jack etc) into some internal audio bus ?
The occasional missing node error (sending messages to an already ended node) may be a simple booking keeping error. I can show how to set up a handler that is called when the synth ends.
Hello Chris.
The Faust error was solved after you told me to make manually the file sclang_config.yaml (If I remember well). I'm using the normal supercollider working without any issues, and I'm not patching the audio in any way.
One difference between the way that the normal supercollider works, I think since the version 3.7, is that I don't have to start jack manually before start the server. And after starting the server, if I open QJackCtl, I see it off, although I know that Jack is on. If I run the examples I tried and look at QJackCtl, it will be turned on.
I have no idea if this is useful information, but with a detailed description of what is happening there is a better chance to spot what is going on.
Show me how to set up the handler. Let see if this helps.
thanks
best regards, Gil
Chris Sattinger notifications@github.com schrieb am Mi., 30. Nov. 2016 um 12:44 Uhr:
Ah, I was on mobile and didn't see your pic ! Hello gil !
Maybe they are separate problems. You don't hear sounds. I remember there was a Faust error/complaint you had. Is normal supercollider still working ? (from the IDE)
Did you patch the audio (with jack etc) into some internal audio bus ?
The occasional missing node error (sending messages to an already ended node) may be a simple booking keeping error. I can show how to set up a handler that is called when the synth ends.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/crucialfelix/supercolliderjs-examples/issues/2#issuecomment-263853966, or mute the thread https://github.com/notifications/unsubscribe-auth/AI-AKubBJtQCwUOYm7w39UMXEb-LIZSmks5rDWGOgaJpZM4K9zkQ .
Hi Chris. Just to follow up, I managed it to work manually connecting the Supercollider server to the system output with QjackCtl. I still get some of this errors though: error : [ "/fail", "/n_set", "Node 1028 not found" ]
See you soon in UdK best regards, Gil
Hi. I'm trying to test the webserver example in Linux, but I'm getting no sounds. The scserver starts but it remains silent. I'm on Linux btw. Here is what I have after npm run start:
And here is a message with the mouse button pushed:
... and after I release the button ( note the "Node 1000 not found" ) :
I got some warning while doing the npm install. I have no idea if this can be related with the problem, but here they are: at the beggining: npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree. and at the end: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.0.15: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN webserver@1.0.0 No repository field. gil@Lirou-Niu:~/scjs/supercolliderjs-examples/webserver$
If you think I can help doing any tests, just tell me.
best regards, Gil