Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - smier

#1
Thanks for the answers. If I wanted to see the difference between a deflicker target level of -4 and -2, could I shoot at -4 and then use dmilligan's bridge script to additively add 2ev/stops of exposure? Would the results be the same if I were to begin with the deflicker target level of -2?
#2
Has anyone experienced ETTR blowing out the highlights on night to day timelapses? Unfortunately I do not have the debug DNGs, but as the sun rose the ISO and shutter speed did not change for probably 25 shots which caused massive overblown highlights (like 75% overblown). There was plenty of time between shots for ETTR to evaluate, and I only had a highlight ignore of 0.5%. Even after it adjusted, it was still a bit overblown but not as bad. This was not in direct sunlight either.


Also just to help me understand, what exposure target does is knocks the histogram back to the left (darker) based on the setting? an exposure target of -0.5 will take the original ETTC calculation and move it 0.5 stops to the left and -1 will move it 1 stop to the left, etc?

What about the in the deflicker module, deflicker target level, how does that work? The wiki states "Desired exposure level for processed pics", and is recommended to leave at -4. I guess this means that my photos will be lowered 4 stops on the histogram with the XMP files.
#3
I've just tried a timelapse with AETTR and Dual ISO, I have a question about the workflow.

After importing all my files, do I want to process all the dual ISO into DNGs before editing the image or do I edit the cr2 file, then process the dual ISO into DNGs? I'm assuming the first option but just wanted to make sure.

Any other workflowthat I may need to consider for AETTR Dual ISO timelapse vs AETTR timelapse? I'm using the LR Cr2DNG plugin from another thread and adobe bridge deflicker script if the ML deflicker XMP files aren't enough.
#5
Is this because shooting different ISOs and modifying exposure in post result in the same image? For example, if I take a photo at 5",  ISO6400 with the exposure lowered equal to ISO4000, and take another photo at 5" ISO4000 they will result in the exact same image?

Does it work in reverse too? An image shot with ISO4000 with it's exposure increased in post equal to ISO6400 will look like a photo shot at ISO6400?
#6
I've noticed during a night time lapse that my 6d only uses full stops of ISO (100, 200, 400, .., 6400) and not any of the intermediary ISO levels between the full stops. Really makes night scenes less flexible to minor changes compared to day scenes. Is there any plan to modify this in a future nightly?
#7
The module seems to be fixed! Zero flickers in today's time lapse. Had to cut it short cause it started to rain, you can see the leaves start to droop at the end.

1080p

4k glory!


An observation — to save transfer speed time I tried lowering my RAW size to medium and small but both had "RAW ERROR" displayed on the screen when it tried to calculate the ETTR. Looking at this thread it seems to be a known bug though.


Thanks the quick fix on the module. The script you linked also worked to deflicker the previous time lapse as well, thanks for that too.
#8
I'll test the module when I get home. Remoting to my home computer and trying out the script you linked, procrastinating at work :P
#9
Very interesting! Glad I could help troubleshoot some stuff. Let me know if there's anything more I can test.
#10
So I just had another go, seems to be a lot less flickering when I increased the highlight ignore to 8% from 5%, but it still occurs.

Here's the video

around the 30 second mark there's several flickers. I found the frames that occur at one of these flickers. Between 8564 and 8565 the camera exposure settings are the same and there is no significant change in the scene lighting but the deflicker exposure value changes significantly. On 8565 the shutter speed changes but the deflicker exposure value correctly compensates it.

CR2, XMP and diagnostic DNG files can be found here

So I guess the camera just didn't calculate the correct post deflicker exposure value?
#11
Thanks Alex, I'll try this tonight after work!
#12
Quote from: dmilligan on June 17, 2014, 03:37:38 AM
Not everyone owns (expensive) Adobe software. UFRaw is free software.

That makes sense, thanks for clarifying.

I just did my first test yesterday evening. It worked out pretty good but still had some flickering. I looked at the XMP values and several times they jump quite large distances. I had a Highlight Ignore of 5%, 5 Midtone SNR, 2 Shadow SNR. Any advice? This is on a 6D
#13
Just read the entire thread, one question. Are the post processing XMP and UFRaw guides in the OP two different methods that produce similar results or are they both required? If the former, why wouldn't everyone just use XMP since it's less than half the steps of UFRaw? There must be some sort of advantage. Maybe I misinterpreted the OP.