gnilcyc

how-can-i-send-and-receive-data-between-two-raspberry-pi-through-osc

RNBO doesn't have any specific notion of OSC and the OSCQuery Runner (the program that runs your patcher on the raspberry pi) doesn't yet have a way to remap OSC messages and send to another host, at least not at this time.

Your best bet is to write a script that runs on your master pi and listens to messages from one runner then re-formats and sends them off to the other.

"Your best bet is to write a script that runs on your master pi and listens to messages from one runner then re-formats and sends them off to the other."

I added the pi corresponding to Slave as a listener to the pi corresponding to the master, and I succeeded in receiving the output value of the [outport] of the master pi from the [outport] of the RNBO patcher uploaded to Slave.

But what I want to do is to have the sound triggered on the slave pi every time a value is output(for example, clock) from the master pi. (To work with only two pi without a computer)

Master pi and slave pi have succeeded in sharing the value through the [outport] object with each other, is there any way to reuse the value within the slave RNBO patcher? As you know, [outport] objects don't have outlets, so they can't be used to trigger other objects.

Is it impossible to use two raspberry pi without a computer? Tell me if there's any other good way.

To tell you what I've done...

I added the pi corresponding to Slave as a listener to the pi corresponding to the master, and I succeeded in receiving the output value of the [outport] of the master pi from the [outport] of the RNBO patcher uploaded to Slave.

But what I want to do is to have the sound triggered on the slave pi every time a value is output(for example, clock) from the master pi. (To work with only two pi without a computer)
Master pi and slave pi have succeeded in sharing the value through the [outport] object with each other, is there any way to reuse the value within the slave RNBO patcher? As you know, [outport] objects don't have outlets, so they can't be used to trigger other objects.

Is it impossible to use two raspberry pi without a computer? Tell me if there's any other good way.

"Master pi and slave pi have succeeded in sharing the value through the [outport] object with each other, is there any way to reuse the value within the slave RNBO patcher?"

I'm curious to know how you verified that?

"Is it impossible to use two raspberry pi without a computer? Tell me if there's any other good way."

A raspberry pi is a computer, just a small single board one. You can definitely use it without a separate computer. At this time there is nothing that simply lets you hook 2 RNBO patchers running on separate raspberry pis together, you'll have to write a program that manages the communication from one to the other.

This is a cool idea though, there was a feature request not too long ago to allow for outports to send arbitrary OSC messages. I could see this working in your case, your outport on your master pi could trigger an inport message to be sent to the other one. This is not implemented yet though, but it is exactly what I'm suggesting you do if you write a custom script, listen for /rnbo/inst/0/message/out (I forget the exact path) and then send an appropriate /rnbo/inst/0/message/in to the other pi.

"Master pi and slave pi have succeeded in sharing the value through the  [outport] object with each other, is there any way to reuse the value  within the slave RNBO patcher?"

"Is it impossible to use two raspberry pi without a computer? Tell me if there's any other good way."

A raspberry pi is a computer, just a small single board one. You can definitely use it without a separate computer. At this time there is nothing that simply lets you hook 2 RNBO patchers running on separate raspberry pis together, you'll have to write a program that manages the communication from one to the other.

I just thought of one approach that might work sooner than later.

If you can use parameters, individual numbers, to do your communication, you could have some parameters that you only write to but don't read on one host and then read them on the other.

You still have to add a listener to host A that will forward messages to host B.. but I think you've already figured that one out?

I just thought of one approach that might work sooner than later.

If you can use parameters, individual numbers, to do your communication, you could have some parameters that you only write to but don't read on one host and then read them on the other.

host A:
number -> [param foo]

host B:
[param foo] -> do something

You still have to add a listener to host A that will forward messages to host B.. but I think you've already figured that one out?


Oh, that's right! This is it! Why didn't I think of doing [param]? Thank you. '

Oh, that's right! This is it! Why didn't I think of doing [param]? Thank you. '
I solved it!! 🤩

----------