display simple text from PureData?

Remork

ok, so if i make changes to the background process' render.cpp, i need to run it in the foreground at least once.
then reboot. that works.
getting somewhere now! 🙂

Remork

well.. good news and bad news.
the startup sequence works beautifully when i run it in the background, behind a simple OSC test Pd patch.
the OSC parsing still needs some attention, but it seems to work.
note that this is without audio, arrays for randomness etc.

however.
when i try to run my actual patch - the big one - i get this in the console:

Nov 03 17:16:48 bela stdbuf[254]: make: Warning: File 'libraries/OnePole/build/OnePole.d' has modification time 128404949 s in the future
Nov 03 17:16:48 bela stdbuf[254]: Running /root/Bela/projects/JukeBoxArrays/JukeBoxArrays -p64 -C4 -B16 -H0 -N1 -G1 -M0 -D0 -A0 --pga-gain-left=10 --pga-gain-right=10 -X0
Nov 03 17:16:48 bela stdbuf[254]: make: warning: Clock skew detected. Your build may be incomplete.
Nov 03 17:16:48 bela stdbuf[254]: make: Leaving directory '/root/Bela'
Nov 03 17:16:49 bela systemd[1]: bela_startup.service: Service hold-off time over, scheduling restart.
Nov 03 17:16:49 bela systemd[1]: Stopped Run Bela at boot.
Nov 03 17:16:49 bela systemd[1]: bela_startup.service: Start request repeated too quickly.
Nov 03 17:16:49 bela systemd[1]: Failed to start Run Bela at boot.
Nov 03 17:16:49 bela systemd[1]: bela_startup.service: Unit entered failed state.
Nov 03 17:16:49 bela systemd[1]: bela_startup.service: Failed with result 'start-limit-hit'.

not sure what that means, all i know is it doesn't work.
am i asking too much of the poor thing?

giuliomoro

can you post the full log you get with

journalctl -fu bela_startup -n 1000 | cat

Are you using P9.27 for anything? That'd be the Bela button pin and should be left alone ...

Remork

will do tomorrow.
i was planning on breaking out P9.27 for a graceful shutdown button, so not using it for anything at the moment.

Remork

