pi-Stomp!

pi-Stomp is a DIY high definition, multi-effects stompbox platform for guitar bass and keyboards

For more info about what it is and what it can do, go to treefallsound.com

pi-Stomp Software and Firmware

We start with a 64-bit Raspberry Pi lite operating system. We then add MOD, which is an open source audio host & UI created by the awesome folk at moddevices.com

The pi-Stomp hardware requires drivers to interface with the LCD, potentiometers, encoders, footswitches, MIDI, etc.

A pi-Stomp software service, mod-ala-pi-stomp, uses the drivers to monitor all input devices, to drive the LCD and to, among other things, send commands to mod-host for reading/writing pedalboard configuration information.

This repository includes: * the pi-Stomp hardware drivers ('pistomp' module) * the mod-ala-pi-stomp service ('modalapistomp.py' & 'modalapi' module) * setup scripts for downloading/installing the above along with: * python dependencies * MOD software * sound card drivers * system tweaks * hundreds of LV2 plugins * sample pedalboards

Installing

For full installation instructions including etching the initial operating system, see this guide

After first boot, establish an ssh session to the RPi (the password is the one set during OS install):

    ssh [email protected]

Once connected, download the pi-Stomp software:

    sudo apt-get -y install git

    git clone https://github.com/TreeFallSound/pi-stomp.git

    cd pi-stomp

Now run the setup utility to install the software and audio plugins. It could take over a half hour. There are a few setup options based on your system hardware. Typical systems should run:

    nohup ./setup.sh > setup.log | tail -f setup.log

The IQAudio Codec Zero is the default audio card, so the above command is equivalent to adding -a iqaudio-codec (eg: ./setup.sh -a iqaudio-codec). For an audioInjector card, add: -a audioinjector-wm8731-audio For HiFiBerry add: -a hifiberry-dacplusadc For the original v1.x hardware, add -v 1.0

If all went well, the system will reboot, then finally display the default pedalboard

Issues

MIDI learn only working for existing pedalboards

opened on 2023-03-04 19:36:11 by MarnixMeersman

Hi,

I have a problem where I can only assign potentiometers and switches via MIDI-learn when I'm in the pedalboards that came with the installation. If I make a new pedalboards and save it on my pistomp, (I verified it was saved since I could play through it without the pi connected to WiFi) I'm unable to assign any midi control.

I went through every option in the troubleshooting guide on the tree fall sound website. Nothing worked.

Hoping someone can help.

Cheers Marnix

saving plugin presets doesnt work

opened on 2023-02-05 12:53:23 by protectorateindustrial

Saving plugin presets isnt working. Presets disappear after rebooting.

UI restarts when trying to connect with browser

opened on 2023-01-20 23:31:13 by fcebreros

Hi, I dont get any audio processed (bypass sounds OK) and when I try to connect to the pistomp with a browser it starts to load the patch on the screen and then looses connection and screen on the pistomp reloads. I get this error and I'm not sure if it's related to the audio problem. Thanks Frank -- Journal begins at Wed 2022-09-21 22:06:10 -05. -- Jan 20 18:19:39 pistomp systemd[1]: Stopped MOD-ALA-PI-STOMP. Jan 20 18:19:39 pistomp systemd[1]: mod-ala-pi-stomp.service: Consumed 11.116s CPU time. Jan 20 18:19:39 pistomp systemd[1]: Started MOD-ALA-PI-STOMP. Jan 20 18:19:43 pistomp python3[5472]: ERROR:root:Cannot connect to mod-host Jan 20 18:19:44 pistomp systemd[1]: mod-ala-pi-stomp.service: Succeeded. Jan 20 18:19:44 pistomp systemd[1]: mod-ala-pi-stomp.service: Consumed 2.441s CPU time. Jan 20 18:19:46 pistomp systemd[1]: mod-ala-pi-stomp.service: Scheduled restart job, restart counter is at 1. Jan 20 18:19:46 pistomp systemd[1]: Stopped MOD-ALA-PI-STOMP. Jan 20 18:19:46 pistomp systemd[1]: mod-ala-pi-stomp.service: Consumed 2.441s CPU time. Jan 20 18:19:46 pistomp systemd[1]: Started MOD-ALA-PI-STOMP. Jan 20 18:20:32 pistomp systemd[1]: Stopping MOD-ALA-PI-STOMP... Jan 20 18:20:33 pistomp systemd[1]: mod-ala-pi-stomp.service: Succeeded. Jan 20 18:20:33 pistomp systemd[1]: Stopped MOD-ALA-PI-STOMP. Jan 20 18:20:33 pistomp systemd[1]: mod-ala-pi-stomp.service: Consumed 7.021s CPU time. Jan 20 18:20:33 pistomp systemd[1]: Started MOD-ALA-PI-STOMP. Jan 20 18:20:38 pistomp python3[5673]: ERROR:root:Cannot connect to mod-host Jan 20 18:20:39 pistomp systemd[1]: mod-ala-pi-stomp.service: Succeeded. Jan 20 18:20:39 pistomp systemd[1]: mod-ala-pi-stomp.service: Consumed 2.424s CPU time. Jan 20 18:20:41 pistomp systemd[1]: mod-ala-pi-stomp.service: Scheduled restart job, restart counter is at 1. Jan 20 18:20:41 pistomp systemd[1]: Stopped MOD-ALA-PI-STOMP. Jan 20 18:20:41 pistomp systemd[1]: mod-ala-pi-stomp.service: Consumed 2.424s CPU time. Jan 20 18:20:41 pistomp systemd[1]: Started MOD-ALA-PI-STOMP.

No creation of plugin box on the pistomp lcd when a footswitch is connected to any function.

opened on 2022-03-22 09:29:39 by dormirj

Currently, when a footswitch is connected to any function of a plugin in the pedalboard configuration it will not be visible as a box with a name in the pistomp ui on the screen. This is fine if the footswitch controls the bypass button of the plugin, but creates an issue when the footswitch is connected to any other function on the pedal (e.g. tap-tempo, loop record, etc.), because then you can't bypass the plugin from the unit.

A fix for me would be the option to show all plugins not depending on whether they are connected to a footswitch or not, or, probably more involved, to check if the footswitch controls the bypass or something else.

pisound-btn coming back

opened on 2021-11-08 10:26:23 by ozbenh

This is for keeping track of the discussion we had on the forums. Updates to pisound-btn will cause it to re-enable itself which we don't want.

Blokas has now merged my pull requests, so any time soon, we should see pisound-btn 1.15 and patchbox-wifi 1.0.0 hitting the repos (well, I hope...)

When they show up, we should update the setup/update script to ensure we pull in patchbox-wifi and remove the pisound-btn package completely (and pisound-ctl while at it).

Confusing Controller class hierarchy

opened on 2021-11-01 05:30:47 by ozbenh

So there's a base class that doesn't do much, there's duplication of the midi message config accross the subclasses, it's unclear what self.value is for esp vs. self.last_read that some subclass maintain, etc...

I'm happy to help clean that up (ie, write the code), this issue is to discuss what the end result should look like.

I would suggest having a more comprehensive controller base class that has the basic support for setting/sending midi messages, getting/setting a "value" and notifying handler via callback of changes.

A "value" could be the enabled state for a footswitch, the analog value for analog controllers, etc...

Is there any reason why set_value does nothing on analogmidicontroller (and value changes aren't reflected in self.value) ? Note: the test backend currently exploits this "feature' but it's a hack, i would rather add a callback.