Messages

what did you use to send the midi messages?
what midi board did you use?

i had some trouble with overlapping adrresses at some point

OK, so i'm trying to figure out ways to use pi-stomp with easy live tweaking (i dont want to use my cell phone every time i need to adjust something quickly)
is there a way to make the knobs parametric?
for instance - highlight a pedal in the SW and the knobs are assigned per a specific pedal?

(i will soon have some demos of my pi stomp in a live show, and s demo of my arduino foot controller with code and instructions)

I dont know if wnyone has seen it yet' but NAM now runs on MOD dwarf
their newest OS has NAM preinstalled and you can actually download the plugin with the "nano" models - has anyone tried this on their PI-stomp yet?

can 1 midi command do 2 things?
for instance - i want one midi command (button push) to turn of effect on and aonther off, simultaniously

if not - can this be a feature request?

So after installing the new version i got around to playing with amp models, and they really sound great.
this is on the same level as NAM, and the MOD forum really has a lot more captures recently - including people re-training NAM models for AIDA X.

i have one issue though - i tried putting 2 instances of AIDA on an A/B switch, and they crackle.
when they're in series it's dead quiet, and only when i connect the outputs from the switch it starts to crackle/ seeing as there's only one switch - did anybody else notice this? is there a fix that somebody knows of?

thanks

Arie

isthere a way to convert models from neuralpi (alsp json based' with similar headers) to aida-X?
we seem to lacking in models
or - where can we find somw models for the aida X?

something similar happened to me when i first built the unit
i forgot to specify the audio card
solution by randall was:
ssh with this:
~/pi-stomp/util/change-audio-card.sh

type 2, enter
reboot

would i need a full reinstall to update to the latest version?
how would i load in more models?

so NAM wouldn't be usable live on the pistomp?
how much CPU power is used?
i'm not a heavy modulation user

i wnated something that would fit my pedalboard, so it has to be just the right size

with very easy modifications and a few multiplexers you can add virtually any number of buttons, and expression pedals as potentiometers

i forgot to mention this code also outputs the state of the button to an LED, and you can always wire and LED in line with any potntiometer if you want

so i've been playin around with the neural amp modeler (https://github.com/sdatkinson/neural-amp-modeler )
and they also have an LV2 plugin https://github.com/mikeoliphant/neural-amp-modeler-lv2, would this work on the pi stomp?
does the pi-3 have enough computing power for this?
i'm thinking about a mod involving this and a simple DI for balanced output straight to the PA

Arie

hi, so i just saw this now and i'm planning todo a whole thread on this - but i managed to code an arduino with 4 bankakble midi over usb footswitches, and up to 4 potentiometers
I'm using the control-surface library, and it works.
this is my code:

Code Select Expand

#include <Control_Surface.h> // Include the Control Surface library

// Instantiate a MIDI over USB interface
USBMIDI_Interface midi;

// Instantiate four Banks, with eight tracks per bank.
Bank<4> bank(8);
//   │       └───── number of tracks per bank
//   └───────────── number of banks

// Instantiate a Bank selector to control which one of the four Banks is active.
IncrementDecrementSelector<4> selector = {
    bank,       // Bank to manage
    {2, 3},     // Push button pins (increment, decrement)
    Wrap::Wrap, // Wrap around
};

// Instantiate an array of latched push buttons that send MIDI CC messages
// when pressed.
Bankable::CCButtonLatched<4> buttons[] {
  { bank, 4, 0x10 },
  //  │   │    └──── Base MIDI CC controller number
  //  │   └───────── Button pin number
  //  └───────────── Bank that changes the controller number
  { bank, 5, 0x11 },
  { bank, 6, 0x12 },
  { bank, 7, 0x13 },
};

// The bank controls the offset of the controller number relative to the
// button's base address. The amount of offset depends on the "number of
// tracks per bank" argument used when creating the bank. In this case,
// it's 8 tracks per bank, so for every bank you go up, 8 is added to the
// controller number of each button:
//
//         │  Button 1  │  Button 2  │  Button 3  │  Button 4  │  Offset
// ────────┼────────────┼────────────┼────────────┼────────────┤
// Bank 1  │    0x10    │    0x11    │    0x12    │    0x13    │  0×8=0
// Bank 2  │    0x18    │    0x19    │    0x1A    │    0x1B    │  1×8=8
// Bank 3  │    0x20    │    0x21    │    0x22    │    0x23    │  2×8=16
// Bank 4  │    0x28    │    0x29    │    0x2A    │    0x2B    │  3×8=24

// The array of pin numbers for LEDs that display the states of the buttons.
const pin_t ledPins[] = { 10, 11, 12, 13 };

// Get the length of an array
template <class T, size_t N> constexpr size_t length(T (&)[N]) { return N; }

static_assert(length(buttons) == length(ledPins),
              "Error: requires same number of buttons as LEDs");

CCPotentiometer knobsTop[] {
  {A0, MIDI_CC::General_Purpose_Controller_1},
  {A1, MIDI_CC::General_Purpose_Controller_2},
  {A2, MIDI_CC::General_Purpose_Controller_3},
  {A3, MIDI_CC::General_Purpose_Controller_4},
};

void setup() {
  Control_Surface.begin();  // Initialize the Control Surface
  for (auto pin : ledPins)  // Set the pinMode to output for all LEDs
      pinMode(pin, OUTPUT);
}

void loop() {
  Control_Surface.loop();  // Update the Control Surface

  // Loop over all buttons and LEDs
  for (size_t i = 0; i < length(buttons); ++i)
      // Update the LED states to reflect the toggled switch states
      digitalWrite(ledPins[i], buttons[i].getState() ? HIGH : LOW);
}