yesterday, shortly before my live gig I had trouble keeping my nanoKontrol midi controller connected. I have built myself a tool like svvvvitcher to switch between patches and sometimes after switching it just didn’t react anymore. I never had those problems before but I guess it has something to do with those enums? Could it be that those enum ids get changed when I connect a new patch which uses enums as well?
Anyway, I found a solution by just not connecting the midiInput pin of the MidiController node to an enum… (don’t know if that’s really the solution but somehow it worked).
Now I have actually two questions:
Am I on the right track or are there other known issues regarding midi controllers?
When I lost the connection I always had to restart vvvv completely. Is there any other way to quickly re-establish the connection? I tried “scan for externals” but that didn’t do anything…
I had similar issues with other controllers… Create only one midi controller and a spread, Stallone, and multiple send nodes for each of the sliders,knobs,faders and things that you need to use from your controller, all that on one patch.
Then on your project create the receive nodes , for me this way it’s easier and in the possible scenario of a crash or USB disconnection of the controller, just close the midi patch and reopen it. This won’t freeze or force you to stop the rest of the work. Enums it’s a different problem not related to midi, i can’t help you with that because I don’t know enough experience but check on the forums about enums issues.