Topics

for a new device without an existing .FIR file, is there a procedure to get an initial firmware dump for a Digic 6+ camera?

[0 frame rate]

traveling with 5D3 and 50D shooting magic lantern raw along with several time lapses.
returned with 470GB - 311+ raw clips, 2300 CR2s (most from several time lapses)
both cameras worked very well with magic lantern.

most of the raw video clips look great - absolutely stunning images for frames of video. changing settings does take time and in outdoor lighting conditions, it is difficult to see through the glare.  some ML features (e.g. ability to roll through menu options from high value to low) while convenient in the studio require more care in the field.

ML flicker-free timelapse features worked well on each camera.  you have to manually adjust using the top dial the shutter speed to get low speeds (less than 1/24) - you can't do this from the ML menu.

for photos, turned off Auto-ETTR  when i had shots with large dynamic range and preferred to let parts of the sky blow out (didn't try to adjust percentages and channel options).
when i did want to switch from video to photo shooting it seemed to take some time to adjust settings and it is not as easy as turning the canon c1 c2 on the mode dial. 

table and description of errors encountered below.
will post edits when ready. any interest in comparison of  50D and 5D3 similar shots?

Code Select Expand


Errors 0 rate, slow  rate, rawmagic crash, Err 70, Err 80, camera lock up
TOTALS 11 8 1 1 1 1
50D
clips 60
1584x982 24 0 2
1920x1080 36 1 5

5D3
clips 251 1 1 1
1920x1080 165 8 1 1
1920x1288 12
2048x1152 8
2240x1260 37 2
2560x1320 8
2880x1320 4
3584x1320 16
640x240 1


Errors so far:
0 frame rate:  11
rawmagic or raw2dng report a frame rate of 0.
1 5D3 clip which reported 0 rate in rawmagic causes rawmagic 1.0 beta7b to crash.
raw2dng can process all frames - though the frames after the point where rawmagic crashes are corrupted.
battery was running low as card was filling - so i'm happy to have 7489 out of 7532 good frames.

slow frame rate: 7 (1?)
rawmagic or raw2dng report a frame rate lower or different than camera setting.
7 of these occurred on the 50D when outside temperature was 113 degrees F (45 C)
1 clip on the 5D3 (different day) has raw2dng fps 29.776 and rawmagic rate 29.97  both are strange when all other clips in the sequence are at 23.976 (of course could be accidental setting - but why difference between raw2dng and rawmagic?)

camera errors
on 5D3 also encountered one Err70 and one Err80 both easily resolved by dropping battery and power cycling.
got the message for card full once when the card was not full.
experienced 1 camera lock up where the camera would not turn on described on post

... no power with or without cards issue last week on a 5D3...

rawmagic was able to process completely all but 1 clip including one which spanned 9 files.
screenshot of clip which crashes rawmagic 1.0 beta7b

magic lantern src/raw.c uses the DxOmark screen data for the dynamic_range of each camera at each ISO.
the code computation assumes the values begin at ISO 100, however available data on DxOmark does not include a value for ISO 100. http://www.dxomark.com/index.php/Cameras/Camera-Sensor-Database/Canon/EOS-50D

Code Select Expand


Measuered ISO,  manufacturer ISO,   dynamic range Ev
    ,100,   
158,    200,    10.94
306,    400,    10.6
618,    800,    10.05
1172,   1600,   9.19
2342,   3200,   8.26
4433,   6400,   7.26
9210,   12800,  6.33


in src/raw.c we had

Code Select Expand

static int dynamic_ranges[] = {1094, 1060, 1005, 919, 826, 726, 633};

what value should be used for ISO 100?
a 3rd degree polynomial fit to existing data gives a value of 11 for the ISO 100 value.

Code Select Expand

static int dynamic_ranges[] = {1100, 1094, 1060, 1005, 919, 826, 726, 633};

for the 100 ISO value DxO mark also reports almost the same "ISO Sensitivity" for manufacturer ISOs 100 and 200 - 157 and 158.

http://www.clarkvision.com/articles/digital.sensor.performance.summary/ Individual Sensor Data Table for 50D show lower dynamic range for ISO 100 10.95 vs. ISO 200 11.14

perhaps contrarily, Bill Claff reports higher photographic dynamic range - 8.77 at ISO 100  and 8.46 at ISO 200 http://home.comcast.net/~NikonD70/Charts/PDR.htm

shooting a set of images as on http://www.rawdigger.com/howtouse/pixel-capacity-and-amplifier-gain
does not show the behavior of ISO 50 on 5D2 with ISO100 on 50D.
data below. shooting a tungsten lit wall at f5.6

Code Select Expand


Shutter ISO G avg G std deviation
S 1/5, 100, 5386.8,  127.02
S 1/10, 200, 5337.39, 136.3
S 1/20, 400, 5361.66, 152.85
S 1/40, 800, 5346.62, 182.41
S 1/80, 1600,  5320.95, 229.62
S 1/160, 3200, 5229.87, 301.09
Test 2
S 1/5, 100, 5086.95, 119.03
S 1/5, 200, 10198.97, 244.73

this quick test shows lower standard deviation at ISO 100 with the same signal (Green average value).
the example shown on http://www.rawdigger.com/howtouse/pixel-capacity-and-amplifier-gain for the 5D2 at ISO 50 shows a much greater noise (standard deviation) at ISO 50 which is why it considered a non-native ISO.
on the 50D, ISO 100 appears (subject to a statistical validation of the quick test here) to be a native ISO for the camera with lower noise than ISO 200 and is a valid selection for shooting.

still leaves the question of what is the correct value for ISO100 dynamic range in the magic lantern code.
scaling the clarkvison number to match DxO at ISO200 would give 10.75 at ISO 100
scaling the Bill Claff number would give 11.34 at ISO 100

my quick and not-statistically validated test give a very similar noise level at ISO 100 and 200 (7 % lower standard deviation - 13% lower squared standard deviation). so the value should be expected to be close to the value at 200.

the current code is an improvement as otherwise, the dynamic range values would be lower for all ISOs and this would restrict the apparently available exposure range.

[Update 26 June 2013]

This topic is for discussing specific 50D builds for raw video. A build is a specific set of collection of compiled code and modules packed up into a zip file.  Raw video is under active development and the behavior of various features and functions is rapidly evolving.
Update 26 June 2013 - there is a new "Small Hacks" feature in the raw_rec module.  in the Raw Rec Detail Menu enable Small Hacks.  50D builds hit 81MB/s for hundreds or more frames at 1920x1080 in crop/zoom mode only. The goal is 83/84 MB/s as this would permit continuous 1080p24 recording. 

Latest builds:
pick the most recent from the download locations below:

based on hudson/unified, the main branch for all cameras from the code in: bitbucket.org/hudson/magic-lantern: https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/ sporadic builds from me until 9 July 2013 as i will have limited internet access.

1% is posting tragic lantern the latest high speed builds to
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
these could contain advanced settings so be prepared and have fun.

Andy600 is producing hybrid builds for testing some new code based on tragic lantern and unified
https://bitbucket.org/andy600/andy50d/downloads/
read thread posts for notes on specific test builds.

Users / testers: please include the build file name when reporting results bugs.
for a good example of a detailed bug report which led to a resolved issue, please look at http://www.magiclantern.fm/forum/index.php?topic=6976 and note the care with which user @platu describes exactly how to reproduce the error.  a1ex directs people to http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

If you are a new user, go through the guides.
RAW video & ML -- Beginners Guide, FAQ & Useful Links -- READ FIRST
http://www.magiclantern.fm/forum/index.php?topic=5520.0

PostProcessing -- Beginners Guide
http://www.magiclantern.fm/forum/index.php?topic=5654.0

General discussion of  Raw video on 50d and 40d  is on the thread http://www.magiclantern.fm/forum/index.php?topic=5586.0
For the super speed builds from Andy600 and 1% please be sure to read the latest information.

Build your own
If anyone wants to build hudson/unified 50D releases and add them to this thread or otherwise share them with your friends, please go ahead.

• - hg clone https://bitbucket.org/hudson/magic-lantern
• - create Makfile.user  - enable modules CONFIG_MODULES = y, CONFIG_TCC = y, CONFIG_PICOC = n, CONFIG_CONSOLE = y
• - create modules/Makefile.modules.user - ML_MODULES_DYNAMIC ?=ettr raw_rec pic_view file_man bolt_rec
• - make modules then make zip in the platform/50D.109 directory (i posted a very simple shell script to do this, simply edit for the directory where your source code is https://bitbucket.org/GregoryOfManhattan/magic-lantern/src/a678cd4f9539619acbb4b2e08b895b34d6902a45/build50Dwithmodules.sh?at=50DrawNow )

i'd like to shoot cinemascope at 1920x720 raw video on a canon 50D

after editing (had to revert raw_rec.c to de0bcff) can record and convert dng, tiff, mov, ...
what else needs to be coded to have the liveview display more accurately reflect the recorded frame
50D settings in camera for full 1k cinemascope


on set shooting will be difficult when the LiveView is only showing a portion of the frame on the top and left and cutting off the top, right and bottom.

viewfinder display


capruted frame


magic lantern raw video is looking good, but i would love to simultaneously be able to frame a shot.
at the moment, its creatively imagine a floor a little higher, double the top and triple the width on the left.

edited by Audionut:  Images resized to fit in the forum better.