Generic OSC Listener - Outside of Companion Service

drjeffries commented 4 months ago

I would love the ability to get feedback from devices that don't necessarily have current support via OSC; or to get OSC messages back for Dev purposes.

As it stands right now, the generic OSC module only allows for sending OSC commands.

The name of the device, hardware, or software you would like to control.

Companion custom variables

What you would like to be able to make it do from Companion.

Generate or update an internal variable, so other modules can reference the custom var.
It would be great if it could parse either the last /xyx of the message or the whole sring.
Bundles are interesting but not critical

Direct links or attachments to the ethernet control protocol or API. Without this, it can be very difficult, and in some cases, impossible to fulfill your request.

It would seem that the current service could be repurposed for a module like this:
companion/lib/Service/OscListener.js
https://github.com/CNMAT/OpenSoundControl.org/tree/master

thedist commented 4 months ago

Is there a reason you want this as a separate module, rather than as a feature request for the Generic OSC to be updated to allow for this sort of functionality?

drjeffries commented 4 months ago

Honestly, no. I was just focused on what that looks like.

It probably makes the most sense to extend the generic OSC module.

On Fri, Feb 23, 2024, 7:13 AM Jeff Martin @.***> wrote:

Is there a reason you want this as a separate module, rather than as a feature request for the Generic OSC to be updated to allow for this sort of functionality?

— Reply to this email directly, view it on GitHub https://github.com/bitfocus/companion-module-requests/issues/1409#issuecomment-1961221114, or unsubscribe https://github.com/notifications/unsubscribe-auth/BD54U7DBX4F4FOA6CV4HQ6TYVCBXDAVCNFSM6AAAAABDVTNQ36VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRRGIZDCMJRGQ . You are receiving this because you authored the thread.Message ID: @.***>

dnmeid commented 3 months ago

Your usecase "updating custom variables" from OSC is already possible using Companion's OSC API. Even if it was not possible, it would be better to extend the existing OSC module than to request a new one. So as this is possible, I'm closing this issue.

drjeffries commented 3 months ago

As reference in the built-in (I didn't see it previously)

/custom-variable/<name>/value <value> Change custom variable value

bitfocus / companion-module-requests

Generic OSC Listener - Outside of Companion Service #1409