Hmm, each one should have a unique name.
With BP open, can you make a new Max patch and create a [r hover] object, and connect it to [print]. This should show you what the MIDI learn is ‘seeing’ when you hover over an object. I didn’t write the MIDI learn code for this, but the way it works is that when you turn on MIDI learn, it opens a gate that joins together whatever you are hovering over and whatever controller number is being twiddled too.
Since everything in TPV works on 0. to 1. range, it scales the 0-127 MIDI input to 0. to 1.
So the first thing is to test to see if it’s seeing the correct parameter (ie 1karma_pitch, 2karma_pitch), then to make sure it’s sending the right data (should be sending 0. to 1. stuff).
If you then make a [r thispatcher] once you’ve made a mapping, you can connect that to print and see the messages that are being sent around. It should be something like “script sendbox param 1karma_pitch 0.3”.
Can you see what you get when you test that and maybe paste some of the [r thispatcher] stuff in here?
Also, take a look at the file called “MIDI-assigns” that should get saved in the BP folder after you create a mapping. That shows what’s mapped to what. (You can actually just edit/create MIDI mappings in that, if you find that to be faster than manually hovering over everything).
