Messages

[6D]

Yes, I think it's the same way I did you can do, it's about CMOS 0 Registers at ISO 100, Some cameras have different registers than others for
the same model, (I don't know yet if it will be more than two Registers for same model, waiting 700d users to feedback)

So you have to see your registers on your camera by adtg_gui.mo (Assuming adtg_gui.mo is working on canon 650d)

1-Set ISO at 100
2-Set camera on movie mode 1080/24
3-After loading the modules, turn on adtg_gui in Debug submenu
4-Turn on dual_iso
5-Go to PLAY mode then go back to liveview
6-Check your CMOS 0 Registers data and write it down (In the white box)


7-Now go to photo mode
8-Take a picture and Check your CMOS 0 Registers data and write it down again.

--> Now in dual_iso.c
This value for movie mode

        FRAME_CMOS_ISO_START = 0x********;

and this for photo mode:

        PHOTO_CMOS_ISO_START = 0x********;

Leave the (0x) and change the others to the values you wrote, Compile and test it in the camera!

Tried this with my 6D which I bought in Japan. Frame CMOS I changed to 40e6190 and photo CMOS I changed to 404e4e06. Still ISOless PH 3.  Only Magic-Lantern-4k crop mode has the issue. Not the Nightly build.

EDIT: It works! It was only me who didn't read everything. New values in CMOS 3 and not CMOS 0:

404e61b6
and
404e4e08

Hello, does anyone have a Samsung Evo Plus microSD card and did or could do the benchmarking? It seems to be a promising alternative. Generally it is also able to achieve approx. 90MB/s bulk write speeds but at much lower cost than SanDisk Extreme Pro. As an example: 128GB Samsung Evo Plus is at Amazon equally priced to 64GB SanDisk Extreme Pro (39€ vs. 38,99€). Both are sold by Amazon, so the risk of counterfeit should be equally low.

Funnily, according to some sources, the transfer drops by roughly a half when using the provided MicroSD -> SD adapter. If another adapter can overcome this bottleneck and if similarly high speeds can be achieved with an EOS camera it for me unknown so far. It will decide if it's really an alternative. If yes, it would be a bargain.

Samsung PRO 32GB here. 41MB/s default with 6D. 65MB/s overclocked.

i'd really love to get hands on for e.g. 600D, 7D or 5D3 to dig a bit deeper into how the camera is calibrated

$250. It is sure expensive https://www.spt.info/sptstore.php/canon-eos-7d-essential/software-canon-eos-7d-advanced-
Start a donation for the software and I am sure we can add some money.

Start by asking for the demo over there and check out the software.

By checking out the demo it seems wifi and GPS only are locked by software.

Canon 6D and 64GB Sandisk Extreme Pro UHS-I 95MB/s

2018/04/03 15:37:47
===================
Before the hack: r:44MB/s w:42MB/s  W:42MB/s R:44MB/s  : )  [best 42MB/s]
SDR50 @ 96MHz  : r:44MB/s w:40MB/s  W:42MB/s R:44MB/s  meh [best 42MB/s]
SDR50 @ 96MHz  : r:44MB/s w:43MB/s  W:41MB/s R:44MB/s  : )  [best 43MB/s]
SDR50 @ 80MHz  : r:37MB/s w:35MB/s  W:36MB/s R:37MB/s  meh [best 43MB/s]
SDR50 @ 80MHz  : r:37MB/s w:36MB/s  W:35MB/s R:37MB/s  meh [best 43MB/s]
SDR50 @ 120MHz : r:54MB/s w:53MB/s  W:53MB/s R:55MB/s  : )  [best 53MB/s]
SDR50 @ 120MHz : r:54MB/s w:51MB/s  W:51MB/s R:54MB/s  meh [best 53MB/s]
SDR104 @ 96MHz : r:44MB/s w:40MB/s  W:43MB/s R:44MB/s  meh [best 53MB/s]
SDR104 @ 96MHz : r:44MB/s w:43MB/s  W:41MB/s R:44MB/s  meh [best 53MB/s]
SDR104 @ 80MHz : r:37MB/s w:35MB/s  W:36MB/s R:37MB/s  meh [best 53MB/s]
SDR104 @ 80MHz : r:37MB/s w:36MB/s  W:35MB/s R:37MB/s  meh [best 53MB/s]
SDR104 @ 120MHz: r:54MB/s w:51MB/s  W:52MB/s R:55MB/s  meh [best 53MB/s]
SDR104 @ 120MHz: r:54MB/s w:53MB/s  W:51MB/s R:54MB/s  meh [best 53MB/s]
SDR104 @ 132MHz: r:60MB/s w:58MB/s  W:59MB/s R:60MB/s  : )  [best 58MB/s]
SDR104 @ 132MHz: r:60MB/s w:54MB/s  W:57MB/s R:60MB/s  meh [best 58MB/s]
SDR104 @ 160MHz: r:72MB/s w:69MB/s  W:69MB/s R:72MB/s  : )  [best 69MB/s]
SDR104 @ 160MHz: r:72MB/s w:69MB/s  W:68MB/s R:72MB/s  : )  [best 69MB/s]