here we are:
-- Logs begin at Thu 2016-11-03 17:16:43 UTC. --
Nov 03 17:16:44 bela stdbuf[105]: make: Entering directory '/root/Bela'
Nov 03 17:16:44 bela stdbuf[105]: make: Warning: File 'libraries/OnePole/build/OnePole.d' has modification time 128404952 s in the future
Nov 03 17:16:45 bela stdbuf[105]: Running /root/Bela/projects/JukeBoxArrays/JukeBoxArrays -p128 -C4 -B16 -H0 -N1 -G1 -M0 -D0 -A0 --pga-gain-left=10 --pga-gain-right=10 -X0
Nov 03 17:16:45 bela stdbuf[105]: make: warning: Clock skew detected. Your build may be incomplete.
Nov 03 17:16:45 bela stdbuf[105]: make: Leaving directory '/root/Bela'
Nov 03 17:16:45 bela systemd[1]: bela_startup.service: Service hold-off time over, scheduling restart.
Nov 03 17:16:45 bela systemd[1]: Stopped Run Bela at boot.
Nov 03 17:16:45 bela systemd[1]: Started Run Bela at boot.
Nov 03 17:16:45 bela stdbuf[165]: make: Entering directory '/root/Bela'
Nov 03 17:16:46 bela stdbuf[165]: make: Warning: File 'libraries/OnePole/build/OnePole.d' has modification time 128404951 s in the future
Nov 03 17:16:46 bela stdbuf[165]: Running /root/Bela/projects/JukeBoxArrays/JukeBoxArrays -p128 -C4 -B16 -H0 -N1 -G1 -M0 -D0 -A0 --pga-gain-left=10 --pga-gain-right=10 -X0
Nov 03 17:16:46 bela stdbuf[165]: make: warning: Clock skew detected. Your build may be incomplete.
Nov 03 17:16:46 bela stdbuf[165]: make: Leaving directory '/root/Bela'
Nov 03 17:16:46 bela systemd[1]: bela_startup.service: Service hold-off time over, scheduling restart.
Nov 03 17:16:46 bela systemd[1]: Stopped Run Bela at boot.
Nov 03 17:16:46 bela systemd[1]: Started Run Bela at boot.
Nov 03 17:16:46 bela stdbuf[192]: make: Entering directory '/root/Bela'
Nov 03 17:16:47 bela stdbuf[192]: make: Warning: File 'libraries/OnePole/build/OnePole.d' has modification time 128404950 s in the future
Nov 03 17:16:47 bela stdbuf[192]: Running /root/Bela/projects/JukeBoxArrays/JukeBoxArrays -p128 -C4 -B16 -H0 -N1 -G1 -M0 -D0 -A0 --pga-gain-left=10 --pga-gain-right=10 -X0
Nov 03 17:16:47 bela stdbuf[192]: make: warning: Clock skew detected. Your build may be incomplete.
Nov 03 17:16:47 bela stdbuf[192]: make: Leaving directory '/root/Bela'
Nov 03 17:16:47 bela systemd[1]: bela_startup.service: Service hold-off time over, scheduling restart.
Nov 03 17:16:47 bela systemd[1]: Stopped Run Bela at boot.
Nov 03 17:16:47 bela systemd[1]: Started Run Bela at boot.
Nov 03 17:16:47 bela stdbuf[218]: make: Entering directory '/root/Bela'
Nov 03 17:16:47 bela stdbuf[218]: make: Warning: File 'libraries/OnePole/build/OnePole.d' has modification time 128404949 s in the future
Nov 03 17:16:48 bela stdbuf[218]: Running /root/Bela/projects/JukeBoxArrays/JukeBoxArrays -p128 -C4 -B16 -H0 -N1 -G1 -M0 -D0 -A0 --pga-gain-left=10 --pga-gain-right=10 -X0
Nov 03 17:16:48 bela stdbuf[218]: make: warning: Clock skew detected. Your build may be incomplete.
Nov 03 17:16:48 bela stdbuf[218]: make: Leaving directory '/root/Bela'
Nov 03 17:16:48 bela systemd[1]: bela_startup.service: Service hold-off time over, scheduling restart.
Nov 03 17:16:48 bela systemd[1]: Stopped Run Bela at boot.
Nov 03 17:16:48 bela systemd[1]: Started Run Bela at boot.
Nov 03 17:16:48 bela stdbuf[245]: make: Entering directory '/root/Bela'
Nov 03 17:16:48 bela stdbuf[245]: make: Warning: File 'libraries/OnePole/build/OnePole.d' has modification time 128404949 s in the future
Nov 03 17:16:48 bela stdbuf[245]: Running /root/Bela/projects/JukeBoxArrays/JukeBoxArrays -p128 -C4 -B16 -H0 -N1 -G1 -M0 -D0 -A0 --pga-gain-left=10 --pga-gain-right=10 -X0
Nov 03 17:16:48 bela stdbuf[245]: make: warning: Clock skew detected. Your build may be incomplete.
Nov 03 17:16:48 bela stdbuf[245]: make: Leaving directory '/root/Bela'
Nov 03 17:16:49 bela systemd[1]: bela_startup.service: Service hold-off time over, scheduling restart.
Nov 03 17:16:49 bela systemd[1]: Stopped Run Bela at boot.
Nov 03 17:16:49 bela systemd[1]: bela_startup.service: Start request repeated too quickly.
Nov 03 17:16:49 bela systemd[1]: Failed to start Run Bela at boot.
Nov 03 17:16:49 bela systemd[1]: bela_startup.service: Unit entered failed state.
Nov 03 17:16:49 bela systemd[1]: bela_startup.service: Failed with result 'start-limit-hit'.

so apart form the date being way off (this was run this morning at 8:30), maybe except for that one file, it seems to have done the same thing 5 times?
screen routine starts up nicely, but the Pd patch itself is unresponsive.

Remork

to give you an idea of what's going on in the patch:

at startup, i'm building three arrays. two are filled with a list of numbers from .txt files (just numbers in random order, but i do it this way to avoid repeats, part of the [urn] solution), the third is filled with a count up from 0 to 272.
these are the 'originals' and are copied into 'local' arrays using the [tabplay~]/[tabwrite~] combo you suggested.
i set one digital pin for button input (digital 6, Pd 17).
i load three more .txt files into [text]objects for later use with the display (list of artist/title) and [readsf~] objects (lists of soundfile paths.).

