clipka <ano### [at] anonymousorg> wrote:
> Am 22.11.2013 12:59, schrieb Bill Pragnell:
> > The mirror ball is smiling in the first image :)
>
> He's ROTFL :)

RSROTCPL?

Post a reply to this message

Am 22.11.2013 15:58, schrieb Bill Pragnell:
> clipka <ano### [at] anonymousorg> wrote:
>> Am 22.11.2013 12:59, schrieb Bill Pragnell:
>>> The mirror ball is smiling in the first image :)
>>
>> He's ROTFL :)
>
> RSROTCPL?

Almost - except that the P isn't really C but rather S.

Post a reply to this message

Bill Pragnell wrote:

> The mirror ball is smiling in the first image :)

And sickly non-smiling in the second, but luckily that is blurred ;)

Looking great!

Post a reply to this message

clipka <ano### [at] anonymousorg> wrote:
> Hi folks,
>
> can you guess the next major feature for UberPOV?
>
> First image rendered in 8m 33s.
> Second image rendered in 22m 28s.
>
> Still a bit of detail work for interoperation with radiosity and SSLT,
> but I guess I'll do a pre-release tomorrow to see you toy around with it.

Thank you !! This is great! And you really have a good sense of priority to spot
the most wanted features for pov and add them. would it do deformation motion
blur e.g. from a pov sphere animated non uniform scale, or if a mesh2 object's
points moved? will this uberpov branch merge some of its patches quicker into
pov trunk than megapov or will it keep diverging for long?

Post a reply to this message

clipka <ano### [at] anonymousorg> wrote:
> Hi folks,
>
> can you guess the next major feature for UberPOV?
>
> First image rendered in 8m 33s.
> Second image rendered in 22m 28s.
>
> Still a bit of detail work for interoperation with radiosity and SSLT,
> but I guess I'll do a pre-release tomorrow to see you toy around with it.

Thanks for your effort on this, the motion blur and the other Uber features are
great additions, I just need to find some time to play around with them now.

Sean

Post a reply to this message

Am 28.11.2013 19:15, schrieb Mr:

> Thank you !! This is great! And you really have a good sense of priority to spot
> the most wanted features for pov and add them.

I think it's more kind of "spot the features /I/ want most for pov..." 
;-) But I'm glad they happen to be wanted among the community, too.

> would it do deformation motion
> blur e.g. from a pov sphere animated non uniform scale, or if a mesh2 object's
> points moved?

What's currently in there is pretty basic in /how/ it does motion blur - 
which, thankfully, makes it ultimately flexible in /what/ it can do.

In essence, whatever you could imagine to do by rendering an animation 
and then averaging all images, you can do with this feature in just a 
single render pass.

The idea behind it is simple: Think of the render as a photograph with a 
certain non-zero exposure time. Now if you have any moving object in the 
scene, you create N copies of it with slightly different positions, 
orientations, shapes, textures or whatever you can imagine, and assign 
each copy an individual time interval within the exposure time.

UberPOV will then fire rays into the scene that are not only 
characterized by their trajectory in space, but also by a point in time; 
objects that do not match this particular time are ignored for this 
particular ray and all secondary rays (shadow rays, reflection rays etc) 
it spawns.


In the future, this approach will be complemented by features catering 
to more specific use cases, such as an object moving along a linear 
trajectory or rotating about a fixed axis. Those will then be both 
easier to set up (probably just specifying a translation or rotation) 
and also less memory-consuming (only one instance of the object will be 
needed).


> will this uberpov branch merge some of its patches quicker into
> pov trunk than megapov or will it keep diverging for long?

That's difficult to tell.

On one hand, from what I see UberPOV is in a similar situation as 
MegaPOV was: Aside from being a collection of patches, it was also 
intended to be a testbed for new features, and AFAIU it was also 
maintained by people closely affiliated with the POV-Ray dev team, so 
there's no reason there to assume that UberPOV should fare any better: 
At the end of the day it all boils down to whether the POV-Ray dev team 
as a whole decides to integrate a given feature into POV-Ray proper.

One thing that is a big obstacle for UberPOV's main features is that 
they are all based on stochastic stuff, i.e. random in nature, which 
does not go well with animations because it can create flickering (at 
least that's the lore - I'm already pondering a way around that); 
traditionally, POV-Ray has always been reluctant to incorporate such 
features.

On the other hand there have been changes in the dev team recently, 
which might affect the future course of POV-Ray; if so, I would expect a 
less dogmatic and more pragmatic approach to new features. But only time 
will tell.

Post a reply to this message

Just a rapid test of the blink patch, with James Holsenback's beautiful 
metallic texture.

Only ten instances of the ovus used here so the result is crude but it 
shows me the way to go :-)

Thomas

Post a reply to this message

Attachments:
Download 'stochastic_blink.png' (458 KB)

Preview of image 'stochastic_blink.png'

Am 29.11.2013 10:05, schrieb Thomas de Groot:
> Just a rapid test of the blink patch, with James Holsenback's beautiful
> metallic texture.

BTW, I'm still looking for a smarter name for that keyword. Anyone have 
any suggestions?

Post a reply to this message

Le 29/11/2013 12:19, clipka a écrit :
> Am 29.11.2013 10:05, schrieb Thomas de Groot:
>> Just a rapid test of the blink patch, with James Holsenback's beautiful
>> metallic texture.
> 
> BTW, I'm still looking for a smarter name for that keyword. Anyone have
> any suggestions?
> 

only a few suggestion & hints via questions:
 1. what is the syntax ? Is it something like

...
  foobar { object MyObject repetition 20 movement ...

? Or something totally different (like photon adding blocks everywhere ) ?

 2. what is the intended effect ?
 3. how is it achieved ? and would that be the only forever way to
achieve it ?

 4. remember that short but significant name are best.
 5. Is there something similar already in another domain.

Your candidat is "blink", but we are rendering static image (no animated
gif output!), and blink reminds me of a tragic extension of Internet
Explorer.

The effect on first post of thread make me think of the after-effect
that was used in the "Flash" serie (post 90's)
so I could suggest:

 * flash_effect (not my favortie at all)
 * drag / pull / dragging / moving
 * shutter_drag
 * blurry / blur
 * moving_supersampled
 * motion_trails
 * motion_blurred
 * trails
 * motion
 * shutter_control
 * shutter
 * slow_shutter
 * slow
 * extended_exposure

And of course, use a synonym website to find correlated name/verb until
you have the perfect match.

The term in photography is shutter drag, or dragging the shutter, but
it's just a bit too long for my taste. (and there is the option to add a
flash point (or many) for a more solid capture of the subject along its
course).

What do you think of "blurry" ?

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

Post a reply to this message

On 29-11-2013 13:09, Le_Forgeron wrote:

> What do you think of "blurry" ?
>

motion blur is the closed definition I believe. so maybe: "moblur"?

Thomas

Post a reply to this message