Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Randall (Admin)

Pages: [1] 2 3 ... 15
If you have ssh connectivity but not browser, then I might suspect browser settings, dhcp, etc.  But since you have ssh access, might try figuring out the IP address using either:

Code: [Select]
ping pistomp.local

Code: [Select]
ifconfig    (inet for wlan0 is what you want)

Then enter that IP address (eg. to your browser URL bar.

To toggle hotspot mode from the command line:
Code: [Select]
sudo systemctl enable wifi-hotspot;  sudo systemctl start wifi-hotspot
The default password is: pistompwifi

To switch back:
Code: [Select]
sudo systemctl stop wifi-hotspot;  sudo systemctl disable wifi-hotspot

General / Re: Availability pi-stomp v3?
« on: November 27, 2023, 01:31:58 PM »
True, pi-Stomp Core (v2) sold out long ago.  v3 will be the next available kits.  v3 prototypes are working well.  We'll do a slight PCB change.  Firmware is mostly done.  We have enclosure prototypes.  Instruction and user manuals have been started.  We're still working out part supply issues and a few manufacturing issues, those are beyond our control and thus, the main unknowns.  So, I can't tell you when.  We're Hoping by February.  We'll update the news page and post something here when we have some more clarity.

There was an issue that I fixed on beta last week.  Without that fix, it was possible for the screen to blank without any obvious error from the pi-stomp service.  If you're still having that issue, I suggest you update your software.

To do that, you can run:
git pull

The change I made requires an extra package that would install, but to avoid you reinstalling, you could just add the package manually yourself:
sudo /usr/bin/pip3 install RPi.version

Then restart with ps-run

Regarding your other questions:
Trigger bypass via MIDI?  Not currently.  Would require that pi-Stomp be a MIDI listener which it currently is not.  Mod does the listening.  Because of that, MOD WILL reflect plugin bypass or parameter tweaks that were mapped to a MIDI controller (pi-Stomp or external controller connected via DIN/USB/OSC).

MOD-UI doesn't publish change events, except for Pedalboard changes.  So that's the only MOD-UI change that the LCD will respond to.

If you're display is going white though, that's an unexpected malfunction.  The audio dropping too.  Both of those could be due to MOD problems or audio card problems.  Running the pi-stomp service manually, might reveal something.  To do that:


Definitely would always love to hear whatever feedback you have, good, bad, or otherwise.

One additional caveat regarding the 'beta' branch:  It's mainly been used for v3 development.  We strive for backward compatibility with v2 and v1 even, but we're not actively testing that beta branch on v1 and v2 hardware.  We certainly will before merging it to master, but just be warned that some stuff that used to work, could be broken, or is simply missing because we've not re-implemented it using the new LCD UI lib, yet.  Analog knob and expression assignments for example, aren't being drawn yet.

Since it requires some additional packages and OS setup, you'll need to install from scratch.  When it comes time to clone, use:  git clone -b beta

Building pi-Stomp / Re: pi-Stomp v3 with rpi5
« on: October 03, 2023, 01:41:16 AM »
I did see a lot of sellers with the "sign up and we'll email you" type, but I pre-ordered from Sparkfun and they have already charged my card, their confirmation calls it a "purchase" and states: "Your order has been received, and will be processed soon."

That said, given all the pent up demand from the last two years, I wouldn't be overly surprised if I get a mail eventually saying "sorry, we have refunded your purchase due to limited stock".


I get that the footswitch display is somewhat redundant.  Back in 2022, a user like yourself created the foundation for a better, more customizable LCD UI.  I integrated that a few months ago into the 'beta' branch.  That branch is usable, but still has some rough edges so won't be ready for general use until probably December.  But, I would recommend that code base if you're going to be modding the LCD code.   It's much more simple to code, it looks better, adds overlay dialogs, and the sections (panels) of the screen (like the plugin grid) are scrollable.

If you wanted to avoid showing the footswitches, you could just comment out calls to draw_footswitch() and draw_unbound_footswitches()

And if you want the plugin grid to extend into that space, just grow the Y dimension of the 'main_panel' from 170 (line 106) to 240.

For testing, you'll want to stop the pi-stomp service and then run it manually.  There are shortcut commands available for that:

Building pi-Stomp / Re: pi-Stomp v3 with rpi5
« on: October 02, 2023, 12:36:48 AM »
... and yeah, hardware-wise, pi-Stomp v3 was designed around the pi4, but since it appears that pi5 should have full GPIO compatibility and footprint compatibility (well, the USB and Eth ports swapped locations, but still), we're guessing it can be a drop in replacement from the hardware point of view.

Micah and I each have a pi5 on pre-order so we can be ready ASAP to make pi-Stomp work with it and take advantage of the huge horsepower advantage.

Hacking pi-Stomp / Re: RGB stomp switch led
« on: September 04, 2023, 11:27:16 PM »
See this line:

LED_DMA = 12          # DMA channel to use for generating signal (try 10)   # TODO XXX need to figure this out

12 worked for pi3a+, 10 appears to work for pi4.  Please try 10.  That got rid of the DMA errors and the pi-stomp error for me.

As the my TODO comment suggests, we need to figure this out  ;)

