Skip to content
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

Recieving OSC when rhizome is on web #135

Open
tatecarson opened this issue Oct 17, 2016 · 1 comment
Open

Recieving OSC when rhizome is on web #135

tatecarson opened this issue Oct 17, 2016 · 1 comment

Comments

@tatecarson
Copy link

Hello again,

As I work more I keep running into further issues and things I need more understanding in. Here's another problem. I'm trying to receive a message from rhizome to supercollider and it works perfectly when using localhost but when tried on AWS it doesn't work, and returns no errors. All of my security permissions are totally open so that shouldn't be a problem. Here's the code relevant to receiving data:
from SC

thisProcess.openUDPPort(9002);
b.sendMsg("/sys/subscribe", 9002, "/");

OSCdef(\nodeTrigReceive, { |msg|
  "received from rhizome".postln;
  msg.postln;
  Ndef(\tester, {SinOsc.ar(rrand(200, 600))*EnvGen.kr(Env.perc)}).play;
}, '/trigger');

in the JS

if(this.onset.x == 100) {
   client.send('/trigger', [1])
}

Again, this works when on localhost and with nothing changed fails on AWS. Any ideas? I'm not even sure what to try.

Thanks again!

@sebpiq
Copy link
Owner

sebpiq commented Oct 25, 2016

Hmmm ... so the problem is for sending/receiving OSC to/from AWS
right? I have done that before with a server I have bought from some
other company. I did a couple of remote performances, and they all
went pretty smoothly ... So, they only thing I can think of - if
you're totally sure that you have opened all the ports on your aws
instance - is that your local network is blocking the connection ...
are you using windows? Windows can be a bit fiddly with this kind of
things ... look in your settings if these ports are opened for the
application you use. Do you have a firewall in the network you use?
etc ...

If you give me the IP of your aws (you can send it to me by email) and
setup the base/ example on it, I can try sending/receiving OSC, so we
can see f it comes from the server or if it comes from your
computer/network.

On 10/18/16, tatecarson notifications@github.com wrote:

Hello again,

As I work more I keep running into further issues and things I need more
understanding in. Here's another problem. I'm trying to receive a message
from rhizome to supercollider and it works perfectly when using localhost
but when tried on AWS it doesn't work, and returns no errors. All of my
security permissions are totally open so that shouldn't be a problem. Here's
the code relevant to receiving data:
from SC

thisProcess.openUDPPort(9002);
b.sendMsg("/sys/subscribe", 9002, "/");

OSCdef(\nodeTrigReceive, { |msg|
  "received from rhizome".postln;
  msg.postln;
  Ndef(\tester, {SinOsc.ar(rrand(200, 600))*EnvGen.kr(Env.perc)}).play;
}, '/trigger');

in the JS

if(this.onset.x == 100) {
   client.send('/trigger', [1])
}

Again, this works when on localhost and with nothing changed fails on AWS.
Any ideas? I'm not even sure what to try.

Thanks again!

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#135

Sébastien Piquemal
*
*
*
----- @sebpiq*
-----* http://github.com/sebpiq
*
----- http://funktion.fm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants