Magic Lantern Forum

Developing Magic Lantern => Modules Development => Topic started by: dmilligan on September 21, 2013, 12:53:31 AM

Title: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on September 21, 2013, 12:53:31 AM
WIP for replacing this module with a script -> http://www.magiclantern.fm/forum/index.php?topic=17570




Advanced Intervalometer (adv_int.mo)

This module is for advanced ramping and control of exposure parameters during an intervalometer sequence.With this module you specify the ramping by creating keyframes with the values of various parameters that you want to ramp to. When the intervalometer is running, this module ramps the specified parameter(s) from one keyframe to the next.

Update: The Advanced Intervalometer menu now shows up under the Intervalometer submenu.

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fbitbucket.org%2Fdmilligan%2Fmagic-lantern%2Fdownloads%2Fadv_int_av_ramp_setup.gif&hash=a13b7f634185120541233496e5f54f73)

I think some cool effects can be done by ramping aperture (and let AutoETTR compensate the expo with Tv, ISO) and focus or a combination of the two. You could have a scene where everything is in focus with f/22 and then ramp down to f/2 to blur out everything but your subject. The video below is my first quick and dirty test of this module and does just that:
I ramped the Av from min to max and back to min, and let AutoETTR+Post Deflicker take care of the exposure.

The other potential use for Av ramping is a full day to full night (or vice versa) time-lapse, where you might want a pretty small Av during the day, and then open it all the way wide open and move to focus infinity to get the faint light of stars/milky way when it gets dark. So basically you are making the "artistic" exposure choices, with your knowledge of time of sunset/twilight, while AutoETTR takes care of then optimizing the exposure.

Here's some examples where I used Av ramping with AutoETTR:


Tv ramping could be very useful for doing some varying amounts of motion blur. Think car lights at night: by varying the shutter angle, you vary the length of the streaks of car lights. I've seen this done in timelapses, and the effect is very cool.

Changing the actual intervalometer period allows you to create accelerating or decelerating timelapses with out having to waste shutter actuations (you can easily accelerate or decelerate in post, but you will in essence be throwing out frames). Another thing you could do is to actually slow down your footage in post by the same amount you ramp the intervalometer period. This would give the effect of the time-lapse not actually chaining speed, but it would become more or less "choppy".

