I posted this in the other thread–but will move the discussion here.
I am wondering how TR will change things in my current studios setup.
We currently use NET for the c4d guys where I work and overall works well.
Although there are things I like about TR, there are a few things I’m wondering about.
Not sure I like how your workstation now becomes the render manager. Its a benefit in some situations, like when you aren’t doing production work on it (but good if you are leaving for the day).
Srek mentions that you can turn off the rendering aspect of TR on your workstation so its only being used to distribute and collect assets and rendered frames via P2P, but I guess until I see how much RAM or CPU resources TR is using in the background Im a little bit concerned. Hopefully any system slowdown would be negligible. Also wondering if restarting the workstation computer could interrupt the rendering process on the clients?
The other issue is that although its good for one guy who might need to push through a render, in a studio situation where people are working independently and launch renders when needed, it appears that there could be some conflicts. With NET, each guy simply starts their render and they move to the queue–same queue shared by and seen by everyone. With this new TR method, it looks like each person would launch their render from their own workstation, unaware of other possible renders. I’m not sure if TR has a central queue that the files would be sent to like in NET, or if the renders would attempt to use the same boxes on the network which another animator might be already using.
If this IS the case (and I could be totally off here), I would really prefer to keep the legacy NET render if possible, or have Maxon release Team Render as a manager app as well.
Hopefully I got this all wrong and we will not need to go with a 3rd party render manager.