MODEP UI customization: is it possible?

Patchbox OS MODEP
1

hello I’m new around here. today I installed patchbox on a Raspberry 5 and I was testing some things in MODEP. this is great! so much fun…

this is my query: I just want to use MODEP for the moment, as one more pedal for my guitar set. is there any way that every time I start the Raspberry Pi I don’t have to open a browser, put the IP, go to the pedalboard tab and choose one, all this on a super small screen? is there a way that the screen only shows me the pedalboards that I have stored and I only have to choose one? or even if it is possible to modify the MODEP IU so that it only shows the tab of choice of pedalboards and not the main screen, unusable on the small screen I have? just a simple interface with preset selection

thanks

2

@lucayala welcome to the community!

First off, modifying the UI of modep is possible but could be a difficult and time consuming task.

Beyond that there are a couple of options:

  1. Use the PiSound app if you have an android device. You’ll need to put the pedalboards that you want to be able to select from in a specific bank.
  2. You could try out my node-red dashboard app that can be installed on the pi: Node-Red and MODEP

I made a diy midi controller and am in the process of expanding that code to allow for selection of a pedalboard but that project is not progressing very quickly.

2 Likes
3

I found this topic: Open Chromium Full Screen at Startup that is close to what I was looking for

that’s another great solution. excellent work. I’m going to try the 2 options to see which one works best for me

thanks a lot!

4

In my experience the modep interface is hard to use on a small screen. Even harder if it’s just a touch screen. The few times I’ve tried I’ve messed up my pedalboard.

5

yes. I don’t want to use the interface. I just want to have easy access to the pedalboards list to choose the desired one. so I originally asked for some way to modify the MODEP interface so that it only shows the list of pedalboards. but your solution with node-red is much better

6

sorry, @jtemple967. I can’t install nodered. I’m using a RP5 with patchbox 64-bits. I get a “the following packages have unmet dependencies” message. and it list nodejs, npm and python3, but the 3 are installed. maybe nodered can’t work in the beta 64-bit OS

7

@lucayala I’m running node-red on my Pi5 with the 64-bit patchbox beta. It might be a permissions issue and I’ll be the first to admit that my instructions may not be 100% correct. I wrote some of it from memory.

First, I couldn’t remember if node-red was installed at all. If installed it would be listed under the “Programming” menu on the desktop. If not installed, when you installed node-red did you prefix the command with “sudo” so it looks like this: “sudo apt-get install nodered”? Might be a permissions issue.

8

it’s not installed and I did use sudo in the command. I don’t know what can be

9

Can you post the command and the results here? I’d like to see what the messages say.

10

here it is:

Linux patchbox 6.6.20+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.20-1+rpt1 (2024-03-07) aarch64
  ___      _      _    _                ___  ___
 | _ \__ _| |_ __| |_ | |__  _____ __  / _ \/ __|
 |  _/ _` |  _/ _| ' \| '_ \/ _ \ \ / | (_) \__ \
 |_| \__,_|\__\__|_||_|_.__/\___/_\_\  \___/|___/

Run `patchbox` to customize.

Last login: Thu Jan 16 20:15:07 2025
patch@patchbox:~ $ sudo apt-get install nodered
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 nodered:armhf : Depends: nodejs:armhf (>= 12) but it is not going to be installed
                 Depends: npm:armhf (>= 7) but it is not installable
                 Depends: python3:armhf (>= 3) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

nodejs is already the newest version (18.19.0+dfsg-6~deb12u2)
npm is already the newest version (9.2.0~ds1-1)
python3 is already the newest version (3.11.2-1+b1)

11

Hmm…let me check on my setup at home. I wish I had written down the instructions.

1 Like
12

I can help

I have a workflow that involves using the modep interface to create pedal banks, copying the LV2 data with some scrips, setting up all the LV2 simulators in memory, and the Jack connections in-between - but for system I/O, and then using a Rust programme to switch the I/O rapidly in response to a pedal

I have started using in live

The code is here: GitHub - worikgh/120Pedal

This works well. The hardest part is getting decent hardware for the pedals

On a PI4 I was switching pedals in about 100ms, which is fast enough to not hear a glitch

The Modep mod-ui stack is brilliant. Makes building simulated pedal banks (LV2) a breeze. It is unsuitablr live work. Horses for courses.

Any way I am very keen to help you get yours set up

W

13

@worik would love to see some screenshots of what you’ve put together

14

It is not really the point. There is nothing to see.

The user interface is a pedal and the command line to set it up.

15

@lucayala I haven’t forgotten my intent to get you some good instructions on how to setup my node-red dashboard. I realized that one of the things that makes it work is a change to the MOD web server to get the current snapshot. I made that change locally but never got beyond that.

This weekend I created a PR for Blokas to incorporate that change into their code base. Once that is done you’ll be able to install node-red and my dashboard and it should work. Stay tuned, sorry about the delay.

1 Like
16

no need to apologize, @jtemple967. thank you very much for your work