Magic Lantern adds 1/3-1/2 stop of dynamic range - just like that.

[weixing]

Re: Magic Lantern adds 1/2 stop of dynamic range - just like that.

Does anyone think Canon is reading this stuff because I am baffled as to why they would cut shot the DR and cheat on RAW's with fast lenses.

Hi,
IMHO, commercial product don't push their product to the limit... they usually hold back to ensure reliability... it's just like computer when you can overclock the processor on your custom made PC to the limit, but most major brand PC manufacturer won't overclock the same processor on their PC to that limit.

Have a nice day.

 

[funkboy]

Re: Magic Lantern adds 1/2 stop of dynamic range - just like that.

The impossibility of the boot flag reset (= warranty loss) ist the only thing that stops me and thousands other people from trying the ML RAW. So far I could not find any way to do it.

A Canon rep was quoted on the record as saying something to the effect of:

There's no way to "void" your warranty on a Canon camera. There is only the question of "covered" repairs and "uncovered" repairs. If the camera is still within the warranty period, the specific repair request you're submitting will be evaluated by the repair center as "covered" or "uncovered" based on whether the issue is determined to have been caused by a problem covered by our warranty policy.

Google it a bit & I'm sure you'll find it.

Basically it means that if you change the boot flag in all likelyhood the only warranty repair that wouldn't be covered would be if the camera was determined to be damaged by you monkeying with the firmware.

...which is a much better policy than e.g. certain Android phone makers that say "sure we'll give you the knob so you can unlock the bootloader, but don't expect us to repair your phone if the camera module dies".

 

[Marsu42]

Re: Magic Lantern adds 1/2 stop of dynamic range - just like that.

...which is a much better policy than e.g. certain Android phone makers that say "sure we'll give you the knob so you can unlock the bootloader, but don't expect us to repair your phone if the camera module dies".

I'm sure this depends a lot on local law, but in the EU/Germany it was ruled again and again that tampering with a product doesn't automatically void all warranty even if the manufacturer says so. This esp. concerns badges "warranty void if removed", but will also apply for example to mechanical failure which has nothing to do with the installed ML.

 

[Scott_McPhee]

Re: Magic Lantern adds 1/2 stop of dynamic range - just like that.

Is this the new nightly build for the 5D3 that adds this?

Latest Build

Built on: 2014-01-24 00:11:15 +0000
Changeset: 42c206c28f3a8b33e04ac075f66526dcf55901bc

I am really interested to try this on my 5D3 as I have seen some wonderful shots taken using features such as dual ISO but just concerned, as we all are, of damage to the camera.

I work with a single 5D3 and have heard about boot times being much longer.
Also, how does any settings I have like AFMA and Canon stock settings work along with ML - are they still used?

Sorry for the questions, ML newbie here!

 

[cayenne]

Re: Magic Lantern adds 1/2 stop of dynamic range - just like that.

The impossibility of the boot flag reset (= warranty loss) ist the only thing that stops me and thousands other people from trying the ML RAW. So far I could not find any way to do it.

A Canon rep was quoted on the record as saying something to the effect of:

There's no way to "void" your warranty on a Canon camera. There is only the question of "covered" repairs and "uncovered" repairs. If the camera is still within the warranty period, the specific repair request you're submitting will be evaluated by the repair center as "covered" or "uncovered" based on whether the issue is determined to have been caused by a problem covered by our warranty policy.

Google it a bit & I'm sure you'll find it.

Basically it means that if you change the boot flag in all likelyhood the only warranty repair that wouldn't be covered would be if the camera was determined to be damaged by you monkeying with the firmware.

...which is a much better policy than e.g. certain Android phone makers that say "sure we'll give you the knob so you can unlock the bootloader, but don't expect us to repair your phone if the camera module dies".

I"m actually no that worried about the warranty stuff....

I'm more concerned with the long boot and wakeup times that seem to also be a permanent change even if you remove the ML software.

 

[John Thomas]

The critical question:

Does ML work with the latest 5D3 firmware?

The version 1.2.3 of the firmware has enough time now in our cameras, however ML supports (AFAIS) just 1.1.3

It is so hard to fix / test it against 1.2.3?

 

[flowers]

Re: Magic Lantern adds 1/2 stop of dynamic range - just like that.

The impossibility of the boot flag reset (= warranty loss) ist the only thing that stops me and thousands other people from trying the ML RAW. So far I could not find any way to do it.

We have got to kill that myth…

You will ONLY void the part of the warranty that has to do with the software and firmware of the camera.

Say fx, you install ML… and within two weeks, your accidentally break the LCD or a button comes off or what ever. Those things are still covered. It's impossible to void anything that has not directly to do with the things that ML changes.

Having said that…. I haven't had a single issue with ML on my 5D3. And since you keep ML in the SD card slot and record to the CF card slot, you can remove ML pretty easily… simply power off, remove SD card, remove battery, and you are back to the old Canon again.

Actually, not correct (unless they have changed their mind at Canon). Canon firmware is still covered. It will not be covered only if Canon comes to the conclusion that the fault was directly caused by the ML firmware and not Canon firmware. A slight but important distinction.

 

[flowers]

The critical question:

Does ML work with the latest 5D3 firmware?

