pepper - loop scripts

thetechnobear

can we add the 'loop' patch behaviour too pepper as default.

Ive had a quick play

differences to salt , are

/usr/local/bin/bela-cape-btn --pin 89 --hold /opt/Bela/bela_button_hold.sh   --delay 10 --monitor-click 0 --verbose --hold-press-timeout-ms 1000 --pressed 1

so pin # and --pressed 1

(I think the timeout, for both salt n' pepper, should be extended to 2 seconds, 1 seconds is a bit easily to false trigger)

this could be added to

I believe we can use the /opt/Bela/bela_button_hold.sh , as that just stops current patch.
which will then make next patch run?!

so we can pretty much just copy resources/salt to resources/pepper

is something else rely on ~/.bela/belaconfig = salt to make this work?

giuliomoro

thetechnobear is something else rely on ~/.bela/belaconfig = salt to make this work

no, all this does is telling the core to invert the readings/writes from/to the analog/digital I/O, which is not needed for Pepper, so you should be fine.

giuliomoro

oh also the looping behaviour is enabled for all the boards, just select •loop_• as the program to run on loop from the IDE's "Project settings"

thetechnobear

cool, so I guess if I add the above in a service then it should work ... I'll test it out.

do you want as a PR for pepper?

I guess, Id still need to include a make_pepper script, just to enable the service?!

is there anyway to tell at runtime if its a salt,pepper, or bela?
this is something that's often needed...

2 scenarios i run into (as i have bela, salt, pepper and minis)

voltage range differences,
i have to scale the float differently. e.g salt = -5,5v peppers is 10v in but 5v out, bela is 5v, 5v

ui differences
salt has 4 buttons/leds, pepper 2 buttons but 10 leds
bela = no ui.

runtime or compile time?
compile time is probably best, since scaling voltages is often done in render loops, so const will be more efficient.
ui, doesnt really matter so much as its out of the render loop.

giuliomoro

thetechnobear is there anyway to tell at runtime if its a salt,pepper, or bela?

You can call BelaHw Bela_detectUserHw() (see here) at runtime to parse ~/.bela/belaconfig, or parse it for yourself at compile time. (note: I have refactored this code in a different branch so that the board_detect command returns the content of ~/.bela/belaconfig (without need to parsing it for yourself), but this is not getting mainlined very soon because it's intertwined with many other changes).

However, currently there is not a Pepper type. Adding support for it would require editing the board_detect.cpp file to make Pepper behave like Salt currently does. Not sure it's worth the effort, because of the forthcoming refactoring. Given how you are ok with a compile-time solution, why don't you just add a manual compile-time flag for now?

thetechnobear

giuliomoro

yeah, I'm already doing with compile time flags... so not an issue for my projects.
really its more about if others want to share projects...

ok, Ive added the pepper scripts for button B1 to switch patches like Salt, and pushed to my current PR.
i've not added make_pepper as you were talking about refactoring in this area.
so I guess you can consider these scripts as something you might want to incorporate in that.

one 'interesting' thing I found, was the button service stops working once it has switched patches the first time.
the reason is, the polling seems to be failing. the script is returning ok, and if I don't call the script to kill the patch it works fine

my 'guess' is that for some reason starting a new patch, is some how making it so gpio cannot be read anymore by bela-cape-btn ... (oddly this works fine on salt, perhaps hardware diff on pin 60 vs 89?)

for now, Ive worked around this by simply restarting the service after switching patches, and this is working fine for me.

anyway, its cool to be able to switch patches on pepper now 🙂

giuliomoro

thetechnobear my 'guess' is that for some reason starting a new patch, is some how making it so gpio cannot be read anymore by bela-cape-btn ... (oddly this works fine on salt, perhaps hardware diff on pin 60 vs 89?)

It seems like a good guess. The pin used on Salt is not a "Bela Digital" pin. It's probably failing when it cannot export the pin (because it has already been exported by someone else, namely the Bela program). Also interesting, maybe the issue is that the "stopping" Bela program unexports it? Have to look into it.

thetechnobear anyway, its cool to be able to switch patches on pepper now

nice 🙂