# Multirender Synchronization Application

**URL:** <https://discourse.libcinder.org/t/multirender-synchronization-application/538>\
**Category:** Uncategorized\
**Created:** [February 2, 2017, 7:16am UTC](https://discourse.libcinder.org/t/multirender-synchronization-application/538 "2017-02-02T07:16:41Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![petros](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.libcinder.org/petros/32/26_2.png) [@petros](https://discourse.libcinder.org/u/petros)\
**Post date:** [February 2, 2017, 11:20am UTC](https://discourse.libcinder.org/t/multirender-synchronization-application/538/4 "2017-02-02T11:20:02Z")

</div>

Hey,

I think NDI ( network device interface ) would be an ideal candidate for your purposes and I doubt that you would get better results with anything hand-rolled on a LAN with stable bandwidth.

I have an initial implementation that wraps the basic functionality into a Cinder block [here](https://github.com/PetrosKataras/Cinder-NDI) but the SDK has been updated since then which means that it would need some small tweaking for getting it up and running again. That said I know that @num3ric has been working with it on Windows and I think he has kept it up-to-date with the latest SDK changes. You can find his fork [here](https://github.com/num3ric/Cinder-NDI).

You can see it in action here :

https://player.vimeo.com/video/202182941

This is sender running on OSX and receiver running on a Linux VM. For some more info you can also check the original post I made for Cinder-NDI [here](http://discourse.libcinder.org/t/wip-cinder-ndi/322) .

Cheers,  
Petros

---

_[View the full topic](https://discourse.libcinder.org/t/multirender-synchronization-application/538)._