Hi
I am working on an Arduino Leonardo based M.I.D.I controller to control VoiceMeeter potato. So far everything is working well except for muting the virtual inputs and all the outputs. The buttons I have to control muting are locking push buttons (press once for on and again for off). These work well for the physical inputs because the M.I.D.I mapping window has PTT options for these mappings. However this option is missing from both the virtual inputs and all the outputs. Is there a way to get this functionality from for these mappings? I also plan on using a SPDT toggle switch to selectively mute my speakers/headphones and this would also rely on the PTT functionality.
I know about using MacroButtons program however I would like to avoid that as I have had trouble with it in the past and if I can avoid another start up program then that would be great.
Thanks
Tom
M.I.D.I PTT mute on virtual strips and all buses
-
- Posts: 23
- Joined: Tue Nov 06, 2018 4:06 pm
-
- Posts: 23
- Joined: Tue Nov 06, 2018 4:06 pm
Re: M.I.D.I PTT mute on virtual strips and all buses
is no one able to help me with this?
-
- Posts: 23
- Joined: Tue Nov 06, 2018 4:06 pm
Re: M.I.D.I PTT mute on virtual strips and all buses
i have also noticed that there is no PTT option for Solo on any of the inputs
-
- Site Admin
- Posts: 2139
- Joined: Sun Jan 17, 2010 12:01 pm
Re: M.I.D.I PTT mute on virtual strips and all buses
if you need more options like this , you may program them with MacroButtons (installed with Voicemeeter)
that can also react according MIDI code (from the same device connected to Voicemeeter Midi mapping).
see Voicemeeter user manual for details.
that can also react according MIDI code (from the same device connected to Voicemeeter Midi mapping).
see Voicemeeter user manual for details.
-
- Posts: 23
- Joined: Tue Nov 06, 2018 4:06 pm
Re: M.I.D.I PTT mute on virtual strips and all buses
hi
thanks for the reply. i am currently using MacroButtons and while it works there are some problems with it for this use. it works well for instant actions however is not great for PTT (or for me push to mute) style actions. the main problem is during restarts. if i have the mute button pressed when i shutdown my computer (or voicemeeter and macro buttons) then at shutdown the macro button is "active" (light blue) however when it starts up again the button is "inactive" but voicemeeter has not executed the "button up" code. this is despite the physical mute button not being depressed. this requires multiple toggles of the physical button to bring everything back in sync and when there are 8 or 9 buttons that need to be fixed every time this can be a bit annoying.
when using the PTT option in the midi mapping window this does not happen and upon restart everything reflects the state of the midi controller at shutdown. if the controller was changed while the system was off then that is a different matter.
in any case, ether making the MacroButtons program save button states on shutdown or adding PTT to the other toggles in the midi mapping menu (solo, mono and select would also benefit from this) would solve this problem, the midi mapping change would seem easier as the code is already there for 5 of the inputs. however, i think that both would add more flexibility as there are still some things that can only be done with MacroButtons.
thanks for your help and thanks for making an excellent tool.
thanks for the reply. i am currently using MacroButtons and while it works there are some problems with it for this use. it works well for instant actions however is not great for PTT (or for me push to mute) style actions. the main problem is during restarts. if i have the mute button pressed when i shutdown my computer (or voicemeeter and macro buttons) then at shutdown the macro button is "active" (light blue) however when it starts up again the button is "inactive" but voicemeeter has not executed the "button up" code. this is despite the physical mute button not being depressed. this requires multiple toggles of the physical button to bring everything back in sync and when there are 8 or 9 buttons that need to be fixed every time this can be a bit annoying.
when using the PTT option in the midi mapping window this does not happen and upon restart everything reflects the state of the midi controller at shutdown. if the controller was changed while the system was off then that is a different matter.
in any case, ether making the MacroButtons program save button states on shutdown or adding PTT to the other toggles in the midi mapping menu (solo, mono and select would also benefit from this) would solve this problem, the midi mapping change would seem easier as the code is already there for 5 of the inputs. however, i think that both would add more flexibility as there are still some things that can only be done with MacroButtons.
thanks for your help and thanks for making an excellent tool.
-
- Site Admin
- Posts: 2139
- Joined: Sun Jan 17, 2010 12:01 pm
Re: M.I.D.I PTT mute on virtual strips and all buses
maybe you can use Initial State script in macro button to reset Voicemeeter on startup with your initial states... no?
-
- Posts: 23
- Joined: Tue Nov 06, 2018 4:06 pm
Re: M.I.D.I PTT mute on virtual strips and all buses
that is what i am currently doing however that still leaves macro buttons and voicemeeter out of sync with the midi controller. and i have 2 macro buttons that are push and hold buttons to switch outputs. these are controlled by a single SPDT switch on the midi controller so one of them is always pressed and i cant set that in an initial state script.