Page 1 of 1

Color Balance and Remap display a bigger output

Posted: March 31st, 2018, 1:29 pm
by davidh
1. Start the PWP8 - latest update
2. Open an image
3. Run Color Balance or Remap, do something and click OK
-> the output displays a bit larger then input. The dimensions shown are unchanged.
3. Swith to input thumbnail and click on the Zoom to Fit button in the image area
-> the input also displays larger, now input and output match

From now on during the session the image displays at this larger size even if closed and reopened.

It happens only at the beginning of a session.

Re: Color Balance and Remap display a bigger output

Posted: March 31st, 2018, 1:44 pm
by jsachs
This is a generic problem will all the transformations -- I need to experiment a little, but I think I should just do a fit to screen every time the bypass button is clicked. Currently, if the image will fit on the screen at 1:1, it is displayed at 1:1 initially, while output images are automatically expanded to fit the screen. Thus when you switch back and forth the size changes until you make the input image fit the screen as well.

Re: Color Balance and Remap display a bigger output

Posted: April 1st, 2018, 10:08 am
by davidh
According to my observations that does not happen with all transformations equally.

There are, in fact, three different inputs-outputs display sizes.

Here is what I have found so far:

Group A
With some transformations if you just open them, leave them at their defaults and click OK the output takes over the original input diameters and shrinks the input. The input edns up even smaller then it was when loaded. For example Color Balance, Remap, Brightness Curve, Selective Correction.

Group B
With some others, such as Autorange, Color curves, Rotate - Mirror, Saturation, Remove Purple Fringe, etc. there is no change in size if the are left at their defaults: Output size = input size.

Group C
With some of the transformations from the the group A when some change is done to the image, the output image results larger than was the original input size. E.g. Color Balance, Remap

Example:

1. open image - size 1
2. open Color Balance, leave at defaults, click OK - output = size 1, input shrinks - size 2
3. reopen Color Balance, do something, click OK, - output gets larger - size 3, output from step 2 = size 2 and input = size 2

The initial size 1 is no longer displayed with any of the images.

What is interesting is that Brightness curve belongs to the group A, while Autorange and Color curves belong to the Group B even though they all seem to be similar. Could it be a clue?

One last remark:
When I switched between Before and After I never used Bypass buttons but I always clicked on the thumbnails. It very probably makes no difference. Still...

Re: Color Balance and Remap display a bigger output

Posted: April 1st, 2018, 11:17 am
by jsachs
There are two classes of tools/transformations - those that always preserve the size of the image and those that do not. Examples of size-preserving transformations are color balance, sharpen, brightness curve, composite, etc. -- size changing transformations include crop, add border, warp, level, resize, etc. Synchronized scrolling is only available as an option for transformations/tools that preserve image size.

I realize it is all over the map currently, but my plan to clean this up is to implement the following: switching bypass on and off for size-preserving transformations preserves the zoom and scroll settings from the current view when switching if synchronized scrolling is enabled. If synchronized scrolling is disabled, when an auxiliary input is selected, and for those transformations that do not preserve the image size, zoom and scroll are independent between the two views and have to be manually adjusted. This also means the synchronized scrolling button must remain visible even if split screen is turned off.

Re: Color Balance and Remap display a bigger output

Posted: April 2nd, 2018, 7:44 am
by davidh
Thanks for the explanation, Jonathan. I have posted it just as an observation that might make some users (like me) think why the preview zooms by itself.