Messages

LED FIR with wider address range 2048 addresses from 0xd20b0000
is displaying blinkenlights - should i start to build an opto sensor as on olde chdk dumps?

[blinkenlights]

blinkenlights
card formatted in camera, adding LED .FIR and autoexec.bin on a not bootable card.
click to load firmware
get only a single blink along with the loading... screen
led goes off
then screen goes black
http://imgur.com/a/Qo1dB
camera remains on but locked up with no display of any kind not even a single blinkenlight.
waited 5 minutes and pulled the battery.
same result with CF or SD card.

same process with DISP_5D3.FIR and the same autoexec.bin on a 5D3 shows the Magic Lantern Rescue screen

also tried with 64GB CF card and Portable ROM dumper did not run.
same card work immediately on 5D3 this time without even moving the power switch to On.

trying to load firmware shows Loading... and hangs, this is different from the behavior using an SD card.

wonder if I should try a different build of the ROM dumper - is this built from the recovery branch?

Portable ROM Dumper does not appear to work on this camera.
Have tried with .FIR provided and autoexec.bin from http://www.magiclantern.fm/forum/index.php?topic=16534.0
on a 32 GB SD card formatted in camera made bootable with contrib/make_bootable.

Same card works immediately on a 5D3.

Attempting to load new Firmware displays Update file cannot be found.

great, thank you. will try Portable ROM dumper.
I believe that I will also need a signed binary .FIR - I will search for how to generate that.

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

Already find how to fix the problem with HEX editor...
But entire problem remains: when CF completely is filled up - last file is corrupt.
I hope my opinion it will be useful.
Thanks!

hi Jake, i have filled up several cards - 2 without problem and 1 with the issue below where the card was almost full at the same time the battery warning was flashing (lost a couple of seconds at the end of a 5 minute shot).  so in this case it wrote a correct footer, but had frame errors which crashed rawmagic.

is this a consistent issue on your camera?

Thomas,
thank you - rawmagic is working well. wanted to let you know that i have 1 clip (actually span of 8 files) which crashes rawmagic 1.0 beta 7b. please let me know if you'd like any crash logs, DNGs, or other information. the battery was running low as the card was filling up - so its not surprising there are errors.
raw2dng can process all the frames. the last 44 frames are corrupted in an alternating pattern of 80% good top image 20% pink followed by a frame 80% pink corrupted top portion with bottom 20% OK.

~/bin/raw2dng M02-244-concatted.RAW
Resolution  : 1920 x 1080
Frames      : 7532
Frame size  : 3629056 bytes
Frame skip  : 1
FPS         : 0.000
Processing frame 7532 of 7532...
Done.

new 50D unified builds posted with more correct Dynamic range information.
previously to July 15, 50D unified has been underestimating available dynamic range at most ISO settings.
have corrected this, albeit with a potentially inaccurate ISO 100 dynamic range value.
see discussion on Topic: Is 100 a native ISO on 50D? Correct Dynamic Range values for 50D http://www.magiclantern.fm/forum/index.php?topic=7102.msg59340#msg59340

Histogram and Zebras should now be more accurate.
if the ISO 100 zebras or Histogram appear to be inaccurate based on your photographs, please weigh in on Topic: Is 100 a native ISO on 50D? Correct Dynamic Range values for 50D.
if underestimating dynamic range is better (safer) - the value could be set lower.

very underexposed - so good to know and explains why i have clips which when running raw2dng do not show the EV HDR correction info - though this is the first time i'm seeing the banded DNG.

uploading now - if you want to see - try these in a couple of minutes when upload is complete
http://50.56.67.113//ml-20july13/M20-0958.RAW 32.7MB

http://50.56.67.113//ml-20july13/000000.dng 2.7MB

yes - good to know better use cases may not be the extremes and
to consider the value (thematically and exposure wise) of what's in field of focus.

is raw2dng in unified supposed to be able to process dual iso clips?
tried 5bad65ff8cb8 and it isn't converting a dual shot clip - instead it creates banded DNGs.

easy enough to download a different version.

To choose other options, just flip the conditional defines from the source code (INTERP_*). For shadow aliasing, adjust f_shadow.

great we can make our own custom blends.
modules/lv_rec/raw2dng.c
modules/dual_iso/cdr2hdr.c

if a clip is dual_iso will the current raw2dng always display the HDR info and the EV offset?