To use, download the latest nightly (http://builds.magiclantern.fm/) and add this module to the ML/modules folder:
https://bitbucket.org/dmilligan/magic-lantern/downloads/adv_int.mo

See the readme (https://bitbucket.org/dmilligan/magic-lantern/src/ffd10dcab10f2eefefea3ef1b78c271649686e6d/modules/adv_int/?at=adv_int2) for instructions on how to use.

Current list of settings that can be ramped

Updates:
[2014-2-25] Updated to work with new menu features (mult-level submenus and menu_caret)
[2014-3-8] Updated to work with module version 5, Added ability to adjust Tv, Av, ISO from within adv_int menu, so you don't have to leave the menu and come back



Disclaimer:
I'm not responsible for anything that might happen to your camera from running my code. Use at your own risk.
Title: Re: Intervalometer Ramping Module
Post by: britom on September 21, 2013, 04:46:57 AM
GREAT WORK!
Title: Re: Intervalometer Ramping Module
Post by: RenatoPhoto on September 21, 2013, 09:24:28 PM
Fatastic! This could be the LRTimelaspe for ML!  Maybe you should post 5D3 autoexec.bin and the module for testing.
Title: Re: Intervalometer Ramping Module
Post by: dmilligan on September 22, 2013, 02:38:42 AM
Added builds and readme, see first post.
Title: Re: Intervalometer Ramping Module
Post by: RenatoPhoto on September 22, 2013, 03:15:09 AM
Great, I downloaded the module and will start learning how to use it.

One of the things I wish to have a better control is White Balance.

Of course the access ETTR parameters like SNR and highlight ignore will be very useful for optimizing day to night to day timelaspes.

I have done some experimenting with ETTR+DUAL ISO in a Timelapse and the results are very good. 

ETTR + DUAL ISO = 14 Stop Dynamic Range Timelapse - Postprocessing Guide
http://www.magiclantern.fm/forum/index.php?topic=8443.0

And.. thanks for sharing this module, the idea is great!
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: Doyle4 on September 22, 2013, 03:41:52 AM
600D please dude! if i could compile id do it my self but i have no clue what's so ever.

Cheers, this be sweet for what im after doing!
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on September 22, 2013, 05:29:53 AM
Added 600D build, see first post

@Doyle4,
btw, compiling is really not hard at all, if you have a Mac I made a script to set everything up to compile ML. Just install xcode  from app store and command line tools from xcode prefs, then just type this in the terminal, and you should end up with a compiled ML:
Code: [Select]
bash <(curl -L https://bitbucket.org/dmilligan/magic-lantern/downloads/SetupML.sh)(this script downloads code from the main repo, not mine, so you'd just need to checkout mine instead for testing this module)
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: Doyle4 on September 22, 2013, 10:00:15 AM
Thank you very much.

Mac user here too, ill copy that and have a play, thanks again.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: Doyle4 on September 22, 2013, 01:36:41 PM
getting an error at the end..  :-\

[ VERSION  ]   ../../platform/60D.111/version.bin
make[1]: truncate: No such file or directory
make[1]: *** [../../platform/60D.111/version.bin] Error 1
make: *** [60D] Error 2
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: fpena06 on September 22, 2013, 01:52:24 PM
I would love to test 7D
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: mageye on September 22, 2013, 02:50:26 PM
I have been using my 500D for timelapse so would really appreciate a build for this camera.

Thanks in advance :)
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on September 22, 2013, 03:25:12 PM
@Doyle4,

type these line the terminal, I'll fix my script with this also:

Code: [Select]
export PATH="$PATH:$(brew --prefix coreutils)/libexec/gnubin"
echo "export PATH=\"\$PATH:\$(brew --prefix coreutils)/libexec/gnubin\"" >> ~/.bash_profile
cd ~/magic-lantern
make clean
make
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: Doyle4 on September 22, 2013, 04:01:42 PM
Thank you dmilligan,

Im guessing when i build this it grabs the other stuff from the nightly builds and then adds your module?
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: mageye on September 22, 2013, 04:03:53 PM
Just a thought. This system is based on keyframes which is fine. I was wondering if such events could be dictated by global time? (as in the cameras main clock). Or the keyframes could (optionally) be global time values?

This (if it could be implemented) could be a way to change values at actual times based around, for example, when the sun sets or rises.

I don't know if this would be possible? but I think it could be useful? :-\
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: RenatoPhoto on September 22, 2013, 04:21:10 PM
I don't know if this would be possible? but I think it could be useful? :-\
Agree, easier to prgram based on time rather that frames.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: Doyle4 on September 22, 2013, 04:38:51 PM
Just a thought. This system is based on keyframes which is fine. I was wondering if such events could be dictated by global time? (as in the cameras main clock). Or the keyframes could (optionally) be global time values?

This (if it could be implemented) could be a way to change values at actual times based around, for example, when the sun sets or rises.

I don't know if this would be possible? but I think it could be useful? :-\

Like sound of this..

Be also nice to work along side autoexposure, but Intervalometer Ramping Module could stop aperture and iso change in autoexpsoure allowing just shutter time to changed if worked out correctly.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: Doyle4 on September 22, 2013, 09:45:53 PM
@Doyle4,

type these line the terminal, I'll fix my script with this also:

Code: [Select]
export PATH="$PATH:$(brew --prefix coreutils)/libexec/gnubin"
echo "export PATH=\"\$PATH:\$(brew --prefix coreutils)/libexec/gnubin\"" >> ~/.bash_profile
cd ~/magic-lantern
make clean
make

Still getting error on 60d... odd one.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on September 22, 2013, 11:14:36 PM
more builds up

I don't know if this would be possible? but I think it could be useful? :-\

Yes this is something I considered and plan on implementing. It's not really difficult at all to do, the main problem is simply creating a user input method for time. It's really easy to use the ML menu API to input integers (like the number of frames), it's going to be a little more challenging to create a date/time input method. This is why I went with the frame method to begin with, it's easy to input and I can have something that I can start using to test with. As this is mostly just a connivence issue, I'm probably going to work on some of the more pressing things first (like adding new parameters to control, and working out bugs), just so we can be trying them out and getting new ideas. I will get to it eventually though.

Some other ideas I have:

The next thing I will work on will be adding WB, ETTR, and DUAL ISO parameters.

(I almost always shoot RAW picture quality for timelapse so WB is a non-issue for me, but I can see the need for it if shooting JPEG to save memory, esp for extremely long timelapses)
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: RenatoPhoto on September 22, 2013, 11:27:54 PM
The next thing I will work on will be adding WB, ETTR, and DUAL ISO parameters.
(I almost always shoot RAW picture quality for timelapse so WB is a non-issue for me, but I can see the need for it if shooting JPEG to save memory, esp for extremely long timelapses)
I use RAW but I need a means of changing the WB from night to day in a progressive manner, you can probably do this in light-room but if you use ACR alone it is not possible.
Thanks
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on September 22, 2013, 11:33:50 PM
you could probably do it with exiftool, xmp sidecars, and a script, but that would be hard

IMO after effects needs a way to keyframe ACR settings, that would be freakin awesome (also very useful for RAW video)
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: glubber on September 23, 2013, 09:10:21 AM
Never heard of LRTimelapse?
Its capable of doing various transitions of exposure, wb and other develop parameters of LR/ACR using xmps.
If you stick under 400 frames it's free-trial.
-> http://lrtimelapse.com/ (http://lrtimelapse.com/)

you could probably do it with exiftool, xmp sidecars, and a script, but that would be hard

I had this idea too in order to ramp the deflicker xmps in post.
the workflow is using exiftool and excel (or oo calc).
In fact it's hard and cumbersome  :P
http://www.magiclantern.fm/forum/index.php?topic=5705.msg70401#msg70401 (http://www.magiclantern.fm/forum/index.php?topic=5705.msg70401#msg70401)
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: mageye on September 23, 2013, 03:09:33 PM
@dmilligan

Thanks for everything you are doing with this. It looks as if you have a vision for this and that's good to see :D. I am glad you had already thought about the time based thing too and I believe that it will just be a matter of time (and hard work of course) that this feature is realised; along with the many more that you have mentioned. I have faith :).

I am keen to test this out. I will start with some tests on my 5DmkII so I can familiarise myself with the practise. What I really need (personally) is for my 500D to be able to run this too.

The build you provided (for the 500D) seems to function with all the modules excluding the ettr.mo and silent.mo modules :(. Obviously I would like for them to be functioning alongside your module so I can put it to the test properly.

So I am sorry to bother you with this but: Is it possible that you could provide one that works with the ETTR? (and possibly silent pics too ;))

Thanks again and keep up the good work :D.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on September 23, 2013, 03:19:41 PM
@mageye
you're very welcome, thanks for the compliments

a1ex has just merged in my core changes, so as of the next nightly you will just be able to use the nightly builds and simply add my adv_int.mo to the ml/modules directory. After the next nightly is built, I will update the first post with just a link to the .mo and direct ppl to the nightlies.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on September 23, 2013, 03:32:28 PM
Never heard of LRTimelapse?

Never heard of it, but it looks cool, however I don't like paying for things I could probably write myself ;) . I have some experience writing adobe scripts, I might be able to write a script for AE that makes ramping ACR settings easier. I know that the script API for AE has some pretty good integration with the native AE GUI, but I'm not that familiar with the AE scripting, I've mostly only done photoshop scripting. Yet another thing on the todo list ;)
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: a1ex on September 23, 2013, 04:08:09 PM
so as of the next nightly you will just be able to use the nightly builds and simply add my adv_int.mo to the ml/modules directory.

Next nightly is up and running, can you check it?
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on September 23, 2013, 04:11:09 PM
not til I get home from work in about 5 hours  :-\
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: Doyle4 on September 23, 2013, 04:17:06 PM
8352: Merged core changes from https://bitbucket.org/hudson/magic-lantern/pull-request/232/adv_int-module

What i saw in outpost. no adv_int.mo in 600d nightly 23rd sept.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on September 23, 2013, 04:27:17 PM
he didn't merge the module itself (b/c it's not done yet), just the changes I need to the core, you will still need the adv_int.mo from me (you can pull it out of any of those builds that I posted, unfortunately I can't post the adv_int.mo file by itself til I get home)
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: RenatoPhoto on September 23, 2013, 05:32:08 PM
I did an hg pull and hg update and cannot find the adv_int directory in modules

Update:  Oops Ok!  I did not read your post above.  Thanks
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on September 23, 2013, 10:05:54 PM
Next nightly is up and running, can you check it?

I can confirm it is working. I have updated the first post to simply link to my .mo file and direct ppl to d/l the latest nightly
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on September 24, 2013, 12:31:45 AM
update:

added WB (only the kelvin setting, not fine tuning adjustments, will anyone need those too?),

also did some rounding suggested by a1ex to help canon firmware accept computed ramp values that might be inbetween values accepted by the canon firmware, as well as rounding ISO to the nearest analog ISO.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: mageye on September 24, 2013, 02:51:38 PM
OK so now the latest updated nightly for 500D no longer includes ETTR module :(
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: RenatoPhoto on September 24, 2013, 04:33:36 PM
added WB (only the kelvin setting, not fine tuning adjustments, will anyone need those too?),
I used the latest autoexec.bin and load the (latest) adv_int.mo to check for functionality of WB on 5D3.
It worked!  I ran a test of ten shots and created a list of keyframes to follow, then I checked the images and the WB was properly set.  The minimum jumps were of 100, from 3100 to 3200, etc.  I noticed that if I move the slider in ACR I get increments of 50, so I dont know what kind of jumps will be acceptable to have a timelapse with smooth WB transition.  Maybe 100, maybe 50 or maybe less.  I suppose this will have to be tested to determing a correct jump, maybe operator selectable?
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on September 24, 2013, 05:15:38 PM
I rounded using the KELVIN_STEPS (which is 100) macro in the ML source, I wasn't sure if the canon firmware would just accept any old kelvin value and assumed I needed to round. If it will take any old value, then I have no problem dropping it to 50, or just not rounding at all. a1ex will have to answer this question
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: Doyle4 on September 24, 2013, 09:27:11 PM
look at the bottom ;)

http://www.magiclantern.fm/forum/index.php?topic=8443.new#new
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: RenatoPhoto on September 25, 2013, 04:27:09 AM
Ran some test and experienced some problems with the list of Frames.

If you go in the List Keyframes and there are no keyframes then you have to get out of ML to get out of this menu.  Should just press Q tog get back.
The first time you use the list of keyframes it works, but editing the list is not working well, the values at the previous list do not show.
Then if you try to edit an existing frame, it appears that the old frame is also listed.
When using WB I set my firts frame to 5000 and in frame 10 to 3000.  What happens is that the current setting for WB (whatever it is) is used in the first two frames instead of setting the first frame at 5000 as i programmed it.

I used a 5D3 with the latest binaries.

Let me know when you fix this so i can test it again.

Thanks for this great idea

Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on September 25, 2013, 01:50:38 PM
If you go in the List Keyframes and there are no keyframes then you have to get out of ML to get out of this menu.  Should just press Q tog get back.
I noticed that too, this is problem with the ML menu API. The same thing will happen if you go to some of the ML Help menus, without any of the help data on your card, those menus will be empty and you can't get out of them w/o leaving ML completely. I have just submitted a bug on the issue tracker for this.

When using WB I set my firts frame to 5000 and in frame 10 to 3000.  What happens is that the current setting for WB (whatever it is) is used in the first two frames instead of setting the first frame at 5000 as i programmed it.
I know what happened here (I took out some code alex thought was redundant, and it was for the most part redundant, but it did cover this case), and I'll fix it so that it gets set correctly after the first frame instead of the second, but it's important to note that the keyframes operate AFTER the frame is taken. The way it's set up I can't really do anything before the first frame, so make sure your camera is already set how you want it for the first frame.

Maybe I should shift the numbers by one so that 5 means before frame 5 instead of after, start the numbering at 2, and automatically create a keyframe 1 from the initial settings of the first frame, this might be a little more intuitive, and you wouldn't have to create the inital keyframe. What do you think?

Thank you so much for the feedback!
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: RenatoPhoto on September 25, 2013, 02:31:42 PM
Or take the first frame to confirm that the module is operating properly by announcing on Life View that the next frame will have the proper settings.

Also there is a little variable which is critical to making a Timelapse which I have not used or tested yet, but Alex is using it.  It is the Exposure Target found in ETTR advanced mode.  By using this we can change the overall target exposure of the timelapse without affecting the deflickering.  It is like an exposure ramp on top of the deflickering exposure compensation.  I think Alex uses this to make the night timelapse a bit darker since now it is kind of too bright.  It is not possible to go above -0.5, now for this to work on a keyframe we would need a finer access to this value so it could be ramped smoothly ie +-0.1
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: a1ex on September 25, 2013, 02:40:45 PM
That's something meant to set once, not ramped. ETTR is not supposed to give you the final look, but only a technically correct exposure for RAW (which can't be flicker-free because it meters for highlights).

If you try to ramp this, post deflicker deflicker will "undo" it with exposure compensation.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: RenatoPhoto on September 25, 2013, 02:52:28 PM
If you try to ramp this, post deflicker will "undo" it with exposure compensation.
Thanks for clarifying this, so it is not possible to use this for an exposure ramp  :'(
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: a1ex on September 25, 2013, 02:54:02 PM
This is best done in post (at deflickering stage or after that).

If you underexpose before that, you'll get noise, if you overexpose before that, you get clipped highlights. If you do both of them in post, these problems disappear.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on September 26, 2013, 03:54:31 AM
updates:
I fixed all the bugs RP found
Implemented global time, so you can enter times of day for the keyframe times

For the time of day entry menu, since I wanted to allow precision of entry down to the second, but scrolling through every second of the day would take forever, and I didn't really want to have 3 separated menu items to enter the time (hours, minutes ,seconds), I have implemented an experimental accelerating scroll wheel for this menu item. If you scroll slowly, it will change only the seconds, if you scroll a little faster it jumps to 15s increments, faster still: 30s, even faster 1min, and scroll very fast and it will jump by 10min increments.

Play around with this and let me know what you think, and if you think it works well enough to keep.

@a1ex, perhaps a modified version of this using more accurate timers (I just used LoadCalendarFromRTC, which only has 1 second resolution and it still works pretty well) and slightly better more general acceleration algorithm would be useful to build in to the menus for items with large ranges. That would allow user to enter any value for something like say intervalometer period, but still be able to quickly get to large values, without having to make it start jumping by 5s, then 10s, then 30, etc, like is done currently (see commit (https://bitbucket.org/dmilligan/magic-lantern/commits/4ed48c2deda6a1bbbadd984df7f56aefc2b36b5e) line 395)
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: RenatoPhoto on September 26, 2013, 04:27:54 AM
Wow!  Looks really good..  I will have to test it soon.  :D
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: Danne on September 26, 2013, 06:54:52 AM
Thanks for clarifying this, so it is not possible to use this for an exposure ramp  :'(

Ettr is the best.
Havn, t done extensive testing but when I skip using xmp deflickering going from day to night gives me a ramp curve much like using av mode on the camera. Even with ettr module. Of course this would give me some flickery files. With xmp deflickering I was under the impression It wants to even out exposure going from lightest and darkest picture and night pics have to be set down in post?
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: glubber on September 26, 2013, 09:48:28 AM
@danne:
Your impression is right!  ;)
If you're making a sunset/sunrise timelapse with ML-deflicker you have to adjust the exposure in post.

The ETTR tries to make the most bright picture,
and deflicker keeps the median of highlights/ midtones constant.
So if the overall scene is getting darker both ETTR and deflicker will brighten up the image.

A1ex is working on an app which is able to ramp the exposure in post.
http://www.magiclantern.fm/forum/index.php?topic=8443.msg78255#msg78255 (http://www.magiclantern.fm/forum/index.php?topic=8443.msg78255#msg78255)

Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: Danne on September 26, 2013, 09:52:08 AM
Thanks Glubber
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: RenatoPhoto on September 26, 2013, 05:40:35 PM
Tested the new module with WB.  Basically set up two frames, begining and end, and the module did a nice job bumping the WB in 50 increments.  The resulting WB changes seemed smooth for the 1 hour tested.  I ramped WB from 3900 to 5000 in 60 frames so it skiped some frames and the bump 50.  I could not tell the jump or the change in WB so I think it is good.

Changing the time is a bit strange but it works, I used the joystick and had a better feel
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on September 28, 2013, 03:11:11 PM
Full day to full night time-lapse:
I used AutoETTR with an aperture ramp. The Av ramp was almost exactly right. I had it start about 15mins after sunset and ramped from f/11 down to f/4 over 15mins, had I made the ramp just a bit longer it would have been perfect. The ramping started right about when AutoETTR hit 25" shutter speed, and it kept ETTR from bumping up the ISO when it hit the max of 30" (I did the ramp just a little to fast and ETTR actually had to compensate the exposure back to 15", somewhere darker this would have probably been just the right speed). Interval time was 45".

I'm excited to try this somewhere much darker than a city!
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: saltador on September 29, 2013, 11:03:27 PM
i must be too slow for this... :)

I'm trying de av-ramp....i got to set first keyframe...ok..that's good..how i set the last keyframe? sory if it was clear i did not see it.

I set the exposure values in canon..
i set a keyframe #1 in ML (A) menu

then what?

sorry...and thanks..
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on September 29, 2013, 11:11:27 PM
Change the the keyframe time menu item under the "new keyframe" menu, then when the settings for that keyframe are like you want select "create keyframe"

Sorry the UI is not the most intuitive, the ML menu API is all I have to work with and wasn't exactly intended for doing complicated data entry like this.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on September 29, 2013, 11:28:52 PM
here's an example, to ramp Av from f/22 to f/4 in 20 frames do this:

You can set keyframes based on time of day as well, just turn "Use Global Time" on, then in the "New Keyframe" menu under keyframe time, you sill see a time (hh:mm:ss) rather than frame # (and on the right side is the current camera time)

To change a keyframe you already created, you can set the keyframe time to the time of the keyframe you wish to edit (if you do this you will see a warning that you will be overwriting an existing keyframe).
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: saltador on September 30, 2013, 04:19:18 AM
weird...i did a short test and upload all  20 images time-lapse to lightroom and i see av ramping but all images are just white and weird ping stripes..can't see nothing...

follow all the steps as you wrote.

only thing i had is advance intervalometer ON , in A menu..could that be the problem..doubt it..will try
without.

thanks.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: saltador on September 30, 2013, 04:22:51 AM
also..i install the las built..sept 28..for 5dii...and drop the advent.mo in the module folder...is this right?

thanks
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on September 30, 2013, 04:35:05 AM
If you can see the A menu and can create keyframes then you have it installed correctly.

If you turn it off then it won't do the ramp when you run the intervalometer, but do a test without it to verify it's not the module causing the white frame thing (could it perhaps be your exposure settings? If your in M mode ramping the Av like this without compensating with shutter or ISO is going to make your image brighter and brighter possibly pure white unless your scene is changing i.e. a sunset) so you should probably run it in Av mode or with AutoETTR turned on.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: saltador on September 30, 2013, 04:50:16 AM
yes i see the A menu..


I'm doing a test in M mode..auto ETTR..always on....no deflickering...av ramp... intervalometerevery 6 sec..

weird..

doing another right now..with a higher intervalometer..now at 12sec..lowest shutter at 1/6..ETTR always on..no deflickering..
will let you know..if i get same messy frames again..

thanks
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: saltador on September 30, 2013, 05:22:48 AM
ok...reporting again..

did a few test...looks like it has to do with this module cause the image preview in the importing window in LR looks fine
but once imported into light room the become a white and colored mess...

I tried it with deflickerin on and off, with different intervals and always the same...

anybody else having issues..

arrrrrrr...

i rather be doing timelapses...hehehe

thanks.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: saltador on September 30, 2013, 06:14:48 AM
my mind keeps insisting...

so i deleted ML from card..droped unified version..add it built 29-09..add it ad_int.mo..did a test and same things..frames look white as it updates previews..

so, i checked the settings and it looks like is doing the av ramp but the iso and shutter are not changing at all..from looking at the exposure setting (frame is all weird colored, not visible at all).

good nite.  :'(
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on September 30, 2013, 12:55:26 PM
You say the previews look fine in Lr, but then it doesn't open right, to me this sounds like a problem with Lr. Do the images look okay in camera? Do they look okay if you open them in a different program? What happens if you just take some pictures with the same settings you have and open them in Lr. What if you put the camera in JPEG mode instead of RAW? Do you have dual_iso turned on? if so you'll have to preprocess them with cr2hdr first or they wont open correctly in other programs.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: saltador on September 30, 2013, 04:38:45 PM
You say the previews look fine in Lr, but then it doesn't open right, to me this sounds like a problem with Lr. Do the images look okay in camera? Do they look okay if you open them in a different program? What happens if you just take some pictures with the same settings you have and open them in Lr. What if you put the camera in JPEG mode instead of RAW? Do you have dual_iso turned on? if so you'll have to preprocess them with cr2hdr first or they wont open correctly in other programs.



yes...you save me here..thank youuu...i was tired testing variations to find the error..and you help me solve this.

In case it happens to others.
I had press the link to dual iso in the auto ETTR menu but i did not load dual iso in the module menu.

I think this is what solve my issue.
now it loads fine in LR
back to more timelapses test.

thanks

I promise to read more ...hehehe...thanks
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: audunbrekke on October 03, 2013, 11:04:01 PM
Hi. This seems like a greate module with many options for manual setting of keyframes. Would it be possible to make a function like the intervallometer with sunset / sunrise that was in earlier ML releases ? The sunset function was like this: the ML would adjust the Tv and iso as needed from exposure metering, but only in one direction for brighter exposures. It was also possible to adjust what the maximum average change could be, to prevent flickering. I know everybody is talking about AETTR, but the intervallometer with sunset function was a fast and easy function.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on October 03, 2013, 11:26:58 PM
This module was not designed to do anything "automatically", IMO AETTR is much faster and easier than the previous sunset/sunrise function. You could however create a manual sunset or sunrise keyframe sequence with the module and save it. The module allows you to save your keyframes, I'm currently working on expanding this a little, right now the filename it saves to is hardcoded, so you can only save and restore one keyframe sequence.

Have you tried the post deflicker option in ML? I've found it works really well as long as you give it enough time to work between frames (5-10secs usually). I think alex is working on making this a tool you run in post, which would be even better.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on October 08, 2013, 02:59:56 AM
Update: added looping
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: Joachim Buambeki on October 20, 2013, 04:57:23 PM
IMO after effects needs a way to keyframe ACR settings, that would be freakin awesome (also very useful for RAW video)
... I might be able to write a script for AE that makes ramping ACR settings easier. I know that the script API for AE has some pretty good integration with the native AE GUI, but I'm not that familiar with the AE scripting..
Did you find time to look into this? Beeing able to do everything within After Effects would be revolutionary!
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on October 21, 2013, 02:14:56 PM
I decided to go with Br instead (hence the script I created), it's much faster. AE takes several seconds to render a RAW frame, even on low quality (this is so annoying, why adobe why?!), Br has some kind of fast preview mode that takes fractions of a second. It's just much easier and faster to do in Br.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: jezhunziker on October 21, 2013, 03:04:44 PM
Wow amazing module!! I've been testing this on 5Dii some great results, a couple of things to report and would be interested to hear thoughts on these... Most of my testing has been with Focus changes...

1./ I have found that focus keyframes require more than 4 second interval otherwise the intervalometer slows down to compensate for change, (could this be improved by adjusting any of the ML focus parameters?)

2./ I find that the most accurate way to determine how many focus steps are required is to frame up scene then choose "Focus Rack End Point" (from ML menu), from here I adjust focus in steps to the desired focal end point and record this number to input into the Adv Int keyframe. Is there a quicker method? ie is it possible to change focus on camera manually and store as a keyframe?

3./ Using 24-105 L lens at 80mm has more steps than at 24mm and at higher zoom (ie 105mm) it can include more than 1000 steps, is it possible to include a higher number in next build ie -3000-3000, (I know it's possible to change the step size to 2 but the focus change isn't as smooth)?

4./ As focus keyframes need camera to be in live view. Is there any way to save battery or turn off Liveview whilst running a time-lapse?

Thanks so much for all amazing work, I'll post some tests shortly,

 8)
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on October 21, 2013, 03:48:33 PM
1. Yes, I've found the same to be true. I used the code in the core that does the focus change. I tried taking some stuff out to speed it up, but it stopped working altogether. I assume that whoever wrote that code knew what they were doing and probably tried to make at fast as they could (they certainly know more than me). I think the only possible improvement would be reverse engineering a lot further Canon's focus control mechanisim, which is way beyond my current abilities.

2. No, there's not really a better way to do this, I wish there was, but again it would probably require more reverse engineering. ML has no way to really figure out how many "steps" the current focus position is at when focused manually. Basically all it can do is step the focus and count the number steps you take. I could potentially at least pull in the focus rack end point setting automatically, but that requires a change to the core (to allow modules to read this value). I've already submitted a pull request for what I would need to do this (and reading/writing many other ML settings), but its still pending.

Perhaps you can spend a little time creating a chart for each lens of steps vs. focus distance. You could even put marks on your lens like the distance markings, with step numbers, if you dont mind defacing your lens. I've thought about doing this to my nifty fifty (also add distance markings too since it doesn't have those either).

