@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 things and get back to you.
Since my original post, I've been streaming pre-recorded mocap data out of Studio. It's a recording of me doing some test movements in the suit.   

@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

@skuven

I've added this to our existing feature request for this

Hey all, maybe someone can give me an idea of how to proceed.

Some info: I created a movie + live music show and we have performed it only once in a small cinema. We use two MacBooks, one on stage (with Ableton for all the audio, click, cues, etc) and one in the projection room (with Isadora and the movie itself, subtitles, etc). The whole thing is connected via timecode over audio.

But apart from all that, I also used an instance of Isadora on the stage MacBook to control the stage lights. It was very simple, just MIDI info from Ableton to Isadora dealing with a main dimmer and some color changes. Then this was sent to my DMX Enttec PRO and straight into the eight PAR Leds by the stage sides. It all worked smoothly.

But here's the thing: we got an unexpected call to do the show in a big theater, about a month from now. They have loads of lights (7 DMX universes) and an ETC EOS Gio. And now I'm not really sure how to rework my system into this new setting. The light controls now have to be on the OTHER MacBook because of the distance, but that one will not be running Ableton to send the MIDI (and even if it was, it would not sync up with the timecode)

Any ideas? I'm looking into other stuff I don't really know about like MIDI Show Control.

@emullis

I'm very confused now that it worked without gloves for you, as we apparently had an issue in our database that said that Rokoko crashes with the Rokoko SmartSuit Pro II if you're not using gloves, but then we resolved it because it looked like the problem was resolved.

If we can't reproduce it reliably, we can't make a fix, so we need to isolate what causes and doesn't cause it.

Between it crashing, then not crashing, then crashing again, did you do anything like:

• Plugging in the suit while streaming instead of using wifi
• Changing the network the suit was on
• Changing the network your computer was on
• Changing the port being used
• Un-checking and re-checking streaming in Rokoko
• Using a different Scene in Rokoko
• Unassigning and/or re-assigning the suit from an actor in Rokoko before starting to stream data
• Unassigning and/or re-assigning the suit from an actor in Rokoko while streaming data
• Unassigning and/or re-assigning the suit from an actor in Rokoko after ceasing to stream data
• Anything else you can think of?

Could you also try making sure that your computer is only connected to one network (the one being used for Rokoko) and disabling your computer's connection to any other networks?

If none of that seems like it affects anything, we could proceed with more tests (I wish I could do them myself, but I don't have a v2 suit).

@woland No I don't think that will help as the ports pertain to what midi device you're connecting to. Inside the sysex actor is a script you have to write, then you insert perameter values using 'P1'  'P2' etc. There are workarounds where I trigger specific sys ex actors with some characters pre determined. 

It would be a great feature to be able to put way more parameters into these actors generally. Same with the text formatter actor