Feature request: add a means for PPT to control Companion

[mark-epstein]

It would be nice to have Powerpoint running OSCPoint be able to effect changes in Companion. This could include the full complement of button presses, page flips, button appearance changes, and variable updates; but for simplicity a facility that would only change variables would be enough.

A different product, RemoteShowControl, did this by submitting to Companion an HTTP POST request, the contents of which were embedded inside [] brackets in the Powerpoint notes. When the slide opened, the http request was issued and Companion reacted accordingly.

While this connection between RSC and Companion remains functional to date, the developers at Companion have stated their side will change sometime in the future breaking this link, and Irisdown says that future development of RSC has already reached its end. I'd like to be prepared for that eventuality.

[phuvf]

Thanks for the note and the feedback.

I've not added any of this functionality directly into OSCPoint as I was pretty sure this would already be possible using Companion triggers. Your message prompted me to check if this is really true.

The control flow is:

• Set a trigger to run whenever the $(OSCPoint:notes) variable changes
• Search this variable for a keyword (I've used [BUTTON 1] in the example below
• If the keyword is found, press a button in Companion - or perform any other action you'd like

There's no pre-defined list of keywords here - you'll need to set you own.

My simple example would need one trigger for each separate action (BUTTON 1, BUTTON 2 etc.), but there's probably a smarter way of doing this where you can define the button address directly in PowerPoint (using something like [PRESS BUTTON 1/0/3]). If I get a chance I'll look into this further.

[mark-epstein]

Of course you are correct, and that works for buttons and pages. But what I would really like is to set variables from a PPT slide. For example I'd like to say [var1=85] and [var2=blue]. If I know every possible value I could search the way you suggest, but that seems like an overwhelming task for a large domain of values. Note: my current list isn't that long, and this is probably exactly what I'll do in the meantime. It's also possible that the latest Companion will let me parse my variable values out of the OSCPoint:notes variable. I haven't dug into that enough to be sure. FWIW I prefer variables (or keywords like [HALFWAY POINT]) because buttons on my Stream deck get moved from time to time, and searching through all my triggers every time that happens is an arduous task

…

On Mon, Dec 15, 2025, 05:02 Nick Roberts ***@***.***> wrote: *phuvf* left a comment (phuvf/oscpoint#93) <#93 (comment)> Thanks for the note and the feedback. I've not added any of this functionality directly into OSCPoint as I was pretty sure this would already be possible using Companion triggers. Your message prompted me to check if this is really true. The control flow is: - Set a trigger to run whenever the *$(OSCPoint:notes)* variable changes - Search this variable for a keyword (I've used *[BUTTON 1]* in the example below - If the keyword is found, press a button in Companion - or perform any other action you'd like There's no pre-defined list of keywords here - you'll need to set you own. My simple example would need one trigger for each separate action (*BUTTON 1*, *BUTTON 2* etc.), but there's probably a smarter way of doing this where you can define the button address directly in PowerPoint (using something like *[PRESS BUTTON 1/0/3]*). If I get a chance I'll look into this further. image.png (view on web) <https://github.com/user-attachments/assets/dfa3d29f-cdba-4b94-b3a0-379fe1c7be31> — Reply to this email directly, view it on GitHub <#93 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATEBQIH3T6LFNFNGJFQROZT4B2BMJAVCNFSM6AAAAACPAQLISCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNJUG44TCNZWGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>