-
-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OSC input from Resolume does not work #1255
Comments
Here is the output from Protokol when using that OSC command (Ontime cannot be running for it to see it): It has this when clicking away from the column: |
Hi @MilkMGN, thank you for this I will try to see if there are any issues on ontimes side, meanwhile, could you please send us your project file? |
Hey, the showfile used is the standard one that comes default on install.On Oct 11, 2024, at 3:15 PM, Carlos Valente ***@***.***> wrote:
Hi @MilkMGN, thank you for this
I will try to see if there are any issues on ontimes side, meanwhile, could you please send us your project file?
You can send it to the email ***@***.*** or hop in to discord and find me there
https://discord.com/invite/eje3CSUEXm
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
I see. Could it be as simple as Ontime OSC input not being enabled? It isn’t in the demo file |
Hey, it does say enabled in the screenshots? Is there something else I have to do to enable it? |
Hi, no. I apologise I didnt see the Ontime screenshot. To debug this you will need the Network logger Can you please double-check that?
|
Just done some quick testing here (on 3.6.1):
|
Hey, sorry work is stretching my time thin. Going to have a look at this in half an hour or so. I did try using |
@cpvalente Sending |
Hi @MilkMGN I believe you may be sending the index as part of the address and not the payload. I suggest you test the OSC into Ontime independently to understand the API and then try and apply in Resolume if you are having a hard time figuring it out hop into the discord server and we can help |
hey @MilkMGN Do you by chance have Wireshark on you computer and could take a look at the packet? |
Hey, using Protokol to try the same command i get
|
I think the issue is the output from Resolume I tested with the latest version of Resolume and when you set an OSC shortcut Resolume tacks on additional arguments to indicate pressed/released/active or something like that. Example of having the select of a clip set to the address resolume_osc.mov |
I think this is it, thanks. @cpvalente Is there a way to have it trash those values / only listen to the value 1 and trash 0? i don't think people will need the ability to trigger on time when a clip gets deselected |
Hi @MilkMGN , we took some time to investigate from our side We believe that Ontime is behaving appropriately to the data that is receiving, and that patching behaviour from Resolume on our side is not correct. As a system integrator, I believe there is no valid reason for an application to inject payload out of my control. As a work around, I suggest routing the message from a middleware application such as companion or chataigne. This middleware would be able to do the translation and trigger Ontime In the meantime, I would also suggest that you open a ticket in the Resolume side so that this behaviour can be revised by their team Hope this helps, please let us know if we can provide any further help here |
Hello,
It's Christmas rehearsals time again, and again I am here automating Ontime. This year, we are not timecoding the whole show. This means I have to either manually trigger Ontime, or figure out another way, which leads me to my problem.
I am trying to output an OSC message from Resolume to trigger cues.
This is what I am sending as a test (Will use Event IDs in the production deck)
These are the configs from Resolume and Ontime.
Using an OSC monitor tool, like Protokol, I can see the message being sent when i click the column in Resolume, however when I have Ontime running and do the same, nothing happens.
Maybe I'm doing something wrong.
Thanks
The text was updated successfully, but these errors were encountered: