Render Farms

Mailing List

Home

Forum Home

Softimage

Carrara

trueSpace

Dir3d-l

Maya - a powerful 3D animation and visual effects software

Macromedia Flash Development

Subjects

•	Cameras
•	scaleDown command
•	black out solved
•	Aircraft Tutorial
•	Mathematical XYZ ?
•	Its done This vs That
•	Its done first week
•	recommendations for screen video captures?
•	3DExplorer "Oddity "
•	New Director
•	ProTeam renewals
•	Fuel 's new websites (X post)
•	Blue peter create a make toy
•	targeting groups question
•	XPost: Shockwave 3D game ( sort of )
•	RES: RES: RES: Fish Modeling
•	Emitting particles from object intersection
•	Fuel 's new websites (X post)
•	Texturing
•	Big Break Contest Videos
•	New Plugins
•	Models and Texture on my updated site
•	Error Installing Patch tS6 6
•	Plasma?
•	Looking for Inspiration
•	Weird EMail Q
•	It 's done first week ?
•	Cherry not cranberry
•	New game
•	Camera Animation Problem
•	Particle plugins?

Render Farms

Render Farms

2005-04-08 - By Sean Dunn

Back

Reply: << 11 12 13 14 15 16

I dislike Perl as well, but something that may not be so obvious is that
you really can use any language you want with it. All communication with
the running frame is through environment variables, command line
arguments, and text files. By customizing it, it may be harder for
support (Greg) to diagnose your problem, but Rush's openness is probably
the reason why I like it the most.

Sean

__ __

From: Raffaele "ThE_JacO" Fragapane [mailto:jaco@(protected)]
Sent: Friday, April 08, 2005 7:49 AM
To: XSI@(protected)
Subject: RE: Render Farms

We use rush here for XSI, Maya and shake, while HDN sort of lives in its
own space.

Rendering and basic asset management of several aspects is what we use
it for.

Considering I've been involved in several entry points in the pipeline
(had to learn to read bloody perl for the thing, and that wasn't funny
at all) for the XSI side of things, and considering the amount of work
that goes into something like rush, I wouldn't advice about it for
anything less then 32 units, and even then it could probably be overkill
unless you already have dedicated IT staff that can dub on
rendermanagment and/or wrangling.

Also if you want to use rush you have to start taking into account that
it will pay for the investment only in a linux environment, with tight
administration and a very, very solid knowledge of perl from at least
one of the IT staff members.

As an upside it needs to be mentioned that the support you get for rush
is second to none, it goes hand in hand with the quality of support we
learnt to expect from Soft.

We were able to get it up and going for XSIbatch for both rendering and
processing, standalone MRays, Maya's MRay and shake's rendernodes (be
wary you have to pay a hefty sum for every shakenogui that doesn't run
on a mac btw if you plan on farming shake renders), all this on both
farm and local boxes when they don't have anybody logged in (like at
night).

~Raffaele Fragapane
~Lead "I'm sure we can make it work"
~Peerless Camera Company

__ __

From: owner-xsi@(protected) [mailto:owner-xsi@(protected)] On Behalf
Of Stefan Andersson
Sent: Friday, April 08, 2005 2:59 PM
To: XSI@(protected)
Subject: Re: Render Farms

another thing about BatchServ... will it ever get updated? and when will
it be linux compatible?

RoyalRender seems to be nice as a rendering dispatcher. Rush also seems
very nice, although it require some serious setup and management. But
Rush is probably the best investment if you are going to have more than
20 computers in the farm.

regards
stefan andersson

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.859 / Virus Database: 585 - Release Date: 14-Feb-05 (See http://Feb-05.ora-code.com)

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft
-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1=
"urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC
-html40">

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PersonName"/>

<style>

</style>

</head>

<body lang=EN-US link=blue vlink=blue>

<div class=Section1>

I dislike Perl as well, but something that
may not be so obvious is that you really can use any language you want with it.
All communication with the running frame is through environment variables,
command
line arguments, and text files. By customizing it, it may be harder for support
(Greg) to diagnose your problem, but Rush’s openness is probably the
reason why
I like it the most.<o:p></o:p>

<o:p> </o:p>

Sean<o:p></o:p>

<o:p> </o:p>

<div>

<div class=MsoNormal align=center style='text-align:center'>

<hr size=2 width="100%" align=center tabindex=-1>

</div>

From: Raffaele
"ThE_JacO" Fragapane [mailto:jaco@(protected)] 
Sent: Friday, April 08, 2005 7:49
AM 
To: <st1:PersonName w:st="on">XSI
@(protected)</st1:PersonName> 
Subject: RE: Render Farms<o:p></o:p>

</div>

<o:p> </o:p>

We use rush here for XSI, Maya and shake,
while HDN sort of lives in its own space.<o:p></o:p>

Rendering and basic asset management of
several aspects is what we use it for.<o:p></o:p>

<o:p> </o:p>

Considering I’ve been involved in
several
entry points in the pipeline (had to learn to read bloody perl for the thing,
and that wasn’t funny at all) for the XSI side of things, and considering
the
amount of work that goes into something like rush, I wouldn’t advice
about it
for anything less then 32 units, and even then it could probably be overkill
unless you already have dedicated IT staff that can dub on rendermanagment
and/or wrangling.<o:p></o:p>

<o:p> </o:p>

Also if you want to use rush you have to
start taking into account that it will pay for the investment only in a linux
environment, with tight administration and a very, very solid knowledge of perl
from at least one of the IT staff members.<o:p></o:p>

<o:p> </o:p>

As an upside it needs to be mentioned that
the support you get for rush is second to none, it goes hand in hand with the
quality of support we learnt to expect from Soft.<o:p></o:p>

<o:p> </o:p>

We were able to get it up and going for
XSIbatch for both rendering and processing, standalone MRays, Maya’s MRay
and
shake’s rendernodes (be wary you have to pay a hefty sum for every
shakenogui
that doesn’t run on a mac btw if you plan on farming shake renders), all
this
on both farm and local boxes when they don’t have anybody logged in (like
at
night).<o:p></o:p>

<o:p> </o:p>

<div>


~Raffaele Fragapane 
~Lead "I'm sure we can make it work" 
~Peerless Camera Company<o:p></o:p>

</div>

<div>

<div style='margin-left:.5in'>

<div class=MsoNormal align=center style='text-align:center'>

<hr size=2 width="100%" align=center tabindex=-1>

</div>

</div>

From:
owner-xsi@(protected) [mailto:owner-xsi@(protected)] On Behalf Of Stefan Andersson 
Sent: Friday, April 08, 2005 2:59
PM 
To: <st1:PersonName w:st="on">XSI
@(protected)</st1:PersonName> 
Subject: Re: Render Farms<o:p></o:p>

</div>

<o:p> </o:p>

another thing about BatchServ... will it ever get
updated? and when will it be linux compatible? 
 
RoyalRender seems to be nice as a rendering dispatcher. Rush also seems very
nice, although it require some serious setup and management. But Rush is
probably the best investment if you are going to have more than 20 computers in
the farm. 
 
regards 
stefan andersson<o:p></o:p>

<o:p> </o:p>

</div>

</body>

</html>
 

--- 
Outgoing mail is certified Virus Free. 
Checked by AVG anti-virus system (http://www.grisoft.com). 
Version: 6.0.859 / Virus Database: 585 - Release Date: 14-Feb-05 (See http://Feb-05.ora-code.com)