![]() ![]() Even though the string is being recognized in the log by Millumin, it's just not fuctioning after that point, even if you link up interactions with cues. So when it comes to using Companion, in order to get the cuing and GoTo to function properly, you must use the " OSC-Millumin- MAIN: Send message without arguments" command." The " OSC-Millumin- MAIN: Send string" will not provide the results you're looking for. Thank you for pointing me in the right direction! That helped break the mental log jam. You helped solve something for me, but it wasn't quite as simple as changing the OSC Input to 1 for me. Hey so much for the response, and my apologies for the prolonged delay. (Companion command= OSC-Millumin-Send string). This works.at least with Millumen seeing the command, but not firing the cue tied to it. #1- OSC-Send string command from Companion To give a little more detail, here are a couple of screen shots to help you understand what I can see, and what I cannot seem to get to work. ![]() I think though in my troubleshooting over here, for some reason Millumen simply is not taking the OSC command, and firing the cue that should be triggered, and which was made in the interactions once that command is sent to Millumen. Please correct me on this if I am wrong, and do tell me what the parameter is that needs to be sent. It just simply is not functioning the way it should be inside Millumen.Īlso, I have found no difference in the Millumen logs between the OSC command of "Send message without aurguments" or "Send string" except the value/parameter being sent along with the command. However, what I was expecting should have been an interaction fired correctly, but it is not. What you stated with regards to the OSC message and the string parameter validates that I was setting things up the way they should be. Hey will check out the Beta most certainly. Thank in advance for any and all feedback. Here are some screenshots to help understand what I'm saying. What am I missing, or did something break, or change between v3 and v4 that I need to be taking into account? A start cue for a column with the /goto-30 string, etc.) In fact any of the OSC commands, while they are coming in properly into the system will not fire any cues I create once they are mapped to the interactions. However, even though I have connected the OSC commands to the Cues through the Interactive Learning window, the cues simply will not fire. The OSC string is being sent correctly, and is being acknowledged by Millumen as the correct string. The GoTo cues once created are firing correctly if I fire them manually from the cue list. So thanks for taking the time to respond. ![]() I'm having a similar issue to what mentioned, although I believe it is slightly different, and all of your help on this thread has been great. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |