Make sure you have updated to the latest version of the module
Is there an existing issue for this?
Describe the feature
I would like a feedback that I can use for local variables in an expression variable that returns the argument(s) received from a specified incoming OSC message path. I could see this being implemented where instead of evaluating a condition like in the existing feedbacks, it would match the OSC path from the incoming message and then just return everything that comes after the path for that message.
You could also make it a dual purpose with the existing feedbacks, where you can either specify a value to compare for use in logic and Boolean triggers or leave the value field empty to have it return the argument(s); or instead have an on/off switch that when it's set to off it compares the argument with value in the value field and when it's on it disables the value field and just returns the argument.
The following is an example for what I mean by the dual purpose function with the existing feedbacks using the On/Off switch:
For the "Listen for OSC messages (<data type>)" it would look like this (I know the Boolean is just a checkbox, but it would apply the same to the other input fields) (The Multiple Arguments type would also look the same, but instead of "Capture Argument Value" it would be "Capture Arguments" and "Value" would be "Arguments")
For the "Listen for OSC messages (Specific Arguments)" it would look like this
The "Listen for OS Messages (No Arguments)" would remain the same.
Usecases
The use case for this would be for when you are communicating with a OSC client that receives and sends OSC messages and you would like to use the feedbacks from the target in variables and feedbacks for various buttons and expressions. Specifically in my use case, I want to control the faders of my ETC Element 2 running EOS, but I want to get the real time value/position of each fader and I want to get it's label so that I can display on the button/rotary title. I would also like to use this to capture the names of EOS direct selects and have a more dynamic custom direct select page than what is provided in the ETC-EOS module. Because the console sends messages for just about everything that happens, there would be no need to poll for label or system status changes. Because many other consoles do similar things, this would allow a programmer to fill in whatever gaps they may have in whatever Companion module they use for their console or device. Additionally, this can also be used to set up send and receive commands where the OSC message that you send via a button action will trigger the target to send a return value back to the client that sent the message.
Make sure you have updated to the latest version of the module
Is there an existing issue for this?
Describe the feature
I would like a feedback that I can use for local variables in an expression variable that returns the argument(s) received from a specified incoming OSC message path. I could see this being implemented where instead of evaluating a condition like in the existing feedbacks, it would match the OSC path from the incoming message and then just return everything that comes after the path for that message.
You could also make it a dual purpose with the existing feedbacks, where you can either specify a value to compare for use in logic and Boolean triggers or leave the value field empty to have it return the argument(s); or instead have an on/off switch that when it's set to off it compares the argument with value in the value field and when it's on it disables the value field and just returns the argument.
The following is an example for what I mean by the dual purpose function with the existing feedbacks using the On/Off switch:
For the "Listen for OSC messages (<data type>)" it would look like this (I know the Boolean is just a checkbox, but it would apply the same to the other input fields) (The Multiple Arguments type would also look the same, but instead of "Capture Argument Value" it would be "Capture Arguments" and "Value" would be "Arguments")
For the "Listen for OSC messages (Specific Arguments)" it would look like this
The "Listen for OS Messages (No Arguments)" would remain the same.
Usecases
The use case for this would be for when you are communicating with a OSC client that receives and sends OSC messages and you would like to use the feedbacks from the target in variables and feedbacks for various buttons and expressions. Specifically in my use case, I want to control the faders of my ETC Element 2 running EOS, but I want to get the real time value/position of each fader and I want to get it's label so that I can display on the button/rotary title. I would also like to use this to capture the names of EOS direct selects and have a more dynamic custom direct select page than what is provided in the ETC-EOS module. Because the console sends messages for just about everything that happens, there would be no need to poll for label or system status changes. Because many other consoles do similar things, this would allow a programmer to fill in whatever gaps they may have in whatever Companion module they use for their console or device. Additionally, this can also be used to set up send and receive commands where the OSC message that you send via a button action will trigger the target to send a return value back to the client that sent the message.