Am 08.02.2015 um 20:26 schrieb Mike Horvath:
> Is there a easy way to stop rendering based on a condition, sort of like
> a break statement in a loop? I know I can wrap my entire scene in a
> condition, but I am hoping there is something simpler. Thanks.

POV-Ray is quite a fascinating thing: It provides ways to do plenty 
different things, sometimes in more than one fashion.

Therefore, rather than ask about a very specific mechanism, it is often 
a more promising approach to ask about the goal you ultimately want to 
achieve; the mechanism you have in mind for it might be unavailable, but 
there might be other ways around it.

Post a reply to this message

On 2/8/2015 3:20 PM, clipka wrote:
> Am 08.02.2015 um 20:26 schrieb Mike Horvath:
>> Is there a easy way to stop rendering based on a condition, sort of like
>> a break statement in a loop? I know I can wrap my entire scene in a
>> condition, but I am hoping there is something simpler. Thanks.
>
> POV-Ray is quite a fascinating thing: It provides ways to do plenty
> different things, sometimes in more than one fashion.
>
> Therefore, rather than ask about a very specific mechanism, it is often
> a more promising approach to ask about the goal you ultimately want to
> achieve; the mechanism you have in mind for it might be unavailable, but
> there might be other ways around it.
>

One thing I want to do is stop parsing when frame_number equals some 
number. I've created an animation with duplicates that I don't need. But 
I can think of other instances where this could be handy.

Post a reply to this message

Le 08/02/2015 21:32, Mike Horvath a écrit :
> On 2/8/2015 3:20 PM, clipka wrote:
>> Am 08.02.2015 um 20:26 schrieb Mike Horvath:
>>> Is there a easy way to stop rendering based on a condition, sort of like
>>> a break statement in a loop? I know I can wrap my entire scene in a
>>> condition, but I am hoping there is something simpler. Thanks.
>>
>> POV-Ray is quite a fascinating thing: It provides ways to do plenty
>> different things, sometimes in more than one fashion.
>>
>> Therefore, rather than ask about a very specific mechanism, it is often
>> a more promising approach to ask about the goal you ultimately want to
>> achieve; the mechanism you have in mind for it might be unavailable, but
>> there might be other ways around it.
>>
> 
> One thing I want to do is stop parsing when frame_number equals some
> number. I've created an animation with duplicates that I don't need. But
> I can think of other instances where this could be handy.

You just want the +EF option ( end-frame, followed by the number of the
frame after which to stop the rendering of the range.)

Look also at SF (start frame) to start after the first one.

Post a reply to this message

On 2/8/2015 4:18 PM, Le_Forgeron wrote:
> Le 08/02/2015 21:32, Mike Horvath a écrit :
>> On 2/8/2015 3:20 PM, clipka wrote:
>>> Am 08.02.2015 um 20:26 schrieb Mike Horvath:
>>>> Is there a easy way to stop rendering based on a condition, sort of like
>>>> a break statement in a loop? I know I can wrap my entire scene in a
>>>> condition, but I am hoping there is something simpler. Thanks.
>>>
>>> POV-Ray is quite a fascinating thing: It provides ways to do plenty
>>> different things, sometimes in more than one fashion.
>>>
>>> Therefore, rather than ask about a very specific mechanism, it is often
>>> a more promising approach to ask about the goal you ultimately want to
>>> achieve; the mechanism you have in mind for it might be unavailable, but
>>> there might be other ways around it.
>>>
>>
>> One thing I want to do is stop parsing when frame_number equals some
>> number. I've created an animation with duplicates that I don't need. But
>> I can think of other instances where this could be handy.
>
> You just want the +EF option ( end-frame, followed by the number of the
> frame after which to stop the rendering of the range.)
>
> Look also at SF (start frame) to start after the first one.
>


No. For example I may want frames 1-3 and 5-6 parsed and rendered, but 
not frame 4. Your suggestion doesn't work in this case.

