Messages

Yes, you understood right, I think too that you have the bootflag on, to turn it off you need a fir for that but I don't know if there is one yet.

If I'm following how this is all working I think you're right there scrax. I can't find a method or a .fir that will turn the bootflag off.

Ok , from what i can understand using the alpha should not enable the bootflag, you load ML manually with the firmware update menu and ML is not .bin it's .fir (signed)
Loading the fir that way will not need the bootflag enabled.

but there are some .fir for developers that will enable the bootflag, are you sure you didn't load them also?

I've been using the ordinary Alpha, versions 3 I think, for several months, since the time it came out, and that has always work as you're describing - it doesn't enable bootflag and every time I wanted to use it I had to go through the firmware update procedure.

I know it doesn't enable the bootflag because throughout that time I was using CF cards interchangeably between my 5d2 and my mark 3, and the CF cards all had 5d2 Magic Lantern on. As the MK3 bootflag was not set that was never an issue. I rar 5d3ML alpha from SD when needed.

That changed when I tried the RAW enabled version.
I followed the EOS HAD instructions from here:
http://www.eoshd.com/content/10352/easier-5d-mark-iii-raw-guide-in-4-steps
which directed me to download magic lantern from here:
http://www.magiclantern.fm/forum/index.php?topic=5413.0
That's the nightly builds thread.

The actual zip I used was "Magic Lantern May 19 e91e2bc.zip" but I imagine the other nightly builds behave the same way, right?

Does the camera show any other symptoms beside not showing the black and green success screen?

There's no problem with the camera.

The only 'symptom' it has is the bootflag is enabled and it seems to be impossible to turn it off. But I don't think it's unique to my camera because as far as I can tell no one else has managed to turn off the bootflag once enabled on their 5d3 either.

I can't turn off the bootflag because to do so it seems I need to get to the green on black screen - which I can't do.

How did you enabled the boot flag first?
I suppose there is a fir for that, have you tried to run it twice? I suppose that second time it will toggle bootflag off.
maybe Alex knows better

There's a .fir file on the card that I used to install/run magic lantern. That's the firmware it's running right?
And I run it by doing  a firmware update?

Doesn't do anything, never get to the green on black screen.

Can't you just update to firmware 1.21 and ML is no longer there?  Or should the title be "not possible to reverse the bootflag option"?

The title is "completely un-install" because that's what I want to be able to do. The bit that's not possible is is turning the bootflag off, as far as I can tell.

Sync the series in Camera Raw - which is a separate program from Photoshop but comes bundled with it.

I've been using sidecar files with .CR2, not tried with DNG yet. Reading Adobe's site it works slightly differently for DNG. http://help.adobe.com/en_US/lightroom/using/WS638E3AC9-A04C-4445-A0D3-F7D8BA5CDE37.html seems to say it should work the same, but with the metadata written into the DNG files rather than as sidecar files.

I believe Premiere is pretty much always editing with proxies behind the scenes anyway, just hiding that inconvenice from the user, so it doesn't require realtime playback/debayering of original .r3d or .raw files.

Just had another though  if anyone is struggling with inconsistencies in Lightroom.

As Lightroom and ACR use the same RAW conversion engine (provided they are on the same versions of Camera Raw) you could get around inconsisten Lightroom highlight recovery by:


