[Script Info]
Title: 
[Events]
Format: Layer, Start, End, Style, Name, MarginL, MarginR, MarginV, Effect, Text
Dialogue: 0,0:00:00.54,0:00:04.35,Default,,0000,0000,0000,,- To use a machine in Team Render, either\Nthe Cinema 4D application or the Team
Dialogue: 0,0:00:04.35,0:00:09.09,Default,,0000,0000,0000,,Render client application must be open in\Na user session. In most cases, you'll want
Dialogue: 0,0:00:09.09,0:00:12.08,Default,,0000,0000,0000,,to use Team Render client because it\Ndoesn't need to licensed, and can be
Dialogue: 0,0:00:12.08,0:00:15.89,Default,,0000,0000,0000,,installed on as many computers as you\Nwish. In this tutorial, we're going to
Dialogue: 0,0:00:15.89,0:00:21.37,Default,,0000,0000,0000,,look at how to install and configure the\NTeam Render client application. Now if you
Dialogue: 0,0:00:21.37,0:00:26.14,Default,,0000,0000,0000,,have already installed Cinema 4D on the\Ncomputer, Team Render client is usually
Dialogue: 0,0:00:26.14,0:00:32.32,Default,,0000,0000,0000,,installed right beside Cinema 4D. So in\Nthat case, you can simply double-click to
Dialogue: 0,0:00:32.32,0:00:36.80,Default,,0000,0000,0000,,open it. But in most cases, your computer\Nwon't already have Cinema 4D on it because
Dialogue: 0,0:00:36.80,0:00:42.06,Default,,0000,0000,0000,,it's only being used as a render slave.\NWhen it comes to deploying Team Render
Dialogue: 0,0:00:42.06,0:00:47.68,Default,,0000,0000,0000,,client, you have three main options. The\Nfirst is to simply install on each client
Dialogue: 0,0:00:47.68,0:00:54.09,Default,,0000,0000,0000,,through the Maxon installer application\Njust as you a Cinema 4D GUI instance. This
Dialogue: 0,0:00:54.09,0:00:58.50,Default,,0000,0000,0000,,is probably the most fool proof method of\Ninstallation, as it ensures you get all of
Dialogue: 0,0:00:58.50,0:01:04.98,Default,,0000,0000,0000,,the libraries necessary to run Cinema 4D.\NHowever, it is a multi-step process that
Dialogue: 0,0:01:04.98,0:01:09.97,Default,,0000,0000,0000,,can't very easily be automated. So when\Nyou're installing on a lot of render
Dialogue: 0,0:01:09.97,0:01:15.65,Default,,0000,0000,0000,,slaves, it can get very tedious very\Nquickly. Another option is to simply
Dialogue: 0,0:01:15.65,0:01:19.81,Default,,0000,0000,0000,,install on one client and copy the\Ninstallation, and this will work well.
Dialogue: 0,0:01:19.81,0:01:25.78,Default,,0000,0000,0000,,However, you do need to ensure that all of\Nthe libraries are installed on each of
Dialogue: 0,0:01:25.78,0:01:29.80,Default,,0000,0000,0000,,your render slaves. The benefit to this is\Nthat you can get an installation set up
Dialogue: 0,0:01:29.80,0:01:34.39,Default,,0000,0000,0000,,exactly the way you want it. Any plug-ins\Ncan be installed in the application
Dialogue: 0,0:01:34.39,0:01:42.56,Default,,0000,0000,0000,,plug-ins directory and you can simply copy\Nit then onto each computer. The final
Dialogue: 0,0:01:42.56,0:01:48.42,Default,,0000,0000,0000,,option, and the one that I personally\Nutilized most is to install on a server in
Dialogue: 0,0:01:48.42,0:01:53.19,Default,,0000,0000,0000,,a single location and launch each instance\Nfrom the server location. Now you do have
Dialogue: 0,0:01:53.19,0:01:56.74,Default,,0000,0000,0000,,to be a little careful on this because\Nrunning the app does rely on the
Dialogue: 0,0:01:56.74,0:02:00.31,Default,,0000,0000,0000,,connection to the server. However, it\Nallows you to have a single Team Render
Dialogue: 0,0:02:00.31,0:02:04.72,Default,,0000,0000,0000,,client installation where you can manage\Nall of your plug-ins and updates without
Dialogue: 0,0:02:04.72,0:02:09.48,Default,,0000,0000,0000,,having to manage separate installations on\Neach separate computer. Just like the
Dialogue: 0,0:02:09.48,0:02:13.20,Default,,0000,0000,0000,,previous method, with this one you do need\Nto make sure that you manually install the
Dialogue: 0,0:02:13.20,0:02:19.81,Default,,0000,0000,0000,,necessary libraries. To run Release 16 on\NWindows, you'll need the Microsoft Visual
Dialogue: 0,0:02:19.81,0:02:25.85,Default,,0000,0000,0000,,C++ 2005 redistributable, 2010\Nredistributable, and 2012
Dialogue: 0,0:02:25.85,0:02:32.18,Default,,0000,0000,0000,,redistributable, as well as the Intel XE\N2013 redistributable. You can find these
Dialogue: 0,0:02:32.18,0:02:39.15,Default,,0000,0000,0000,,on the Microsoft and Intel websites or on\Nthe Cinema 4D installer disk. It's also a
Dialogue: 0,0:02:39.15,0:02:43.41,Default,,0000,0000,0000,,good idea to install QuickTime. While this\Nisn't necessary on clients unless you're
Dialogue: 0,0:02:43.41,0:02:47.99,Default,,0000,0000,0000,,using special image formats or QuickTime\Nmovies as textures, it's still a good idea
Dialogue: 0,0:02:47.99,0:02:53.12,Default,,0000,0000,0000,,to have it installed. And if you don't,\Nyou may see an error message on launch. As
Dialogue: 0,0:02:53.12,0:02:58.88,Default,,0000,0000,0000,,of Release 16, Cinema 4D doesn't have any\Nspecific library dependencies on Mac OS.
Dialogue: 0,0:02:58.88,0:03:02.63,Default,,0000,0000,0000,,Now of course, most of this is all taken\Ncare of by the installer if you manually
Dialogue: 0,0:03:02.63,0:03:06.58,Default,,0000,0000,0000,,install Team Render client on each\Nmachine. So let's take a quick look at how
Dialogue: 0,0:03:06.58,0:03:10.36,Default,,0000,0000,0000,,to install Team Render client via the\Ninstaller, because you'll always have to
Dialogue: 0,0:03:10.36,0:03:15.98,Default,,0000,0000,0000,,do that on at least one machine. So you\Nsimply take your installation disk or ISO,
Dialogue: 0,0:03:15.98,0:03:24.05,Default,,0000,0000,0000,,run the Maxon start application, choose\Nyour language. Within the installer,
Dialogue: 0,0:03:24.05,0:03:28.94,Default,,0000,0000,0000,,you'll want to continue through the first\Nscreen, enter your name, company, street,
Dialogue: 0,0:03:28.94,0:03:33.92,Default,,0000,0000,0000,,city, and country information here on this\Npage, but you can leave the serial numbers
Dialogue: 0,0:03:33.92,0:03:38.79,Default,,0000,0000,0000,,blank and just hit continue again. And\Nbecause you didn't provide any serial
Dialogue: 0,0:03:38.79,0:03:42.80,Default,,0000,0000,0000,,number, it will give you the option to\Ninstall Team Render client and Team Render
Dialogue: 0,0:03:42.80,0:03:49.05,Default,,0000,0000,0000,,client only because it doesn't need a\Nlicense. Hit continue, and here we can
Dialogue: 0,0:03:49.05,0:03:53.75,Default,,0000,0000,0000,,choose to install the application, we'll\Nhit install, agree to the end user license
Dialogue: 0,0:03:53.75,0:03:58.85,Default,,0000,0000,0000,,agreement, and hit install again. Double\Ncheck the path and then on Windows, you
Dialogue: 0,0:03:58.85,0:04:03.01,Default,,0000,0000,0000,,can create start menu entries\Nautomatically. Whenever you're ready, just
Dialogue: 0,0:04:03.01,0:04:09.42,Default,,0000,0000,0000,,click install. It's going to, on Windows,\Nask for user account control. On Mac,
Dialogue: 0,0:04:09.42,0:04:15.80,Default,,0000,0000,0000,,it'll ask for your password. Go ahead and\Nget through that, and wait for it to
Dialogue: 0,0:04:15.80,0:04:19.80,Default,,0000,0000,0000,,complete the installation. Again, the\Ninstallation here is pretty much identical
Dialogue: 0,0:04:19.80,0:04:24.12,Default,,0000,0000,0000,,to Cinema 4D, it's just installing only\Nthe Team Render application instead of
Dialogue: 0,0:04:24.12,0:04:30.11,Default,,0000,0000,0000,,installing the main GUI application. So\Nwe'll go ahead and let that installation
Dialogue: 0,0:04:30.11,0:04:36.48,Default,,0000,0000,0000,,complete and come back as soon as the\Nprogress bar hits 100%. So now the
Dialogue: 0,0:04:36.48,0:04:43.00,Default,,0000,0000,0000,,installation is complete, and we can start\NTeam Render client. We'll hit finish. Team
Dialogue: 0,0:04:43.00,0:04:47.83,Default,,0000,0000,0000,,Render client should open immediately. The\Nfirst time you launch Team Render client,
Dialogue: 0,0:04:47.83,0:04:54.26,Default,,0000,0000,0000,,or Cinema 4D for that matter, on a Windows\Ncomputer, you'll get a Windows firewall
Dialogue: 0,0:04:54.26,0:04:59.93,Default,,0000,0000,0000,,prompt, assuming you're using the built-in\NWindows firewall. And by default, only
Dialogue: 0,0:04:59.93,0:05:05.10,Default,,0000,0000,0000,,domain networks is checked in this prompt.\NIn most cases, you'll want to go ahead and
Dialogue: 0,0:05:05.10,0:05:09.67,Default,,0000,0000,0000,,check private networks and public networks\Nas well to ensure that Team Render works
Dialogue: 0,0:05:09.67,0:05:14.81,Default,,0000,0000,0000,,properly. If all of your clients are on\Nthe same domain, you may be able to leave
Dialogue: 0,0:05:14.81,0:05:19.52,Default,,0000,0000,0000,,it simply on domain. However, in many\Ninstallations, your slaves will not be a
Dialogue: 0,0:05:19.52,0:05:24.36,Default,,0000,0000,0000,,part of the main Windows domain or you'll\Nhave a mix between Macintosh and Windows
Dialogue: 0,0:05:24.36,0:05:28.50,Default,,0000,0000,0000,,computers. And in that case the domain\Nexception for Team Render client isn't
Dialogue: 0,0:05:28.50,0:05:34.58,Default,,0000,0000,0000,,enough. So I recommend always checking\Nboth private and public as well as domain,
Dialogue: 0,0:05:34.58,0:05:38.81,Default,,0000,0000,0000,,and go ahead and hit allow access. On\NMacintosh, you won't see this option,
Dialogue: 0,0:05:38.81,0:05:43.02,Default,,0000,0000,0000,,however you do need to make sure that your\Nfirewall is either off or that there is an
Dialogue: 0,0:05:43.02,0:05:48.62,Default,,0000,0000,0000,,exception for Team Render client on the\NMac firewall settings as well. For more
Dialogue: 0,0:05:48.62,0:05:52.27,Default,,0000,0000,0000,,information on adjusting the Mac or\NWindows firewall options, refer to the
Dialogue: 0,0:05:52.27,0:05:56.36,Default,,0000,0000,0000,,troubleshooting videos later in this\Ntutorial series. Now once we have Team
Dialogue: 0,0:05:56.36,0:06:02.00,Default,,0000,0000,0000,,Render client open, you'll want to go\Nahead and choose Help, check for updates,
Dialogue: 0,0:06:02.00,0:06:06.16,Default,,0000,0000,0000,,and download any incremental updates that\Nhave been issued since the initial release
Dialogue: 0,0:06:06.16,0:06:11.98,Default,,0000,0000,0000,,of Team Render. At the time of this\Nrecording, we're at Cinema 4D 16.038,
Dialogue: 0,0:06:11.98,0:06:17.79,Default,,0000,0000,0000,,which is the third incremental update and\Nit is very important to make sure that all
Dialogue: 0,0:06:17.79,0:06:22.08,Default,,0000,0000,0000,,of your Team Render clients are updated to\Nthe most recent version of Cinema 4D, both
Dialogue: 0,0:06:22.08,0:06:27.59,Default,,0000,0000,0000,,because everything must be on the same\Nversion in order to run Team Render, and
Dialogue: 0,0:06:27.59,0:06:32.16,Default,,0000,0000,0000,,also more importantly, because there's\Nvery important stability enhancements to
Dialogue: 0,0:06:32.16,0:06:38.10,Default,,0000,0000,0000,,Team Render that are happening with each\Nincremental release. So we'll simply
Dialogue: 0,0:06:38.10,0:06:43.78,Default,,0000,0000,0000,,choose to install the update, hit install.\NOnce again, we'll need to accept the EULA,
Dialogue: 0,0:06:43.78,0:06:50.97,Default,,0000,0000,0000,,hit install again, and just hit install\None more time. This is going to initiate a
Dialogue: 0,0:06:50.97,0:06:56.41,Default,,0000,0000,0000,,download, downloading all of the updates\Nonto the computer, and then it will
Dialogue: 0,0:06:56.41,0:07:00.90,Default,,0000,0000,0000,,install the update. So this, again, a\Nmulti-step process, and I'll be back as
Dialogue: 0,0:07:00.90,0:07:05.38,Default,,0000,0000,0000,,soon as it's finished. Once the download\Nhas completed, you'll be prompted to
Dialogue: 0,0:07:05.38,0:07:10.90,Default,,0000,0000,0000,,restart the applications, so we'll go\Nahead and hit restart. You'll be prompted
Dialogue: 0,0:07:10.90,0:07:15.04,Default,,0000,0000,0000,,for user account control, or on Macintosh,\Nyou'll be prompted for your username and
Dialogue: 0,0:07:15.04,0:07:25.28,Default,,0000,0000,0000,,password. And we'll go through the actual\Nupdate process. And this one's fairly
Dialogue: 0,0:07:25.28,0:07:35.55,Default,,0000,0000,0000,,quick so we'll stay with you. And Team\NRender client will launch once again. So
Dialogue: 0,0:07:35.55,0:07:38.86,Default,,0000,0000,0000,,that's the most manual, but most\Nfoolproof method of installing Team
Dialogue: 0,0:07:38.86,0:07:43.51,Default,,0000,0000,0000,,Render client using the Maxon installer.\NOnce again, you can also choose to use one
Dialogue: 0,0:07:43.51,0:07:47.95,Default,,0000,0000,0000,,of the other two deployment options we\Ncovered briefly, installing just a single
Dialogue: 0,0:07:47.95,0:07:52.20,Default,,0000,0000,0000,,client and then copying the installation\Nor installing and copying that
Dialogue: 0,0:07:52.20,0:07:55.99,Default,,0000,0000,0000,,installation to the server and launching\Neach instance of your Team Render client
Dialogue: 0,0:07:55.99,0:08:00.22,Default,,0000,0000,0000,,from a single server location. Regardless\Nof how you choose to install Team Render
Dialogue: 0,0:08:00.22,0:08:04.22,Default,,0000,0000,0000,,client, you also need to make sure that\Nany necessary plug-ins are installed.
Dialogue: 0,0:08:04.22,0:08:08.08,Default,,0000,0000,0000,,Generally, command based plug-ins and\Nscripts don't need to be installed on the
Dialogue: 0,0:08:08.08,0:08:12.74,Default,,0000,0000,0000,,render instances. You do, however, need to\Ninstall any object based plug-ins, shader
Dialogue: 0,0:08:12.74,0:08:17.05,Default,,0000,0000,0000,,plug-ins, rendering plug-ins, and plug-ins\Nof that nature that actually generate
Dialogue: 0,0:08:17.05,0:08:22.84,Default,,0000,0000,0000,,geometry or adjust the rendering of\Ngeometry during render time. To be on the
Dialogue: 0,0:08:22.84,0:08:27.87,Default,,0000,0000,0000,,safe side, I'd recommend just copying all\Nof the plug-ins installed on your Cinema
Dialogue: 0,0:08:27.87,0:08:32.59,Default,,0000,0000,0000,,4D station onto the Team Render station as\Nwell. In many cases, you'll want to put
Dialogue: 0,0:08:32.59,0:08:37.66,Default,,0000,0000,0000,,them directly into the application's\Nplug-ins directory, even if they install
Dialogue: 0,0:08:37.66,0:08:43.21,Default,,0000,0000,0000,,in Cinema 4D within the plug-in\Npreferences directly, simply because Team
Dialogue: 0,0:08:43.21,0:08:47.98,Default,,0000,0000,0000,,Render client will generate new\Npreferences for each user login. And if
Dialogue: 0,0:08:47.98,0:08:52.21,Default,,0000,0000,0000,,you're utilizing the method of installing\Non a single server instance, it'll create
Dialogue: 0,0:08:52.21,0:08:59.43,Default,,0000,0000,0000,,new preferences for each computer and user\Nlogin on each local computer. So your best
Dialogue: 0,0:08:59.43,0:09:03.55,Default,,0000,0000,0000,,bet is to put them directly into the\Napplications directory so that any time
Dialogue: 0,0:09:03.55,0:09:08.04,Default,,0000,0000,0000,,Team Render client is launched, those\Nplug-ins are initialized. If you do have
Dialogue: 0,0:09:08.04,0:09:12.38,Default,,0000,0000,0000,,plug-ins that must be run from within the\Npreferences directory, you can easily open
Dialogue: 0,0:09:12.38,0:09:18.65,Default,,0000,0000,0000,,that by clicking into the preferences tab\Nand clicking open preferences folder. And
Dialogue: 0,0:09:18.65,0:09:23.95,Default,,0000,0000,0000,,you would put the plug-ins here within the\Nplug-ins folder. Jumping back within the
Dialogue: 0,0:09:23.95,0:09:28.81,Default,,0000,0000,0000,,preferences themselves, you'll find most\Nof the main Team Render preferences folded
Dialogue: 0,0:09:28.81,0:09:34.02,Default,,0000,0000,0000,,under the renderer section here, so you'll\Nneed to click the triangle here to expose
Dialogue: 0,0:09:34.02,0:09:38.71,Default,,0000,0000,0000,,Team Render and click Team Render in order\Nto view the preferences. With Team Render
Dialogue: 0,0:09:38.71,0:09:43.48,Default,,0000,0000,0000,,client, the enable Team Render option will\Nautomatically be checked by default. The
Dialogue: 0,0:09:43.48,0:09:49.03,Default,,0000,0000,0000,,computer name will automatically be filled\Nwith the Mac OS or Windows computer name,
Dialogue: 0,0:09:49.03,0:09:55.82,Default,,0000,0000,0000,,and the security token will by default be\N12345 within Team Render client. The port
Dialogue: 0,0:09:55.82,0:10:02.71,Default,,0000,0000,0000,,as of R16 for Team Render client is 5401.\NAnd by default, announce service via
Dialogue: 0,0:10:02.71,0:10:08.10,Default,,0000,0000,0000,,Bonjour will be enabled. Share machine\Nover network will be enabled and this must
Dialogue: 0,0:10:08.10,0:10:13.00,Default,,0000,0000,0000,,be enabled in order to utilize the power\Nof the this computer within Team Render.
Dialogue: 0,0:10:13.00,0:10:16.14,Default,,0000,0000,0000,,You can choose to customize the number of\Nrender threads that this computer is going
Dialogue: 0,0:10:16.14,0:10:20.45,Default,,0000,0000,0000,,to be used by other people and not\Nstrictly as a render slave in order to
Dialogue: 0,0:10:20.45,0:10:24.13,Default,,0000,0000,0000,,reduce the render thread so that the\Ncomputer remains usable while it's being
Dialogue: 0,0:10:24.13,0:10:28.70,Default,,0000,0000,0000,,used for Team Rendering. And you can also\Nchoose to fetch assets always from the
Dialogue: 0,0:10:28.70,0:10:33.92,Default,,0000,0000,0000,,server. Team Render by default uses a\Npeer-to-peer distribution scheme where
Dialogue: 0,0:10:33.92,0:10:38.36,Default,,0000,0000,0000,,other clients can provide assets to\Nclients. This does provide a little bit
Dialogue: 0,0:10:38.36,0:10:42.57,Default,,0000,0000,0000,,better performance, however it can be a\Nlittle more error prone. So if you're
Dialogue: 0,0:10:42.57,0:10:46.13,Default,,0000,0000,0000,,experiencing issues with Team Render, you\Nmight want to enable the fetch assets
Dialogue: 0,0:10:46.13,0:10:50.82,Default,,0000,0000,0000,,always from server option to ensure that\Nit's getting its textures and Cinema 4D
Dialogue: 0,0:10:50.82,0:10:56.14,Default,,0000,0000,0000,,documents from the server computer.\NAlternatively, if you're experiencing
Dialogue: 0,0:10:56.14,0:11:01.02,Default,,0000,0000,0000,,performance issues, you may want to make\Nsure that this option is disabled so that
Dialogue: 0,0:11:01.02,0:11:05.03,Default,,0000,0000,0000,,the server isn't forced to serve all the\Nassets but the clients can serve the
Dialogue: 0,0:11:05.03,0:11:10.87,Default,,0000,0000,0000,,assets as well. The repository path here\Nwithin Team Render is the temporary
Dialogue: 0,0:11:10.87,0:11:16.45,Default,,0000,0000,0000,,location where the Cinema 4D file and\Ntextures will be stored for the job that's
Dialogue: 0,0:11:16.45,0:11:20.04,Default,,0000,0000,0000,,currently rendering as well as the result\Nfor aims there in the process of being
Dialogue: 0,0:11:20.04,0:11:25.29,Default,,0000,0000,0000,,sent back to the server. In most cases,\Nyou'll want to just leave this path to the
Dialogue: 0,0:11:25.29,0:11:29.34,Default,,0000,0000,0000,,default path unless there's not enough\Nspace on your primary drive, in which case
Dialogue: 0,0:11:29.34,0:11:32.56,Default,,0000,0000,0000,,you might want to put it on a secondary\Ndrive because it does need to store the
Dialogue: 0,0:11:32.56,0:11:37.63,Default,,0000,0000,0000,,Cinema 4D file and all textures for the\Njob that's currently rendering. So if you
Dialogue: 0,0:11:37.63,0:11:41.59,Default,,0000,0000,0000,,have a primary drive that's an SSD, you\Nmight want to move this onto a secondary
Dialogue: 0,0:11:41.59,0:11:46.03,Default,,0000,0000,0000,,drive. The repository path for Team Render\Nclient should not be the same as the Team
Dialogue: 0,0:11:46.03,0:11:51.86,Default,,0000,0000,0000,,Render server repository path, which we'll\Nget to when we cover Team Render server.
Dialogue: 0,0:11:51.86,0:11:56.12,Default,,0000,0000,0000,,Now jumping back to the security token,\Nyou may wish not to use 12345 as your
Dialogue: 0,0:11:56.12,0:12:01.11,Default,,0000,0000,0000,,security token. And in that case, you can\Ntype a custom security token right here,
Dialogue: 0,0:12:01.11,0:12:07.60,Default,,0000,0000,0000,,54321 for instance. And in that case, I do\Nhave to caution you to make sure to hit
Dialogue: 0,0:12:07.60,0:12:12.51,Default,,0000,0000,0000,,tab after entering the security token to\Nensure that it's stored. If you merely
Dialogue: 0,0:12:12.51,0:12:17.88,Default,,0000,0000,0000,,close or switch out of the preferences,\Nthe security token may not be stored and
Dialogue: 0,0:12:17.88,0:12:22.46,Default,,0000,0000,0000,,it will still be using the default old\Nsecurity token. The benefit to the
Dialogue: 0,0:12:22.46,0:12:25.77,Default,,0000,0000,0000,,security token is that you can actually\Nlimit who can access and utilize this
Dialogue: 0,0:12:25.77,0:12:31.62,Default,,0000,0000,0000,,client for rendering. So for instance, if\Nyou have an entire farm set up and it's
Dialogue: 0,0:12:31.62,0:12:35.69,Default,,0000,0000,0000,,dedicated to the Team Render server, you\Nmay want to set a custom security token so
Dialogue: 0,0:12:35.69,0:12:40.92,Default,,0000,0000,0000,,that users of individual Cinema 4D\Ninstallations can't add these clients into
Dialogue: 0,0:12:40.92,0:12:45.98,Default,,0000,0000,0000,,their Cinema 4D Team Render machine's\Ndialog and utilize it for preview
Dialogue: 0,0:12:45.98,0:12:50.52,Default,,0000,0000,0000,,rendering. You can set a default security\Ntoken that will be used whenever Team
Dialogue: 0,0:12:50.52,0:12:54.33,Default,,0000,0000,0000,,Render client is open, and you do this by\Nputting a text file in the application
Dialogue: 0,0:12:54.33,0:13:00.27,Default,,0000,0000,0000,,path. So here is the application path and\NI'm going to simply create a new text
Dialogue: 0,0:13:00.27,0:13:10.96,Default,,0000,0000,0000,,document, and this should be called\NC4D_net_securitytoken.txt. And within that
Dialogue: 0,0:13:10.96,0:13:17.22,Default,,0000,0000,0000,,file, you want to simply type the desired\Nsecurity token. So let's say we want to go
Dialogue: 0,0:13:17.22,0:13:28.30,Default,,0000,0000,0000,,with 98765. We'll save that, close it, and\Nwe'll restart Team Render client. And now
Dialogue: 0,0:13:28.30,0:13:32.61,Default,,0000,0000,0000,,if we go into the Team Render preferences,\Nyou'll see that the security token is
Dialogue: 0,0:13:32.61,0:13:38.40,Default,,0000,0000,0000,,grayed out so it cannot be changed and it\Nhas been set to 98765. So this is how
Dialogue: 0,0:13:38.40,0:13:42.05,Default,,0000,0000,0000,,you'd set a custom security token in all\Nof your Team Render client installations.
Dialogue: 0,0:13:42.05,0:13:46.72,Default,,0000,0000,0000,,Now of course, this is a little bit easier\Nto do on Windows because Windows allows
Dialogue: 0,0:13:46.72,0:13:51.36,Default,,0000,0000,0000,,you to easily create a blank empty text\Ndocument. On Mac, you do need to make sure
Dialogue: 0,0:13:51.36,0:13:57.22,Default,,0000,0000,0000,,to create a text document that is a text\Nformatted document, not a rich text format
Dialogue: 0,0:13:57.22,0:14:03.83,Default,,0000,0000,0000,,document. And you do need to make sure\Nthat it has the .txt extension. So the
Dialogue: 0,0:14:03.83,0:14:10.87,Default,,0000,0000,0000,,file name should be exactly this,\NC4D_net_securitytoken.txt. Now if we
Dialogue: 0,0:14:10.87,0:14:15.47,Default,,0000,0000,0000,,switch to the console tab of Team Render\Nclient, you'll see that immediately on
Dialogue: 0,0:14:15.47,0:14:20.71,Default,,0000,0000,0000,,launch we have a little bit of output\Nthat's provided within the window, that
Dialogue: 0,0:14:20.71,0:14:25.19,Default,,0000,0000,0000,,the local machine was moved to the offline\Nlist, the service was started on port
Dialogue: 0,0:14:25.19,0:14:31.58,Default,,0000,0000,0000,,5401. Now I do want to note that the\Nservice was started because the GUI app is
Dialogue: 0,0:14:31.58,0:14:36.93,Default,,0000,0000,0000,,open. Team Render client does not run as a\Nservice, so the GUI app does need to be
Dialogue: 0,0:14:36.93,0:14:44.17,Default,,0000,0000,0000,,open in a user session in order to run\NTeam Render client. The next couple lines
Dialogue: 0,0:14:44.17,0:14:50.46,Default,,0000,0000,0000,,here that are indented show the DNS name\Nand port by which you can connect to this
Dialogue: 0,0:14:50.46,0:14:57.75,Default,,0000,0000,0000,,client or the IP address and port that can\Nutilize to connect to this client. If you
Dialogue: 0,0:14:57.75,0:15:01.63,Default,,0000,0000,0000,,have multiple active network connections,\Nlike for instance, when you're using wi-fi
Dialogue: 0,0:15:01.63,0:15:05.71,Default,,0000,0000,0000,,to connect to the internet, and ethernet\Nor thunderbolt to connect multiple
Dialogue: 0,0:15:05.71,0:15:09.56,Default,,0000,0000,0000,,computers for Team Rendering, you'll want\Nto make sure that each internet connection
Dialogue: 0,0:15:09.56,0:15:13.46,Default,,0000,0000,0000,,is operating on a different subnet, so\NTeam Render doesn't get confused about
Dialogue: 0,0:15:13.46,0:15:20.39,Default,,0000,0000,0000,,which connection to use. The subnet is\Nusually the third number here in the
Dialogue: 0,0:15:20.39,0:15:26.70,Default,,0000,0000,0000,,sequence of four numbers separated by\Nperiods in an IP address. So here you can
Dialogue: 0,0:15:26.70,0:15:34.04,Default,,0000,0000,0000,,see that we have the wi-fi connection on\Nthe .0 subnet and the ethernet connection
Dialogue: 0,0:15:34.04,0:15:38.79,Default,,0000,0000,0000,,is using the .1 subnet. The Team Render\Nclient will show all of the network
Dialogue: 0,0:15:38.79,0:15:43.60,Default,,0000,0000,0000,,interfaces available on the computer. So\Nit's important when you add the client to
Dialogue: 0,0:15:43.60,0:15:47.94,Default,,0000,0000,0000,,add the IP address that relates to the\Nconnection that you need Team Render to
Dialogue: 0,0:15:47.94,0:15:55.27,Default,,0000,0000,0000,,use. In this case, we would want to use\Nthe 192.168.1.10 address, which relates to
Dialogue: 0,0:15:55.27,0:16:01.00,Default,,0000,0000,0000,,the ethernet cable. So to recap, you'll\Nneed to first choose one of the three
Dialogue: 0,0:16:01.00,0:16:05.83,Default,,0000,0000,0000,,methods to deploy Team Render client. And\Nmake sure that the Team Render client is
Dialogue: 0,0:16:05.83,0:16:12.05,Default,,0000,0000,0000,,open on all client machines. You need to\Nensure that the Team Render client is
Dialogue: 0,0:16:12.05,0:16:18.19,Default,,0000,0000,0000,,updated either on each individual machine\Nor if you're using a central installation,
Dialogue: 0,0:16:18.19,0:16:23.69,Default,,0000,0000,0000,,you'll need to update it within that\Ncentral installation. Install plug-ins
Dialogue: 0,0:16:23.69,0:16:28.42,Default,,0000,0000,0000,,within the applications plug-in path,\Nagain, on each machine or if using a
Dialogue: 0,0:16:28.42,0:16:33.83,Default,,0000,0000,0000,,central server installation within the\Ncentral server installation. Plug-ins that
Dialogue: 0,0:16:33.83,0:16:37.53,Default,,0000,0000,0000,,normally live in the user preferences path\Nneed to be put in the application's
Dialogue: 0,0:16:37.53,0:16:41.39,Default,,0000,0000,0000,,plug-ins path if possible, otherwise\Nyou'll need to reinstall them with each
Dialogue: 0,0:16:41.39,0:16:46.59,Default,,0000,0000,0000,,individual user login on each Team Render\Nclient machine. You also need to make sure
Dialogue: 0,0:16:46.59,0:16:51.37,Default,,0000,0000,0000,,that the Team Render client application is\Nallowed to connect through your firewall.
Dialogue: 0,0:16:51.37,0:16:55.89,Default,,0000,0000,0000,,Finally, adjust your Team Render client\Npreferences as desired. If you'd like to
Dialogue: 0,0:16:55.89,0:17:00.47,Default,,0000,0000,0000,,set up a custom default security token,\Nyou can use a file within your C4D
Dialogue: 0,0:17:00.47,0:17:07.70,Default,,0000,0000,0000,,application path named\NC4D_net_securitytoken.txt. Now that we've
Dialogue: 0,0:17:07.70,0:17:11.64,Default,,0000,0000,0000,,gone over how to install and configure the\NTeam Render client, we'll look at how to
Dialogue: 0,0:17:11.64,0:17:14.37,Default,,0000,0000,0000,,add machines within the next tutorial.