MIDI out with VM + MacroButtons on the same device not working

[Snapper]

Hi there,

I just realized, that I can't use MIDI out (to set LED status) with VM M.I.D.I. Mapping and MacroButtons on the same device... but why is this?
MIDI out does work, because MIDI in signals are (default) forwarded from VM M.I.D.I. Mapping device to MacroButtons.
@Vincent Burel Why is it, that MIDI out isn't also (default) forwarded from MacroButtons to the device selected in VM M.I.D.I. Mapping? Is there a technical difficulty I am not aware of, because this seems to make no sense for me...

-> I wanted to bind a button on my nanoKONTROL Studio to switch Bus A1 between normal and 7.1 Upmix (that's working) and set the corresponding LED on/off (this only is working, when MIDI out1 device exclusively is set for MacroButtons! This suxx a lot, because to use my nanoKONTROL there are set a lot mappings in VM M.I.D.I. Mapping and to set them all in MacroButtons instead, would be a PainInTheAss procedure due to it's "lack of usability" versus VM M.I.D.I. Mapping dialog (especially with using FF mode)...

best
Snapper

[Vincent Burel]

yes, normally a MIDI device can be used by a single application at a time.
(up to now = this could be changed with MIDI 2.0 Microsoft implementation as far as i understand)

That's why i've implemented a MIDI in forwarding process from Voicemeeter MIDI mapping to Macro Buttons.

MacroButton MIDI out will not be able to use MIDI output device used by Voicemeeter MIDI mapping feedback process...
because the feedback process is expected to fulfill your needs... or simply select no MIDI output in Voicemeeter MIDI mapping to be able to use it in Macro Buttons.

Unless you need to use MIDI mapping feedback and MacroButton Midi out function in the same time ?

[Snapper]

Unless you need to use MIDI mapping feedback and MacroButton Midi out function in the same time ?

Yes, this is what I need/what I was talking about
I need MIDI feedback and I need/want to extend the MIDI functionality beyond what is possible with the existing entries in the VM MIDI Mapping dialogue...
I really like the MIDI mapping, it's convenient and easy to use/edit - I have my nanoKONTROL Studio fully mapped, which is a lot of buttons and knobs.

So if, for (technical) reasons, it is not possible to forward MIDI out messages from MacroButtons to VoiceMeeter (as far as I understand).

Would it be possible to add another "custom" page to the VM MIDI Mapping dialogue, where there are additional fields per entry where the user can define the on+off commands (like a very-light version of macro buttons) themselves (instead of pre-defined commands as it is now)? So users could extend MIDI functionality on the same device beyond what is pre-configured/thought in the Mapping dialogue (without using MacroButtons)...

That would be awesome!

Best
Snapper

[Vincent Burel]

did you try the custom feedback ? right click on 'F'.

MIDIFeedbackOption.png (59.54 KiB) Viewed 89 times

[Snapper]

I have seen this in documentation, but don't know really how to use the feedback message fields or what their purpose is for. The manual states it for "complex midi feedback" - but not how to use it nor some examples, just that it exists and I find it a bit non-intuitive...
e.g. Feedback Value ON/OFF is written/stated in decimal, but then following Feedback Message seems to requiere a RAW HEX string - where do I get this string from/how do I "build it"?

I have seen those when when I monitor a devices messages with the software "MIDI Tools", but I can't get it to monitor the output from MacroButtons, no matter what I try (closed all midi apps, only MacroButtons and MIDI Tools alive - nothing).

For test purpose I have written the following codes from MacroButtons in the "feedback Message ON/OFF (HEXA)" fields of a unused entry in the custom feedback dialogue, which after close/reopen is then "translated" to the following line:

System.SendMidi("out1", "ctrl-change", 1, 49, 127);

-> "EE DD 1C CA E1 49 12 "

System.SendMidi("out1", "ctrl-change", 1, 49, 0);

-> "EE DD 1C CA E1 49 "

Seems like ctrl "49" remains still in decimal (tried other values - they remain 1:1) - which is very suspicious, whereas all other code is somehow translated into HEX. I can't figure out how the translation to MIDI RAW HEX is done, all documentation I find online is basically only about converting hex<>dec or about MIDI CC standard messages, which doesn't help at all.

(And for clearence - nothing happens - [System.SendMidi("out1", "ctrl-change", 1, 49, 127);] should light on the LED on ch1/ctrl49 button as it does proper with MacroButtons - even if I change decimal ctrl "49" to hex "31")


But even if it would work somehow, for my initial need (switch BUS A1 output Mode between normal and 7.1 upmix) this wouldn't be a solution, because there is no entry for switching BUS output mode in the VM MIDI Mapping dialogue... (thats why I use MacroButtons for this purpose atm - but with lack of MIDI feedback)