@woland

I hooked up my Smartsuit Pro II and ran tests.
With Studio Open first, then Izzy, then turning on streaming = Immediate Izzy Crash.
With Izzy open first, then Studio, then turning on streaming = Crash after 5 minutes.
Again, this is with the most recent versions of Rokoko Studio and Izzy. 

In terms of your suggestions: 

- I use a dedicated router that goes directly into my laptop, so there is no wifi network in the setup. Suggestions about the network, therefore, don't apply. 
- I unchecked and re-checked streaming in Rokoko.
- I have tried different scenes in Rokoko. 

I can try changing the ports and re-assigning the suit, but these are things I never had to do before. Given that I'm using the same suit, comm setup, and scenes, it doesn't seen like these are potential fixes. The only changes to my setup have been updated Izzy to the most recent version and Rokoko Studio as well. 

Is anyone else having this problem, or is it just me?  

@venusirais

I would not have the knowledge to answer your question and no doubt someone will provide a workflow etc.

As you were saying that the video content and guides was not great, I am wondering if you had a look at the guru session on motion tracking with mark?

LINK

If you use the BRAVE browser, you do not have to suffer the joy of youtube ads.

I am not sure if I am going over stuff you already know and not wanting to patronise etc.

Hope this helps.

eamon

Hey, could anyone suggest a workflow for a security camera simulation? 

I am working on a performance that will have 2 dancers and I would like to create the effect of a red frame around each one with some letters that say "error" while they move through the stage. It would be a live video that is going to be also projected in real time. 

I am using my phone camera, but I get stuck at the blob track and the framing since all the tutorials and info I find seem to be kind of old, and the video I get from the output doesn't show any blob.

My current workflow is a Video In Watcher connected to a Proyector and Eyes++, and Eyes++ to a Blob decoder. Help 

@mark_m

Hi

This is my bad. I confused the qlab one on the add-ons page with a one for isadora/eos.

But, if you peruse the links posted by Woland above, there is a treasure trove of information, guides and files to achieve the aim of using OSC to control lighting cues on the eos consoles. 

I read through those links and ,as usual, leant more than I thought I knew! I would start with those guides and Marks Guru session on OSC. I am sure ETC has OSC guides on their sites as well as having a healthy forum akin to here. One of the links gives a very detailed step by step set up guide here. 

You do not need the console but could practice this set up with 1/2 computers. Once they are speaking via network, then you could play with the command syntax and be ahead of yourself before you enter the venue. The venue lighting staff should be up to speed with this approach as it has become a very normative practice in the industry.

You are only sending a simple GO command to eos at the end of the day. You can specify the number but the syntax is very straightforward etc. Once you have the first one down, then it should be a simple rinse and repeat.

Eamon

@eamon said:

There is an eos/isadora actor on the addons page rhat is worth a look.

 Hi Eamon,

I just tried to find this, but couldn't. Please can you share the link? Or give me more clues for my search?

Many thanks!

Mark (not him)

I'll play around with these suit-related things and get back to you. 

As noted above, after the original crashes while wearing the suit, I've been doing all the tests by streaming pre-recorded mocap clips/data out of Studio. Legacy works great. No crashes. Streaming pre-recorded mocap data out of the most recent version of Rokoko Studio results in Izzy crashing (either immediately or after 30 seconds or so), no matter the sequence of opening the two softwares and turning on streaming. This has happened every time, except for one. 

Also, note that I've tried the set up on two different laptops and that the outcome is the same. 

Out of curiosity, I tried different clips and even just one of the avatars standing in place, but Izzy crashes.  

@gpeddino

in the past, I've got the house tech to programme some lighting states into the desk (GrandMA) and load each of these states onto submasters.
then it is easy to send DMX from Izzy through an Enttec to control these subs.

@woland

Edit, beaten to it! 

@gpeddino

These might help:

1. https://community.troikatronix.com/topic/2919/cueing-etc-nomad-via-isadora/8?_=1696242326127
2. https://community.troikatronix.com/topic/6332/triggering-isadora-3-with-osc-from-an-etc-ion-nomad
3. https://community.troikatronix.com/topic/5351/tutorial-how-to-do-fader-communication-with-etc-eos-lighting-desk-using-osc
4. https://community.troikatronix.com/topic/2924/working-with-the-eos-and-osc/10

@gpeddino

It seems that you might need to change the methodology of how you interact with the lighting rig and Isadora would control this new set up. 

I would split this into two tasks. 

Task 1

- I would use the house system and desk to program up the various needs and looks for your show. It will be infinitely simpler using the EOS and a decent inhouse operator. Isadora as the main controller of lighting might not be the strongest method. 

This way, you do not have to spend most of your day forcing isadora into a semi complicated lighting set up.

Task 2

Once you have programmed your various looks and cues, you now need a way to control this information. 

OSC, Open Show Control, is your new best friend. I do not wish to patronise if you already know this protocol

OSC is a network based inter machine protocol that is perfect for controlling other items. Isadora and EOS will speak this language natively. 

On your mac on stage, you would need to program some OSC transmit actors which would then in turn trwould be used to trigger the various lighting states on the eos console. As said, this is a normal enough practice in the eos/isadora world.

I do not know your knowledge base with networking. 

A simple plan would be to put a network switch at the mac on stage and then run a network cable to the eos console. Depending on their set up, they are probably already running a network based setup. With 7 universes, they should be doing so.

I can explain more of the networking thing if you wish to proceed down that road.

There is an eos/isadora actor on the addons page rhat is worth a look.

You should watch the guru session on OSC on the troikatronix youtube channel. Use the Brave browser to bypass ad fun.

This is how I would look to trigger computers a distance away. I have never used midi and know very little about it. I am a lampie at heart.

OSC is a network protocol and once set up is very robust.

Have a chat to the lighting guys in the venue you are touring into as this is probably second hand language to them. Whilst they may/may not know Isadora, they most definitely have done this process with Qlab etc.

The "reprogamming" should not be that complicated in the above methodology. Let eos do all the lighting cues and then use Isadora to control said cues. You would then have the strengths of both worlds.

Hope this helps

Eamon