MyDMX is NOT intuitive when it comes to MIDI and control/triggering via MIDI.
Issue 1, and this isn't really a "problem" issue, but one you need to be aware of.
When starting up MyDMX, you need your MIDI gear already plugged in. Chances are, 99% of you are using a USB dongle or a USB controller that acts as a MIDI device. Whatever it is, unless it hands OFF a MIDI port, the device(s) provided MIDI connectivity(MIDI interface or USB-MIDI device) must be plugged in before launcing MyDMX.
Issue 2: This is a bit more complicated and again, myDMX is not on this workstation. There are two types of MIDI control MyDMX works off of. One is CC(continuous controller) information, which is ideal for controlling DMX channels/faders. The other is note on, which is ideal for triggering scenes.
Triggers are programmed into the scene in the EDIT tab. You'll see the scene, and to the right will be a Trigger row. Click in there. This is where it will allow for a trigger to be learned. When you see it "waiting for MIDI", hit the key or pedal button you want MyDMX to trigger that scene via, and that's it: the window vanishes and the trigger is learned.
Fader/channel CC control is also learned via right mouse clicking the fader strip in MyDMX and "Learn MIDI" is selected. Again, the window shows up, move the controller you want to use and it learns it.
MyDMX won't work via default with anything for MIDI. It has to be told/shown everything.
I am using a Korg nanoKONTROL, which is a 4-layer "fader control surface". Each layer has 9 faders, 9 knobs and 18 buttons. Times 4, that gives you a lot to work with. Other folks have reported using a nanoKEY, and I see no reason why a nanoPAD wouldn't work well either. It just depends on what your needs are. For me, I need channel control, so the nanoKONTROL is ideal. If I wanted scene triggering, the korg nanoKEY would be my choice. But, since we're talking foodpedals, the korg nanoPAD, designed to be a percussion controller, would be a better equivalent. MyDMX really doesn't care what you're using, it just needs to be told what to react/respond to. The nice part about MyDMX not caring is that there are really little to no restrictions as to what you can and cannot use. The bad part is that it simply requires users to pay attention more and use their brains a bit more as well.
Regardless if you are in DEMO or USB mode, MyDMX will respond to MIDI devices.
DO note that MyDMX has bad MIDI implementation and does not install itself as a MIDI device. The only way it can respond to MIDI is for a true INCOMING signal must hit on on a MIDI IN port on the USB adaptor or USB to MIDI controller(with MIDI ports). You can NOT trigger from "within the box" because MyDMX does not provide an interface for that. As such, it's highly recommended by me that you DO NOT run your sequences/DAW on the same machine as MyDMX if you expect to trigger MyDMX, it's a recipe for failure.
Also, another word about triggering scenes: 1 trigger per scene, which would be "start the scene".