Indigo 2.4 - Don't Make Me Think

[benn]

Cool - thanks for the mockup. Copying.

[benn]

Im adding a todo to this list:

use eventFilter to ignore mousewheel events so that you can scroll up and down in the inspector without randomly changing values.

[Godzilla]

Im adding a todo to this list:

use eventFilter to ignore mousewheel events so that you can scroll up and down in the inspector without randomly changing values.

Another Idea:

Perhaps you could experiment with the input fields and make it so that changes are not applied until you
either:

1.Press the enter key
2.Click out of the input field

An example of the current annoyance:

You are adjusting the ISO of an image, and you want to adjust it from the default 100 to something like 150. In the process of typing 1-5-0, if you pause for whatever reason it will apply the change, even though you are not finished editing the value, so it will change to either 1 or 15, instead of the desired 150.

[neo0.]

If it's not too late, I would like to chip in a small suggestion.. The ability to increase values in fields by clicking and dragging up or down.. It would "pressure sensetive", so the further you drag, the faster the values would change. Maybe even let the user use both left and right and up or down (right increases value, while left decreases it.)

Godzilla : Having to press enter every time might get tedious. What I would prefer would be to just add in a little delay of perhaps a second or half a second before indigo applies your changes. This would take some fine tuning, granted, but I think it would work really well.

use eventFilter to ignore mousewheel events so that you can scroll up and down in the inspector without randomly changing values.

So you can scroll the right panel using the mouse wheel? Sweet!



How about drop lists.. How are they gonna look w/ the new theme?

[Godzilla]

If it's not too late, I would like to chip in a small suggestion.. The ability to increase values in fields by clicking and dragging up or down.. It would "pressure sensetive", so the further you drag, the faster the values would change. Maybe even let the user use both left and right and up or down (right increases value, while left decreases it.)

A feature like this would be nice (Fryrender already has it, go to 0:16), but first Indigo would need to be able to update the image tonemapping settings in real-time, which is not yet possible AFAIK.

Godzilla : Having to press enter every time might get tedious. What I would prefer would be to just add in a little delay of perhaps a second or half a second before indigo applies your changes. This would take some fine tuning, granted, but I think it would work really well.

Yes, that's what I suspect will be the case, but it wouldn't hurt to experiment with it for a bit to see if it is comfortable or not.

[neo0.]

The other option is that it can just wait till you release your mouse button and make the changes like you would in any other way....

EDIT : how could I forget this.. Since light layers are basically limited to values of 20.. why not also have a visual slider for each of them?

How about sliders for tone mapping just like maxwell?

[galinette]

Another suggestion : zooming of the preview image was a great added feature, but it would be much nicer with smooth resize (now it seems to be using nearest neighbor). Bilinear or bicubic would be very fine, and mipmap filtering would be excellent (Useful for resizing down a very large 1920x1080 noisy image to preview it on a small laptop used as pure network master, which is exaclty what I'm doing. Resizing down a noisy image without mipmap filtering is ugly as noise is amplified)

This should be pretty simple if you're developping under Qt, as you may paint with openGL.

Etienne

[galinette]

Another idea : the possibility to launch render of a small area of the picture only.

I know you can do it with the exporter, using a lens shift, and so on (I'm actually doing this) but it would be much more simple to preview a small region, and then start the full render, in the indigo UI.

Etienne

[galinette]

And, last for this morning, I suggested it already in another post, the possibility to query an idle network slave from the master, using an IP and optionnal port, would make the network render perfect.

The auto-connect does work only if you are on the same subnet (I suppose you are using TCP broadcast), which is not my case as I'm in a large company building with several subnets. For now, I must open a remote desktop or terminal on each slave to start it in command line with my master IP address. If another user wants to do the same from another master, he has to restart each slave with his IP address. That's not very convenient.

By the way, congratulations for the auto upload feature of the network render. It makes the job very easy, you do not have to maintain shared network folder with all the scene data. This may be easy for the home user, but complicated in large companies where you need to ask many people for opening a shared folder with all the permissions to access it from both the master and the rendering nodes, which are not on the same domain for security reasons bla bla bla...

[PureSpider]

Another idea : the possibility to launch render of a small area of the picture only.

I know you can do it with the exporter, using a lens shift, and so on (I'm actually doing this) but it would be much more simple to preview a small region, and then start the full render, in the indigo UI.

Etienne

Or to expand that concept, implement the often requested interactive region rendering like:
Render a picture to 1000spp and still got noisy areas?
Just draw a region around them to focus rendering power there.

[galinette]

Still another suggestion, about the win32/<in64 installer : make the start menu links available to all users, not only the admin account it's installed under.

Etienne

[Zom-B]

Another idea : the possibility to launch render of a small area of the picture only.

I know you can do it with the exporter, using a lens shift, and so on (I'm actually doing this) but it would be much more simple to preview a small region, and then start the full render, in the indigo UI.

Indigo supports Region Rendering, so you choose a part of the image from the actual cam, and then when rendering Indigo only focus in this part, keeping all around this area alpha.

Check your Exporter for such a feature

[benn]

I've been working on rendering region directly in the UI, I've got the selection area working, I just need Nick and Lyc to work out the Indigo core stuff.

[pixie]

Say I have 1.00 as a value, if i want to make it 1.10 I have to either delete the 0 and substitute it for 1 or delete all and write 1.1, another thing is that when using keypad the period key doesn't work as it is expecting only a a virgule where on keypad it's a period.

[galinette]

This is a classical Qt bug (not really a bug, but an annoying thing)

In fact Qt uses the regional settings of windows to format and parse the number you put in the QDoubleSpinBox. That means, if you have a comma separated locale (such as in France) it displays numbers with a comma, and expects numbers with a comma.

But in these countries, the keyboard layouts keep a dot on the numpad, not a comma. That means you cannot use the numpad to enter decimals in a QDoubleSpinBox.

The solution to this is to add an eventFilter on the QDoubleSpinBox translating dot to the locale's decimal separator character, that is given by QLocale::decimalPoint ()

As a french user, I always customize my computer's locale to the decimal dot, as commas tends to mess around the anglo-saxon software behavior.

Etienne