Trigger Companion presses by Channel/Note/Velocity

Hey,
I’d like to use this module to have ProPresenter (Windows) trigger Companion button presses, where Channel | Note | Velocity correspond to the 3 variables to actually press a button.
I can use custom variables, expressions, and trigger events to parse apart the MIDI notes when they’re sent, but that’s complex and feels like I’m missing something.

Is there an easy way to do this?

Thanks,
Jonathan

Is this helpful? If not, please explain further what you are trying to achieve!!

I watched that video, it’s looking for a single key combination to then press a button.
I’d like to be able to press any button, where Channel/Note/Velocity says which button is being pressed.

Can you give me an example of the message you are sending to companion and what SD button you want to press? Likely it will take some string manipulation to do it.

BTW, I HIGHLY recommend that you Don’t make the incoming message trigger a button press. You’re much better off to have the incoming message trigger the actual action of that button. Then if you decide to move buttons around, or a different layout is used, you don’t have to re-do all your triggers.

Honestly, straight button presses is probably the simplest use case. I do live event production, and this is what I’d use it for.

ProPresenter is used by a ton of churches, and currently the Windows version only supports MIDI outputs. The ProPresenter plugin used to be most popular plugin for Companion, and supported MIDI until 3.x. I’ve replaced the functionality using 2 softwares, but it would be nice to have only loopMIDI in between Companion and ProPresenter.
Most use cases are simple, like commands to trigger ATEM inputs, or make a DSK live. With Companion 3.x adding the third variable for triggering buttons, using Channel | Note | Velocity is a straightforward solution.

But to answer your question: I’d like to use MIDI Note On command on Channel 1 |Note 2 | Velocity 3 to trigger Page 1, Row 2, Button 3.

Here’s the trigger and custom variables needed:
Click here.

5 posts were split to a new topic: MIDI Module with ProPresenter and ATEM

My man! This works great out of the box! Importing is a pain, but that’s solvable, and you already packaged it with the custom variables which is downright easy.

Thank you!

1 Like

I’ve never imported triggers - just curious why it’s painful?

We use RossTalk to “press” buttons in Companion from ProPresenter.

Here’s a video showing how we have it setup

I don’t use ProPresenter, but others have said that the only external communication available on Windows is MIDI. So it also supports RossTalk?

RossTalk is on the Mac version (and a bunch of other obscure protocols), Windows version is MIDI only.

ah, gotcha. I missed that part of the original post. Though, I may look into using Midi instead of RossTalk as we do have to connect RossTalk in ProPresenter every week. It would be nice not to need to do that.

Copy. This thread looks to be about a Windows implementation, but good to know if anyone is using MacOS.

FYI, I’ve added some additional variables to make the trigger MUCH easier now. No custom variables should be needed anymore.