Hi,
I'm pretty new to DMXIS (but I like what I see, so I might be sticking around). I have a LPD8 MIDI controller to provide a basic user interface using the "Learn" option to connect the controller to various controls and buttons in DMXIS. However, for whatever reason, the bank and present up and down buttons don't seem to work. They appear to "learn" as I expect, the window pops up, I generate a key on message, the window disappears, but then generating the key on message doesn't trigger the button. Other buttons and controls seem to learn without any problem.
I've got the CC32 / program change functionality to work to let me select specific banks and presets, so I've got a halfway house solution, but I'd like to be able to set up a couple of pads on my controller to allow me to select previous and next banks and presets. Am I doing something wrong, or is this a known defect? The user manual seems to imply I should be able to use the learn option to do this.
Preset up/down MIDI learn
-
- Posts: 2131
- Joined: Sat Sep 15, 2012 4:53 pm
- Has thanked: 6 times
- Been thanked: 18 times
Re: Preset up/down MIDI learn
Make sure your LPD8 is transmitting notes with full velocity of 128. By default the pads are pressure sensitive, and you'll need to hit them pretty hard to trigger DMXIS!
Dave Brown - db audioware
Author of Show Buddy Setlist | Show Buddy Active | ArtNetMon
Author of Show Buddy Setlist | Show Buddy Active | ArtNetMon
Re: Preset up/down MIDI learn
Thanks for the advice. I don't think the LPD8's pad velocity can be set to a fixed value (without going through some MIDI routing), but I guess I can use the pads to send Program Change signals instead... if those can be "learned"? Either way, now I know, I can work around it.
As a functionality request, could you add a "velocity threshold value" option that button clicks/toggles could use rather than defaulting to maximum? Understandably, I could see how sometimes you'd want to use the velocity to set a control (like if I was to assign a pad to a fader - it'd make sense to use the velocity value from the pad to give the fader a value), but this isn't the case for binary controls; maximum velocity isn't easy to achieve and I guess minimum velocity would be very easy to cause mis-triggers.
As a functionality request, could you add a "velocity threshold value" option that button clicks/toggles could use rather than defaulting to maximum? Understandably, I could see how sometimes you'd want to use the velocity to set a control (like if I was to assign a pad to a fader - it'd make sense to use the velocity value from the pad to give the fader a value), but this isn't the case for binary controls; maximum velocity isn't easy to achieve and I guess minimum velocity would be very easy to cause mis-triggers.