[ANSWERED] Redundant Simultaneous Instances of Isadora acting as backup in case of failure ?

Bonami

@jfg

Oh I never thought about exploring this ! Definitely going to look into it for specific situations ! Merci beaucoup !

Trevor

I take the simple approach of the USB Go Box. Has two usb outputs, and will trigger cues on diferent machines in sync

https://www.thatlittlebox.co.uk/usb-go-box. Also, is designed as a cueing device to ensure no accidental cues.

CitizenJoe

@trevor That's clever.

Cheers,

Hugh

Woland

@woland said:

I'm already working on an example file for you, but here's a basic explanation of what's coming:

Sorry, I got swamped during the week. Here's what I have so far:

redundancy-heartbeat-switch-2024-02-15-3.2.6.izz

What's really neat is I figured out a way to just use the same patch on both the leader and follower computers with zero configuration in terms of telling which one you want to be the leader and the follower. Here's the basics of how it works:

Launch the patch on the Leader computer.
The patch checks whether or not there's a heartbeat from a Leader.
The patch doesn't see a heartbeat already, so it knows it's supposed to become the Leader.
The patch, running on the Leader computer, starts sending out a heartbeat.
Launch the patch on the Follower computer.
The patch checks whether or not there's a heartbeat from a Leader.
The patch sees a heartbeat, so it knows it's supposed to become a follower.
The patch, running on the Follower computer, starts operating as a follower.
If the heartbeat from the Leader computer stops, the patch, running on the Follower computer, will automatically become the Leader and start sending a heartbeat.
At this point, you could re-launch the patch on the original Leader computer and it would see the heartbeat and automatically start operating as a Follower.

It's totally up to you what to trigger when the switch from Leader to Follower happens, but I got pretty far in creating a mechanism for the heartbeat and triggering the passing of the baton if the Leader's heartbeat stops.

Bonami

@woland

Oh my god Woland ! Ahah this is absolutely above my expectations ! Your first answer was already very clever, I was not expecting such a detailed Izz file on top of it ! I'm navigating your patch at the moment. I had, in the meantime, created something along those lines after your reply, but nowhere near as automatic, complete, and conceptually mature as the file you provided. I'm glad I can learn from your reflexions throughout your patch. Thanks again, really.

Woland

@bonami said:

I'm navigating your patch at the moment.

My pleasure, and thank you for prompting me to make it. I hope it will be helpful to you and others. Let me know if you have any questions as I'd be happy to answer them. I also hope I'll be able to find the time to finish the file soon...

mark_m

@woland

I just want to say what valuable and important work this is: I recently lost an Isadora vs Disguise argument on a production, on the very basis that Isadora didn't have a built-in automatic fallover the way that Disguise systems do. I would rather program in Isadora than Disguise, and if I can demonstrate this kind of redundancy I wouldn't lost these arguments again :-)

Bonami

@mark_m Ahah same thing happening to me ! As I'm trying to push more and more of our live events over to Isadora (We mostly use Watchout and/or Disguise on larger productions) but for most corporate gigs, of all sizes, I would say 95% of them would be abundantly well-served with Isadora. But the last standing blockade is always the redundancy. Now @Woland created this ingenious way for me to solidly implement Isadora as a totally viable, relevant solution throughout our operations.

DillTheKraut

@bonami

I just like to second this! Coming from party/live visuals, going to commercial and musical productions, but also Opera and fine Art festivals and now at municipal theatre.
I have experience with all of them (disguise, Watchout, Wings, Pandoras, milllumin, Touchdesigner and Resolume (starting with 3.x , back in the days and moving to Izzy shortly after, because of limited layers :P ). Non of them have the combined balance of usability, lerning curve and 'give it to the client's hands' probability, as Isadora does! Call it scalability. The price/needed feature combination is far off anyways.
We now are running Wings successor Pixera and I so often miss the scene functionality and the logic possibiltys, beside alot of other issues :D.
The only real missing functionality, which is holding back the switch, are the frame synced multi server/device distribution and the somewhat oldschool GUI (which is just a psychological issue ;-) ).
For most commercial users, probably is the missing hardware complete system solutions + (official) service.

Woland

@woland said:

I also hope I'll be able to find the time to finish the file soon...

@Bonami I just finished the file in my After Hours Isadora Lab. Here's the file: redundancy-heartbeat-switch-2024-02-29-3.2.6.izz

The file and the link to a recording of me building this addition to the file will be posted in the Isadora channel of the Office Hours Discord soon.

This updated file includes an example Content Scene:

One of the things this Scene does is explain how to keep your Scene List in Synch across the two files (it's the section at the top right labeled "#Keeping the Active Scene in Synch Across Two Files").

Here's the guts of the Macro from "Method 1 - Next/Prev Scene" (I'd recommend the second method instead though):

Here's the guts of the Macro from "Method 2 - Scene Synch" (I'd recommend using this method):

It's possible I made a logic mistake somewhere, as I haven't tested extensively with two computers, but feel free to let me know if you encounter problems and I'd be happy to fix the file.

Best wishes,

Woland