Repository navigation
Replies: 2 comments 15 replies
|
Thanks for the suggestion! This indeed can become a simple and efficient mechanism for exchanging with vimix It is implemented in Beta : please try and let me know if this works, what you suggest to improve it. I added it to the documentation at https://github.com/brunoherbelin/vimix/wiki/Open-Sound-Control-API#messages-sent-by-vimix |
15 replies
|
As a fun fact, if you launch two vimix instances, and set the input OSC port of instance A to the output OSC port of instance B, when you ask |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
It would be nice to implement more OSC messages to control vimix sources status from controller or other software.
It would be very helpful if Vimix sent the video players percentage, so I could check the progress of a video from other software.
I would be good also to know from OSC if the video has any flags set.
A good solution can be implement an info message
/vimix /[target] /info {string argument}
and vimix reply...
examples:
/vimix /[target] /info file (return absolute path of video file)
/vimix /[target] /info seek (return actual seek position)
/vimix /[target] /info speed (return actual speed value)
/vimix /[target] /info alpha (return actual alpha value)
/vimix /[target] /info angle (return actual angle value)
/vimix /[target] /info size (return actual size value)
and so on.. in this way vimix output an OSC message only when we ask something about a target and not for all loaded target.
All reactions