Snoothy / UCR

Universal Control Remapper [Alpha]
MIT License
896 stars 90 forks source link

MIDI I/O Suggestion #175

Open Robert-K opened 4 years ago

Robert-K commented 4 years ago

It appears that UCR can't receive from or output to MIDI devices at the moment. However, it does recognize all my MIDI devices (Core_midi). Are you planning to add MIDI input and output? Or have you already and I just can't get it to work?

This would open a whole new world of using secondary keyboards (especially wireless numpads) as MIDI controllers 😮

Huge thanks to everyone working on this magnificent piece of software! 😄

WelpThatWorked commented 4 years ago

Wrote up something that should work.

Take this: MapToMidi.zip Right click it, click Properties>Check "Unblock". Extract the files and place Core_Midi.dll in /Providers/Core_Midi/ and the other two files in /Plugins/UCR.Plugins/

Tell me what you think.

elMuso commented 4 years ago

THIS IS WILD! I have been wanting to use a secondary keyboard as a pad/ midi keyboard in Reaper but haven`t been able to do it without losing the shortcuts. Now i can use 2 keyboards. One for the shortcuts and one for the Midi communication.

Have you considered posting this in the Reaper/FL Studio/CakeWalk/Ableton forums? this is really revolutionary, now there is a cheaper, and lighter alternative to conventional midi controllers <3333

EDIT: It seems the most viable way of using this with a local DAW is using loopbe https://www.nerds.de/en/loopbe1.html instead of the default MidiHub Port

WelpThatWorked commented 4 years ago

Made some improvements: MapToMidi.zip

Added the rest of the midi commands, improved wrapping and made it optional for Midi Step, some other minor changes. Make sure to remove any profiles using the Midi plugins before you replace the DLLs, or you will have a startup error. Tell me if there is anything missing. I'm not familiar with the music production scene, would there be any interest in Axis to midi? Thanks

evilC commented 4 years ago

I just tested MIDI in 0.9.0 and both input and output worked fine - I tested MIDI key to vJoy Axis, and DirectInput axis to MIDI axis. My test device (Behringer Motor 49) has motorized faders, and I am able to map a DirectInput axis to this fader, such that moving the joystick moves the fader on the MIDI keyboard. The use-case I had in mind for outputting to MIDI axis would be for a trim control for flightsims which allowed you to trim multiple axes with one motorized fader - ie press a button, it's in "Calibrate X" mode, and fader moves to current trim position for X axis. Apply trim to X using fader, then press a button and it goes into "Calibrate Y" mode - fader is then moved to current trim value for Y @WelpThatWorked pls feel free to contact me in Discord, we can discuss merging in these changes

chenlola commented 4 years ago

I can bind MIDI Slider to vJoy, but I cannot bind those buttons like S/M/R (solo or mute or record button)

Click Click to bind --> Press button S/M/R --> Press input device no response till time over.

Release v0.9.0 Alpha, Input Device: Korg nano Kontrol2

Adik17444 commented 4 years ago

Hello! On Windows any button send message OnKeyDown and OnKeyUp and when it converts to midi it send NoteOn and NoteOff. But it work like momentory midi message. Handle OnKeyUP in some times not need. 1) Can you correct your MapToMidi and add option to send only one midi command NoteOn without NoteOff and no handle OnKeyUp (full ignore). On next press this button MapToMidi send only one midi command NoteOff without NoteOn and no handle OnKeyUp (full ignore). In midi consoles this mode called TOGGLE and it invert current Note state.