[MIDI conf] no more a nightmare

:control_knobs: DJ MIDI Studio v0.45.0 — A new way to manage DJ MIDI mappings
Hey everyone!

I’ve just released the first public version of DJ MIDI Studio, a desktop application designed to make DJ MIDI configuration easier to inspect, understand, edit, and route.
It currently focuses on workflows involving Serato DJ Pro, Traktor, and MIDI hardware, with support for controllers such as:
• Pioneer DDJ-XP2
• Pioneer XDJ-XZ
• DDJ-1000
• DDJ-FLX4 / FLX10
• DDJ-REV1
• Numark Mixtrack Pro FX
• Hercules DJControl Inpulse 500

What it can do
:level_slider: Explore MIDI mappings by channel, deck, or controller
:control_knobs: Visualize controller layouts with pads, knobs, faders, jog wheels, and mixer controls
:puzzle_piece: Edit and validate Serato MIDI mappings
:satellite_antenna: Monitor live MIDI messages
:repeat_button: Route MIDI between hardware, software, and virtual ports
:three_o_clock: Work with MIDI Clock, Ableton Link, Serato, and Traktor-related workflows
:musical_keyboard: Capture MIDI controls and detect double-click / shifted pad-mode commands
:books: Browse bundled controller documentation and MIDI reference material
:shield: Validate configurations before saving or exporting them
:package: Download native builds for macOS, Windows, and Linux

The goal is to provide a practical bridge between DJ software, controllers, MIDI interfaces, and external hardware — especially for complex setups involving multiple devices.

:handshake: Help shape the project
DJ MIDI Studio is built for real-world DJ setups, and I need your help to make it genuinely useful.
Every DJ setup is different, especially when combining several controllers, MIDI interfaces, DJ software, and external hardware. Your feedback can directly influence the roadmap and help prioritize the features that matter most.

You can contribute by sharing:
• Your hardware and software setup
• MIDI routing or synchronization challenges
• Controller mapping files and MIDI logs
• Feature requests and workflow ideas
• Bugs, screenshots, and reproducible test cases
• Feedback about the user interface and documentation

You don’t need to be a developer to contribute. Testing the application with your setup and explaining what works — or what does not — is already extremely valuable.
If you are interested in helping, please open a GitHub issue or reply here with details about your setup. Together, we can make DJ MIDI Studio a reliable tool for complex DJ and MIDI workflows. :musical_notes:

Download and documentation:
:backhand_index_pointing_right: GitHub: Release DJ MIDI Studio v0.45.0 · guillain/DJ-MIDI-Studio · GitHub

Please note that the macOS build is currently unsigned, so macOS may display a Gatekeeper warning. This is expected for the current release while proper Apple signing and notarization are being prepared.

If you try it, I’d love to hear about your setup, what worked, and where the workflow could be improved! :rocket:

This is pretty interesting. Keep it up!

Few suggestions from a quick test.

  1. IDEA - When setting up a new controller you can’t select multiple rows to say assign everything to the same section at once. Couldn’t find a way to upload an image in the UI.
  2. IDEA - I think allowing users to submit their manually setup controllers from the app will be big in the early stages of the app since it and contribute different device configs so new ones don’t have to do it manually and the supported device list is community fed.
  3. Only user actived devices should show up on the tabs. Right now it’s crowded with the defaults and this adds no value for someone who doesn’t own these.
  4. BUG - At the default window size on macOS a number of elements are being cut off in both dimensions