Is [transport] shared in each pi?
I uploaded a patch like this on each pi. (two raspberry pi)
My prediction is that I could turn [transport] on and off individually, but if I turn [transport] off one pi, all pi will turn off.
Why does it work this way? Am I missing something?
Interesting. How are the two raspberry pis communicating?
We run this application by default in the rpi image that we provide: https://github.com/x37v/jack_transport_link
This syncs your pi's Jack transport via Ableton's Link protocol: https://www.ableton.com/en/link/
You can disable sync, there is an attribute for it in [rnbo.remote]. Once you do that, I don't think the [rnbo.remote] based transport attributes will work anymore but you should be able to control the transport via [transport] objects in your RNBO patcher and you can hook those to [param] objects.
If you're sure you don't want to share transport among devices, you can also disable or uninstall jack_transport_link.
Thank you Alex!
I did some tests after reading your comment. And I have a few more questions.
My current environment is as follows.
Two raspberry pies (each named 'master' and 'slave')
And both of them have uploaded the patches I put on the text.
1. When I use multiple raspberry pies, do they basically share audio?
(I looked up a little bit about 'jack' and I thought it was)
2.
For example, suppose I give each pie the following message.
master: transport/sync 0
slave: transport/sync 1
If you send 'transport/rolling 0' to any of the next two pi, [transport] will stop only slave pi.
Does this mean that basically all the RNBO patches uploaded pi share audio, but the sharing is interrupted by 'sync 0'?
3.
In question 2, no matter which pi you give the 'transport/rolling' message, all pi are affected. 'transport/sync' could be applied individually. Then is 'transport/rolling' a message that applies globally to the entire 'jack'?
It's my first time using jack and raspberry pi, so there are many difficult parts.
I've seen most of the documentation, but if there's anything I can refer to regarding the above, please tell me!
Thank you. 😄
Hi GNILCYC,
1) Multiple PIs don't share audio, but you could set them up to do that if you use additional software/configuration. There is a little bit of info here about that: https://jackaudio.org/faq/netjack.html
2) The PIs (optionally, but by default) try to sync their jack transport to each other, but not audio. If you tell one to not sync, then the rolling message to one should have no effect on the other.
3) If you want to control transport on each PI totally separate from each other, you should set *transport/sync 0* on all of them and then in your patcher use the [transport] object to control rnbo's internal transport only.
Here is a little bit of info about jack transport, though I don't think it is that important for this work: https://jackaudio.org/api/transport-design.html
You're right, the documentation is lacking in this transport/sync area, I'll make a note for that.