3. Thanks for the feedback, I had no idea what the maximum for any possible lens was so I just guessed (none of my lenses step more than several hundred). I'll update that to 5,000 just to be safe.

4. LV has to be running for focus to work but you can try this: http://wiki.magiclantern.fm/userguide#powersave_in_liveview
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: a1ex on October 21, 2013, 03:56:09 PM
I guess it's a good idea to remove the focus ramping from the core, and just leave a basic intervalometer there, right?

Also I'm thinking to merge the module this week, but I want to solve the menu issue first. I thought a bit at how to implement menu with submenus (basically I'll rename submenu_mode to something like submenu_level and keep the existing data structures).
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: jezhunziker on October 21, 2013, 04:22:54 PM
1. Yes, I've found the same to be true. I used the code in the core that does the focus change. I tried taking some stuff out to speed it up, but it stopped working altogether. I assume that whoever wrote that code knew what they were doing and probably tried to make at fast as they could (they certainly know more than me). I think the only possible improvement would be reverse engineering a lot further Canon's focus control mechanisim, which is way beyond my current abilities.

2. No, there's not really a better way to do this, I wish there was, but again it would probably require more reverse engineering. ML has no way to really figure out how many "steps" the current focus position is at when focused manually. Basically all it can do is step the focus and count the number steps you take. I could potentially at least pull in the focus rack end point setting automatically, but that requires a change to the core (to allow modules to read this value). I've already submitted a pull request for what I would need to do this (and reading/writing many other ML settings), but its still pending.

