Doyle; many thanks, your tutorial worked a treat.
Haven't quite worked 'how' it has worked, but I seem to have ended up with some additional XMP files with the suffix 'original' at the end of them. Perhaps Exiftool is being friendly and making backups of the originals? :P
To clarify (if anyone else is having the same issues) this was my process;
1 - Download and install exiftool FOR MAC (There is a specific Mac OSX package)
2 - Prepare/move CR2 files and .xmp files from Magic Lantern in one folder
3 - Open Terminal
3 - Enter the command as Doyle explained above;
exiftool -Exposure2012+=+*.** /drag folder here containing cr2's and .xmp's
Where the *.** is enter the amount you want to set
eg 0.05, next to the number you have chosen
Too the left is +
+=over expose
-= under exposure
4 - Allow process to run (New/backup XMP files were created for me. I waited until the list had finished)
5 - Select all CR2 files, open in Adobe Camera Raw
6 - FILES SHOULD OPEN, DE-FLICKERED
7 - Select all, make White Balance auto. (Unsure about next bit?...)
Make any edits should you want them? Note, that if you change exposure now, you'll undo the de-flickering!
(Perhaps edits should be done first, then you start the de-flickering command afterwards? Needs testing!)
8 - Close Adobe Camera Raw
9 - In After Affects, import the first CR2 image, select 'Camera Raw Sequence.' Create timelpase!
Many thanks Doyle! Maybe this Mac step by step should be added to that top post/tutorial thread?
The first 1byte is some special char.
please share a link to autoETTR module
I cannot get the Batch to work at all. I've done everything it said. I just don't get it lol. Here's what my batch says. and yes i have UFRaw installed.
cd C:\Program Files (x86)\UFRaw\bin
ufraw-batch C:\Users\Johnnie\Desktop\Timelapse\ufrawconvert*.ufraw --out-type=jpeg
You are missing the "\" before "*.ufraw"
ufraw-batch C:\Users\Johnnie\Desktop\Timelapse\ufrawconvert\*.ufraw --out-type=jpeg
Is it possible to process these same files through dcraw, using the deflicker in the xmp files? I'd like to compare results but I'm a bit wet behind the ears when it comes to the command line.
A utility that allowed you to offset exposure gain in post, whilst maintaining deflicker, would be very handy. Does anyone know of a way to do this?
I would be using LRTimelapse for manipulating the xmp files. Adjust some keyframes in LR an LRTimlapse will interpolate beetween them.
Not knowing how the algorithm works setting -4EV to get essentially unity makes no sense to me. And could it be adjustable in finer increments, half or third stops?Your photography isn't crappy
A utility that allowed you to offset exposure gain in post, whilst maintaining deflicker, would be very handy. Does anyone know of a way to do this?Yes we do indeed need a utility to offset exposure gain in post. I asked that a while back and the devs said you could write a script to offset the expo comp values in the sidecar files, but I don't know how to do that. I did also ask for help on writing a script to do that but got no reply.
I don't know of a way to adjust exposure in LR or LRTimelapse without loosing ML deflicker data, and from tests so far I'd say the ML deflicker works better in this situation than LRTimelapses, not to mention the time saved... Perhaps if we all peck him on his forums, he'll add ML-XMP import to version 3. ;)
http://forum.lrtimelapse.com/Thread-must-xmp-be-initialized
@glubber
After some searching it seems this is simple to do with exiftool. A command of:
exiftool -Exposure2012+=-0.5 /path/to/ettr_sequence_folder
will take 0.5 EV off all the exposure values.
Cheers for all the work guys! Love it!
Nice work agent 86 :);)
I've had quite a few tries with ETTR timelapse now and I'm very, very impressed. It's the best ramping solution I've tried, and I've tried a fair few. Most of what I've shot has ended up in the bin due to my crappy photography, or the rebellious British weather, but the two shots bellow have worked out ok. Besides the fly on the lens in the first one, and the motion control going tits up towards the end. But ETTR has performed admirably in all.
These have been shot essentially with default ETTR settings, bar increasing the max exposure time and setting the sidecar to XMP. Processing is limited to static white balance and curves, plus ML deflicker. Ramping over a 13 stop range in the first shot!
I've got a few questions/requests if you don't mind.
Is it possible to process these same files through dcraw, using the deflicker in the xmp files? I'd like to compare results but I'm a bit wet behind the ears when it comes to the command line.
Am I right in thinking that if I tweak the deflicker target down a stop, this will offset the post gain applied by the same value? Would it be possible for this to be a slightly more intuitive scale? Not knowing how the algorithm works setting -4EV to get essentially unity makes no sense to me. And could it be adjustable in finer increments, half or third stops?
A utility that allowed you to offset exposure gain in post, whilst maintaining deflicker, would be very handy. Does anyone know of a way to do this?
I've had a few dropped exposures. Not many but enough to be a concern. Am I pushing it to do a shot every 12 secs with a max exposure of 4 secs on a 5D2? They seem to happen when the exposure is on the long side, but that's an impression, not carefully tested fact.
The resultant RAW files sometimes seem to lack lens correction data, but not always. Easily rectified but I thought worth pointing out.
Is there any way that starting the intervalometer could automatically turn the LCD brightness right down? Be a really handy power saving feature.
My biggest request is the obvious one, speed. The amount of time it takes to process is a limiting factor in these day-to-night type situations. Any little optimisations here would make a big difference.
Once again, I tip my hat to you chaps. And I think Canon ought to send you a very nice christmas card, with a very big cheque inside!
4. Open your timelapse in LR or ACR and choose your keyframes i.e. first and last frame.
Adjust "Exposure" to your liking and write the value next to appropriate frame in the calc sheet.
for example: first frame -> orig value = 2.30553, chosen exposure: 1.45 -> ramping difference: -0.85533
last frame -> orig value = 0.82060, chosen exposure: 2.11 -> ramping difference: +1.2894
#!/bin/sh
# Script to ramp XMP exposure values
# expramp [total ramp] [path/to/sequence]
ramp=$1
path=$2
cd $path
seq_total=$(ls -1 *.XMP| wc -l)
steps=$(expr $seq_total - 1)
inc=$(echo "scale=8; $ramp / $steps" | bc)
n=0
gain=$(echo "scale=8; 0 - $inc" | bc)
while [ $n -lt $seq_total ]
do
n=$(expr $n + 1)
gain=$(echo "scale=8; $gain + $inc" | bc)
xmp_file=$(ls -1 *.XMP | sed -n "$n"p)
echo ""
echo "Processing frame $n: $xmp_file"
echo "The gain to be added is $gain"
exiftool -Exposure2012+="$gain" "$xmp_file"
doneI took overexposed photos at the end.i also ran into this problem, see above (http://www.magiclantern.fm/forum/index.php?topic=5705.msg70401#msg70401 (http://www.magiclantern.fm/forum/index.php?topic=5705.msg70401#msg70401)) for a suggested solution.
Can I set a highest ISO?you can set the max iso in the normal canon menu.
you can set the max iso in the normal canon menu.
exiftool -Exposure2012+=-0.5 /path/to/ettr_sequence_folder will knock half a stop off all the exposures.
#!/bin/sh
# Script to ramp XMP exposure values
# exramp [total ramp] [path/to/sequence]
ramp=$1
path=$2
cd "$path"
seq_total=$(ls -1 *.XMP| wc -l)
steps=$(expr $seq_total - 1)
inc=$(echo "scale=6; $ramp / $steps" | bc)
echo "The path to the sequence is $path"
echo "The total number of .xmp files to process is $seq_total"
echo "The total ramp will be $ramp"
echo "The increment per file will be $inc"
n=0
gain=$(echo "scale=6; 0 - $inc" | bc)
while [ $n -lt $seq_total ]
do
n=$(expr $n + 1)
gain=$(echo "scale=6; $gain + $inc" | bc)
xmp_file=$(ls -1 *.xmp | sed -n "$n"p)
echo ""
echo "Processing frame $n: $xmp_file"
echo "The gain to be added is $gain"
exiftool -Exposure2012+="$gain" "$xmp_file"
done
Doyles-MacBook-Pro:~ doyle$ /Users/doyle/Desktop/Test/exramp 1.2 /Users/doyle/Desktop/Test
ls: *.XMP: No such file or directory
The path to the sequence is /Users/doyle/Desktop/Test
The total number of .xmp files to process is 0
The total ramp will be 1.2
The increment per file will be -1.200000#!/bin/sh
# Script to ramp XMP exposure values
# exramp [total ramp] [path/to/sequence]
ramp=$1
path=$2
cd "$path"
seq_total=$(ls -1 "$path"/*.XMP| wc -l)
steps=$(expr $seq_total - 1)
inc=$(echo "scale=6; $ramp / $steps" | bc)
echo "The path to the sequence is $path"
echo "The total number of .xmp files to process is $seq_total"
echo "The total ramp will be $ramp"
echo "The increment per file will be $inc"
n=0
gain=$(echo "scale=6; 0 - $inc" | bc)
while [ $n -lt $seq_total ]
do
n=$(expr $n + 1)
gain=$(echo "scale=6; $gain + $inc" | bc)
xmp_file=$(ls -1 "$path"/*.XMP | sed -n "$n"p)
echo ""
echo "Processing frame $n: $xmp_file"
echo "The gain to be added is $gain"
exiftool -Exposure2012+="$gain" "$xmp_file"
done
If you have followed the manual and cannot get exposure adjustment with intervalometer action it may be that this feature has not been incorporated to the main builds yet.
but first you should make sure that:
Your camera is on M mode,
In the ETTR module: ETTR is ON, Trigger mode is set to Always On,
In Canon Menu: Image Review is set to at least 2 seconds.
If you want to darken the scene lower the Exposure target to say -2 EV
Found under Advanced ETTR
the problem is that once day rise will come up in my timelapse, then everything will be super dark...(I want a night->day timelapse of a very dark scene with some very bright objects)According to Alex you have to do that in post. I think he set Exposure target to -1EV
I have followed the manual, and set these values. it seems to work if I shoot pictures manually on by one. But if I shoot with intervallometer, it never adjusts the exposure. I can see the overlay and the ettr values on the overlay, but it does not change.
If you have followed the manual and cannot get exposure adjustment with intervalometer action it may be that this feature has not been incorporated to the main builds yet.
So, is auto ETTL the substitute for expoRamp?Not sure what expo ramp is, but yes anyway.... ;D
can i use auto ETTL for night to day and vise versa?Yes
anyone can share setting for this?
Do i need to use extol or other app or can i just open lightroom?
any one has a explanation for a lightroom workflow?
Not sure what expo ramp is, but yes anyway.... ;D
I just finished a test and i feel so stupid right now. It didn't work.
is ETTL supose to change shutter, f-top, iso to adjust exposure?
I know you were joking but i am still not sure what it does.
before this ETTL, intervalometor has a manuel ExpoRamp..i think it was called.
in my test nothing it changing.
i thought i follow all steps but must be missing something.
t3i
auto ETTL always on
intervalometor 5 sec
deflickering on
image review 8sec
is there other module that has to be active?
like auto exposure or something else.
Also read the Opening post for mac xmp workflow
but... I think Lightroom should be able to open the cr2 files and read the exposure adjustment included in the XMP file, even if you are on a mac.
Lightroom reads the xmp files just fine. See to it they are named the same as the cr2 files(I, m on a mac)
According to Alex you have to do that in post. I think he set Exposure target to -1EV
Ramping of this Exposure target would be useful but Alex says that is not possible.
Here is an excellent now ramping module for Timelapse:
Intervalometer Ramping Module (adv_int.mo)
http://www.magiclantern.fm/forum/index.php?topic=8431.0
i still think that i'm not doing it right from the capture..so..i hope to get clear there too.
Here's a picture of the screen during one of those tests
and if I let it go to ISO 12800 it's just massively overexposed, and that's at -4EV exposurehave you taken a few shots to let ETTR stabilize. It might take more than two..
have you taken a few shots to let ETTR stabilize. It might take more than two..
My crystal ball is down today... and by the way you have not even said what camera you are using and what build. maybe this function is not supported...
hi.
i only see the CR2 on the folder from my t3i..is the xmp hidden? how to make it visible?
thanks..
i still think that i'm not doing it right from the capture..so..i hope to get clear there too.
thanks.
Can someone describe the current tools to use for deflickering, since the guide in this thread appears outdated?
Can someone describe the current tools to use for deflickering, since the guide in this thread appears outdated?
According to http://www.magiclantern.fm/forum/index.php?topic=8149, the .xmp method has been removed, at least for the Canon 600D, and I can confirm that with the 10/3 build xmp files are no longer output with the cr2s (though for some reason the .xmp output menu item is still there.)
I can't very well use the ETTR mode without some way of deflickering, so I wanted to ask what to do. I'm using Lightroom to process the .cr2s.
Someone please post an alternative way to downloading UFRAW for MAC, the current download link are outdated , and also not working. Anyone please.I have tested the provided links and they work. Which link does not work?
Nopee haha 2 second interval for me. And I didn't touch ANYTHING in develop mode. I did do everything correctly though right? As far as setting everything up?I dont think ETTR can work properly at 2 seconds interval, try 10 seconds and limit the slowest shutter to 5 seconds.
I dont think so.. some one will have done this on a mac. The other option is to download an Oracle VM virtual box and install a windows OS inside your machine. I assume this is doable, I use the VM virtual box in my windows machine and run Unbuntu 64bits.
Check this site: www.virtualbox.org
sorry to bug, but do you know how to go about that?
What is the advantage of ETTR besides capturing more detail for the image?That is the advantage plus other things: http://www.magiclantern.fm/forum/index.php?topic=5693.0
Also will Post Deflicker perform well without it?It should, I have not tried it.
every time i use it with post deflicker its way overexposed, in camera raw its at +500. My settings are not drastic either, shooting inside house lighting out a window with medium sunlight brightness at 1/25 shutter, iso 100, f4.Dont know what you mean by +500.
Using the .xmp workflow, this creates a 'custom' .xmp file per image. How can we then batch process the .cr2 images in ACR without first converting to jpg? Because now the .xmp files are no longer the same so you can't just duplicate the .xmp file, right?
Hey bro,
Ramping exposure for XMP for Adobe Bridge
...
On the drop down menu you can select any of the xmp settings, default "Exposure2012"
In Start enter the amount to adjust the first image
In End entered the amount to adjust the last image
Clicked additive (To add or subtract the exposure rather than to change it)
click ok
@renatophoto. Found exiftool plugin for lightroom. Might be handy for dngs and such ? http://www.robcole.com/Rob/ProductsAndServices/xEmPLrPlugin/Have you tested?
Have you tested?
NOTE: If you set your intervalometer at 30 seconds and your slowest shutter speed at 30 sec, you will have problems. Set the intervalometer at least = Slowest Shutter speed plus the review image setting, in Canon Menu, plus 3 more seconds.
My guess is that your shuttertime collided with the interval, so etttr-and deflicker-modules have no time to adjust exposure:
I guess your timelapse turns out brighter than the original exposure was due to the ML-deflicker.
So the shuttertime could be over the critical 10 seconds (with interval 15").
Does this require manual white balance? I seem to get the ettr working for a few moments, after which it seems to keep the shutter at the same value for the rest of the time. Any ideas or common mistakes?
@roopepal, @gerfried,
Check the min shutter speed setting for ETTR, it sounds like you are hitting this limit. ETTR wont set the shutter speed slower than this setting, instead it compensates with ISO. Once you hit min shutter setting and max ISO, it's not going to change the exposure any more (it can't go any further). Was the ISO changing? Was your scene lighting actually changing? You're using the 'Always On' mode not LV right? (step number 3 in the OP) and you have image review on? Do you hear the beeps? How many? (3 indicates expo limits reached, it should also say this on the screen)
Perhaps read the OP again, very carefully. I think you probably just need to make sure all your settings are correct. http://xkcd.com/627/ ;)
How do we set the MINIMUM SHUTTER?http://www.magiclantern.fm/forum/index.php?topic=5705.0
http://www.magiclantern.fm/forum/index.php?topic=5705.0
P.S. It is frustrating when people just ask before they even read the manual and try to understand!
totally understand, but i have read it and still cant find the thread or description of setting a minimum shutter, it only says direction of setting the slowest shutter. My question would be would i have to shoot in shutter priority or is there a option to set the MINIMUM shutter inside the Magic Lantern Menu. Yesterday evening i shot a sunset timelapse and i got massive exposure values switching towards the peaking of the sun going down.
But I cant seem to get a day to night timelapse locked down yet, here is one from this evening.
Maybe your xmp files where never read by ACR. To test this hypethesis you need to open one of the cr2 files and look at the exposure compensation, if there is none then that is your problem.
or
Maybe your interval is too short for ETTR and Post-processing to work properly.
what doyou think?:
of couse following instructions in this post.
Paul,
Did you enable these modules in the modules menu? You need to enable them first then power cycle the camera to get it to reboot and load them.
Michael
Thanks, yes I did use ML post deflicker but I couldn't get it to underexpose during the night - it was trying to brighten up the images considerably
Why don,t you use dmilligans script? It,s for postproduction deflickering.
If dmilligan Bridge script does it all, can we do away with xmp deflicker and just use ETTR?
@dmilliganI've seen some intermittent issues with 'resize is undefined'. It typically has something to do with Bridge not giving me valid image preview data. I request the preview from Bridge as 'BitmapData' and then I call a function on it called 'resize' which is supposed to be a function of that class. If Bridge gives me bad data for some or another reason then that function isn't there and you get the 'resize is undefined' message. I think it has something to do with the cache and synchronization stuff. Supposedly I'm in 'synchronized' mode, so that when I request stuff from Bridge, it blocks until the data is valid, but it seems like sometimes that doesn't happen. I don't think there is anything I can really do about as its probably a bug in the Bridge scripting engine.
I'm really not in a position to make a coherent fault report at the moment, except that it often seems to freeze and when I try to quit Bridge I get an error message saying 'resize is undefined'.
In the shot below about 20 frames, distributed seemingly randomly through the sequence, did not have xmp files associated with them.The deflicker might not have had time to finish running. What was your interval time between shots? Getting below about 10s and you can start running into the occasional 'dropped' xmp file, if for some reason the CPU was a little busier. It also has to contend with ETTR's analysis using the CPU as well.
linking the ETTR with the Bulb Timer from ML?
If Bridge gives me bad data for some or another reason then that function isn't there and you get the 'resize is undefined' message.
Getting below about 10s and you can start running into the occasional 'dropped' xmp file, if for some reason the CPU was a little busier.
Is there any ways of using ettr without giving all the preference to the shutter? I mean, because sometimes I want a timelapse at night with an interval time lower than 30 sec, but every time I set the ettr it makes my shutter speed go to 30 sec and my ISO to the minimum as possible. It would be great if we could lock the iso or give preference to the iso till it reach a determined value.You can set the maximum shutter speed for ettr. There's no reason in my mind to lock the ISO or give "preference" to it.
The ML settings override the manual Canon settings, right? So they take care of the changes in exposure going into night?Yes, ML takes control of the Canon settings.
You can set the maximum shutter speed for ettr. There's no reason in my mind to lock the ISO or give "preference" to it.
Then I close the display (turn it facing inwards) to save battery, is this where it goes wrong?
I was shooting a time lapse during daytime so maybe ETTR isn't needed in this situation?Right. If you're scene lighting isn't changing then you don't need this. Just set the exposure in M mode and shoot your timelapse.
Is it best for changing light scenes (ie. sunrise/sunset)?Exactly. Shooting a sunrise or sunset is much more challenging (or impossible) without this workflow.
Will this be mitigated in post delficker even if ETTR is "hunting" around for the correct exposure?Yep. The deflicker script takes care of it.
If the former, why wouldn't everyone just use XMP since it's less than half the steps of UFRaw?Not everyone owns (expensive) Adobe software. UFRaw is free software.
Not everyone owns (expensive) Adobe software. UFRaw is free software.
Upon reflection, I think I caused ML to crash/stop because I hit the review button right after the people passed in front of my frame to check the image.
Sorry, it's not a case of being broken. It was a suggested enhancement, as if you use ETTR my understanding was you need an interval of, say, 10 seconds or more to allow ETTR to settle on a solution.If your exposure is way off (like when you start), possible it could take that long, but once your sequence is going, it should be much shorter, as the exposure is not changing that much from frame to frame (only minor adjustments are needed). I've never used ETTR for timelapse in LV mode though (too much heat and battery usage). In regular photo mode, it just analyzes QR data after each pic, and it only takes a second or two (I recently did a timelapse with slowest shutter 16", interval 18"), and I think most of that time is just waiting for the QR data.
https://bitbucket.org/hudson/magic-lantern/src/tip/modules/silent/README.rst
http://www.magiclantern.fm/forum/index.php?topic=12523.0
Keyframe is the first thing I would try.
I think I am getting the hang of this! Thanks!
I will keep my mouth shut.
I've polished the OP a little. Hopefully it is a little easier to understand.You linked the wrong script of mine, that one can't deflicker ;)
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.No, it moves the median (or whatever other percentile level you select, median is just 50th percentile) of the histogram to 4ev from the right. So it doesn't necessarily move it by -4ev, it may actually move it up some if the median is at less than -4ev.
At highlight ignore = 1%, the image is metered at 99th percentile: that brightness value is adjusted to match the target level. That means, 99% of pixels will be darker than target, the other 1% will be brighter. See http://en.wikipedia.org/wiki/Percentile
For deflicker purposes, you would meter at 50th percentile (median), so exactly half pixels will be darker than the exposure target, and the other half will be brighter.
You may say why not compute the average brightness (simple or weighted) and use that for metering? Answer: median and percentiles are statistically robust (they ignore outliers => less flicker). Average (mean) is not.
Is there a way to convert the .UFR files to XMP to use the Bridge Ramp Multiple and Deflicker Scripts?You don't need to, the Bridge script will deflicker for you, even without XMPs from the camera.
In [622]: 5760./3240
Out[622]: 1.7777777777777777
In [623]: 16./9
Out[623]: 1.7777777777777777
Take two or three pictures until the RAW histogram ETTR hint is less than 0.2jTurn on raw histogram in the overlay menu, make sure image review is not turned off in Canon menu. Take a picture. You will see a histogram and there will be a number on it. This is how many EVs you can increase the exposure until overexposure. Alternatively, simply turn AutoETTR to "always on" and take pictures until you only hear 1 beep after a photo (2 beeps means you need to take another photo, 3 beeps means exposure limits have been reached=>proper exposure is impossible with current settings).
I meant to ask if we could have a 3x crop mode in stills mode as well during time lapses?No, same answer. The size of a pixel is the size of pixel. You can crop in post if you like.
Code: [Select]In [622]: 5760./3240
Out[622]: 1.7777777777777777
In [623]: 16./9
Out[623]: 1.7777777777777777
=> bug invalid.
I feel like it's going to be impossible to get a smooth, flicker free video.Maybe that's how you feel, but in reality it is possible to get really good, flicker free results even with the exposure changing constantly (thanks to Maths (http://en.wikipedia.org/wiki/Histogram_matching)). Why don't you actually try it? Use the deflick module or the script I wrote. Once you have actually tried it, then post back if you still have issues (include sample footage!)
Maybe that's how you feel, but in reality it is possible to get really good, flicker free results even with the exposure changing constantly (thanks to Maths (http://en.wikipedia.org/wiki/Histogram_matching)). Why don't you actually try it? Use the deflick module or the script I wrote. Once you have actually tried it, then post back if you still have issues (include sample footage!)
Ran into my second issue. There is no option for sidecar (XMP) files when using silent mode. Any suggestions?
I had been experimenting with ETTR auto snap at the timeThere's the culprit. I would recommend not using auto snap for timelapse (a flickery scene could trigger extra shots at random times). Instead, quickly adjust exposure manually when adding the ND (this is what I did when I tried doing this sort of thing), or just throw out that one bad frame.
Edit2: Ufraw-batch is now looking for a CR2 - when obviously I have used CR2HRD to create a DNG. Obviously there isn't a converter to go back again - what's best here?
some of my CR2 files do not have XMP, how to resolve this problem ?Like dmilligan said, usually 6 sec is gd. Or u can disable AETTR then u won't have missing files with 5 sec
(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fc4.staticflickr.com%2F8%2F7738%2F17625199674_924966b7c6_n.jpg&hash=917687ae7a98af9fa46d9bae1224c81b) (https://flic.kr/p/sRtKP1)
ETTR-problem (https://flic.kr/p/sRtKP1) by agus telo (https://www.flickr.com/photos/ecek2/), on Flickr
settings: Interval 5s, AETTR slowest shutter 1", post deflickr XMP
Canon EOS 550D Nightly 2015Mar29
It's probably beeping twice because the scene lighting is changing, and by the time it takes the next picture there is less light than AETTR expected there to be, and so AETTR is letting you know the photo was slightly underexposed.
The shutter speed isn't changing because either: you reached the slowest shutter set in the AETTR menu or you had AETTR set to only change ISO.
Also I want to ramp exposure using shutter speed not ISO, but instead throughout the shooting the camera just kept increasing the ISO automaticallyThere is no reason to not increase ISO once shutter speed limit is reached. All else equal (shutter and aperture), higher ISOs have less noise than lower ISOs (i.e. the SNR per photon is better with higher ISOs), otherwise they would be pointless.
Exposure targetBut if I change that setting to let's say -2 EV (what I would need for night time), during daylight I'll get an underexposed shot.
And of course not every photographic situation will lend itself to this technique. A shot taken on a sunny day with a cloud, a mountain and a forest will challenge the dynamic range of any camera, and so there will be little opportunity of biasing the exposure toward the brighter tones without blowing out the clouds.
so i have to use this: http://ufraw.sourceforge.net/Install.html#Mac (http://ufraw.sourceforge.net/Install.html#Mac)
to deflicker?
ugh.
I think ML deflicker makes better output than Lrtimelapse. Reason why i want to take pictures to Lrtimelapse is thats quite good tool for "animating" white balance etc. with keyframes. Any suggestion for similar post production what Lrtimelapset can do?After de flickering in lightroom and importing them in LRTimelapse, just un-check the exposure 2012 and use it as u always do, and skip the deflicker phase.
If pictures are already deflickered there's no need to use Lrtimelapse own deflicker. ..And anyway it doesn't (hopeful) make any chances when pictures are ready deflickered.
Why? There's no good reason for this. The only possible thing that would happen is you end up with a less than ideal exposure. During a sunset you could end up with overexposed shots and during a sunrise you could end up with underexposed shots.Well I am just trying to find a way to avoid "flicker" which is caused by changes of the exposure during the day (or during the night). For example:
Hi Shogran.
i am far from qualify to help..but..
first i thought..do you have the cam set to max iso 1600? i do have mind..
and...do you mean intervalometer stops or ETTR stops? it keeps taking pictures but not well expose?
i just thought i tried to help..sorry..no much better.
After de flickering in lightroom and importing them in LRTimelapse, just un-check the exposure 2012 and use it as u always do, and skip the deflicker phase.
@Edmund-B
I use LR and LRT and with ML ETTR.
I personally first bring my images into LR.
I then go to LRT and point to the folder where the images are.
I do the LRT workflow, eg keyframes and holygrail and export metadata.
Then back to LR and in Lib mode select keyframes from filter and read metadata.
Do any adjustments in LR (on the key frames) and save metadata.
Then back to LRT, read metadata and finsh off LRT phase, before returning to LR, selecting all images, reading all metadata and exporting for video.
Cheers
Garry
Thanks for the reply Garry,You need to uncheck the exposure 2012 in LRTimelapse before saving the animated curves or doing the initial keys.
the problem im facing is i cant use the holy grail wizard because otherwise, i would loose the post-deflicker group of XMP files. And thats not an issue i just uncheck the exposure2012 column and thats alright.
the problem resides where creating keyframes in LRtimelapse dont appear in Lightroom
https://drive.google.com/open?id=0B1whvX7ElUOpdDZZQXZaX3BjYkk
You need to uncheck the exposure 2012 in LRTimelapse before saving the animated curves or doing the initial keys.
1st bring to lightroom, use the ml deflicker then use LRTimelapse to do the keyframes, same Metadata, do your modification in lightroom and when u return to create the animated curves, uncheck "exposure 2012"