Hi,

Trying to guess what you're doing. The execution of the 2000 renderings is
automated in some way but you're getting your data used to create the rendering
script in real time, one image after the other, waiting new data to render the
next image, thus don't know in advance the new parameters. Am I right ?

If that's the case, and if the rendering could be delayed, you could wait until
you acquired the whole data for the 2000 images and implement a solution as
we've suggested in previous posts to render images at the end of acquisition.
But may be you need to render the image as soon as its data are acquired and use
the rendered image to acquire the next data ?

Your video really sparks my curiosity. I'm also working on project using
Pov-ray, real world data and depth images. Would you mind telling us a little
more about what you're doing ? Looks like some kind of 3D reconstruction from
data acquired by a drone ?

I also understand that finding a solution, which I have no idea of, to the
finder problem may be more practical to your use case, but, as jr, I still
believe there may be a work around. The image you render looks simple, and given
the real time constraints (either during acquisition, rendering process or
rendered image post processing) you seem to have, maybe Pov-ray is simply not
the appropriate tool to your use case ?

Hoping to be helpful,
Pascal


Francois LE COAT <lec### [at] atariorg> wrote:
> Hi,
>
> jr writes:
> > Francois LE COAT wrote:
> >> ...
> >> The rendering of POV-Ray synthesis images are done in "real-time". It
> >> depends on past data, and future parameters are unknown. I have a
> >> POV-Ray script from which I substitute series of float numbers, that
> >> produces 2000 different scenes, one after the other.
> >>
> >> I can't launch POV-Ray one time, to produce 2000 images. I must launch
>
> >> it 2000 times, to render 2000 images. ...
> >> The question is how to configure POV-Ray with the command-line, so tha
> t
> >> it is quiet ? ...
> >
> > looking at the ini you posted earlier, am I correct in assuming that th
> e
> > generating "POV-Ray script" produces 2000 scene files named 'pacman_mod
> .pov'?
>
> Well, I have a model "pacman.pov" from which I generate "pacman_mod.pov"
> substituting the parameters at n step. Then I render this script,
> producing "pacman.png". And I move "pacman.png" to "pac%04d.png" with n.
>
> > also, since I cannot believe that you'd invoke a(ny) program 2000 times
>
> > manually, the script must somehow tell 2nd from 23rd run.  do you run t
> he whole
> > thing lot from within another script?  (o/wise how do you prevent overw
> riting
> > 'pacman.png'?)
>
> It results 2000 files, from "pac0001.png" to "pac2000.png" with 2000
> steps. I have launched POV-Ray 2000 times, knowing parameters from
> 1 to n steps. Each step n I have new parameters, but I don't know n+1.
>
> > are you free to modify said POV-Ray script?  then, for instance, you co
> uld
> > change it to generate an array and include that from your scene, using
> > frame_number as index; though there'd likely be other, more efficient w
> ays.  (I
> > also assume that the newly calculated data only depends on previous)
>
> I can't generate an array of parameters, because I know those partially.
> I'm drawing a trajectory, steps to steps, and I can't predict future.
>
> > anyway, I'm fairly certain that the "problem" can be addressed w/out re
> sorting
> > to compiling a new program.  :-)
>
> It's the simplest solution. If there's no command-line option to make
> POV-Ray quiet, I can build a macOS/Macports version, that will be quiet.
>
> Thanks for your help.
>
> Regards,
>
> --

> <http://eureka.atari.org/>

Post a reply to this message