Done.
Please run THOROUGH tests before using!!!

Tried in my 5d Mark II and I get these strong bands in photos
https://www.dropbox.com/s/2br0b39s5125lsv/Image%20139.png?dl=0

I use this https://www.magiclantern.fm/forum/index.php?topic=9102.0

I have replaced cr2hdr in Barracuda folder with this cr2hdr https://builds.magiclantern.fm/utilities.html

True:

Code Select Expand

else if(is_camera("7D", "2.0.3"))
    {
        trace_write(iocrypt_trace_ctx, "io_crypt: Detected 7D");
        iodev_table = 0x2D3B8;
        iodev_ctx = 0x85510;
        iodev_ctx_size = 0x18;

Code Select Expand

else
    {
        NotifyBox(2000, "io_crypt: Camera unsupported");
        return CBR_RET_ERROR;

dfort? g3gg0?

Not really an issue for me anymore. I updated to use the WFT-E5 I got last week, but it seems WFT-E5 isn't really my thing 

I will sell it and I have already downgraded the firmware to 2.0.3 again.

I have never used that module but if I got the addresses right it should work.

https://bitbucket.org/hudson/magic-lantern/pull-requests/878/update-to-7d206/diff#chg-modules/io_crypt/io_crypt.c

[EDIT] The example shows the addresses for 2.0.3 so I updated the example. The values used in the module didn't change with the firmware update.

Updated my 7D to 2.0.6 today. Installed magiclantern-Nightly.2018Feb28.7D206.zip from your https://bitbucket.org/daniel_fort/magic-lantern/downloads/

Downloaded io_crypt https://builds.magiclantern.fm/jenkins/job/io_crypt/2/artifact/modules/io_crypt/io_crypt.mo

When I activate the module I get: "io_crypt: camera unsupported".

I enabled benchmark and arkanoid module, restarted camera, low level formatted the card and restarted, pressed trash can and went into ML menu and memory benchmark (1 min).

Looking for a memory benchmark screenshot with any recent build (older than this post), taken in some particular conditions:

- photo mode, right after startup (without entering LiveView!)
- there should be no images on the card (the PLAY dialog must show "No image")

Running this scenario in QEMU gives artifacts on the screen; just wanted to check whether it also happens on real hardware.

If the screenshot doesn't look fine, try playing Arkanoid - it will show the same artifact.

Might also happen on other D5 models, but I've only seen it on 5D3 1.2.3 (on camera, but clean in QEMU) and on 6D (in QEMU). Enabling the change from 03c5f43 should fix it.

Extracts the second raw file from 5DIV.

https://www.fastrawviewer.com/DPRSplit

6D (better sensor than 5DIII) vs 5DII. http://www.photonstophotos.net/Charts/PDR_MagicLantern.htm

Good news for 2.0.6 -- I've got a working ML-SETUP.FIR Been testing it out and it is working fine.

So now you don't need to downgrade to 2.0.3 in order to set the camera bootflag.

As usual, my test builds are posted on my Bitbucket downloads page.

Does IO crypt also work with the new ML?

Only if you think you're going to get a full 15.4EV of good quality detail not drowned in noise, and you've forgotten that dual_iso has a con that revolves around the difference between the ISO's used.

Thank you.

Simple maths really.

log2(white point/noise).  In this case, the white point is the value recorded at ISO 100 with the noise level being determined at ISO 400.

Lets use the values recorded from my 6D.
https://www.dropbox.com/sh/rrn7chasohg36hk/AAD7fngMRzvGNfrz6IzOgX3pa?dl=0



log2(77323/7.95) = 13.24.  The measured dynamic range of my 6D at ISO 100 is 11.41.  13.24 - 11.41 = 1.83.

In other words, the maximum dynamic range improvement on this 6D with dual ISO 100/400 is 1.83 EV (stops).

Now, photographic dynamic range is an entirely subjective measurement.  If it says some value below 1.83 EV, fine.

I tried your full well capacity at ISO 100 -noise level at ISO 6400
Log2(77323/1,76)=15,4. Dual ISO 100/6400 gives DR of 15,4 Ev? Seems I missed something.

Are you able to use the camera even if your battery hatch is open? If that is the case I just suppose it is not a new firmware but the normal one in service mode.

An Introduction to Service Mode
The Problem
Until now, the only way to test whether you've successfully fixed a fault on an EOS camera is to completely reassemble it, and make sure the battery and memory card doors are closed, because the camera won't switch on otherwise.

This consumes valuable time, and can tempt you into using some precarious arrangements, like leaving the back panel hanging on by just the ribbon cable, or wedging the door switches closed. These arrangements inevitably lead to broken flexi-boards, connectors, switches, or worse.

They are also susceptible to cameras being inadvertently knocked off the desk, or otherwise damaged, if you happen to touch one of the high-voltage lines of the flash charging circuitry, not to mention the physical pain!



The Solution
The Service Mode Plugin solves this problem by setting the camera to a special mode that allows it to power up in a dissassembled state. It also allows you to disable the flash charging circuitry while you perform your repair. This can save many hours of bench time, and prevent those nasty electric shocks.



Service Mode
You can use the software to place the camera in Service Mode and/or Flash Disable Mode before you start working on it. Then simply quit the software in the normal way and unplug it.

While in Service Mode, the camera ignores the on/off switch or the door switches. It will power up with the rear display panel completely removed. It will also power up with other major boards completely removed - even the lower board!

While in Flash Disable Mode, you no longer need to remember to discharge the flash capacitor after every time you've connected the battery for testing.



You can now save hours of bench time, and avoid many potential accidents:

Access the inside of the camera while powered up, for your scope probes or voltmeters - without inviting disaster by having the back panel hanging off and the door switches wedged.
Test whether you've fixed the fault before fully assembling the camera.
Access important adjustment screws, and test their effect with or without SPT software connected.
Work around the high voltage circuitry in safety


Exiting Service Mode
The camera will stay in Service Mode until you reconnect it to SPT Software again. Just press the appropriate buttons on the Service Mode plugin to switch the camera back to normal mode, or switch the flash charge back on.

SPT Software will remind you if the camera is still in Service Mode or Flash Disable Mode every time you quit, so there's no danger of returning it to the customer in the wrong mode.

The difference between 1.1.6 and 1.1.7:

Corrects a phenomenon in which when using the camera with the EF 70-300mm f/4-5.6 IS II USM lens, even if lens aberration correction is set to "Enable", correction will not be applied.

You don't need 1.1.7.

Thank you very much.

If someone want to know the number of actuation on a recent camera, he must send his camera to Canon service center. Only Canon repair center can provide shutter count for these models actually. It's a shame canon won't allow its customers an accurate way to read shutter count.

Not really. http://www.spt.info/sptstore.php?crn=351&rn=713&action=show_detail

No, but this topic should help: http://www.magiclantern.fm/forum/index.php?topic=10111

Do you have a specific question about it?

No specific question. What I am after is something like The Children's Bible instead of the whole Bible. But your links in your link seems to be a good start http://theory.uchicago.edu/~ejm/pix/20d/tests/noise/index.html
http://theory.uchicago.edu/~ejm/pix/20d/tests/noise/noise-p2.html#SNR-DR

https://chdk.setepontos.com/index.php?topic=13014.0

Is there a tutorial for raw_diag.mo like the one for raw histogram http://www.magiclantern.fm/forum/index.php?topic=12096.0

[I tried remapping , didn't work]

I tried remapping , didn't work. I want to add that i work on mac. Danne - I'm not sure if I understand it im not a foreign english speaker but im interested in everything that could work. Could you explain it to me in more simple way please?

Did you try to heat the sensor first by using it for 5 minutes and did you try a couple of times?

Is it confirmed that the manual sensor cleaning thing is the real way of remapping the sensor? What I know, Canon denays it. I have tried my self and it worked, but I want to know why it worked.

http://www.filedropper.com/6dandd30

6D and a camera without ML, D30.