The version 1.2.3 of the firmware has enough time now in our cameras, however ML supports (AFAIS) just 1.1.3

It is so hard to fix / test it against 1.2.3?

Every new firmware is different from the previous and requires a lot of additional testing to be even remotely safe and functional.
1.1.3 with ML will give you a lot more than 1.2.3 without ML. ML is already free, you really shouldn't complain.

 

[Marsu42]

It is so hard to fix / test it against 1.2.3?

It's not hard, but time-intensive because all the addresses of the Canon fw functions have changed, and some function themselves might have. As Canon provides no documentation, all this has to been done by hand which is a lot of work and no progress at all for the ML code itself.

Please visit the ML forum and volunteer to help out a couple of days for free finding these pointers, it isn't hard as you theorized, all has to be done is wading through the ROM dump doing trial & error: http://www.magiclantern.fm/forum ... afterwards you can then help me comment on people's "I want free work for my 5d3 from people who cannot even afford a 6d" attitude over here

 

[eyeland]

In regards to the boot delay, it will feel like an instant after you realize how time-consuming the RAW video post workflow is

 

[East Wind Photography]

So is it really possible to downgrade a 5d3 from 1.2.3 to the required 1.1.3? The 1.2.3 fw docs state that it is not possible to revert back.

 

[tron]

In regards to the boot delay, it will feel like an instant after you realize how time-consuming the RAW video post workflow is

This is comparing apples to oranges: Post workflow with shooting!

BUT, this is not the main issue with the delay. The main issue is the wake up delay (yes there is wake up delay with ML). Power off is one case, waking from sleep is 10-100 fold more often...

 

[Marsu42]

BUT, this is not the main issue with the delay. The main issue is the wake up delay (yes there is wake up delay with ML). Power off is one case, waking from sleep is 10-100 fold more often...

I have to say you're reporting this is the first time I've ever heard this - but then again, I'm on 6d where the boot delay seems to be much shorter anyway. Feel free to report your issue to the ml forum, they can probably find a way to improve sleep wakeup time - unlike the boot delay when ML gets loaded in the first place.

 

[tron]

BUT, this is not the main issue with the delay. The main issue is the wake up delay (yes there is wake up delay with ML). Power off is one case, waking from sleep is 10-100 fold more often...

I have to say you're reporting this is the first time I've ever heard this - but then again, I'm on 6d where the boot delay seems to be much shorter anyway. Feel free to report your issue to the ml forum, they can probably find a way to improve sleep wakeup time - unlike the boot delay when ML gets loaded in the first place.

I am saying this because I do not consider the boot time a significant issue. The issue (wake up delay) is reproducible with my 5D2 actually and the feeling is that this delay makes press the shutter button more than once to activate the camera. It was frustrating until I realized it that it was due to ML. I uninstalled ML, saw that my 5D2 is responsive and then installed ML again. It was nice to know that if I need this speed I will simply uninstall ML and then reinstall it (actually that's why I keep the .fir file with the nightly build. So no issues as long as I uninstall it when I need to

 

[Scott_McPhee]

Some more info on a possible ML for 1.2.3 here:

https://bitbucket.org/hudson/magic-lantern/pull-request/354/ported-ml-over-to-5d3-firmware-123/diff

 

[tron]

Some more info on a possible ML for 1.2.3 here:

https://bitbucket.org/hudson/magic-lantern/pull-request/354/ported-ml-over-to-5d3-firmware-123/diff

Very encouraging. If they also make it capable of boot flag removal I believe it will skyrocket both ML and use of 5D3 for landscapes (thanks to dual_iso module).

 

[Marsu42]

If they also make it capable of boot flag removal I believe it will skyrocket both ML and use of 5D3 for landscapes (thanks to dual_iso module).

The dual_iso module is designed for moving high-dr scenes, for landscape you want to do real bracketing as this doesn't lose detail in the highlights and shadows.

 

[tron]

If they also make it capable of boot flag removal I believe it will skyrocket both ML and use of 5D3 for landscapes (thanks to dual_iso module).

The dual_iso module is designed for moving high-dr scenes, for landscape you want to do real bracketing as this doesn't lose detail in the highlights and shadows.

Yes but sometimes there are leaves that move...
But, even with no moveable parts I still prefer to sacrifice some (slight) resolution and get a single raw file to begin with. Maybe I was talking for myself but I consider Dual_Iso a HUGE advantage of ML...

 

[Marsu42]

Yes but sometimes there are leaves that move...

Good point, as that also counts as "landscape"...

But, even with no moveable parts I still prefer to sacrifice some (slight) resolution and get a single raw file to begin with.

Indeed, that's why I'm so annoyed unlike the 5d3, the 6d doesn't do raw in-camera hdr (thanks, Canon!)

Maybe I was talking for myself but I consider Dual_Iso a HUGE advantage of ML...

It is, but dual_iso also has more noise (since it's interlaced with higher iso) and still unsolved wb issues in the acr workflow, plus it needs double the storage - once for the original cr2 to profit from cr2hdr advancements, and once again for the converted dng. For me it's best to take nice static scenes as real bracketing, but dual_iso is nice for "just gimme more dr" if the result doesn't need to have the best iq.

 

[Sella174]

How much of all this will be down-pulled to the EOS 5D camera?