Perhaps you can spend a little time creating a chart for each lens of steps vs. focus distance. You could even put marks on your lens like the distance markings, with step numbers, if you dont mind defacing your lens. I've thought about doing this to my nifty fifty (also add distance markings too since it doesn't have those either).

3. Thanks for the feedback, I had no idea what the maximum for any possible lens was so I just guessed (none of my lenses step more than several hundred). I'll update that to 5,000 just to be safe.

4. LV has to be running for focus to work but you can try this: http://wiki.magiclantern.fm/userguide#powersave_in_liveview

Thanks for reply, adding extra focus steps will be really useful. The Rack focus end point isn't a bad workaround as we all know a good timelapse is all in the setup...

It's strange how much the focal distance effects the number of steps, I wonder if it's constant from one lens to another, I only have one variable focus lens but I could see if it matches number of steps at 50mm against my nifty 50.. I'll try and post a chart for 24-105mm

Thanks for the advise with LiveView - I'll try and find a way to shut off it off once TL is started either that or will need to purchase a few extra batteries..  ;)
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on October 21, 2013, 04:51:59 PM
I guess it's a good idea to remove the focus ramping from the core, and just leave a basic intervalometer there, right?
Yeah

Also I'm thinking to merge the module this week, but I want to solve the menu issue first. I thought a bit at how to implement menu with submenus (basically I'll rename submenu_mode to something like submenu_level and keep the existing data structures).

That'd be great! I'll make the change to the module as soon as you get that done.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: Francis on October 21, 2013, 06:15:05 PM
Thanks for reply, adding extra focus steps will be really useful. The Rack focus end point isn't a bad workaround as we all know a good timelapse is all in the setup...

It's strange how much the focal distance effects the number of steps, I wonder if it's constant from one lens to another, I only have one variable focus lens but I could see if it matches number of steps at 50mm against my nifty 50.. I'll try and post a chart for 24-105mm

Thanks for the advise with LiveView - I'll try and find a way to shut off it off once TL is started either that or will need to purchase a few extra batteries..  ;)

It definitely is not constant from lens to lens. So many variables such as the motor in the lens as well as the range of the focus ring. It's not even consistent within a lens. My 100mm macro feels almost exponential in the proportion to each step (or physical turn of the ring). By this I mean as you go from the closest focal distance to infinity, the sensitivity of the ring substantially increases. This would make sense for a macro lens where you want a lot of control when focusing on objects at a macro range.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: J24 on October 30, 2013, 04:32:00 PM
I use a motion control system so I'd love to have an option to trigger the ramping and shooting with an external (wired) intervalometer.

Another good option would be if it would be possible to do the reverse: sending the shoot signal from the camera to the external controller? My controller can take the signal as input but can the camera send it? In this scenario ML and adv_int would control both the camera and the moco system.

Either functionality would be cool, since it would make the syncing of the shooting with the camera movement MUCH easier. I think Francis might be trying to achieve something similar here:
I want to be able to trigger an intervalometer sequence using an IR or wired remote.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on October 30, 2013, 05:20:07 PM
I use a motion control system so I'd love to have an option to trigger the ramping and shooting with an external (wired) intervalometer.
Should be pretty easy to do, I'll look into it.

My controller can take the signal as input but can the camera send it?
What kind of signal can it take? ML can send various types. Most flexible is probably PTP over USB. It's also possible send a signal on the mic in line by turning the audio amp on/off. Something like this should probably go in it's own module, really easy to write one for it though, there's a CBR for when the intervalometer takes a pic.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: itsskin on October 31, 2013, 03:14:50 AM
Hi! I think it's really cool to add feature like automatic interval ramping.

"ETTR exporure time" + user set X seconds. This will help to avoid overlaping shoot interval with actual exposure time and give AETTR algorithm enough time to read the preview to determine correct exposure.

Lets say we are doing day into the night timelapse. We want 15 sec intervals during the daytime. But later at night exposure time will be 30 seconds. The feature I'm asking for will do this automatically, so we do not have to predict times and set key frames for manual interval ramping.

Thx!
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on October 31, 2013, 01:33:46 PM
Doing it automatically could lead to some situations where you end up with a lot of jitter b/c ettr might be going back and forth between different shutter speeds. It would be kind of like the exposure flicker you get with ettr, except in the time domain (which is not possible to fix like exposure flicker). If you want to ramp the interval period, it is better to carefully plan it and do it manually so you get a nice smooth ramp in speed. Any good timelapse requires meticulous planning anyway.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: itsskin on October 31, 2013, 02:32:10 PM
You are absolutely correct. I do a lot of timelapses and they force me to stay next to the camera for several hours. Your module + AETTR is a way to put camera on "Auto" and do other stuff. I'm getting really great results of this combo + your deflicker script. And do not mind some jitter in time domain - can fix it in post for what I do. If it's not hard to implement, I think a lot of people will say thank you.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on October 31, 2013, 02:59:42 PM
ETTR itself will actually delay the intervalometer a little bit if need be, to do it's thing (but it's pretty fast to run). See the intervalometer section of shoot_task in shoot.c. So you should already be covered.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: J24 on November 04, 2013, 08:21:21 PM
Should be pretty easy to do, I'll look into it.
Great! Would be awesome! :)

What kind of signal can it take? ML can send various types. Most flexible is probably PTP over USB. It's also possible send a signal on the mic in line by turning the audio amp on/off. Something like this should probably go in it's own module, --
It takes a shutter signal through a 3.5mm plug. Using the mic in sound like a good idea, since it would enable me to use an ordinary stereo audio cable. I might implement this as a separate module, as you suggested. Although, I might not need it, at least for now, if remote shutters gets implemented in your module.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: taneryildirim on November 24, 2013, 03:27:59 PM
Respect to you all! Really cool thing.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: francesco mazzeo on December 24, 2013, 01:16:52 PM
How to install bulb/focus ramping on Canon 6d? I have only Intervallometer and Bulb Timer. Thank at all! Merry Christmas.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on December 24, 2013, 08:45:43 PM
How to install bulb/focus ramping on Canon 6d? I have only Intervallometer and Bulb Timer. Thank at all! Merry Christmas.

Read the OP of this thread:

To use, download the latest nightly (http://builds.magiclantern.fm/) and add this module to the ML/modules folder:
https://bitbucket.org/dmilligan/magic-lantern/downloads/adv_int.mo

See the readme (https://bitbucket.org/dmilligan/magic-lantern/src/fcbdae3b45a6b9bef6a1c07597ac3055a3c08331/modules/adv_int/?at=adv_int) for instructions on how to use:
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: francesco mazzeo on December 24, 2013, 11:49:13 PM
Thank you dmilligan.
I have already Advanced Intervalometer  (ADV) on Canon 6d. I 'm serarching for Bulb/Focus Ramping in shot tools;)
Best ADV or Bulb/focus ramping for timelaps without flickering?
Thank you again. Merry Christams to all :)

Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: pilgrimage on December 27, 2013, 11:08:15 PM
Hi Dmilligan Pls say to me How Can I Use to adv with auto ettr + Post deflicker or just adv ? Which can ı use to parameter ?

thankyou.

Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on December 29, 2013, 12:44:58 AM
Well, there would be several ways you could use the two together. AutoETTR can automatically set shutter (Tv) or ISO; adv_int can manually ramp many things. Typically what I do is to use adv_int to manually control aperture (Av), and let AETTR automatically control Tv and ISO.

Typically for a sunset, I would start with the Av pretty small (say f/16), then I would have it ramp up to wide open (f/2.8 or whatever wide open is for your lens). Use the 'global time' mode. I usually have the ramp start about 5 minutes after sunset, and end 20 minutes after sunset (so the Av is wide open by 20 mins after sunset), but you may have to play with this some depending on your camera, lens, and location/scene.

Use the AETTR with default settings, except change the slowest shutter to about 2-5 seconds less than timer interval. Typically I use 35 second interval and 30 second slowest shutter or maybe 30 second interval and 25 second slowest shutter.

If you do your deflickering in post rather than in camera, you don't have to worry about giving enough time between exposures for ML Post Deflicker to do it's thing (usually you need to give it ~5-10 seconds). I have a script (http://www.magiclantern.fm/forum/index.php?topic=8850.0) for bridge that will let you deflicker in post.

If you wanted even more control you could ramp both Tv and Av manually with adv_int (this would be a lot harder to get right, and probably require some significant trial and error), and just let AETTR set the ISO. One thing you could potentially do with this though, is use a smaller interval period at first, and slow it down as it gets dark, allowing a slower shutter, basically you could keep your 'shutter angle' fixed. I haven't tried this, it would be pretty hard to get right.

I would recommend that you get fully familiar with using just AETTR for timelapse if you haven't already done so, before trying to use adv_int along with it.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: pilgrimage on January 12, 2014, 10:34:23 PM
Thankyou Very Much My Friend.I Tried your information.

Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: joebone on February 06, 2014, 04:53:29 AM
I have really enjoyed the FPS override to make time lapses.  I know its easy mode, but if theres any way to port this over to movie mode and FPS override then that would be awesome.  If it already does that then my bad for being a dummy?

also an exponential change between keyframes would be amazing.  Going from time flying by to standing still and back.

Anyways,  awesome module.  a thousand thanks. I continue to be amazed by all that you guys are pulling out of these cameras.
 
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on February 06, 2014, 01:57:06 PM
That sounds really difficult but potentially doable, not possible with this module though, and probably also beyond my skill level. You'd have to mess with all the engio timers on the fly, I'm not sure if I even fully understand how they work, or if that's even possible.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: joebone on February 06, 2014, 04:49:54 PM
That sounds really difficult but potentially doable, not possible with this module though, and probably also beyond my skill level. You'd have to mess with all the engio timers on the fly, I'm not sure if I even fully understand how they work, or if that's even possible.

k thanks for the quick feedback, awesome mod all the same, thanks
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: Freemountain on February 09, 2014, 04:56:15 PM
Do I get it right that autoramping is not yet available for the 6D? I read through the entire thread but answer weren't clear to me;)
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on February 10, 2014, 12:06:12 AM
I'm not really sure what you're talking about, I've never heard of "autoramping". Perhaps you are asking if AutoETTR is working on the 6D? I have no idea, and this thread isn't really the appropriate place to ask. Currently the 6D is considered "unsupported" as there is no developer with a 6D who is maintaining that port. There is a guy who is working on his own fork, but he doesn't contribute anything back to ML.

As far as this module is concerned, it should work fine on any camera supported by ML, there's nothing platform (camera) specific and only it uses very basic ML core functions.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: marcos bcn on March 01, 2014, 02:08:38 AM
Modules menu : adv_ int said: old API.
And in red at the bottom said wrong version (v4.0, expected v5.o)
How to install it please.
Thank you
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on March 01, 2014, 02:19:20 AM
New version coming very soon, I'll update this thread with new instructions/screenshots/examples when it's ready.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: carbo on March 07, 2014, 05:21:11 AM
I'm not really sure what you're talking about, I've never heard of "autoramping". Perhaps you are asking if AutoETTR is working on the 6D? I have no idea, and this thread isn't really the appropriate place to ask. Currently the 6D is considered "unsupported" as there is no developer with a 6D who is maintaining that port. There is a guy who is working on his own fork, but he doesn't contribute anything back to ML.

As far as this module is concerned, it should work fine on any camera supported by ML, there's nothing platform (camera) specific and only it uses very basic ML core functions.

Hi there I think he may be referring to  Bulb/Focus Ramping as described in the manual here http://wiki.magiclantern.fm/userguide#bulb_focus_ramping (http://wiki.magiclantern.fm/userguide#bulb_focus_ramping) .

It doesn't seem to be available on the 6D?
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on March 07, 2014, 12:47:27 PM
Bulb ramping was removed in favor of AutoETTR, it's not available on any camera ATM. Focus ramping may eventually be removed and replaced with this module once it gets merged (since the focus ramping capabilities in this module are more advanced)
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on March 08, 2014, 09:58:24 PM
some updates, see OP
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: PaulJBis on March 15, 2014, 10:53:33 PM
Hello. I've been trying out this module this afternoon, and I have some doubts that I couldn't find the answer for. Sorry if this was answered somewhere else and it escaped me:

1) I take it that you can't delete keyframes right now. Am I wrong?
2) When creating a keyframe, why can't you set the shutter to less than 1/24?
3) Speaking of which, what's the difference between the shutter setting and the bulb duration one? I created several keyframes varying aperture and bulb duration, but the latter didn't change.

