Weird impact of midi monitor on rack layer selection
Posted: Fri May 07, 2021 6:29 pm
(Live 11, Windows 10, 16G of ram, SSD, i7, ...KMI Boppad) I'm trying to use a boppad's capability to send radius messages (as CC2) to select between samples in an instrument rack (within a drum rack.) I map CC2 to the selector. Two samples are evenly distributed in the rack pad. So it should work that when I hit near the edge of the boppad, CC2's value sends the selector into the range of one sample and when I hit near the center of the boppad (actually the middle of one of it's quadrants) it sends the selector into the range of the other sample. This (per KMI) is supposed to be how you get multiple samples to play in a quadrant... by using radius.
The first problem is that it always takes one hit before the sample changes. The selector moves but I hear the previously triggered sample. On the second hit, I hear the correct sample. Same when I move back to the area that should trigger the other sample. It takes one hit to get there.
The second problem (which is, for some reason, maybe a solution!) is that when I run midi monitor out in front of this whole rack, the first problem goes away!
I can run midi monitor in front of my boppad drum racks but I'd rather not. Ideas?
The first problem is that it always takes one hit before the sample changes. The selector moves but I hear the previously triggered sample. On the second hit, I hear the correct sample. Same when I move back to the area that should trigger the other sample. It takes one hit to get there.
The second problem (which is, for some reason, maybe a solution!) is that when I run midi monitor out in front of this whole rack, the first problem goes away!
I can run midi monitor in front of my boppad drum racks but I'd rather not. Ideas?