Knurl Quartet residency

are you connecting all of the Belas to the same network, or is each of them broadcasting its own network? In the first case, you need each of them to have a unique address, in the second case, then it's fine to have all of them on the same IP, as they won't "see each other" as they are each on a separate network.

RafaeleAndrade On the bela ipadress, you are always able to check how much CPU your bela is using through the webbrowser platform. For the cellists, this might become to much things to do and to set up in the future. I wonder if there is a way to capture this information using supercollider and send to the TouchOSC patch that they will be looking at.

I tried "s.avgCPU" but that does seem to give me only 0.0.

One can easily get the CPU usage of a single-threaded Bela program by running awk '/bela-audio/ { print $8};' /proc/xenomai/sched/stat
if you could run this command on the board and somehow pass its output to TouchOSC, that would be you sorted. It can be done with a simplified/modified version of the program I suggest here https://forum.bela.io/d/2944-realtime-functionality-outside-of-the-bela-context , e.g.:

#include <unistd.h>
#include <libraries/UdpClient/UdpClient.h>
#include <oscpkt.hh>
UdpClient udpClient;

int main()
{
	int port = 1234;
	const char* ip = "192.168.7.1";
	float periodSeconds = 1;
	bool ret = udpClient.setup(port, ip); // use 192.168.7.1 to send to host or 192.168.7.2 to send to other program on Bela
	if(!ret) {
		fprintf(stderr, "Unable to connect to remote\n");
		return 1;
	}
	printf("Connected to %s:%d, sending data every %.3f seconds\n", ip, port, periodSeconds);

	while(1)
	{
		// popen/pclose code courtesy of https://stackoverflow.com/a/646254
		FILE *fp;
		char path[1035];

		/* Open the command for reading. */
		fp = popen("awk '/bela-audio/ { print $8};' /proc/xenomai/sched/stat", "r");
		if (fp == NULL) {
			printf("Failed to run command\n" );
			exit(1);
		}

		oscpkt::Message msg("/address/path");
		/* Read the output a line at a time - output it. */
		// should be just one line
		if(fgets(path, sizeof(path), fp) != NULL)
			msg.pushFloat(atof(path));
		else
			msg.pushFloat(0);
		/* close */
		pclose(fp);

		oscpkt::PacketWriter pw;
		pw.init().addMessage(msg);
		udpClient.send(	pw.packetData(), pw.packetSize());
		usleep(periodSeconds * 1000000);
	}
	return 0;
}

This project will send a float to /address/path representing the percentage CPU usage.

You should run this as an additional service on the board, see https://learn.bela.io/using-bela/bela-techniques/running-a-program-as-a-service/. So, you'd create a project in the IDE, called e.g.: cpu-osc, put this file in there, build it once, and then follow the instructions at the URL above, replacing O2O with cpu-osc.

RafaeleAndrade However, all the Knurl players have notice that the TouchOSC Patch stops to receive information from the instrument after sometime.

is this because the instrument becomes too busy with audio that it can no longer send out OSC?

RafaeleAndrade etime. I did some tests recently and I believe it is causing a break of protocol or on the order of booting things on Bela. I can get messages such as :

A BelaSeverOptions
A BelaSeverOptions
A BelaSeverOptions
Bela disconnected from the system

where do you see that?

RafaeleAndrade Is the pin p2.34 the same digital pin used for the white button from mini bela?

yes

RafaeleAndrade Would I connect this new button as a similar normal digital button set up?

sort of. There is an internal pull-up resistor, so you'd connect P2.34 to a switch and the other side of the switch to ground. Then, when pressing the switch it will behave exactly as it would if you were to press the button on the Bela Mini cape.

RafaeleAndrade Do I need to change anything in the automatic script from mini bela for it?

so no