Messages

OK, i also got bad frames when focus peaking was disabled. So deactivating focus peaking just reduced the amount of bad frames.

Thanx for your reply DeafEyeJedi.

I already tried it several times. I format the CF on my mac to exFAT and then copy the ML-files to the card. Putting the card back into the 5D3 the ML menus are gone. Doing the firmware update function to install ML fails every time.

At the moment i am using a self-made build from yesterday. But i also tried several nightly builds from April to Mai 2015. All do have the same issue. I think it does not matter what build you use. Just try the latest nightly.

I tried several different options with GD on. Histograms, level indicator, zebras - they all do not lead to bad frames. It's focus peaking. Whenever i activate thist function i get bad frames. I tried different options in the focus peaking menu. It doesn't matter. I always get bad frames.

I am going to deactivate focus peaking now. It's too bad cause this is the most important feature for filming.

Btw. i used "Slightly sharper" in LV DIGIC peaking together with Focus Peaking.

I just found the cause of the bad frames!
When global draw is off, everything works fine --> no bad frames.
With global draw is on --> bad frames

I normally use focus peaking, zebras, level indicator and full raw histogram at once.
So i did some further testing and i could isolate focus peaking as the cause of the issue.

Can anyone confirm that by using focus peaking on a 5D3, using v1.1.3 and a build between April and June?

@dubzeebass: i am not using spanning anymore.

@DeafEyeJedi:
No, the card is formated as FAT32. I cannot figure out a way to format it to exFAT and get ML running again using 1.1.3 as firmware version.
I also do get bad frames in MLRawViewer.

Yesterday i accomplished to make a 7 minute video without a single bad or skipped frame using the latest ML-build. Today using the exact same ML-settings and build the first video i tried stopped after about 30s cause of skipped frames. I don't know why. The card is certainly fast enough. The little camera logo is always green.

Than i switched the camera off and on again and tried with the very same settings and i did not get any skipped frames for 5 minutes but some bad frames again.

Does MLV-record work reliable for you guys with the latest builds? Am i the only one having these issues?

So after trying a lot i just updated to the latest ML-build. It looks good. I need further testing but i think the issue is gone.

Does it look like this?
http://www.magiclantern.fm/forum/index.php?topic=5473.msg150360#msg150360

Video also stops quite often cause of skipped frames but the writing speed of the card is not the issue. The camera icon during recording is always green.

Hi guys,

i do keep getting odd pictures in my mlv-videos with my 5D3 v1.1.3 and don't know what to do against. Sometimes they look like this:


and sometimes they look like this:


and this is how it should look like:


I do get about 3 or 4 of these frames per minute. That makes using raw video practically impossible.

I already tried the following things without success:

• different CF-cards
• a lot of different ML-builds from April to May 2015
• copied the same .mlv-file from my card reader to the computer several times to check if my card reader is having an issue
• deactivated card spanning in ML
• with and without the Fix Black Level Option
• different Buffer options
• used MLVMystic with diferent options and also tried mlv_dump in different options

I never had issues like that with the 5D2.

Thanx glubber! I did this once. It made some mistakes but worked most of the time. But having correct metadata is the better way.

Hey guys,
am i the only one who get's wrong exposure times in the final FRSP-DNGs?

To be excat, it looks like this:
a) When .mlv is used as container for the FRSPs:
for exposure times <1s the value is correct. All exposure times >=1s are displayed in Photoshop as 1s-exposure.

b) When .DNG is used for the RSP:
the displayed exposure time is always 1s inpedently of the actual exposure.

This is kind of annoying when doing day-to-night timelapses as lrtimelapse is having a hard time correcting the exposure changes.

Thanx david! With your input i just finished my intervalometer-script:
http://www.magiclantern.fm/forum/index.php?topic=15119.0

Hi,

i finished my script now and am quite happy with it.

If someone has a similar problem here is my solution:

Code Select Expand

shutInterval_menu = menu.new
{
parent = "Intervalometer",
name = "Interval 2x Shutter speed",
help = "Sets the interval to n-times the shutter speed",
update = function(self) return self.submenu["Enabled"].value end,
submenu =
{
{
name = "Enabled",
choices = {"Off","On"},
},
{
name = "shutter-multiplier",
help = "define n [1] for interval = n*shutter; normally n=2",
min = 0.1, max = 10,
unit = UNIT.DEC,
value = 2,
},
{
name = "min. interval",
help = "min. interval value [s]",
min = 0, max = 600,
unit = UNIT.TIME,
value = 10,
},
{
name = "processing time",
help = "min. time between two shots [s]",
min = 0, max = 600,
unit = UNIT.TIME,
value = 7,
},
},
}


function event.intervalometer(shootCount)
if shutInterval_menu.submenu["Enabled"].value =="On" then
multipleShutter = math.ceil(camera.shutter.value*shutInterval_menu.submenu["shutter-multiplier"].value)
shutPlusProces = math.ceil(camera.shutter.value + shutInterval_menu.submenu["processing time"].value)
myInterval = math.max(shutInterval_menu.submenu["min. interval"].value, multipleShutter,shutPlusProces)
interval.time=myInterval
-- for Debugging:
-- print("n: "..shutInterval_menu.submenu["shutter-multiplier"].value, "min. interval: "..shutInterval_menu.submenu["min. interval"].value, "proc. time: "..shutInterval_menu.submenu["processing time"].value)
-- print("#"..shootCount, "Shutter: "..camera.shutter.value, "new interval: "..myInterval)
return true
end
end


