Indigo Network Manager Documentation and Tutorial
Indigo Network Manager Documentation and Tutorial
Hi everyone,
Attached is some preliminary documentation on the Indigo Network Manager.
From the documentation:
The Network Manager does two things:
Floating licences – If you have purchased some floating Indigo licences, the Network Manager is the piece of software that hands out floating licences to computers on your network. However, you don't require floating licences to use the Network Manager for network rendering coordination.
Please contact sales@indigorenderer.com to purchase floating licences.
Coordinating masters and slaves doing network rendering – Indigo supports network rendering, which means that additional computers (slaves) can help other computers (masters) render an Indigo scene. The Network Manager can control and coordinate this network rendering, by assigning slaves to masters.
This documentation will be available as part of the Indigo Manual soon.
Attached is some preliminary documentation on the Indigo Network Manager.
From the documentation:
The Network Manager does two things:
Floating licences – If you have purchased some floating Indigo licences, the Network Manager is the piece of software that hands out floating licences to computers on your network. However, you don't require floating licences to use the Network Manager for network rendering coordination.
Please contact sales@indigorenderer.com to purchase floating licences.
Coordinating masters and slaves doing network rendering – Indigo supports network rendering, which means that additional computers (slaves) can help other computers (masters) render an Indigo scene. The Network Manager can control and coordinate this network rendering, by assigning slaves to masters.
This documentation will be available as part of the Indigo Manual soon.
- Attachments
-
- Indigo Manual Network Manager.pdf
- (163.25 KiB) Downloaded 3720 times
- zeitmeister
- Posts: 2010
- Joined: Tue Apr 22, 2008 4:11 am
- Location: Limburg/Lahn, Germany
- Contact:
Re: Indigo Network Manager Documentation and Tutorial
Hi Ono,
can you explain "floating licence", please?
Did you announce them officially, because I seem to missed it?
Thank you very much!
can you explain "floating licence", please?
Did you announce them officially, because I seem to missed it?
Thank you very much!
Cheers, David
DAVIDGUDELIUS // 3D.PORTFOLIO
·
Indigo 4.4.15 | Indigo for C4D 4.4.13.1 | C4D R23 | Mac OS X 10.13.6 | Windows 10 Professional x64
DAVIDGUDELIUS // 3D.PORTFOLIO
·
Indigo 4.4.15 | Indigo for C4D 4.4.13.1 | C4D R23 | Mac OS X 10.13.6 | Windows 10 Professional x64
Re: Indigo Network Manager Documentation and Tutorial
Hi zeitmaster,
I think this is the classical floating license feature available on many softwares (like 3dsmax). You register the licenses you purchased on a "license server" computer, not on your workstations. Then, when you use the software on a workstation, it connects to the license server which locks a license.
That means, if you have 6 licenses, that you are not anymore limited to install it on 6 workstations, but limited to 6 workstations running the software at a time. And you do not need to ask for a license reset when you change your workstation hardware.
Etienne
I think this is the classical floating license feature available on many softwares (like 3dsmax). You register the licenses you purchased on a "license server" computer, not on your workstations. Then, when you use the software on a workstation, it connects to the license server which locks a license.
That means, if you have 6 licenses, that you are not anymore limited to install it on 6 workstations, but limited to 6 workstations running the software at a time. And you do not need to ask for a license reset when you change your workstation hardware.
Etienne
Eclat-Digital Research
http://www.eclat-digital.com
http://www.eclat-digital.com
Re: Indigo Network Manager Documentation and Tutorial
Sounds great, but before I start messing with this feature I wonder how/if I can convert my Indigo Lifetime Licence and the node Licences to the new scheme? Has anyone done this already or knows if it's possible at all?
Regards,
Erwin
Regards,
Erwin
-
- Posts: 1828
- Joined: Mon Sep 04, 2006 3:33 pm
Re: Indigo Network Manager Documentation and Tutorial
This is most likely a Windows issue, but I'm hoping someone with Windows can help me out here.
I've set up the Network Manager on my main machine (i7 930 + Windows 7) and a Slave on my old machine (AMD Q9550 + Windows Vista). The Network Manager displays the AMD machine under Slaves and the i7 under Masters. So far so good.
When I boot up a rendering on my Master (with the Network Rendering button depressed), it doesn't show anything under the Network Rendering tab; my Slave doesn't show up as a client. On the Slave console, I get "Connection Exception: Could not make a TCP connection to server 169.254.68.122:777,Error code: WSAETIMEOUT" then "Connection to master terminated."
This makes me think that it's a network security issue (and probably a Vista issue) or something and not necessarily and Indigo issue as the Network Manager reads both machines fine. For some reason my Slave cannot connect to my Master at rendertime. I want to get this resolved so that I can use the power of both my machines.
Any tips? Thanks in advance...
I've set up the Network Manager on my main machine (i7 930 + Windows 7) and a Slave on my old machine (AMD Q9550 + Windows Vista). The Network Manager displays the AMD machine under Slaves and the i7 under Masters. So far so good.
When I boot up a rendering on my Master (with the Network Rendering button depressed), it doesn't show anything under the Network Rendering tab; my Slave doesn't show up as a client. On the Slave console, I get "Connection Exception: Could not make a TCP connection to server 169.254.68.122:777,Error code: WSAETIMEOUT" then "Connection to master terminated."
This makes me think that it's a network security issue (and probably a Vista issue) or something and not necessarily and Indigo issue as the Network Manager reads both machines fine. For some reason my Slave cannot connect to my Master at rendertime. I want to get this resolved so that I can use the power of both my machines.
Any tips? Thanks in advance...
-
- Posts: 1828
- Joined: Mon Sep 04, 2006 3:33 pm
Re: Indigo Network Manager Documentation and Tutorial
Any suggestions on this?
Re: Indigo Network Manager Documentation and Tutorial
maybe the port is 7777 instead of 777 ![Wink ;-)](./images/smilies/icon_wink.gif)
![Wink ;-)](./images/smilies/icon_wink.gif)
polygonmanufaktur.de
-
- Posts: 1828
- Joined: Mon Sep 04, 2006 3:33 pm
Re: Indigo Network Manager Documentation and Tutorial
Whoops, typo!Zom-B wrote:maybe the port is 7777 instead of 777
The thing is that my other quad shows up in the Network Manager under 'Slaves' and has my i7 listed as 'Assigned master ID' so it seems that the two machines are talking.
Could it be something I have to configure at my router? For example, in the Mac network rendering thread (link escapes me for a second) someone mentioned configuring the router to allow traffic on a certain port but I don't know how to do that...
Re: Indigo Network Manager Documentation and Tutorial
I actually still use the old way of network rendering, without Network Manager.
Anyway, In Indigos Option Menu you need to activate Network Manager, and deactivate floating license afaik.
I had absolutely no issues combining 2 PCs via Lan & a MacBook via Wlan to render together the "old way".
Anyway, In Indigos Option Menu you need to activate Network Manager, and deactivate floating license afaik.
I had absolutely no issues combining 2 PCs via Lan & a MacBook via Wlan to render together the "old way".
polygonmanufaktur.de
-
- Posts: 1828
- Joined: Mon Sep 04, 2006 3:33 pm
Re: Indigo Network Manager Documentation and Tutorial
Hmmm... well I just got it to work without the Network Manager. I just re-enabled 'Do master search broadcast' and disabled 'Use network manager', booted the slaves and away we went. This is the first time I've gotten any kind of network rendering to work! Thanks Zom-B for your help!Zom-B wrote:I actually still use the old way of network rendering, without Network Manager.
Anyway, In Indigos Option Menu you need to activate Network Manager, and deactivate floating license afaik.
I had absolutely no issues combining 2 PCs via Lan & a MacBook via Wlan to render together the "old way".
Re: Indigo Network Manager Documentation and Tutorial
he he... happy to know it worked out for you ![Smile :)](./images/smilies/icon_smile.gif)
Network Rendering is one of the most important features of Indigo for me,
I use from quick material previews to final renderings, have a slave
in the autostart of your second Computer and you are always ready to rock![Very Happy :D](./images/smilies/icon_biggrin.gif)
![Smile :)](./images/smilies/icon_smile.gif)
Network Rendering is one of the most important features of Indigo for me,
I use from quick material previews to final renderings, have a slave
in the autostart of your second Computer and you are always ready to rock
![Very Happy :D](./images/smilies/icon_biggrin.gif)
polygonmanufaktur.de
-
- Posts: 1828
- Joined: Mon Sep 04, 2006 3:33 pm
Re: Indigo Network Manager Documentation and Tutorial
Definitely will get that going. Eventually I want to have a little rack-mounted render farm set up.Zom-B wrote:he he... happy to know it worked out for you
Network Rendering is one of the most important features of Indigo for me,
I use from quick material previews to final renderings, have a slave
in the autostart of your second Computer and you are always ready to rock
Re: Indigo Network Manager Documentation and Tutorial
I'm dreaming of building a Helmer RenderMonster for quite some time ![Smile :)](./images/smilies/icon_smile.gif)
I still wait to see how GPU rendering develops in the future, and also CPUs combinded with GPU could be interesting here...
maybe even a GPU onboard device on the motherboard could be a nifty little helper regarding price vs. samples/s if Glare would support multi GPU rendering some day...
I hope to see clearer here in 2011![Wink ;-)](./images/smilies/icon_wink.gif)
![Smile :)](./images/smilies/icon_smile.gif)
I still wait to see how GPU rendering develops in the future, and also CPUs combinded with GPU could be interesting here...
maybe even a GPU onboard device on the motherboard could be a nifty little helper regarding price vs. samples/s if Glare would support multi GPU rendering some day...
I hope to see clearer here in 2011
![Wink ;-)](./images/smilies/icon_wink.gif)
polygonmanufaktur.de
- jarmenkell
- Posts: 31
- Joined: Sun Jul 18, 2010 8:37 am
- Location: MSK RU
- Contact:
Re: Indigo Network Manager Documentation and Tutorial
in attempt to collect all network-related issues in one topic i put my question here
the slave writes this:
"Indigo Driver Exception: SceneLoaderExcep: Found unexpected element 'save_images_on_close'. In element 'renderer_settings', around line 9, column 5)
Connection to master terminated.
..then it tries to reconnect and discoveres that he already has failed loading that scene before and then it all gets repeated again.
what can be the problem?
the slave writes this:
"Indigo Driver Exception: SceneLoaderExcep: Found unexpected element 'save_images_on_close'. In element 'renderer_settings', around line 9, column 5)
Connection to master terminated.
..then it tries to reconnect and discoveres that he already has failed loading that scene before and then it all gets repeated again.
what can be the problem?
Re: Indigo Network Manager Documentation and Tutorial
A quite well self explaining Bug Messagejarmenkell wrote:what can be the problem?
![Smile :)](./images/smilies/icon_smile.gif)
Your slave file don't understand some code in the IGS, and also explains you where the problem is!
Since "save_images_on_close" is a new feature it seems you have an older Slave then master version of Indigo...
polygonmanufaktur.de
Who is online
Users browsing this forum: No registered users and 18 guests