LRTimelapse Forum

Hi,

I am using the latest version 1.9.4.

I have various key frames and I am animating the graduation filter.

I have done so many test and now left out any animation with the graduation until key frame 4. So now between the first key frame and the second the saturation value is changing even though its been set to the same, 100%.

I notice this sometimes at file no.2 where the saturation of 100% has applied to file 1 but the immediately at file 2 the saturation looks like its gone back to 0 (This is by looking at it not referring to the table as the values all say 1.000). This is present all the way through the files until the 2nd key frame where it goes back to 100% again.

Key frame no.1 reads: 1st Grad Loc Sat : 1.000

When i hover the mouse over this value the pop up reads 1.00000000

then 200 files later at key frame no.2 the values read the same: 1.000 (1.00000000 when hovered over)

All the files between these 2 all read 1.000 as they should but when hovering over each one they have different values for example:

file 2 = 1.00000453
file 3 = 1.00000882
file 4 = 1.00001311

This increases up until the value of 1.00045824 at a file that is not a keyframe (somewhere halfway between 1st and 2nd key frames) and then starts to decrease again until it gets to the 2nd key frame where it goes back to 1.00000000

I have also noticed that the are 2 columns for 1st Grad Loc Sat. Is this where there is a conflict?

------------------

Also I have noticed other columns in the table doing strange things similar to this where the value should stay the same as it's not changed from one key frame to the next.

For example in this column: 1st Grad Loc Hue

1st key frame 40933.RW2 and value is set at 359.000
2nd key frame 50200.RW2 and value is set at 359.000

but inbetween, the values change as follows:

40933.RW2 359.000
40934.RW2 359.052
40935.RW2 359.102
40936.RW2 359.150

and so on until 40955.RW2 gets to 360.000

This then stays at 360.000 until 50197.RW2 where it then decreases back down as follows:

50197.RW2 359.827
50198.RW2 359.577
50199.RW2 359.294
50200.RW2 359.000

Any ideas?

Hi, thank you for you in depth reporting.
I didn't have the time yet to thoroughly look into this issue but I have an Idea.

The thing ist that the auto transition calculates curves between the keyframes. If you have a constellation where two keyframes have the same value and the third a different, you might get sort of an overshooting like this:



Normally this doesn't matter but in this case the overshooting pulls the value out of range (>1.0) and Lightroom obviously sets the value out of range to zero.

To prevent this I have a routine that clips values to their max/min values accordingly. So normally the limiting should clip the values >1.0 to 1.0. Currently I don't know why this doesn't happen in this case - that's what I'll have to check.

As workaround you can select only the columns affected and than select the rows in the table (here between KF1 and KF2) and apply a linear transition - this will level out the overshooting. It makes sense to check these effects by switching the displayed curve via the combobox above the preview and visually check for overshoots.

I hope this helps for now, I'm going to check the clipping issue soon and then come back to you.

I just wanted to let you know that this will be fixed in Version 2.0 of LRTimelapse. Thank you for reporting.