Author Topic: screen and code  (Read 367 times)

1Bit

  • Newbie
  • *
  • Posts: 2
    • View Profile
screen and code
« on: June 15, 2021, 10:56:35 AM »
hello,
first I want to say how incredible this project is
I found out only today about this but I've been working on a similar scenario for a while now
you did very well and even the size is perfect

however, I wanted to ask
as I've already invested in some of the stuff, I've been using my PI4 and modep for a while with a USB audio card and midi
I have a midi controller as well and things are working fine
I was just working on building the whole thing into one portable pedalboard but not yet decided on the size etc. (if leaving the interface out of the midi pedalboard or all in one - not decided yet

the things I haven't be able to find instruction on is the screen
how you pull the information about the preset from the modep software and how you are able to display them

can part of your code be used to implement such a screen and then use a midi controller to control that?
can you point me to the right part of the code? or ,,, any help/pointers would be highly appreciated

thank you in advance for any input

Randall (Admin)

  • Administrator
  • Full Member
  • *****
  • Posts: 212
    • View Profile
Re: screen and code
« Reply #1 on: June 24, 2021, 12:52:22 AM »
Sorry for the slow reply.

Yes, you could probably use pi-stomp code to drive a display.  When you say, "use a midi controller to control that", I'm not exactly sure what you mean.  Maybe, can it display visual feedback for the parameters values that you're controlling via midi?  That answer would be, "No".  The display is more or less a mini representation of the current pedalboard and preset along with visual navigation for parameter and global settings changes.  It can give visual feedback of pi-stomp footswitch settings because those are connected to the GPIO of the pi.  The pi-stomp hardware simply passes any MIDI messages coming in via the USB port of DIN MIDI jacks on to MODEP.  The pi-Stomp specific software doesn't currently listen for MIDI, it just sends it.  And MODEP, unfortunately doesn't publish any info when it receives a change (via MIDI or via the MOD UI).
 
That said, If you do want to access MODEP data or make pedalboard/preset/plugin changes, you could likely pilfer some pi-Stomp code.  It uses Rest calls to MODEP.  Those calls are all in these two source files:
https://github.com/TreeFallSound/pi-stomp/blob/master/modalapi/mod.py
https://github.com/TreeFallSound/pi-stomp/blob/master/modalapi/pedalboard.py

Search for "root_uri"

If you need to get/set plugin parameters, that required API's that I hack into MODEP.  The scripts that perform the hack are here:
https://github.com/TreeFallSound/pi-stomp/tree/master/setup/mod-tweaks


1Bit

  • Newbie
  • *
  • Posts: 2
    • View Profile
Re: screen and code
« Reply #2 on: June 24, 2021, 04:39:32 AM »
thank you for the reply

and thank you for pointing me to the right code
yes, I was thinking to use a small midi controller I have for interacting with the pedalboard (so thank you for clarifying that it wont work)  :)

I will be thinking then in implementing some controls over the GPIO as I'm not using it for anything at present
sound card and midi are both USB

will look at the code
thanx again for your reply :)