I’m developing my own pedal based on daisy seed. Everything works great, except for midi. I have a p10 trs midi in, that goes throw an IC H11L1 and then goes to pin 37 (GPIO30). I’m using Max DSP and developing in gen. I use Oopsy Daisy to compile. I can’t make midi to work inside Max. I think I have to do something on my oopsy.hardware.json.
On my .json, I have added
“defines”: {
“OOPSY_TARGET_HAS_MIDI_INPUT”: 1
}
But it does not seems to work. Maybe GPIO30 was not the default MIDI input. I don’t know how to set a new one.
Another thing! I can’t debug Midi inside of Max…
Because, if I put an midiin at my max file, and connect it to the gen~ patch, this midiin is not in the same format as the oopsy.midi.parse expects. I believe Daisy Seed expect midi between 0 and 1. But the “midiin” give me higher values. Using scale does not seems to work in this case too.
I think I just found the problem:
I added “OOPSY_TARGET_HAS_MIDI_INPUT”: 1 to my oopsy .json.
But I think it is trying to read MIDI from GPIO 14 (where I have my Toogle Switch).
I have my MIDI on GPIO 30.
I realize this, because my switch (That is connected to gpio 13 and 14) became buggy when I add OOPSY_TARGET_HAS_MIDI_INPUT.
My Switch:
“sw_left”: {
“component”: “Switch”,
“pin”: 13
},
“sw_right”: {
“component”: “Switch”,
“pin”: 14
},
I Still cant realize how to read MIDI from GPIO30 (where I have my connection on my PCB)
We talked on Discord about this, but I can share those info here for others.
So Oopsy will use pin D14 for MIDI but you should be able to change the pin to D30 in a C++ code in libDaisy and then rebuild libDaisy.
It’s probably better to build the hardware for Oopsy-use imo as software customization will involve C++ coding. OP told me that they will rework the PCB to use D14.