I should mention that I'm not using AutoETTR yet, since I want to get a feel for this module on its own first.

Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on March 16, 2014, 12:13:53 AM
1) Sort of, you can only delete all the keyframes, but not individual ones, maybe I'll add a way to do this.
2) I just copied the shutter stuff from the ML expo menu as a convenience to let you change the shutter w/o having to leave the menu, if you want to use a shutter longer than 1/24, set it from the Canon menu. A fix for this would require a change to ML core not this module (try setting the shutter from the ML expo menu, you'll notice the same behavior).
3) Shutter is when you're not Bulb mode (M, Av, Tv, etc), bulb timer is for when you're in Bulb mode (B). There should be menu warnings when you are in a different mode, are there not?

EDIT: just checked #3 and the warnings aren't right for bulb timer, I'll see if I can fix it
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: PaulJBis on March 16, 2014, 01:34:49 AM
Thanks for your answer. Another thing: I've noticed that, if you add keyframes in the "wrong" chronological order (adding first the last ones, etc.), they still get executed, but they don't get cleared from the list afterwards. Is that the correct behavior? Is there any limitation when it comes to the order in which keyframes have to be introduced?
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on March 16, 2014, 04:27:27 AM
I'm not really sure how that could happen, new keyframes are inserted into the list in order so there should be no difference in what order you create them in. Secondly, the data structure I'm using for the keyframes is a linked list. To 'clear' it all I do is create a new head (and deallocate any memory I was using). Worst case scenario is a small memory leak if I don't deallocate everything properly (basically I'm creating a totally new list when you hit clear there's no way for anything to stick around).
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: noealz on March 19, 2014, 12:58:16 PM
It was mentioned previously before but is there anyway to reinclude the holy grail auto ramp exposure? I understand that others find the new ettr easier but others like myself are quite fond of the LRTimelapse software which requires one stop increments
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on March 19, 2014, 05:51:25 PM
quite fond of the LRTimelapse software which requires one stop increments
You should try my script (http://www.magiclantern.fm/forum/index.php?topic=8850.0) for Bridge it's free and works great with AutoETTR (no sort of 1 stop requirements). You could also use darktable (http://www.darktable.org) (also free and open source) if you don't have Bridge, the deflicker was recently ported to that program.

I don't think any developers are going to bring the old way back. (IMHO, ettr is superior, easier and less buggy anyway)
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: PaulJBis on March 19, 2014, 09:20:09 PM
It was mentioned previously before but is there anyway to reinclude the holy grail auto ramp exposure?



Ramping exposure is certainly more intuitive for things like sunset timelapses. This said, I've been experimenting myself with AutoETTR and this module, and it seems to work quite well. The only problems I find are:

-AutoETTR tends to overexpose (and blow out) the night pics. a1ex pointed me to the SNR limits options, and they indeed seem to work... Which brings the question: would it be possible to keyframe and ramp the SNR limits?   ;D (A value of 6 works for daylight shots, while 4 is better for nighttime ones).

-Using the deflicker script precludes you from importing your raw sequence to After Effects in HDR 32 bits, following this recipe by Stu Maschwitz:

http://prolost.com/blog/2006/3/16/linear-color-workflow-in-ae7-part-6.html

Since it also uses Camera Raw and sets the values for the entire sequence... and it uses process 2010.

dmilligan: would the exposure compensation values that your script sets change too much if they were calculated using process 2010, instead of 2012? Or is that irrelevant? Also, I read that you started developing your script for AE before switching to Bridge, because AE was too slow. How slow would you say it was? 10x slower? 50x slower?

(I'm asking because I'm considering porting it to AE, so that I can use it in conjunction with a linear 32-bit workflow, but I'd like to know before if the slowdown makes it unusable).

Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on March 19, 2014, 10:27:40 PM
-AutoETTR tends to overexpose (and blow out) the night pics. a1ex pointed me to the SNR limits options, and they indeed seem to work... Which brings the question: would it be possible to keyframe and ramp the SNR limits?   ;D (A value of 6 works for daylight shots, while 4 is better for nighttime ones).
Yes, it would be possible for the module to ramp ettr settings. Personally, I don't fool with the SNR limits. I usually hit my exposure limits at night anyway, it must not be very dark where you are ;)

-Using the deflicker script precludes you from importing your raw sequence to After Effects in HDR 32 bits, following this recipe by Stu Maschwitz:
Uh, last time I checked there's only 14 bits of data in a CR2. There's no benefit to using 32 bit in AE. 16-bits is more than plenty to fully represent every possible value in a RAW file. (If you use a 16bit workflow in AE, nothing will be clipped that wasn't already clipped in the original RAW file, 32 bit is unnecessary unless you're actually doing HDRI and have HDR merged 32 bit TIFFs or something that you're running through my script, in which case you should be able to get 32 bit output into AE just fine)

would the exposure compensation values that your script sets change too much if they were calculated using process 2010, instead of 2012? Or is that irrelevant?
nope, it should be easy to change to script to use process 2010 if you want to, but I don't think it will make much difference

Also, I read that you started developing your script for AE before switching to Bridge, because AE was too slow. How slow would you say it was? 10x slower? 50x slower?
IDK, that's not really what happened. AE is really slow at rendering previews, because it renders the full size CR2 when you try to playback a RAW sequence. Bridge renders quick, low-res thumbnail previews. It's much faster to use these to preview your sequence then to wait for AE to render out something. Just try it.

The other main reason I used Br is that you get the multi-file ACR dialog and you can preview your ACR settings on any image in the sequence (AE only lets you see the very first image). You often need to ramp stuff like WB, and it's just much easier in Br with being able to star keyframes, open them all in the ACR dialog, match up the WB, then apply a ramp with the script.

If AE gave you some kind of access to ACR parameters like the way the effects work, and you could create keyframes for them and such, then AE would be much faster and easier. But that's just not possible.

It's not so much the speed of the deflicker algorithm, but the UI is better and easier and it's just faster for me to do the things I need to do. You might very well get the deflicker itself to run faster in AE, IDK.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: noealz on March 20, 2014, 03:26:25 AM
If ETTR is here to stay and theres no way to bring back the one stop holy grail ramping method, then I have just one question.

Does ETTR exposure continuously rise only?

There are times when you are doing a timelapse when the exposure changes because of a cloud or something and so exposure takes a small dip but after it passes it goes up again and this causes problems with flicker too.

Does ETTR exposure only rise without taking those small dips? Because that would be very nice.

I hope that I was able to put it into the right words.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: Audionut on March 20, 2014, 03:40:28 AM
AutoETTR is an exposure tool.  So exposure settings change with scene luminance changes. 

http://www.magiclantern.fm/forum/index.php?topic=8850.0
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: noealz on March 20, 2014, 04:55:14 AM
If there was a way to prevent an ettr timelapse ramping timelapse to go down in exposure and only increase in exposure, it would be very good and prevent flicker.

I know there is a deflicker option but this could help eliminate that step.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: Audionut on March 20, 2014, 05:00:29 AM
It would not prevent flicker.  It would simply limit exposure increments to increases.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: PaulJBis on March 21, 2014, 09:18:41 PM
Yes, it would be possible for the module to ramp ettr settings. Personally, I don't fool with the SNR limits. I usually hit my exposure limits at night anyway, it must not be very dark where you are ;)

Bright lights, big city  :) . I'd imagine that changing SNR limits would be useful, for example, when doing a day-to-night timelapse of New York (not that I live there, nor is my city *that* bright, but there's plenty of artificial light here).


Uh, last time I checked there's only 14 bits of data in a CR2. There's no benefit to using 32 bit in AE. 16-bits is more than plenty to fully represent every possible value in a RAW file. (If you use a 16bit workflow in AE, nothing will be clipped that wasn't already clipped in the original RAW file, 32 bit is unnecessary unless you're actually doing HDRI and have HDR merged 32 bit TIFFs or something that you're running through my script, in which case you should be able to get 32 bit output into AE just fine)

I know Canon CR2 only has 14 bits, but even so, there are advantages in working in 32 bits (after all, even the Red Epic's sensor is only 14 bits too, and people in the film/VFX industry work regularly in 32 bit float). The advantage is not so much in the "32 bits" part, but more in the "floating point" part. Working in float gives your software more precision when applying color grades, and allows you to stack up color correction tools non-destructively, even if the original source material is less than 32 bits.

Anyway, since I prefer to use the grading and keyframing tools in AE, what I'm trying to do is to import the full dynamic range of the original raw into AE, preserving detail in the highlights so that they aren't already "pre-clipped" when AE touches them. Stu Maschwitz's recipe is designed precisely to do that. I'll post here with further updates when I start porting your script to AE.

Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: firstlight on April 30, 2014, 09:36:21 PM
I'm trying to start a timelapse at f3.5 iso1600 in aperture priority mode at night for the stars, and then have it ramp to f8 iso100 around sunrise. It is in take pics like crazy mode so there's no delay between frames. I have the settings changed just like described here but the settings don't change at the set global time. Is this because the camera has to be in M mode and not AV? This is on a 550d by the way... Thanks a lot, I'm stumped and really want to get this working ASAP!
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on May 01, 2014, 12:32:23 AM
I'd highly recommend using AutoETTR as opposed to Av. I also highly recommend setting a fixed interval, you do typically want some time between frames, and you really want a fixed interval (or a smoothly ramping one). With exposure being chosen by an automatic routine, the shutter time will jump around which will cause all sorts of strange temporal jitter. Exposure flicker we can handle easily, but temporal jitter is impossible to fix.

As for why it's not ramping, do you see the 'Ramping ...' appear on the screen? You do have to set at least two keyframes (it won't just start from where you are). A screenshot of the menu settings and also the 'List Keyframes' would be helpful to figure out what's going on.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: DoryBreaux on May 19, 2014, 08:58:01 PM
Anyone else having trouble with this on the 7D? Or am I just missing something here...  :)
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on May 19, 2014, 09:58:35 PM
care to elaborate?
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: DoryBreaux on May 28, 2014, 02:34:16 AM
I've tried to set it up several times and it wont ramp anything.

Set the camera to the initial state
Set Keyframe
Back to canon menu and set second keyframe state
Set keyframe
etc
Turn intervalometer on and set normal properties
Start sequence

Stays at the last state the camera was set at.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on May 28, 2014, 04:58:24 AM
Set everything up like you did and then goto "List Keyframes" and tell me what it says, or just take a screenshot of it, or do a "Save" and post the contents of the save file (SEQ.TXT in the ML config directory).
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: DoryBreaux on May 28, 2014, 08:42:34 PM
https://www.dropbox.com/s/i6ganqhmjpoq3fy/20140528_113401.jpg (https://www.dropbox.com/s/i6ganqhmjpoq3fy/20140528_113401.jpg)

When I start the sequence, it holds in the current state and seems to completely ignore the keyframes.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on May 29, 2014, 01:05:45 AM
Does it work if you don't use global time?
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: DoryBreaux on May 29, 2014, 06:53:14 AM
I was using global time.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on May 29, 2014, 01:50:49 PM
I know. Does it work if you don't use global time?
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: DoryBreaux on May 31, 2014, 05:17:11 AM
Oh, ha. No it doesnt.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: RLaudi on June 09, 2014, 10:07:19 AM
@dmilligan: while I was looking into the picoC/TCC scripting option of ML to implement some ramping ideas (and had to find out it's disabled at the moment) I bumped into your brilliant adv_int module which does exactly what I was looking for, so thank you very much for this great tool!
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: johnpooley3 on June 22, 2014, 11:13:01 PM
@dmilligan Thank you very much for your work on this awesome module, this is exactly what I have been trying to find for a while now.

I am running a 650D with Nightly.2014Jun22.650D104 (Because it's the only one I could get the module to load on) and have set the keyframes and have enabled the intervalometer correctly, but the camera never actually ramps the attributes once I begin the sequence. Rather than gradually change the attributes, the attributes remain at their state previous to the start of the intervalometer (which would be the state of the first keyframe or if I forget to change it back, the state of the last keyframe). I am using frame timing rather than clock, and have tried saving and clearing keyframes repeatedly to no avail. The list of keyframes correctly shows the keyframes I've set. What could I be doing wrong?
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on June 22, 2014, 11:35:21 PM
Do you see "Ramping..." on the screen when running?
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: johnpooley3 on June 23, 2014, 12:11:06 AM
Do you see "Ramping..." on the screen when running?

Nope I only ever see the intervalometer timer and the pictures taken counter...
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on June 23, 2014, 01:08:01 AM
It will say "Ramping" if it's doing some ramping so if it doesn't then there's something about your keyframes that is making it think there's nothing to ramp. There are a couple of caveats: you need to have an initial keyframe (if you only make 1 keyframe it won't work). Any parameters you're ramping should be enabled for all keyframes => you can't do something like t1: Tv, t10: Av, t20: Tv, t30 Av
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: johnpooley3 on June 24, 2014, 12:02:58 AM
@dmilligan could you take a look at this album: http://imgur.com/a/Ni24I

I took a picture of every step and was unable to get the "Ramping" indicator.

Thanks!
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on June 24, 2014, 03:49:29 AM
okay, it doesn't appear you have done anything wrong, that setup should work, and it works just fine on my cameras, there must be something strange going on that is specific to the 650D, as I don't have one, I can't really troubleshoot it myself. Does it work if you use "External Source"? (For "External Source" to work you need to have image review enabled) If it does then there's probably something wrong with CBR_INTERVALOMETER, which should be getting called from shoot_task.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: johnpooley3 on June 24, 2014, 04:55:32 AM
@dmilligan Well that's intriguing... If I enable external source and live view then it does ramp correctly
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on June 24, 2014, 02:25:41 PM
"External Source" triggers off of a change in GUI state to QR (quick review), basically this always triggers after picture is taken and the camera enters QR. When "External Source" is off, it triggers off of a CBR (callback routine) that is internal to ML called CBR_INTERVALOMETER. This should be getting called by the ML "core" after each time the intervalometer takes a photo. It appears there is something going wrong here and my cbr isn't getting called (i.e. the module isn't getting notified by the core when the intervalometer takes a photo like it should be). If I have some time and can manage to get QEMU up and running I might be able to debug it, but I have no idea what could be wrong, it doesn't make much sense.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: fauxtoejoe on July 31, 2014, 06:28:58 PM
 I'd love to try this out, but cant seem to find the right combination of nightly build and adv_int.mo.
I get the "wrong version (v5.0, expected v6.0)" when loading.
Is v6.0 available?
Does anyone know of  a nightly that works with v5.0?

Thanks.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on August 01, 2014, 02:46:35 AM
I updated it, download again.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: fauxtoejoe on August 05, 2014, 01:16:25 AM
@dmilligan Thank you very much!  It works. I've been testing it all day and I think this will be one of the most useful modules I've used. Still trying to figure some stuff out though...

I'm unclear about exactly what 'focus steps' are. Are these fixed units of distance, or are they relative to each lens' range? I hope I'm phrasing this right...
Does one step equal 1/5000th of a lens' range? This doesn't seem right, so why is the option for +/-5000?
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on August 05, 2014, 01:21:30 AM
It's different per lens. It's just the smallest amount you can move the lens focus motor.  Different lenses have different ranges. 5000 is just arbitrarily large to hopefully accommodate any lens.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: stevek1006 on August 09, 2014, 03:20:57 AM
I am a complete nubie. I have Aug 8 build of Magic Lantern running fine on my 7D. I copied adv_int to the module folder and it appears in the menu, but when I activate it in the Module Menu and restart the camera, I get the following error message:

tcc: error: undefined symbol 'get_config_var'
tcc: error: undefined symbol 'set_config_var'
  [E] failed to link modules

Any help would be greatly appreciated.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: Walter Schulz on August 09, 2014, 09:02:40 AM
Delete AUTOEXEC.BIN and ML folder.
Copy extracted nightly contents to card's root.
Copy adv_int.mo into module folder.
Results?
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on August 09, 2014, 01:17:05 PM
Aug 8 of what year? You'd probably get that message if you were using a build from Aug 8 2013.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: stevek1006 on August 10, 2014, 08:24:12 PM
I am using the 08AUG2014 nightly build.  Walter, I will try your suggestion as soon as I return from vacation Thanks.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: beo on September 11, 2014, 01:24:53 PM
Great module!!!
Can you  explain better how to use the keyframes for focus?
Thank's
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on September 11, 2014, 06:21:26 PM
The value for a focus keyframe is the "number of steps" positive or negative from the current lens position (negative means closer IIRC). A "step" is rather arbitrary and depends on the lens. To figure out how many steps you want to move for your particular scene and lens, use the rack focus feature in the ML Focus menu (the "steps" talked about in that menu are the same as what I refer to here). Also make sure you have plenty of time between frames, b/c changing focus is somewhat slow (you also have to be in LV).
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: jimbr549 on October 10, 2014, 08:02:17 PM
This is brilliant!  I can see so many uses for it.

Dmilligan, since you seem very up to speed on ML's intervalometer, I have a quick question.

Do you think it would be possible to create a setting in the intervalometer based on this formula:

shutter speed (dynamic) + write time (fixed) = interval.

That is to say, if I set my write time as 2 seconds, the interval dynamically changes to the shutter speed plus 2 seconds even as i ramp the shutter speed up or down.

That would be very useful!

Thanks for your input.

Jim
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: ShaunWoo on November 26, 2014, 12:12:08 AM
got the same messege as:
fauxtoejoe


"wrong version (v5.0, expected v6.0)" when loading."
even thought you said you updated it download again, because i downloaded it today as of 2014.11.25 using this link:

https://bitbucket.org/dmilligan/magic-lantern/downloads/adv_int.mo
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on November 26, 2014, 03:41:13 AM
What is the date of the nightly build you are using?
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: Ottoga on November 27, 2014, 10:30:41 AM
Quote
From dmilligan

here's an example, to ramp Av from f/22 to f/4 in 20 frames do this:
  • set the Av to f/22 in canon
  • go into ML menu
  • A > New Keyframe...
  • Select "Aperture" menu item and turn it ON (this means this parameter will be included in the keyframe)
  • Select "Create Keyframe"
  • go back to canon and change the Av to f/4
  • go into ML menu
  • A > New Keyframe...
  • Change "Keyframe Time" to 20
  • "Aperture" should still be "ON"
  • Select "Create Keyframe"
  • Go back up one level and select "List Keyframes", you should see two, T=1 and T=20
You can set keyframes based on time of day as well, just turn "Use Global Time" on, then in the "New Keyframe" menu under keyframe time, you sill see a time (hh:mm:ss) rather than frame # (and on the right side is the current camera time)

To change a keyframe you already created, you can set the keyframe time to the time of the keyframe you wish to edit (if you do this you will see a warning that you will be overwriting an existing keyframe).

I have installed the adv_int module on my 7D today and tried the above example. I have tried it both in manual and AV mode without any apparent success. Whilst the intervalometer takes a photo at the defined time intervals there is no change in the aperture. Each photo is taken using whatever aperture happens to be dialed in on the Canon at the time. Esssentially every photo is exactly the same bar any movements due to the time differences.

Have I overlooked some critical preparation step/s not detailed in the example? or does it not actually work on the 7D?

Any thoughts?  Thanks in advance for any suggestions.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on November 27, 2014, 05:11:43 PM
Does it say "Ramping..." on the screen when the intervalometer is running?
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: Ottoga on November 28, 2014, 03:09:32 AM
No it didn't.

Today I decided to reset ML back to default settings and try again in case I had some conflicting setting enabled.

This seems to have resolved the issue. I aso changed the order that I established the intervalometer and advance intervalometer settings.

In this attempt I:
- set the key frames first,
- then enabled the adv_Int function
- then set the intervalometer parameters
- lastly enabled the intervalometer
- Turned on liveview.

In my original attempt the workflow was in the reverse order (I'll try his again and see if it was the issue, I expect not)

So I guess all good. Thanks for your efforts in developing and supporting this module.

Time to get more adventurous.

Cheers.... Otto
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: beanz on January 15, 2015, 10:15:25 AM
Is it possible to lower the interval to .5 sec instead of 1 sec either in camera or adjusting the code?
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on January 15, 2015, 01:32:21 PM
No
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: beanz on January 23, 2015, 06:13:43 PM
Too hard basket?
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on January 23, 2015, 07:12:52 PM
not possible in a module
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: beanz on January 24, 2015, 03:27:00 AM
Ok mate cheers.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: georgegates5 on February 13, 2015, 05:19:34 AM
Would like to ask why isnt this module availble even in the latest nightly build (29/1/2015 ) for canon 60D? .Any ideas or does this module needs to be downloaded separately ?
Title: Intervalometer Ramping Module (adv_int.mo)
Post by: DeafEyeJedi on February 13, 2015, 05:28:47 AM
Download link is here (https://bitbucket.org/dmilligan/magic-lantern/downloads/adv_int.mo). (It is actually on the first post - please read!)

Add it into the Module folder within ML on your card.

Be sure to enable it on under Modules section in ML menu and then restart camera.

Good luck!
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: jfgout on March 24, 2015, 02:42:31 PM
This module seems extremely useful for what I want to do (pictures of a lunar eclipse), thanks for making this available. Unfortunately, I'm having some big issues running it on a 5D Mark II (ML nightly build March 22, 2015). The ramping seems to work only ~1 in 10 times and I cannot figure out what makes it work/not work (although re-booting and starting from fresh seems to help).
For example, I would set the ML intervalometer to take 8 pictures with 3 seconds interval (start when taking first picture) and turn on the advanced intervallmeter with the following keyframes:
- keyframe 1 (=after 3secs): Shutter speed = 1/2000
- keyframe 4 (=after 12secs): Shutter speed = 1/800

When I exit the menu, my shutter speed on the canon display is set to 1/800... So, I put it back to 1/2000 and start the series of pictures. The intervalometer works fine (it takes the 8 pictures, with 3 seconds in-between each) but there is no ramping at all! I was hoping to see ny shutter speed move up to 1/800 at frame #4 (with possibly some ramping between on frames 3 and 4), but no, nothing. It's like the advanced intervalometer is not doing anything!

I checked the list of keyframes before starting the series of pictures and my 2 keyframes show up correctly. I also tried with external trigger ON/OFF, but no luck.

I ran maybe 20 tests like that, trying to reboot, change the start/end parameters, ... and maybe 2 or 3 times it did what I wanted but I could not figure out why it worked on these specific occasions but not the rest of the time.

Any help would be much appreciated!

Thanks,

jf
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on March 24, 2015, 10:38:11 PM
It seems there's an issue with the 'take a pic' trigger. It should work fine with 'leave menu'. I'll see if I can fix it.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: jfgout on March 25, 2015, 12:35:01 AM
Thanks for the answer @dmilligan. Using "Leave menu" instead of "Take a pic" to start the sequence seems to work!
The shutter speed is now updated at the given keyframes. However, I still have a problem when trying to change the interval time. I tried to reduce interval time from 5 seconds (the parameter given in the 'normal' ML intervalometer) to 2 seconds on the third keyframe but it did not work. I'll try to run more tests tonight. One possible problem is that I was trying to change both shutter speed and interval time on this keyframe. Shutter speed did change correctly, but not interval. Maybe I should try with a key frame dedicated to changing interval.
Also, is the interval ramped or is it an absolute changed? For example, say I start with an interval of 10 seconds, and I set a keyframe to change the interval to 1 second at the 10th frame. Will the interval be 10 seconds for the first 10 images and then switch to 1 second or will the interval slowly decrease from 10 seconds, to 9, then 9, 8, 7... all the way to 1 second? If it is the latter, I imagine that one solution to obtain a direct transition would be to add a keyframe just before the one with interval=1second and set it to interval=10sec, so that there would be no ramping.

Thanks again for providing this very useful module to the community !

jf
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: jfgout on March 26, 2015, 03:24:37 PM
OK, so it looks like creating a keyframe dedicated to changing the interval time works! Maybe there is a bog in the code when changing multiple parameters in one keyframe? I'll try to have a look at the code when I have a minute.

jf
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on March 26, 2015, 04:15:41 PM
One possible problem is that I was trying to change both shutter speed and interval time on this keyframe. Shutter speed did change correctly, but not interval. Maybe I should try with a key frame dedicated to changing interval.

You can change multiple things in a keyframe, but if you want to do this, you need to have those items in *every* keyframe you make, otherwise it won't work correctly. Getting around this limitation is possible, but would add a lot of complexity to the code.

Example:

keyframes like this won't work:
Code: [Select]
T=1   Tv=30", Av=f/2.8
T=10  Tv=10"
T=20  Av=f/8

you have to do this:
Code: [Select]
T=1   Tv=30", Av=f/2.8
T=10  Tv=10", Av=f/4
T=20  Tv=10", Av=f/8

Also, is the interval ramped or is it an absolute changed?
Everything is ramped, always. The solution like you say is to simply create adjacent keyframes with the transition.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: jfgout on March 31, 2015, 07:06:03 PM
Thanks for the precisions. The eclipse is only 3 days ago... I hope everything works!

jf
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: squidman90 on June 13, 2015, 05:37:26 PM
hey there,

Just wanna get some opinions on making sunset time lapses using this adv_int.mo module. I've installed it on my ML Canon 7D and seems to work fine.

I'm planning next week to do a time lapse of the sunset from roughly 5pm to (Night) 6.40pm.  I'm bit of a newb so bare with me.
I understand bulb ramping and I want to ramp my shutter speed (Tv) over the course of roughly 2 hours to pitch black (night). I'm thinking of having constant ISO and Aperture - as I'm shooting mountains and don't want to change my depth of field.  I notice people keep talking about using auto-ETTR when using this module but i don't quite understand it.

I'm thinking of starting the shooting at 5.07pm which is civil twilight with these settings - (Tv) 1/8, (Av) 5.0 , (ISO) 150
then have it ramp to 6.41pm with - (Tv) 5 ", (Av) 5.0 , (ISO) 150   <<rough guess

I've work out that with a Interval of 10 seconds it would take 600 shots to get to the duration of 1 hr 40 min.

So therefore my plan would be to input keyframe settings as below.
Keyframe - Time 1           Keyframe - Time 600
Shutter - 1.8 "                 Shutter - 5.0 seconds
Aperture - 5.0                   Aperture - 5.0
ISO - 150                        ISO - 150

Questions that are coming into my mind - when the exposure is ramping (inclining) does it do it linear?  I would believe the suns light goes down in logarithmic fashion?.
Also i think it would go longer than 1 hr 40 min as when the shutter speeds time keeps increasing it adds to overall time, right?

Before i go any further i would love to get your opinions?

thanks matt

Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on June 13, 2015, 08:32:00 PM
It would be extremely difficult to guess exposure correctly, and what you're describing is not really the intention of this module. I would suggest following this method: http://www.magiclantern.fm/forum/index.php?topic=5705.0
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: leandroprz on July 29, 2015, 04:03:37 PM
Lately I've been reading about this module and after experimenting a bit I noticed the interval ramping only works with integers. Would it be possible to change that behavior to have it ramp using decimal intervals? That way it would be more accurate and more similar to a bulb ramping when used along with Auto ETTR.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on July 29, 2015, 11:01:24 PM
I assume you're talking about the "interval time" being in integer seconds? The current ML intervalometer implementation is only accurate to seconds (it only allows integer number of seconds as the interval)
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: leandroprz on July 30, 2015, 06:27:00 AM
Yes, that's what I meant. So even though this is a separate module you can't change that behavior? Is that because it depends on the core intervalometer?
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on July 30, 2015, 01:00:06 PM
correct
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: keepersdungeon on December 05, 2015, 06:32:35 PM
This is amazing! I've just heard of it. Was wondering Why it's added to the nightly builds by default? Anw thanks for sharing this!
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: pdiegmann on December 08, 2015, 08:35:11 AM
Hi everyone!

Really seems to be just the plugin I needed. I just got a question regarding an external intervalometer. Which settings should I use for "Take a pic every" and "Start trigger" to leave the timing up to the external intervalometer (assuming I already have set "Advanced Intervalometer" -> "External Source" to "on").

Thank you for your help and this great plugin!

Best,
Phil
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on December 08, 2015, 12:51:55 PM
If you are using an external intervalometer, the internal one should be turned off, and the settings for it don't matter. Only make sure that 'Advanced Intervalometer' is enabled and set to 'External Source'
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: pdiegmann on December 08, 2015, 01:40:29 PM
If you are using an external intervalometer, the internal one should be turned off, and the settings for it don't matter. Only make sure that 'Advanced Intervalometer' is enabled and set to 'External Source'

I've connected the external intervalometer via the standard cable and tried it with different settings. If I have the intervalometer setting set to on, i get more shots than planned, as both the internal intervalometer as well as my external one are firing. If I disable the internal intervalometer, but have keyframes set, these keyframes have no effect. I'm using a 5DIII with ML 1.2.3. I attached some screenshots of the settings used.

Thank you for any ideas :)

(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fs27.postimg.org%2Fnwsqycj7z%2FVRAM0.jpg&hash=92743783071d001567596b1cf30b3f33) (http://postimg.org/image/nwsqycj7z/) (https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fs27.postimg.org%2Fs77etxob3%2FVRAM1.jpg&hash=cfbf5852ba24b5f9c2fef0f9128dcb3e) (http://postimg.org/image/s77etxob3/) (https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fs27.postimg.org%2Foovexjnf3%2FVRAM2.jpg&hash=1fe602b0ac160423bcb67896e1c6d892) (http://postimg.org/image/oovexjnf3/)
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on December 08, 2015, 10:38:29 PM
You need to turn regular ML intervalometer off. Only Advanced Intervalometer should be On.

Do you have image review off in Canon Menu? Works fine here as long as image review is not turned off.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: pdiegmann on December 09, 2015, 08:49:58 AM
You need to turn regular ML intervalometer off. Only Advanced Intervalometer should be On.

Do you have image review off in Canon Menu? Works fine here as long as image review is not turned off.

Okay, I just tried your suggestions, but the keyframes do not have any effect, neither on ISO, nor on Aperture.
Do you see any setting I set wrong? Preview is currently set to 2 seconds.

(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fs14.postimg.org%2F6gx7g94gt%2FVRAM3.jpg&hash=a5bb4c68d3495504f213590b80c11272) (http://postimg.org/image/6gx7g94gt/) (https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fs14.postimg.org%2Fgs9k8ww65%2FVRAM4.jpg&hash=0747ba3932ee133512ceba69ba086b2d) (http://postimg.org/image/gs9k8ww65/) (https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fs14.postimg.org%2Fpkqiwlhb1%2FVRAM5.jpg&hash=41bd7ef42870316a1da815cd2bb19a8b) (http://postimg.org/image/pkqiwlhb1/) (https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fs14.postimg.org%2Fln3976uhp%2FVRAM6.jpg&hash=f176ac2ad4783929994509bf1c6c253a) (http://postimg.org/image/ln3976uhp/)
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on December 09, 2015, 09:52:48 PM
Do you see the words "Ramping X" (where X is some number) on the screen after you take each photo?
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: pdiegmann on December 10, 2015, 07:48:17 AM
Nope. I'll be on the road for about two weeks and won't be able to check this forum, but thank you for your support :)
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: Piotr.23 on January 15, 2016, 09:40:16 PM
dmilligan, where can I download version 5.0 of the module?
The most recent version 6.0 works with 5DIII firmware of 2015-12-20, but I'm, getting pink frames in MLV, so I downgraded to no-pink frames firmware of 2014-05-23
And firmware of 2014-05-23 says I need 5.0

Thanks | P
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: tucson50 on February 05, 2016, 08:54:54 PM
Thanks to all who have worked on this module! I use it frequently and have had great success.

I have a question, however.  I want to Use Global Time for a time lapse that runs from before sunset until after sunrise, but that means I am entering frames from about 16:00:00 to 19:00:00, and then from about 6:00:00 to 9:00:00.

Will this work?  Does the algorithm essentially loop around after midnight to start over with the lower times to hit my sunrise target?  I have had problems with this, but with as many variables as there are making a long time lapse, I am unsure of whether I might have made some other mistake.

Thanks for your feedback and your great work.

EOS M, Sigma 4.5mm fisheye
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: Ottoga on April 21, 2016, 09:52:14 AM
@dmilligan

April 19, 20 and 21 nightlies display the flowing error message on my 7D when trying to load the adv_int module:



Linking..
tcc: error: undefined symbol 'get_out_of_play_mode'
    [E] failed to link modules


Note that error only appears if the adv_int module has been selected to load. I proved this by trying to load it on its own with no other modules selected and got the error. If I exclude this module then all other modules load successfully.

Nightlies prior to April 19 don't have this error.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: Walter Schulz on April 21, 2016, 10:37:16 AM
Fall back or compile latest changes. Or wait about about 16 hours to see it in next build. Has been merged today ... https://bitbucket.org/hudson/magic-lantern/pull-requests/678/advanced-intervalometer-module/diff
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: a1ex on June 26, 2016, 09:51:04 PM
Today I had the chance to try the advanced intervalometer.

Background: we have a flower that opens at 9 pm, like this (https://www.youtube.com/watch?v=O-l3Dn5qa4Y). I wanted to record a timelapse of it, but with intervalometer set to 3 seconds, I would run out of card space very quickly, and with larger intervals, I would miss the action. Therefore, I enabled the advanced intervalometer to ramp the interval time from 30 seconds (outside the blooming time) to 3 seconds in the middle of the action.

Result: it didn't ramp - probably I've restarted the camera after setting up the keyframes. Will try again.

Meanwhile, here are my initial suggestions:

- keyframe auto-load (already implemented it locally)
- keyframe editing (after defining them)
- debug messages on the console (to check what is ramping)
- ETTR slowest shutter in sync with intervalometer time, to allow longer exposures as the interval time increases (already implemented it locally)
- minor: what about renaming the module to ramping.mo and the menu entry to Intervalometer -> Ramping options ?

Possible bug:
- saving/loading sometimes introduces a dummy keyframe (T=00:00:00, no options, sometimes at the beginning, sometimes at the end of the list, seems random; not sure if it has any effect on the functionality)
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on June 26, 2016, 10:06:32 PM
I had intended to port it to Lua, if I ever find time. It would be significantly easier to manage the keyframe data structures and serialize/deserialize them as Lua. There's probably a few minor things here or there that need to be exposed in the API.

I agree "ramping" is a better name.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on July 16, 2016, 10:04:06 PM
I had intended to port it to Lua, if I ever find time.
WIP (http://www.magiclantern.fm/forum/index.php?topic=17570)
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: stefgodin on August 17, 2016, 06:42:15 AM
Hello

I'm stephane, a french pro photographer, nice too meet you !!

I just try ML to shoot timelapses with a Canon 6D.
Magic lantern works fine BUT do you know if it is possible to ramp ISO setting by 1/3 values as speed values ?
Shutter speed vary with 1/3 value but ISO only with entire value... 100 - 200 - 400 - 800 etc

No way to change this ?

Thanks !

stef
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: stephane.meril on October 20, 2016, 10:15:58 AM
Hello,

I'm discovering the advanced intervalometer module and don't realy understand how to use the keyframe.

I usually work with the "simple" intervalometer for day to day timelapses but have to verify every day the settings of these ones.
What I'd like to do would be to program a 60d or a 5d2 to start each day at 8 am for 500 shot with a 57 seconds interval without my intervention.

I've done this kind of work for a building, but using an harbortronics controller enclosed in a pelicase (with the EOS and a power system). Trying to program  this (without realy understanding the keyframe method) with the advanced intervalometer, I don't obtain any good result. Could some of you help me to know if it's possible to do this with the advanced int' and how to do that, please ?

I don't need anithing else than the start and stop. No ramping exposure (it's inside with always the same light), no ETTR.

Thanks for all your advises and help.

Stéphane.

Sorry for my english, I'm french...

Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on October 20, 2016, 11:11:36 PM
Starting and stopping the intervalometer itself is not really what this module is meant for.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: stephane.meril on October 21, 2016, 01:11:32 AM
So, dmilligan, do you think Magic lantern is not the right toll for this ?

If not, would you know some useful tools to do that ?

Thank you.

Stéphane.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: stephane.meril on October 23, 2016, 02:08:41 PM
After some research, I suppose I will use this way : https://madisprojects.wordpress.com/2014/06/29/a-timelapse-project-with-dslr-raspberry-pi-eye-fi-and-gphoto2/
Thank you for your precisions and the work you've made with magic lantern, a incredible and necessary hack for every EOS user.

Stéphane.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dreamingof8a on November 11, 2016, 02:26:07 PM
One question regarding ADV_INT and AETTR: Does ETTR take the ramping into account? For example, I'm changing from f/4 to f/3.5 at some point; does ETTR automatically compensate for that by chosing a shorter exposure time in order to be closer to the optimum exposure rather than overexposing due to the aperture change?
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: dmilligan on November 11, 2016, 02:52:17 PM
It depends. If you are using AETTR continuously in LV with expo override, then yes (so long as there is enough time between exposures for LV to start back up and ETTR to run). The next LV frame after the aperture changes, AETTR will recompute and the new aperture will be taken into account. If AETTR is only running in QR, then technically no, but I highly doubt it would be an issue (and it might actually help). Keep in mind that your scene may change between exposures and cause more of an issue than this (your scene could easily change more than 1/3 EV, which would totally outweigh the issue of 1/3 EV from ramping). Furthermore, you're likely ramping in the direction of scene lighting changes, so having the ramp change not actually taken into account may actually help because it will compensate for a change in scene lighting. Finally, you can always give AETTR more headroom with the exposure target setting.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: a1ex on February 24, 2018, 08:38:07 PM
Some minor updates I did a while ago:

https://bitbucket.org/hudson/magic-lantern/pull-requests/907/advanced-intervalometer-updates/diff

Sorry, the changes are untested; didn't manage to record any other timelapses since then.
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: anykill on March 04, 2018, 03:17:03 PM
Some minor updates I did a while ago:

https://bitbucket.org/hudson/magic-lantern/pull-requests/907/advanced-intervalometer-updates/diff

Sorry, the changes are untested; didn't manage to record any other timelapses since then.

Alex, do you mind to share the new module?
And do you have any readme or tutorial how to use that, I want to achieve the holly grail... day to night with LR Timelapse!
Thank you for your hard work!

BTW, the original ML 2.3 version, have an automatic Bulb/focus ramp, why we dont have it anymore?
Thank you very much
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: nicotom on February 27, 2020, 02:31:54 AM
Hi,

I recently baught an eosM 2.0.2
I am trying to use intervalometer and Bulb ramping for day to night timelapse in ML.
I am a little lost here.
I saw differents versions of ML (here, on bitbucket.org/Dannephoto )

I tried diferent version but i can not make the intervalometer work and I can't find any ramping option neither advance intervalometer with ramping option.

Could someone help me ???

Thanks a lot

Nicotom
Title: Re: Intervalometer Ramping Module (adv_int.mo)
Post by: Walter Schulz on February 27, 2020, 02:54:27 PM
Sorry, what does "can not make the intervalometer work" mean? Support staff loves detailed error descriptions and steps to reproduce a problem...

And read https://wiki.magiclantern.fm/camera_help#intervalometer