Indigo Renderer Forum

Some collected suggestions for violet:


tungee:
Sliders should be in the right or left side of the gui ....
The width of the sliders should be smaller i think...
a field beside the slider to write directly your wish value

fused:
would be cool to have an "update" button and some checkbox to disable auto-updating

kosmokrator
something easy to implement....drag and drop .igi files into tonemapper gui...to open them

johanjohan
its possible to save adjustments in the future Violet?

joegiampaoli
Just one thing maybe, like when a feature is disabled, like bloom, and I want to tweak it, it still updates although it's not active, maybe disable autoupdating on inactive features untill we activate them... don't know if that's possible...

If that's the place for requests, then...

- unclamped numerical inputs for tone mapping.
- use of tabs for settings, so they display one at a time beside the output pane.
- a panning function, just by clicking and dragging the image.
- someone told about on-demand image update, I second that.
- zooming seems to force to recompute settings, is that requested ?

As usual, these are more suggestions than requests (but the first one), I'm still finding Violet very handy !

Ok... so here I go again:

- saving pictures as EXR using up to date 1.4.0 for B44 compression etc.
- saving depth information inside the igi file for a easy "set focus" by clicking on Picture,
and align camera settings for DOF effects as you like!
- finally a integration into Indigo (render window), so on the Fly changes for Indigo Parameters would be possible,
and focusing renderpower on parts of the Image using a "Lasso selection"

hehehe req req req...i think all this are enought....

I believe the "Depth" one you listed isn't possible with the way currently Indigo works. It could be faked easily enough, though - depthmap based blur.

zsouthboy wrote:I believe the "Depth" one you listed isn't possible with the way currently Indigo works. It could be faked easily enough, though - depthmap based blur.

it should be.... or how do you think Indigo calculates DOF at the moment for each pixel?

But I'm no Pro, so only Ono can tell us

At the moment I also do my DOF using a depthmap rendered from C4D
and using Photoshop.
But a build in solution would nice (and free )

it should be.... or how do you think Indigo calculates DOF at the moment for each pixel?

That would be faked dof. AFAIK indigo has real dof as it fakes a thin lens camera. I think that's it anyway!

IanC wrote:

it should be.... or how do you think Indigo calculates DOF at the moment for each pixel?

That would be faked dof. AFAIK indigo has real dof as it fakes a thin lens camera. I think that's it anyway!

Yep, that's what I was talking about. Indigo (and Radium, IIRC) have a real camera model - just as you can't change the DOF afterwards with a real camera (okay, if you have a plenoptic one, yeah), so it is.

but therefore its unbiased and looks very bombastic, a post dof have a lot of artifacts,because in the depth info you havent all information about verdeckte information.

DOF arises naturally in Indigo because the camera aperture has non-zero area. It's not done with a blur based on depth or anything like that.

Hi,

I would like to see a logarithmic scale on the pre-scale and post-scale sliders, so that the sliders have a range from -10 to 10, which is evaluated as

postScale = power(2, sliderValue)

This would give better control for small values (<< 1) which are difficult to set with the current implementation.

In photography it is common to work with logarithmic scales, for example the iso increases as 100, 200, 400 etc.

...512...

Yes, I have been using up to 512 for prescale and burn (nice for some designs).

+1 for the logarithmic stuff

Another useful extension would be "sample white point", which is common in converters for camera raw formats. By clicking in a region which is white(-ish) in the image the white point is set from the chroma values at this point, which makes it white in the final image. I think it is possible to just use the raw chroma data as the white point.

just check "Adobe light room" for everything we wan't to see inside this GUI

And an automatic white balance, based on the colour of the brightest light source (or if possible, on the influene of it, as far away lightsources may not make that much difference, althugh they are stonger than closer ones...
Something like, how strong light is at the focus point )