Menu

Show posts

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

Show posts Menu

Messages - B.Rae

#1
Yep for T3i/600D it's Firmware 1.0.2 from Canon. 
#2
And Dmilligans bridge ramp script worked like a charm.  It is super user friendly I love it! :). I cropped files in Lightroom updated the metadata then imported to bridge ran the script for a few passes, exported to after effects and the end result was flicker free :)


B.Rae
#3
Thank You Audionut my research lead me to the Bridge ramping script today and I am about to give it a go. 


cheers for your reply!


-B.Rae
#4
I searched around but didn't find anything based on my specific problem (and it is most likely my problem not ML functionality)  regardless I would like to reach out for some help/clarification.   

I successfully shot a golden hour time lapse yesterday evening using ETTR + Post Deflicker modules (using CR2 and XMP files).  I work on a MAC and I was able to get the files imported to light room (in the thread regarding how too ETR/Post Deflicker it says this works) I could get it to read the metadata fine and I even moved the files to bridge to preview for any flicker between frames (it was looking great).  Once I cropped my images in Lightroom is where the trouble started (I think).  I used lightroom to crop to 16:9 then I exported the files out to high quality jpeg and imported as footage to After Effects.  I thought all was well but my final render from After Effects was full of flicker. 

Anyone have any suggestions or can you take pity on this fool (fool being me) and show me the error of my ways? 

By the way just for reference I'm using the latest nightly build for my 600d/T3i

    magiclantern-Nightly.2015Apr19.600D102.zip
    Built on: 2015-04-18 17:59:10 -0700
    Changeset: e08c6c0



thanks in advance for your time!


B.Rae
#5
it's good point of view ... you got me thinking and I realize i had a fundamental misunderstanding of how the interval/shutter speed relationship works with the whole bulb ramping/ETTR feature.  Really if I'm shooting a time lapse of the sunset through into the dark hours with the interval set at a 30 or 40 seconds you figure it would be about 3 or 4 seconds of sunset for 25-30 seconds of milky way footage at 24fps which would simulate pretty well the last hour of the day and a good portion of the night sky with milky way.  My mistake was thinking of it more in a linear sense like the balance of screen time between the sunset and the milky way clips but for continuity I think you are right doing it the way I wanted to do would be slow through sunset and then suddenly the night sky would be flying by in the same amount of time give or take but at a much faster rate in time lapse terms.   Thanks for your time it makes more sense to me now... sometimes I just have to stick my neck out to learn something new :D
#6
I'm using the same exact build and having the same issue on my (600D).  From messing around with it last night it would seem like an issue with the interval related to shutter speed.  I was playing around with 30 second exposure times with a 5 second interval but I realized I have to set the interval to 35 seconds to have a 5 second gap with a 30 second exposure or else it would freak out and start shooting random frames once the current exposure completed (like it was trying to play catch up).   


UPDATE:  The above may have been due to my fundamental misunderstanding of how the interval/shutter speed relationship works when using ETTR module.  I did still seem to think there was some funky-ness regarding the timing of the intervalometer,  even when I had a situation where the shutter speed was much slower than the interval sometimes it would take shots at an obviously delayed rate and sometimes shoot pics double time.  I'd be interested to hear what the developers think about this. 
#7
First of all I'm glad to be here and glad to be trying out Magic Lantern on my Eos Rebel t3i (600D) for the first time.  So far I see many possibilities for this software and look forward to digging deeper into it's features as time progresses.  with that said I have recently become very interested in Bulb Ramping and downloaded version 2.3 but then realized there is a new Module called ETTR.  I began playing with it and at first it was taking pictures very erratically and not following the time I set for the intervalometer. 

It took me a while to realize that the interval needs to be added to the exposure length otherwise the camera immediately tries taking another picture while one is still being exposed... ie: if I have a 5 second interval with 30 second exposure it's no good. So for example it would need to be give or take 37 seconds to give me the 5 seconds I'm looking for plus the 2 second image preview.  With that said unless I'm missing something (and I read a ton of information about this last night but didn't find an answer)  it seems like the interval doesn't work how it would on a traditional wired intervalometer where that 5 seconds would be the time between exposures no mater what the exposure length was. 

Am I missing something here?  My hope is to work out a golden hour time lapse from day into night and move straight in to Milky Way time lapse (using ETTR Module) but as I understand it now I would have to set an extremely long interval in order to make it work once it's dark and that would not be ideal for the daylight portion of the timelapse.  Any info on a workflow would be appreciated. 


FYI I am running the following Nightly Build:

magiclantern-Nightly.2015Apr19.600D102.zip
Built on: 2015-04-18 17:59:10 -0700
Changeset: e08c6c0

Regards,


-B.Rae