very nice concept - I have so far wondered why MIDI devices are not used more for typical user interactions.
That being said, I suggest to give real-world examples of what this software is capable of doing - and also state what is not (yet?) possible.
e. g.:
I own DJ controllers, Pioneer DDJ-SB2 and Reloop Ready. Can these be used with IEMidi?
Using my DJ controllers, for what can I use its inputs? Can I assign keyboard buttons (e. g. letters) mouse buttons, complex macros (copy and paste)? Can I use the jogwheels for stuff such as scrolling back and forth in video players, video editors, SDR radio frequency tuning?
Is it possible to leverage my DJ controller's outputs? e. g. the volume indicators on the Pioneer device or the multicolor LEDs below Reloop's beatpad buttons?
Also a filmed video would be great showing such kinds of interactions.
Thank you! More features will be added in the future such as Midi output callbacks, however IEMidi does support running custom console commands with the addition of passing an optional numeric value to the command, and a tutorial on that will be posted in the near future.
Trippy, this is an improved version of my first ever programming project [0]! I literally didn't know how to program so my version is awful but I love seeing the idea come around into a fully realized app!
IEMidi is a cross-platform MIDI editor built with ImGui and RtMidi, allowing users to map any MIDI message to various actions such as volume control, mute, executing console commands, and opening files.
It is powered by the IECore app engine developed by Interactive Echoes and utilizes IEActions, a cross-platform action library for OS-level interactions.
Designed to be open-source, OS-independent, and lightweight, IEMidi provides a simple MIDI mapping solution for any MIDI controller.
Contributions are welcome to expand its functionality and supported actions.
Amazing, this is exactly the kind of thing I happened to be looking around for this week. I'm sure I can reason it out but would you mind adding macOS steps to the readme? I notice you marked an issue about macOS compilation as completed so I assume it works?
Nice! yes IEMidi is cross platform and works on macOS, but i haven't gotten the time to finalize the Packaging for that system yet, but extremely glad it works right out of the box on your macOS.
I don't understand why they chose ImGui. As it is immediate mode framework, it means it repaints whole window for every incoming event, like pointer motion? Ridiculously inefficient.
Also I don't think it is safe to add third-party repositories as they suggest to do for Linux users. I never do this.
very nice concept - I have so far wondered why MIDI devices are not used more for typical user interactions.
That being said, I suggest to give real-world examples of what this software is capable of doing - and also state what is not (yet?) possible.
e. g.:
I own DJ controllers, Pioneer DDJ-SB2 and Reloop Ready. Can these be used with IEMidi?
Using my DJ controllers, for what can I use its inputs? Can I assign keyboard buttons (e. g. letters) mouse buttons, complex macros (copy and paste)? Can I use the jogwheels for stuff such as scrolling back and forth in video players, video editors, SDR radio frequency tuning?
Is it possible to leverage my DJ controller's outputs? e. g. the volume indicators on the Pioneer device or the multicolor LEDs below Reloop's beatpad buttons?
Also a filmed video would be great showing such kinds of interactions.
Thank you! More features will be added in the future such as Midi output callbacks, however IEMidi does support running custom console commands with the addition of passing an optional numeric value to the command, and a tutorial on that will be posted in the near future.
Trippy, this is an improved version of my first ever programming project [0]! I literally didn't know how to program so my version is awful but I love seeing the idea come around into a fully realized app!
[0] https://github.com/ericyd/midi-unbound
Awesome! Happy to take on your contributions
IEMidi is a cross-platform MIDI editor built with ImGui and RtMidi, allowing users to map any MIDI message to various actions such as volume control, mute, executing console commands, and opening files.
It is powered by the IECore app engine developed by Interactive Echoes and utilizes IEActions, a cross-platform action library for OS-level interactions.
Designed to be open-source, OS-independent, and lightweight, IEMidi provides a simple MIDI mapping solution for any MIDI controller.
Contributions are welcome to expand its functionality and supported actions.
Amazing, this is exactly the kind of thing I happened to be looking around for this week. I'm sure I can reason it out but would you mind adding macOS steps to the readme? I notice you marked an issue about macOS compilation as completed so I assume it works?
Edit: Yes yes yes this is awesome, thank you!
Alright alright I did it myself :)
* git clone https://github.com/Interactive-Echoes/IEMidi.git
* git submodule update --init --recursive
* cmake .
* cpack
I also had to install Vulkan because I didn't have it
Nice! yes IEMidi is cross platform and works on macOS, but i haven't gotten the time to finalize the Packaging for that system yet, but extremely glad it works right out of the box on your macOS.
The capitalisation of the name evokes something more related to earphones than MIDI.
It's an acronym. Write it "MIDI" to be most correct, or "midi" to be lazy, but please never "Midi".
Tangentially related, the hobby market for converting MIDI to USB HID via hardware, which is popular for using electronic drum kits' and keyboards' MIDI output in rhythm and music games. Most of these are driven by the Pi Pico, like https://rolllimitless.com/ and https://santroller.tangentmc.net/wiring_guides/midi.html
Newer open-source rhythm games like YARG also handle MIDI-over-USB directly: https://docs.yarg.in/en/Instruments
I don't understand why they chose ImGui. As it is immediate mode framework, it means it repaints whole window for every incoming event, like pointer motion? Ridiculously inefficient.
Also I don't think it is safe to add third-party repositories as they suggest to do for Linux users. I never do this.
The app is meant to run in the background or minimized once you've edited your Midi profile. Your rendering costs are zero.
The app will eventually be packaged as a flatpak and submitted to flathub in the near future.