- Grade one DNG in lightroom,
- save the settings to xmp sidecar data (Ctrl-S is the keyboard shortcut on Windows, but it's in the menus too)
- close lightroom and open that dng in ACR lightroom settings should already be applied to it (brought across via xmp)
- synch this dng to all the others in ACR

I think it's not possible, but would like to know for sure either way.

I definitely think anyone considering installing Magic Lantern for the first time should be told if there's no way to do a complete uninstall.

---------------------

I've been trying for several days now to remove all traces of the RAW video version of Magic Lantern from my 5D Mark III.
It's easy to delete the ML files from any given CF card, and straightforward to use EOScard to stop a CF card being bootable, but I can find no way to disable the bootflag in the camera.

I've searched these forums pretty thoroughly and spoken to a few people on here, but AFAIK no one knows how to disable the bootflag on the MKIII, so no one knows how to uninstall ML fully.

This thread "HOW ML START (or why it doesn't boot topic) & Restore Camera Settings"
http://www.magiclantern.fm/forum/index.php?topic=2522.0
explains how ML and the bootflag works in terms of install.

It gives a method to uninstall ML:
1. Start the firmware update procedure (with battery full, no accessory, M mode...) from canon menu and wait the green text.
2. change mode on the dial and wait the white text.
3. Restart camera, clear settings and Custom Func. and format card, low level (NOTE: you will lose also your pics of course).

But that method doesn't work on the MKIII as far as I can tell, because in point (1) it never gets to the point where there's green text on a black screen.


The wiki page gives no more help, because I think it's referring to the same method:
http://wiki.magiclantern.fm/faq#how_do_i_uninstall_it



a1ex suggests disabling the bootflag on a 60d on this thread http://www.magiclantern.fm/forum/index.php?topic=5594.0
by

"placing Canon FIR on the card"

Mikkel S. says on this thread http://www.magiclantern.fm/forum/index.php?topic=3852.0

"I put the 1.1.3 firmware from Canon (5D300113.FIR) on a blank card and turned on the camera."

but he's not sure if that really disabled the bootflag or not and it definitely doesn't for me.


I've now tried every combination of ML, ML+Canon and just canon .fir files on bootable and non-bootable cards, but none of them get me to the green text on black screen that I think is required to disable the bootflag.


-------------------


I've used ML on my 5D2 (two of them) for several years, and I've been using the alpha Mk3 software for many months, without any problems.

My preffered method with the MK3 is to run the ML Alpha from the SD slot, using the CF slot to store pictures and movies.
I can leave the 5D2 ML files on all my CF cards, and this way can share CF cards between cameras. With the bootflag permanently enable in my mk3 that no longer works.

I also have an Eye-Fi card, and the ML wiki makes me think this now won't work reliably.

... so there is no way to uninstall it? I think if everyone knew this there'd be a lot less people using Magic Lantern.

[Restore camera AND card]

Restore camera AND card to an original state from a working ML installation:

1. Start the firmware update procedure (with battery full, no accessory, M mode...) from canon menu and wait the green text.


2. change mode on the dial and wait the white text.


3. Restart camera, clear settings and Custom Func. and format card, low level (NOTE: you will lose also your pics of course).

This doesn't work on 5dmk3 with the RAW firmware.

After doing the firmware update procedure the camera just goes straight back to working, the greentext on black screen is never shown.

As far as I can tell there is no repeatable way to fully uninstall Magic Lantern from a 5dmlk3!

I put the 1.1.3 firmware from Canon (5D300113.FIR) on a blank card and turned on the camera. It started a regular firmware update automatically and the Camera is back to factory default firmware.

I tried this and it doesn't work for me. You don't say whether your 'blank' card had the bootflag enable on the card or not. I tried it with and without and neither helped.

With the bootflag and the 5D300113.FIR file on the card the camera seems to not power up when it's turned out - I think it#s trying to boot something that's not there.

With the bootflag not set on the card the camera just comes on as normal, no automatic firmware update. If I update it manually, going from 1.1.3->1.1.3 (the same version) it makes no change to the bootflag of the camera.

Are you sure you really got rid of ML from your camera?

Thank you!!! It worked, put canon 1.1.3 firmware on card, and everything is back.

I also trying to disable bootflag on my 5d3 but can't figure it out.

Which card did you put the 1.1.3 firmware on?
Did it also have all the magic lantern files?

NO, It will not load ML for that session.
To remove the bootflag and understand better the boot process read this

I'm having the same problem uninstalling magic lantern from my mark 3. I can't disable to bootflag. I read the page you linked to, but following the instructions doesn;t work because my camera never gets to the screen of grren text. This one:
http://wiki.magiclantern.fm/_media/success.png

The way I get it to work is by making the card bootable with all your usualy ML shit on their and the fir that you used to install it in the first place. When "update" it'll look like it's installed again but tell you to move to another shooting mode to remove the bootflag.

That is on a 6D and we don't even have alpha yet lol

So you use the same card you used to install magic lantern, with exactly the same files, with magic lantern already loaded you run the firmware update again?

The green text on black still doesn't appear for me.

I have a similar problem. I've just tried out the new raw firmware for the Mk3 which enabled bootflag, but now I can't disable it.

I need to disable it because I usually run 5d3 alpha Magic Lantern from the SD card while using large CF cards in the CF slot. The CF cards all have 5d3 magic lantern on becuase I used them with that camera too.

Is there a way to disable to bootflag on the Mk3 and completely remove ML?

------------

The uninstall instructions given here:
http://magiclantern.wikia.com/wiki/Unified/Install

Don't seem to work:

" Uninstalling ML from the camera
    With a Magic Lantern card, launch the Firmware Update process and follow the instructions on-screen. "

That doesn't work because the firmware update just finished and there are no on-screen instructions.

It would be much more likely we could get support in Red Giant's new "Bulletproof" app

http://www.redgiant.com/blog/2013/05/21/red-giant-bulletproof-beta-download-it-now-for-free/

It's still in beta so being actively developed, and Stu Maschwitz is involved, this guy:
http://prolost.com/blog/2013/5/15/space-monkeys-raw-video-and-giving-us-all-youve-got.html

http://en.wikipedia.org/wiki/Fixed-pattern_noise
This is how your sensor looks +3 stops @ 160 ISO. It's got nothing to do with ML except for the fact it's no longer denoised and compressed in camera.

I don't think that's a major problem, why would you ever want to push a nearly black image by 3 stops???
Would be good to get rid of it anyway though!



I see you're shooting at ISO 160, why?

The idea of shooting in multiples of 160 is only relevant for standard compressed video shooting, due to the way intermediate ISOs are processed in camera. Eg 160 is a 1/3 stop pull from ISO 200 sensor data before writing to h264.

The 'real' ISOs of the mk3, as evident from analysis of RAW stills , are:
100, 200, 400, 800, 1600, 3200 and 6400. Maybe also 12800.

Going forward for maximum RAW quality these are the multiples we should be shooting in a think

I would have preferred to be able to use Lightroom 4 processing raw. Too bad that batch processing show inconsistent results. For instance when getting highligts back whites treats differently on different frames. This is not a problem in adobe camera raw. Personally I believe the raw engine has gotten worse in lightroom 4 compared to version 3. Lightroom 3 is also inconsistent but not as much.
For now I work with fast conversion to ProRes422HQ via AE, using either the PS camera raw engine or directly in AE. It,s only one or two steps away after the files are converted. Made a workflow tutorial about this, easy to follow.

'http://www.youtube.com/watch?v=MSHVi7Jx9r0

//D

Many people process timelapses in Lightroom, so it must be possible to get consistent frame-frame exposures using it.

This plugin
http://lrtimelapse.com/
is specifically for doing timelapse in Lightroom and it may be some use for processing frames of video too.

If you don't like the current way Lighrtoom deals with RAW you can revert to the old 'process version', it's in the develop module under 'Camera Calibration' (near the bottom of the right hand panel.

Adobe says (and my experience tallies with this) that equivalent versions of Lightroom and Camera Raw use EXACTLY the same conversion engine, so I don't know why you'd have different results with the two, maybe you have slightly different versions installed, as Camera Raw gets updated more often than Lightroom, but Lightroom is sometimes ahead on big releases.

Sadly, I've upgraded to 1.2.1 and my 5D3 is being used with an Atomos for a project... so I can't test this builds out until it is done.

But, I was thinking... the main problem it seems we're dealing with here is the write speed of the CF cards, right?

There are plenty of companies that make CF to SSD converters... there HAS to be a way to adapter SSD to CF.  Right?

That would solve all the issues of speed, and storage with raw shooting.  Some sort of external module with a cable connector
and a pin converter...

Or am I just being hopeful?

Dave

How about recording to the CF and SC cards in parallel? Twice the capacity and ???x the speed?