Realtime Note Input (Manual) - Advance Bug

Hi. I have a generic midi controller (Yamaha UX-16) and a Privia PX-120. I've used multiple Electronic footpedals and gotten the same result, so I'm going to leave that out (I don't know what brand they are either. But I know they are relatively cheap. Pretty Cheap. They're cheap, haha).

So far my favorite input method in musescore is the Manual Realtime Note Input Method as it allows me to easily develop my ideas on the spot during composition. However, I am only able to use one hand on my keyboard at a time or sometimes have other smaller complications as I am forced to press the num-pad enter key [default] to advance. When I use midi-mapping under note-input on preferences, I can also change the button to other button on my keyboard with ease, and they function perfectly (Like the Grand Piano selection buttons). When I map Real-Time Advance to the foot pedal, It advances 3 units at a time. So if I hold down a chord and have the quarter note selected, pressing the pedal once will make one tick, but 3 beats will have been inputted, creating a dotted half note instead of a quarter. Or if I just tap the notes, I get a quarter note and two rests. If this is a problem on my end that I could solve I'd be elated to fix this. If not. I'm happy to report a possible bug.
(Also, I did a little bit of searching to see if this was posted already and I couldn't find anything, so I don't think this has been posted before)

Edit/Update: So I think I may have figured out my problem. My keyboard/controller operates on 3 channels allowing me to play 2 instruments (2 Channels) + (1 channel) Effects simultaneously on my actual keyboard (So this caters to live performance with the keyboard). The issue with this and musescore is that musescore is built to pick up any one midi event and my pedal or rather keyboard inputs sustain for 3 channels at once. Maybe this could be accommodated for if Manual Realtime Input was modified to pick up only 1 channel at a time but I'm no coder and this probably isn't significant enough to make it into a musescore update. While it's possible this may not be the case, it makes the most sense to me. I think it seems rather logical... Well anyhow, I had to correct myself. This isn't a bug or glitch, but seems to be a comparability problem.

Edit/Update 2 - My current solution:
So I actually have 2 Midi controllers. #1 (Yamaha UX16 [generic controller] + Privia PX-120 [keyboard]) and #2 (Arturia MINILab mkII). They are both USB, so I can plug them into my computer at the same time. I'm using a program called Midi-OX to merge them; both of their inputs are being funneled into #1, which I am using with musescore. So I have plugged my sustain pedal into #2 which is routed into #1. And #1 goes into musescore. That solved my problem. It does because #2 is meant for DAW input and not performance, so the pedal only creates one midi event. :)

But for specifics, the program "Midi-OX" is for everything midi and I have a program called "LoopBe1" which is a virtual midi controller. Using Midi-OX, I set my two actual midi controllers as inputs and LoopBe1 as an output. Then in musescore I set LoopBe1 as my midi input device. And with that, any missing, broken, or extra functionalities can be covered with the use of multiple midi controllers being merged into one this way.