have tried out the dual_iso module with raw2dng at 7351be3d3c0c
sequences processed through resolve.

room was so dark i moved the Base ISO up to 800 and that may not have been enough.
did no camera preparation before this event - so i can't confirm that the comparison clips had significant Ev offsets applied.

dual iso mode seemed to work at all resolutions i tried - here's a 3586x1320 DNG
http://50.56.67.113/ml-17july13/000012.dng
http://50.56.67.113/ml-17july13/1927-3584x1320-000012.jpg - same thing as an RPP processed jpg at 1/2 scale



3.5K did not seem to work as well as builds from last week or at least the usual small and memory hacks didn't work as well when i tried them - only got 1-2 seconds of 3.5K.  2.2K seemed continuous.

had one lock up where i needed to pull the battery

which repository has the code with median23 and other options? will have time to test this weekend.

[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

this is why i put the file_man in the unified builds - figure that people will see
file_man and figure out that it means
file manager and
click on things to see what happens (or use search on the internet).

you can set each module to load or not by default.
many times i only leave ettr and raw_rec active.

I tried the removing the battery and card about a dozen times and nothing happened.

I kept trying and then finally... it came back to life.   It appears to be working normally now and hasn't happened since.

Not sure what happened there but the camera is now fine.

Thanks for your help and advice everyone  :-)

Adam

AdamJ - glad it is working fine now - it is very strange when power does not come on - was going to advise you to continue trying and to pull the battery in between each attempt.

I ran into this "no power with or without cards" issue last week on a 5D3.
Started when i inserted a blank 128GB sd card.
Camera would not start without a card (flipping power switch did nothing).
Tried various other cards, pulling the battery.  Tried sd-card only, tried cf-card only. 
Eventually camera started with a cf-card with magic lantern.
This took less than 10 minutes of real time - seemed to be resolved when i went through the cf-cards one after another, pulling the battery in between (also tried waiting 30 seconds with no battery).
Have not been able to reproduce the issue and the 128GB card works fine (not sure if i had formatted it ExFat before all this happened).

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.

Yes, put an interpolated ISO 100 value, because all my other code assummes that.

thanks - glad you refactored code and i looked through it - seemed to assume 100. (GiovanniC or someone else had previously warned of this)
submitted pull request after calculating that the 50D goes to 11 (100 ISO Ev dynamic range is 11.00)

so after this update, would the 50D raw video look any different?
seems that in active movie_mode raw_info.dynamic_range will be compute_dynamic_range - so no change for raw video.
photo mode images in liveview will now have a more correct dynamic range applied.

Edit: question answered by GregoryOfManhattan. Thanks

I must be using the wrong build, since Small Hacks don't show in the raw video menu. Which build shall I download from the Tragic Lantern directory?

hi EOSHD -
1% has been producing builds and developments to
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
and its critical that a significant group of users try those builds under his direction and report back issues.

based on the code which a1ex has integrated into unified, i put together builds for 50D at:
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads
these make it easier for me to use the exact same code on a 50D as well as a 5D3 and hopefully helps the community to ensure that unified works well on the 50D.

the big speed ups the past month have happened with variable buffering and much experimentation by a1ex and the "Small Hacks" that 1% discovered to slow down Canon dialog refresh and disable Canon AE and AutoWB.

hopefully its not too confusing that there are different code bases for this alpha stage software.
a1ex and 1% may use different terminology.
with either code base, at the moment and for weeks now, one can record at 1920x1080p24 for 1000s of frames.
the instructions for the unified builds apply to all cameras - so what helps you achieve 1920x1080p24 on 50D gets you 2.2k on 5D3 and increases the number of frames at 3.5k.

several users have posted 50D 1920x1080p24 videos over the past 2 weeks with 80MB/s and more.

basically, as several users have asked - you don't get because you don't need 80MB/s for regular 1584x896p24 RAW video on the 50D - you only need 58MB/s
for 25p anamorphic shooters you could use 70MB/s for 1584x1058p25
with any of the recent builds "Small Hacks" enabled on unified - you should be able to shoot at
1584x1058p25.
i just did a test and have continuous recording at 1584x1058p25

please confirm that you can get that data rate and perhaps you could update your 11 July article as to the 65 MB/s limit.

[Update 26 June 2013]

