<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
A view file is supposed to represent one (1) view. The last line of the
view file is considered to be the view spec. Considering a view file
to be a collection of multiple views is counter productive.<br>
<br>
It seems to me that there are a few ways to do what you want:<br>
<ol>
<li>create multiple rif files with each one representing a "view
group" and containing multiple "view=" lines, note this is really one
of the things that rif file is for, that is to create coherent
groupings of views with respect to a set of geometry/materials/lighting
as defined in an octree....<br>
</li>
<li>enhance your script to include a separate "view group" file, the
script can parse the view group file and pass the relevant views to the
rif file, in essence building a rif file on the fly....</li>
<li>ranimate, as Thomas suggests, you could probably do something
with the ANIMATE parameter for ranimate pointing to a script to produce
the correctly modified octree and use a VIEWFILE with all your views in
it.<br>
</li>
</ol>
-Jack<br>
<br>
Thomas Bleicher wrote:
<blockquote
cite="mid:89355c0f0907220502m19f12a2p3ed66f8b867980f6@mail.gmail.com"
type="cite">
<pre wrap="">Have you considered using ranimate here?
Thomas
On Wed, Jul 22, 2009 at 9:05 AM, Lars O. Grobe<a class="moz-txt-link-rfc2396E" href="mailto:lars.grobe@nus.edu.sg"><lars.grobe@nus.edu.sg></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
I am not sure whether this would break anything, but it would be a rather
useful way of organizing renderings:
At the moment, I can pass a view name to rad using the -v parameter, and
this will cause exactly one view to be rendered, which must have been named
in the view= line in the rif file.
Now, this view= line can point to a view file, which may contain more then
one view. I would have expected rad to render all the views in that file,
but as -v is defined to render exactly one view, rad takes only one of the
views defined in the view file and ignores the others.
I would propose to change this behaviour. If I call rad e.g. as
rad -v myview myoctree.oct
it would be very useful if rad would look whether it finds a view= line for
myview. If it finds one defining one view, render that. If it finds one
pointing to a view file, render all the views in that view file. If I call
rad as
rad -v anotherview -v myview myoctree.oct
it should render all views defined in the view= lines for anotherview and
myview, be it view files or view definitions inside the rif.
One reason this would be helpful is as such: I am currently working on a
scene, which needs some view-dependent processing. So I have a script which
does some work, cleans up, creates an octree, creates photon maps, and then
calls rad. Now I would like to call the same rif-file for all of these, as
it eventually contains the same information for all renderings except the
views. And I cannot render all views at once, as I have to modify the octree
before moving to the next "view group" (this translates to rooms in my
example).
I am sure that there are other uses for this. What do you think? Is there
any way people may have used the -v parameter that could imply the risk of
breaking compatibility by introducing such a change?
Cheers Lars.
--
Lars O. Grobe (Mr) :: Research Fellow, Solar Energy Research Institute of
Singapore SERIS :: National University of Singapore :: 7 Engineering Drive
1, Block #E3A-06-35, Singapore 117576 :: 65-6516 5816(Tel) :: 65-6775 1943
(Fax) :: <a class="moz-txt-link-abbreviated" href="mailto:serlog@nus.edu.sg">serlog@nus.edu.sg</a> (E) :: <a class="moz-txt-link-abbreviated" href="http://www.seris.sg">www.seris.sg</a> (W) :: Company Registration
No: 200604346E
Important: This email is confidential and may be privileged. If you are not
the intended recipient, please delete it and notify us immediately; you
should not copy or use it for any purpose, nor disclose its contents to any
other person. Thank you.
_______________________________________________
Radiance-general mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Radiance-general@radiance-online.org">Radiance-general@radiance-online.org</a>
<a class="moz-txt-link-freetext" href="http://www.radiance-online.org/mailman/listinfo/radiance-general">http://www.radiance-online.org/mailman/listinfo/radiance-general</a>
</pre>
</blockquote>
<pre wrap=""><!---->
_______________________________________________
Radiance-general mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Radiance-general@radiance-online.org">Radiance-general@radiance-online.org</a>
<a class="moz-txt-link-freetext" href="http://www.radiance-online.org/mailman/listinfo/radiance-general">http://www.radiance-online.org/mailman/listinfo/radiance-general</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
# Jack de Valpine
# president
#
# visarc incorporated
# <a class="moz-txt-link-freetext" href="http://www.visarc.com">http://www.visarc.com</a>
#
# channeling technology for superior design and construction
</pre>
</body>
</html>