Post a reply to this message

Am 09.02.2015 um 01:31 schrieb Mike Horvath:

>>> One thing I want to do is stop parsing when frame_number equals some
>>> number. I've created an animation with duplicates that I don't need. But
>>> I can think of other instances where this could be handy.
>>
>> You just want the +EF option ( end-frame, followed by the number of the
>> frame after which to stop the rendering of the range.)
>>
>> Look also at SF (start frame) to start after the first one.
>
> No. For example I may want frames 1-3 and 5-6 parsed and rendered, but
> not frame 4. Your suggestion doesn't work in this case.

So what you're after is not really stopping a render, but skipping 
individual frames in it.

No, at the moment I can't think of any mechanism by which POV-Ray might 
support this (other than rendering only subsets of the animation in the 
first place). The "#error" directive came to my mind, but it does not 
only abort parsing of the current frame, but also the entire render job.

Post a reply to this message

> No. For example I may want frames 1-3 and 5-6 parsed and rendered, but
> not frame 4. Your suggestion doesn't work in this case.

Do you not want frame 4 rendered to save time, or because you physically 
don't want the file to be created?

If you want to save time, but don't mind the file being there, then just 
let it render an empty scene with no objects for the frames you don't 
want, it will only add a fraction of a second.

It should be easy if you could render another .pov file, and put 
something like this in it:

#if(frame_number<>4) // or whatever condition
  #include "mainPOVscene.pov"
#end

Post a reply to this message

Le 09/02/2015 01:31, Mike Horvath a écrit :
>
> No. For example I may want frames 1-3 and 5-6 parsed and rendered, but
> not frame 4. Your suggestion doesn't work in this case.

If frame 4 has already a output file, I wonder if the -C (or is it +C ? 
I know they are opposite of each other, but cannot remember which one 
would try to look if the output image already exist and is complete) 
option would not skip the render of it when detecting that it is already 
complete ?


-- 
Just because nobody complains does not mean all parachutes are perfect.

Post a reply to this message

On 2/9/2015 3:23 AM, Le_Forgeron wrote:
> Le 09/02/2015 01:31, Mike Horvath a écrit :
>>
>> No. For example I may want frames 1-3 and 5-6 parsed and rendered, but
>> not frame 4. Your suggestion doesn't work in this case.
>
> If frame 4 has already a output file, I wonder if the -C (or is it +C ?
> I know they are opposite of each other, but cannot remember which one
> would try to look if the output image already exist and is complete)
> option would not skip the render of it when detecting that it is already
> complete ?
>
>

If frame 4 exists most likely the others will as well. I tend to 
accumulate renders and not delete them for years at a time.

Post a reply to this message

On 2/9/2015 3:14 AM, scott wrote:
>> No. For example I may want frames 1-3 and 5-6 parsed and rendered, but
>> not frame 4. Your suggestion doesn't work in this case.
>
> Do you not want frame 4 rendered to save time, or because you physically
> don't want the file to be created?
>
> If you want to save time, but don't mind the file being there, then just
> let it render an empty scene with no objects for the frames you don't
> want, it will only add a fraction of a second.
>
> It should be easy if you could render another .pov file, and put
> something like this in it:
>
> #if(frame_number<>4) // or whatever condition
>   #include "mainPOVscene.pov"
> #end
>


I'm sure there's a workaround for every example I can come up with. A 
break statement would just be a lot simpler and easier.

Post a reply to this message

Am 09.02.2015 um 21:02 schrieb Mike Horvath:

> I'm sure there's a workaround for every example I can come up with. A
> break statement would just be a lot simpler and easier.

 From the user's point of view - yes, probably.

 From the developer's point of view - not so much. The current, grown 
architecture doesn't lend itself to just skipping the parsing of a 
frame, as all the set-up (most notably the deletion of an existing file 
with the same name as the output file!) is done before invoking the 
parser module.

Post a reply to this message