Using pi-Stomp / Re: MIDI works on one channel only
« on: September 01, 2023, 01:51:02 PM »
There are tons of options:

but I can't tell ya why you can't connect.  The hotspot presented, is not specific to pi-stomp.  I'd wonder if it's a security setting on your computer not allowing connection.  Make sure you are physically close to it. 

Using pi-Stomp / Re: MIDI works on one channel only
« on: August 31, 2023, 11:22:23 AM »
Yes.  ssh then:
a) 'sudo raspi-config' > System Settings
b) edit /etc/hostapd/hostapd.conf

Using pi-Stomp / Re: MIDI works on one channel only
« on: August 30, 2023, 11:17:35 PM »
The default password for the hotspot is 'pistompwifi'

Using pi-Stomp / Re: MIDI works on one channel only
« on: August 30, 2023, 12:51:45 AM »
If it's "working", as in the LCD is displaying everything, audio is passing, etc. but you can't connect the MOD-UI, try with a fresh browser tab and enter: pistomp.local/

(with the trailing slash)

If that doesn't seem to work, can you ssh to it?  If neither MOD-UI or ssh works then you can either see if a reboot fixes the wifi issue, or switch to Hotspot mode (via system menu) and avoid your router all together. 

Using pi-Stomp / Re: Filer Manager
« on: August 26, 2023, 03:43:09 PM »
It's not pi-Stomp specific, but pi-Stomp software v2.1 and later include a more recent version of MOD which has a file manager.

I have a tutorial here for IR files

Audio files are in the same location in the MOD-UI

Using pi-Stomp / Re: parametric knobs
« on: August 07, 2023, 05:56:28 PM »
By "highlight a pedal in the SW", do you mean select a plugin via the LCD and the "knobs" will be reassigned to controls of that selected plugin?

As you probably know, currently, All "knobs", whether they are pots connected as analog controllers, or knobs connected via MIDI, are seen as MIDI CC inputs.  You can map them to specific parameters on specific plugins on a pedalboard.  So the knob functions can change per pedalboard, but not within the current pedalboard.

You can also longpress on a plugin to get a menu of parameters for that plugin, then tweak, but I'm guessing you're still looking for an easier solution for live tweaking and I totally understand that one wouldn't want to traverse menus.

The MOD Dwarf has 3 tweak knobs.  In "Control Mode" it will display 3 parameters at a time, then you can "page" thru to additional parameters (they say up to 8 pages).  But this doesn't seem much better, right?

The issue that I see, is how would one specify which parameters to offer as tweakable when a plugin is selected?  Some plugins have dozens of parameters.  It appears that MOD just displays the first ones it finds.  If your pedalboard/plugins have too many, too bad, they don't show.

So, anyway, bottom line is the MOD software doesn't currently have any facilities for specifying "favorite" parameters.

There is a little known feature in pi-Stomp where you can specify a config file, just like default_config.yml, but per pedalboard.  I suppose we could extend the file syntax to include a "favorite parameters" list.  Maybe even a list per MIDI_CC.  So when a MIDI_CC change is received, we could consult the list to see if there's a parameter match and if so, send a change for that parameter.  Might not even require plugin selection as long as specified favorites were qualified by their plugin.

All that might not be trivial to implement, but I can imagine it being powerful.  Let me know your thoughts.

Pages: [1] 2 3 ... 15