/selectedLayer/mapping/topLeft to move corner at./selectedLayer/rotation to rotate at 90°./selectedLayer/position/y to move on Y at 21px (short form is /selectedLayer/y)./selectedLayer/position/x to move on X at 12px (short form is /selectedLayer/x)./selectedLayer/position/xy to move at (short form is /selectedLayer/xy)./selectedLayer/opacity to update opacity at 75%.Here are some properties that can be used for layers : OSC messages are case insensitive ("selectedLayer" is the same as "selectedlayer") to target the selected light in the interface (in orange) to target the selected layer in the interface (in orange) to target the element at index 99 (see Preferences to display the indexes) to target the element named "myElementName" You have different alternative, depending on how you manage your elements : To send a 'ping', so Millumin returns multiple OSC messages, that describe the state for all the layers : /action/brush to move the brush with a pressure of 0.7./action/brush to move the brush in the middle with a maximum pressure (1).To move the brush-tool (normalized coordinates) : To play/pause the timeline that you are editing : To play/pause all media in the dashboard : /action/launchColumn to launch the column named "test"./action/launchColumn to launch the 11th column.You can launch or stop a specific column : Please note that such a command in the Terminal will not send OSC, but a "string" that Millumin will interpreat as OSC. If you want to quickly test OSC, simply open a Terminal and type the following command to change the opacity of the selected layer to 50% □Įcho -n "/selectedLayer/opacity 0.5" | nc -4u -w1 127.0.0.1 5000 Test/Opacity is the same as /test/opacity Lastly, Millumin's OSC API is case insensitive : □ However, feedback messages will always have the /millumin prefix. millumin/test/opacity is the same as /test/opacity To control Millumin, it is up to you to use /millumin prefix : □ Keep in mind that in most OSC softwares or libraries, address and arguments are defined separately. Įxample to set the opacity to 75%, of the layer named "test" : In brief, an OSC message has 2 parts : the /address and the. See this tutorial.Ĭreating an OSC message is simple, please refer to the Developer-Kit to get examples in many technologies. This protocol is supported by many applications on computers or mobile devices.įor example, by TouchOSC or OpenStageControl. It also sends messages (see feedback section). Millumin uses OSC messages to receive orders : for TouchOSC layouts, or to create an application that collaborates with Millumin. OSC is a communication protocol that works over the network. OSC documentation for Millumin V1 is available here. OSC documentation for Millumin V2 is available here. OSC documentation for Millumin V3 is available here. So it's not just a Mitti issue.□ THIS DOCUMENTATION IS ONLY FOR MILLUMIN V4 I have also tried using PVP, ProPresenter and Millumin and all have eventually had the same issue. This is sending to a Spyder X80 which is also genlocked. It will eventually get back in sync, only to go back out at random times. But over time it gets out of sync like in the video. At first I thought that fixed it because it worked right away. Which is what my switcher is getting and what the 2 outputs out of Mitti are set to. This DeckLink card has a sync in and I am sending it 59.94. Once again the old Intel Macs had no problem with this. I have moved to doing it this way because I have given up on the extended displays syncing up. I am using a DeckLink 8K Pro in a Sonnet eGPU Breakaway Box connected to a Mac Studio with an M1 Ultra Chip. I'm using Mitti to play the video with it positioned in the middle where the two outs line up. In the video I've linked here what you're seeing is 2 4Ks next to one another. The old intel chips had no problem doing this. Ever since moving to the M1 Max and Ultra chips I have had issues not getting the extended display to stay in sync.
0 Comments
Leave a Reply. |