Any build instructions

[Schizo]

Hey, it's a very new repo but I would like to give it a try, could you provide some build instructions?

[janivanecky]

Hey! I'll add an update to README with build instructions today/tomorrow.

[Schizo]

Much appreciated!

[janivanecky]

https://github.com/janivanecky/Physarum#build-instructions

Let me know if it works for you

[Schizo]

Hey Thanks! :D It's kind of an unconventional way of having a build system, but it worked! I wanted to change parameters, I do that with F1 right? but when I do that particles are gone and moving sliders doesn't change anything, only if i turn DOF i get a static Image of a phsarium. Can you elaborate how to change parameters?

[janivanecky]

Hey! This is happening because I set up parameters to be controlled by MIDI controller - if you don't have it connected, it's not going to work. Anyways, that was pretty stupid to have as the default option so I changed the code so MIDI controller isn't required. Just pull the most recent version of master branch and everything should work.

[geslotencirkel]

FYI - you can also change line #39 looking for midi controllers
bool use_midi = true;
and change that to false.

Personally got more than 1 midi controller including internal loopMIDI routings, so seemed like the app was detecting midi devices and preventing the ui from working - yet it wasn't clear if the controllers were working. Not sure if the app specifically checks if Midi devices are present and if yes, binds everything to an "AKAI_MIDIMIX..." which i don't have.

would be sweet of course to trigger it from an audio app or whatever, but please let me know if the controllers are hard coded by some sort of system name and whats the best way to find the right system name. Alternatively, would be cool to just receive any midi ccs in on any or specific channel.

[janivanecky]

I have only tested MIDI support with AKAI MIDIMIX controller, so cannot guarantee that it works correctly with other devices, however the only difference I can think of between my and other devices is in the identifier for specific sliders/knobs/buttons that are used. If you look at midi.h, at the top of the file, there's a lot of definitions for specific sliders and buttons on the controller I have. Those are just hex numbers though, so if you know the number identifiers for buttons/sliders on your controller, you can just use those. If you don't know the identifiers, you can use http://www.midiox.com/ to get them. Let me know if you have more questions about this, there might be more details I missed.

[geslotencirkel]

With a midi monitor like midiox i can see the control change and channels of a controller that was moved, but how to translate this to the format needed in midi.h i am lost.

#define AKAI_MIDIMIX_KNOB_0_0 0x10 this is a line from the section you are talking about right?
0x10 would be CC16 - so Physarium is looking for any incoming messages on CC16 or specifically from AKAI MIDIMIX KNOB 0 0 ?
I got a NanoKontrol2 from Korg here and MIDIOX sees it as nanoKONTROL2, but having it on Midi channel 1 with CC16 assigned isnt recognized in Physarium I think.

just wondering - are the control changes from a midi controller recognized without the editor menu open? so you can pretty much make it a midi controlled visualizer? or is it only when a menu is open?

also gotta say, the dof you put in this is awesome.

[janivanecky]

Inside MIDIOX you can see the number identifying the specific knob/slider/button in the DATA1 column. Then you can just use that number in get_controller_state call.

The midi controls are recognized also if the UI is not shown.