I have been shooting with the 50D, feel free to pixel peep this. Variety of modes - full sensor with anamorphic 1.5x, 2x and crop mode. I'm getting 1920x818 continuously in crop mode. 65MB/s seems to be my maximum. What do you have to turn off to get 80MB/s?

...
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. 

on unified builds for many cameras the options are
Movie->Raw Video->Small Hacks

https://bitbucket.org/hudson/magic-lantern/commits/b77a85f7ac68098b219754d827fe2102fdbc5c38

new unified build
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/magiclantern-2013Jul11.50D.109.go.unified.5db91070a1aa.zip
changes include:
- pic-view incorrect size fix based on an excellent bug report http://www.magiclantern.fm/forum/index.php?topic=6976
- refactoring of dynamic range code in raw.c NOTE: 50D users should consider these changes the DxO values for 50D start at 200 ISO and have 7 total values. i added these from www.dxomark.com but wonder if the value for 100 ISO should be interpolated see src/raw.c get_dxo_dynamic_range
- Fix raw settings refresh after zoom mode change
- new ime input modules are in process

Hey all,

I still have some strange behaviour in the latest unified builds:

When I adjust shutter speed in M mode, it does not change freely but at some point ISO starts changing. So I get 800eq while the top LCD shows 1600 ISO.

Will appreciate any tips.

hi @rommex - did you have LiveView off?
with LiveView off - the shutter speed cannot be adjusted lower than 1/24 from the ML Exposure menu.
obviously, you can use the canon top main dial to adjust the shutter speed to any desired value.
i had to do this last night setting up a timelapse with LiveView off.

see discussion "Shutter speed, what am I missing"  http://www.magiclantern.fm/forum/index.php?topic=4055.0

... then, hit the crop mode, now take a look on the right side of your screen(should be no need to even record). Do you see the black bar?...

yes i see it as well. don't have time / gear with me to verify that when you see the black bar on screen you will get it on a raw video. (have loaded in the last a1ex commit based build 3ecd25)

When you move the joystick 5 steps to the left from the middle in crop mode the black bar is gone, no matter which resolution you chose after that it's gone till you turn of the camera. That's with the 5DMKIII.

thanks you - easy workaround - you could also activate and NOT use digital dolly.

does it seem to you that the right side black bar happens when you are exactly centered and going left or right the right side black bar goes away?
it also appears at the end of a digital dolly.

I was under the impression ... it would be able to record fine without issue.

alpha open source software -  find and accurately report bugs - enjoy what you can get - test builds in advance for your specific photo/video application - be careful on projects. 
https://en.wikipedia.org/wiki/Software_release_life_cycle#Alpha

The black bar doesn't look very well, did you enable anything related to ADTG?

I've just tried with 3ecd254bdba1 (didn't update to latest stuff yet) and these 3 resolutions look normal here, without any black border. Focus box was perfectly centered; the focus box snap trick was not enabled.

haven't enabled (to my knowledge) any ADTG or other debug settings.
for these shots had default values.
Preferences-> Focus Box Settings -> Snap Points -> Center (off)
will try the 5x zoom setting.

I told you before - if it's that beautifully detailed, it's not ML grayscale, it's Canon LiveView with a workaround for masking the pink tint.

1% enabled display filters. You probably need to do the same thing; I'd research a more robust method instead, using the EDMAC, because the 5D2 method leaves LiveView in a "hacked" state (single-buffered, with tearing).

yes - sorry for any repetition - thank you - wanted to alert the 50D users and ask if it was different on 1% builds.
so on 50D it is not ML Grayscale - rather gray covering up the pink.

hi @aaphotog - moving the focus box would be for a diagnostic test to see if different positions lead to a different number of black pixels on the right.  it may or may not have any affect.

we pay dearly for every pixel recorded, so we don't want to waste any precious bitrate on black.
for 2880x1320 looked like about 110 pixels of black (needs to be precisely measured)
110x1320x(14bit/8bit/btye/frame)x24frame/s -> 5.8 MB/s of black waste

here are some DNGs in which the black pixels could be measured.
2880x1320: http://50.56.67.113/ml-07july13/M03-2040_raw2dng.dng
2560x1320: http://50.56.67.113/ml-07july13/M03-2041_raw2dng.dng
2240x1260: http://50.56.67.113/ml-07july13/M03-2042_raw2dng.dng