i'm holding off on opening the OSC connection, because i don't know whether it's happening in the right order - didn't want Pd to connect to something that isn't there. so what i do now is to have the startup code for the display (the background script, 1309_Display) show me an invitation to do a long press on the button. that way i'd know the OSC receiver in that same script is up and running in the background.
a long press on the button would open the connection in Pd, and shift the function of the button to the random file selection for the remainder of running time.

giuliomoro

From the log it seems that the project doesn't start at all, or you'd get the Pd
initialisation printouts. Does the project run fine in the IDE with the OSC program in the background?

Can you also add -v to the project's custom command line options, then select •none• at boot and then the JukeBoxArrays project again? That should make the startup log more verbose

Remork

giuliomoro Does the project run fine in the IDE with the OSC program in the background?

not sure i understand this.
you mean not having any 'program at startup' in the settings, and start manually from the IDE?
will have to try that. will be this afternoon, running late as it is!

Remork

ok, so it won't start up from the IDE either.

Building project ... Build finished Running project ... Bela stopped

probably something wrong with the patch then? will try to pick it apart and rebuild block by block.

giuliomoro Can you also add -v to the project's custom command line options

where do i do that?

Remork

now that i'm looking over that log - does

bela_startup.service: Service hold-off time over, scheduling restart. Stopped Run Bela at boot. Started Run Bela at boot.

mean that it's booting, shutting down, rebooting, shutting down, etc..?
because i could understand it only wants to do that 5 times 🙂

hah. log.

[ it's log, it's log
it's big it's heavy it's wood
log, log
it's better than bad, it's good ]

haven't had much sleep

giuliomoro

I mean when the board boots by the time the IDE shows up, your Bela Pd program will have given up starting after five attempts as we have seen from the log. Then, try starting it from the IDE: does it run OK?

giuliomoro

Remork ok, so it won't start up from the IDE either.

try to clean the project and rebuild . You may have ended up with a corrupted file.

Remork where do i do that?

"Settings->user command line arguments:"

but hopefully the above fixes it already.

Remork

giuliomoro try to clean the project and rebuild . You may have ended up with a corrupted file.

Yay! that seems to have done it.
genius.

still need to iron out some rough spots, but this is about as far as i ever got with it.
i can smell the finish line. again. 🙂

giuliomoro

Remork again

🔝

Remork

is there a way to send two or three strings in a single OSC message?

like in the OLED example

if (msg.match("/tr").popStr(trString).isOkNoMoreArgs())
    {
        const char *ctrStr = trString.c_str();

        setTextSize(1);
        setTextColor(WHITE);
        setCursor(10,20);
        print_str(ctrStr);

        Display(); 
    }

something that becomes

if (msg.match("/tr").popStr(trStringA).popStr(trStringB).isOkNoMoreArgs())
    {
        const char *ctrStrA = trStringA.c_str();
        const char *ctrStrB = trStringB.c_str();
        setTextSize(1);
        setTextColor(WHITE);
        setCursor(10,20);
        print_str(ctrStrA);

        setTextSize(2);
        setCursor(10,50);
        print_str(ctrStrB);

        Display();  
    }

?? well, you get what i'm looking to do i hope. 🙂

giuliomoro

Remork if (msg.match("/tr").popStr(trStringA).popStr(trStringB).isOkNoMoreArgs())

this should work. If you want to do a variable number of arguments(or an arbitrary one without a lot of code duplication), see what I have done here https://forum.bela.io/d/314-is-anyone-successfully-using-i2c-oled-lcd/99

giuliomoro

but if the question is about the Pd side of things, I have no idea!

Remork

well, as i understand it, a symbol in Pd equals a string for OSC.
so if i can pack symbols into a list, i'm hoping it will get picked apart as seperate symbols (=multiple strings) by the parseMessage thingy. will try.

Remork

well, that does work indeed!
just needed to define the new variables:
std::string trStringA; std::string trStringB; std::string trStringC;

now i can go
if (msg.match("/Selection").popStr(trStringA).popStr(trStringB).popStr(trStringC).isOkNoMoreArgs())

and then define what to do with that info.
on the Pd side, every one of those strings is a symbol, and i just packed them into a list:

[pack s s s]
l
[oscformat /Selection]
etc.

giuliomoro

brilliant!

« Previous Page Next Page »