Midi controller values incorrect when starting up axoloti

#21

Hmm using the Arduino serial monitor it does not seem to send anything until I fiddle with the pots....as for the other problem could I add a timer that counts down before the other code starts in order to allow some time for the axoloti to start up?

#22

yes, you can add a delay in the setup routine, that waits until the axoloti is ready. put a

delay(4000);

after the MIDI.begin line.

this should make it sit there for 4000ms (4 seconds). best is to measure the time until the axoloti gets ready (leds stop flashing) and add some little time to that measurement.

also, can you try this code in setup and tell me if it sends something on startup now? (after 4 seconds)

void setup() {
  MIDI.begin(MIDI_CHANNEL_OFF);
  delay(4000);
  MIDI.sendControlChange(20,127,1);
}

this should just send a cc 20 message on channel 1

unfortunately i leave for a 10 days tour friday night and will not be able to help you further until i get back...

#23

Siiick. Ill give it a shot tomorrow, have fun and that is for the help!

#24

you could also write to the notes and volts guy, he is usually pretty responsive and ask him if he could add a "send all controller values on startup" option to the library. describe your use case...

#25

Hi, have you thought about storing your controller data in a table? That was my solution to retaining settings on startup...

I basically send all my controllers through objects that stores the values in a table on the sdcard. Then, before I turn off the axoloti I press a button that saves the table (saving all the controller data). Then when I turn on the axoloti it automatically restores the settings. I think this should do what you want, with the exception that if you move the controller while the axoloti is off it won't pick that up on startup. But it will retain the controller values exactly as you had them when you turned off.

#26

it is for sure a possibility, but as you write yourself, not ideal if a pot gets moved when power is off. then again, your method might even be more "wanted" because it eliminates the accidental pot turn preset messup :slight_smile:

#27

Ahhrg yeah I tried a few time through a few different channels but no response from him . Hopefully I can catch him on a livecast one day....also haven't got to test out the new code yet, just wired up a protoboard for switches and LEDs today before work...so excited to have a shitload of switches yeeeheee!

#28

The ability to save the values is DEFINITELY something I want to do. Do you have an example patch of this?

For this case though, youre correct. I'm concerned that the knobs may be moved while the axoloti is switched off but also want to ensure that the previous values are retained without having to manually save them as I'm pretty forgetful...one day I'll try to figure out how to set up a table to save values then add a knob and LCD screen so I can flip through them....not yet though!

#29

I'll make an example next time I'm at my pc and post it.

For me the table method is great because I want the patch to load with my last used settings. I use my controllers with other equipment/patches and so the knobs are rarely in the same positions as they were when I last used a patch. But I can see why you want it to match the controller, it gives you that 'what you see is what you get' thing.

#30

Awesooome!! I can't wait to make some tutorials for these things!

#31

using tables to store controller settings.axp (14.7 KB)

#32

I put together the above to show the table storage, and added a bit about using tcopy to save/load tables on the fly without glitches.

#33

PS many thanks to rbrt for all your objects, I use them in every patch!

#34

Kickass! I can't wait to try this out this weekend.