Sending unique information to different displays

JoelBird

not sure if it's relevant but if I run O2O by itself I get the following messages:

alt text

giuliomoro

not sure if it's relevant but if I run O2O by itself I get the following messages:

I assume that's because it's already running in the background and so the UDP port is already taken by the background process.

JoelBird

Okay just tested with a 100 ms refresh and now the displays are as responsive as when only using one display (with the obvious reduction in frame rate of course).

JoelBird

I seem to remember in one my of my other posts [https://forum.bela.io/d/3438-updating-parameter-values-when-using-osc] you suggested that using latest branch of O2O should result in more responsive displays, so I'll give that a try.

giuliomoro

JoelBird if(gDisplayPtr == kColumns) {
// the buffer is full, schedule the other task, which will send the data to the display
Bela_scheduleAuxiliaryTask(gSendToDisplayTask);
}

this schedules the thread 128 samples after a trigger. How many times that happens per second depends on how many times it triggers per second, which in turn depends on gFrequency, with a maximum of 44100/128 = 344 times per second.

JoelBird

if(gDisplayPtr == gRefreshSamples)
             gDisplayPtr = 0;

But doesn't this bit mean that the display pointer only resets with the refresh rate (which in this case is set to 20 Hz / 50 ms)?

giuliomoro

oh yes you are right, sorry I didn't notice that earlier. Yup looks good. Just reduce the frame rate and use the other branch as per the other thread.

giuliomoro

As the displays are handled in the same thread, they'll slow each other down if you are sending to them both every time. If you want higher throughput overall, try sending to each only when a change relevant to that one takes place.

If you need to have both displays refresh at a higher frame rate, then the best option is to connect each of those to a dedicated I2C bus. Then you can have two instances of O2O running, one for each display.

JoelBird

Okay, I tried updating both the OscSender library and to the O2O-only-latest branch, and I am now able to run both screens at the desired refresh rate with no issues. However, I no longer seem able to send different things to each display, as no matter what I try it sends the same function to both screens. If I only have one message set up (eg waveform) I can select which screen it goes to as expected, but with two messages it only sends the second one, and it gets sent to both displays.

giuliomoro

I pushed a commit that should hopefully fix that, please try again with the latest only-latest branch

JoelBird

I'm still getting the same result, with both screens displaying the same thing. I tried setting up a second sendToDisplay function that only does the one thing, so that each can be called separately, which had some weird results. The function that displays text (the using the /number message) works as expected, but the /waveform function just will not work unless it is the only one being called. With both running the O2O project gave these messages:

root@bela ~/Bela# journalctl -n 20 -u O2O-only-latest | cat
-- Logs begin at Thu 2016-11-03 17:16:43 UTC, end at Thu 2023-08-31 10:53:35 UTC. --
Aug 31 10:53:33 bela O2O-only-latest[949]: Message from 127.0.0.1:54427
Aug 31 10:53:33 bela O2O-only-latest[949]: received /number 448
Aug 31 10:53:33 bela O2O-only-latest[949]: Message from 127.0.0.1:54427
Aug 31 10:53:34 bela O2O-only-latest[949]: received /number 449
Aug 31 10:53:34 bela O2O-only-latest[949]: Message froOscReceiver: oscpkt error parsing received message: 3
Aug 31 10:53:34 bela O2O-only-latest[949]: OscReceiver: oscpkt error parsing received message: 3
Aug 31 10:53:34 bela O2O-only-latest[949]: OscReceiver: oscpkt error parsing received message: 3
Aug 31 10:53:34 bela O2O-only-latest[949]: OscReceiver: oscpkt error parsing received message: 3
Aug 31 10:53:34 bela O2O-only-latest[949]: OscReceiver: oscpkt error parsing received message: 3
Aug 31 10:53:34 bela O2O-only-latest[949]: OscReceiver: oscpkt error parsing received message: 3
Aug 31 10:53:34 bela O2O-only-latest[949]: OscReceiver: oscpkt error parsing received message: 3
Aug 31 10:53:34 bela O2O-only-latest[949]: OscReceiver: oscpkt error parsing received message: 3
Aug 31 10:53:34 bela O2O-only-latest[949]: OscReceiver: oscpkt error parsing received message: 3
Aug 31 10:53:34 bela O2O-only-latest[949]: OscReceiver: oscpkt error parsing received message: 3
Aug 31 10:53:34 bela O2O-only-latest[949]: OscReceiver: oscpkt error parsing received message: 3
Aug 31 10:53:34 bela O2O-only-latest[949]: OscReceiver: oscpkt error parsing received message: 3
Aug 31 10:53:34 bela O2O-only-latest[949]: OscReceiver: oscpkt error parsing received message: 3
Aug 31 10:53:34 bela O2O-only-latest[949]: OscReceiver: oscpkt error parsing received message: 3
Aug 31 10:53:34 bela O2O-only-latest[949]: OscReceiver: oscpkt error parsing received message: 3
Aug 31 10:53:35 bela O2O-only-latest[949]: OscReceiver: oscpkt error parsing received message: 3

giuliomoro

JoelBird I'm still getting the same result, with both screens displaying the same thing. I tried setting up a second sendToDisplay function that only does the one thing, so that each can be called separately, which had some weird results.

This was harder to track down than I hoped it would be. It is due to u8g2 internally sharing the same buffer between all displays. If you get the latest version of that branch, clean the project and rebuild it entirely it should work now. I tested it the best I could without having actual displays.

JoelBird Aug 31 10:53:34 bela O2O-only-latest[949]: OscReceiver: oscpkt error parsing received message: 3

this looks like the result of an error in the formatting of the sent message. You can hopefully go back to the previous version of the code that was working.

JoelBird

Everything's now working exactly as expected, thank you so so much for all your help