Just had an experience that I thought I'd relate in case this happens to you.
I recently noticed that one of the keys (F#3) on my MIDI controller was no longer recording MIDI data into DP. Just the one note.
My first thought was that my controller had a problem, most likely a guitar pick that had fallen into the keybed or something, so I got ready to open it up and check. But thankfully, before I did, I switched the synth over to local control just to verify that the key mechanism wasn't working. But the key worked fine playing the internal synth sounds. Based on how that hardware works, I couldn't imagine a scenario where a single key would trigger the internal sounds but not send MIDI data. It made no sense.
I then checked, and found that MIDI data was indeed being received by my interface from that key. Checking DP's MIDI monitor, I saw that DP could see the data come in as well - but still that note did not work.
I called up the Input filter, expecting to see somehow that I had excluded that particular key, but that wasn't it. Then I manually pencilled in the suspect note in the MIDI editor, and that worked fine- therefore it wasn't some kind of MIDI note muting.
At that point, I was flummoxed - until I remembered that I had recently watched one of the DP video seminars that talked about setting custom key combinations for DP functions. After seeing that video, I played with setting up a few custom commands of my own.
I checked, and sure enough, while I had been working to customize a few commands, I must have hit that key on my controller while scrolling through the long list of commands, and inadvertently assigned it to a command (I think it play-enabled chunk "Sequence 1", so nothing obvious happened in my single chunk project). I deleted the custom command and voila, all is now back to normal..
So keep both hands on the computer keyboard at all times when setting custom key commands!