You do have the possibility so select three values:
shutter-multiplier ... the interval is calculated by shutter multiplied with this value (n*shutter; normally for 180°-shutter you choose 2 here)
min. interval ... minimal interval between two shots
processing time ... the amount  of time the camera needs for processing (AETTR) and MLU between two shots (shutter + processing time)

In the end the script calculates three intervals and chooses the maximum out of it. So you can be sure the acutal interval is always bigger than the minimal interval, it is always greater than n-times the shutter and there is alwas enough time for MLU and AETTR.

Hi David,

i read all your docu and alle the menu-samples but i still can't get the following thing working. I want a menu whos parent is "Intervalometer". When you press that menu it activates or deactivates the function. In the submenu i need decimal values to choose the minimal interval and to choose the minimal processing time between two shots. This can either be a decimal number or a time value. I tried it several times but i fail implementing such a menu structure. Could you give me a sample how to do that?

Best regards

Peter

Hi David,

i am still working on my intervalometer-script. At the moment i want to manipulate the shutter speed that is determined by AETTR. The idea is that small changes in shutter speed are ignored.
The thing is that i cannot manage to do operations directly after a shooting-task. The following code is not started after pressing the shutter or using the intervalometer. I don't know why. Could you give me hint?

Code Select Expand

function event.post_shoot()
print("post_shoot()")
end

I finished my first script now and the automatic intervalometer changes by shutter time a working perfectly now. Thanx David! LUA is just awesome!

I am going to try the script in a timelapse with AETTR tonight. I hope it does not start raining...


So here is my script. It's quite basic and i am still confused by the LUA syntax but it works:

Code Select Expand

minInterval = 10;
shutInterval_menu = menu.new
{
parent = "Intervalometer",
name = "Interval 2x Shutter speed",
help = "Sets the interval to 2x the shutter speed; min. interval is 10s",
choices = { "Off", "On"},
value = "Off",
}

function event.intervalometer(shootCount)
if shutInterval_menu.value =="On" then
shutTimeAPEX = camera.shutter/10
shutTime = 1/(2^shutTimeAPEX)
myInterval = math.ceil(shutTime*2)
if myInterval < minInterval then myInterval=minInterval end
interval.time=myInterval
print("#"..shootCount, "Shutter: "..shutTime, "new interval: "..myInterval)
return true
end
end


Thanx David! It's working perfect now!

Thanx David for your fast reply!

Hi David,

i am still amazed by alle possibilties poosible with LUA scripting on ML!

At the moment i am having some troubles calculating the actual shutter speed from APEX to seconds. As "^" is not working i tried it with math.pow, but it didn't work. My code looks like this now:

Code Select Expand


menu.new
{
    name = "Shutter speed",
    help = "Show the shutter speed",
    select = function()
        console.show()
shutTimeAPEX = camera.shutter/10
shutTime = 1/(2 ^ shutTimeAPEX)
        print("Shutter APEX: "..shutTimeAPEX)
        print("Shutter: "..shutTime)
    end
}


Is there a better way to convert APEX to seconds?

Greetings
Peter

Amazing! I just spent a bit more than an hour to download and compile ML but Lua-scripting is now working and i am amazed. Just awesome!
I am now starting to write a script for that. When i am finished i am going to post ist here. THANX!

Hi guys,

i experiment with timelapses and AETTR and find it very useful. Just awesome!
One thing that would be very handy for all timelapsers out there who do day-to-night or night-to-day-lapses would be to adjust the intervalometer automatically with the actual shutter time. Simple algebra would be nice. Something like two times shutter time plus 2s.

Of course you can adjust the intervalometer with the adv_int-module but its static and you need to program the intervals by guessing the exposure time that will be needed.

Greetz
Peter

No ideas?

I tried using FRSP with A-ETTR in a day-to-night timelapse two days ago with the actual nightly. For that purpose i used the .mlv-format, set A-ETTR to a max shutter-time of 10s and used a 12s interval. The result was that A-ETTR worked fine but i only got a picture every 24s and in the metadata the shutter time was always 1s but i can see from the exposure of the picture that the shutter time changes very often. So A-ETTR worked correct but the metadata was written wrong. Aperture and ISO worked fine.
Do you have any ideas about the shutter time? Is there something wrong in the code or a user-error?

I can confirm that expo-override does not work on 5D3 + EF 40/2.8 STM in the latest nightly. I had the same issue yesterday. The aperture does not close more than about f/4.0 or f/5.6.
It works fine with other lenses.

Hi guys!

I recently upgraded from the 5D2 to the 5D3 and found the trap focus feature extremly powerful on the Mark III. It was unaccurate with the Mark II AF-system but works unbelievably wonderful with my MF-lenses on the Mark III.

Most of the time i photograph kids and for that i want to prefocus with AF-assist and use the trap focus feature only when things go really fast. For that it would be wonderful to switch fast between trap focus and the normal operation.

Is it possible to use the AF-on-button for AF-assist and the half-shutter for trap-focus? I know it's possible to recognize the half-shutter as you already use double-half-shutter for AETTR.

Thanx!

Peter

It's a joke. I had it on my 5D3 as well. See:
https://bitbucket.org/hudson/magic-lantern/issue/2235/5dmk2-bricked-urgent-please

I just set my cameras date to April 2 and everything worked again.