Magic Lantern Forum

(http://www.magiclantern.fm/images/5dhello2.jpg)

ML will work on 5D Mark III. Right now it's in very early stage - the early testers reported it as almost unusable.

I hugely look forward to this as an old user (and donator) when I had the 60D I found the software outstanding... now months on I'm getting the 5DIII and really look forward to getting ML back.

We may have a early beta for 5D3 in one or two months, so stay tuned.

Hi all

just wanted to say how amazing yours projects are.
I have been working on semi-professional cameras, now owner of a mark III, I have to say that I am stunned with the quality (blacks are real nice) but stil, what a lack of features.

!!Please develop the Mark III software!!

Seriously that is some sick updates, I NEED the Magnification and Zebras, so usefull.

Thanks for your time again, I hope to get news as soon as you guys can reach an early stage of development.


One

The only way to get it quicker is to help us buy a 5D Mark III ;)

Done ;)

Well sort of despite only having a 5D III so cannot use Magic Lantern I am a long time supporter (I donated back when I had the 60D), now if only another 199 or so would do the same you'd have a shiny new body in your hands and we'll all have ML on our cameras.

Come on guys dig in and get it sorted!

Can someone with a 5d3 please send me a ROM dump from 0xFF0C0000 - 0xFFFF0000 of firmware v1.1.3?

coutts, if you (or anyone else) explain me (or send me a link of) how to do it, i'll send it pretty soon! :D
I tried to find a clue of how to do it, but I got lost with all I found.

- regards from Brazil!

I'll prepare you a test binary.

oook, I'll wait for it!

Having been using ML on a 550d for yonks, and just upgraded to a 5DM3, I keep finding myself think wtf... where's the functionality gone... oh yeah no ML.... Can't wait for this to be ready

If you need anything else please feel free to ask - did you get the ROM dump?  If not then tell me how and I'll do one for you.

I am willing to contribute $200 by Paypal in buying a Canon 5D Mark III. This way if only 20 of us chip in, we can all lay our hands on a working copy of ML faster.

What do the others think.

Cheers vijaymukhi712 - that will have made a decent dent in the needed funds (or will when you donate) - I wish I had the spare cash to stump up that kind of money but if everyone puts in whatever they can afford I think we can get there pretty quickly.

I just used Paypal to make a contribution of $50 + $150 to Magic Lantern.

I would like to place on record that I am not doing anyone a favor, Alex and his team at ML are doing all of us a favor by allowing us to do with our Canon cameras what Canon does not want us to do. I do not understand why it is only in the camera ecosystem where everything is so closed. I also do not understand why the camera companies are not learning from the Computer/Mobile world on opening up their systems.

I may never use ML to take professional photographs, for me what is most important is using ML to understand the internals of a camera. DryOS brings back the good old days of MS-DOS which allowed you to get into the internals of computers. That makes me very old.

I live in Mumbai , India and if Alex and his ML team are ever in this part of the world, it would be an honor for me to buy them lunch or dinner at place of their choice.

Vijay Mukhi

That is very kind, thank you Vijay - thats us all a step closer and I'm sure Alex and the team don't mind getting a shiny camera either ;)

I know what you mean about camera companies learning, for years now I've said that they should take a long hard look at what they are doing here and integrate the features into their cameras - well apart from audio graphs which they have nicked - imagine if they did what the normal chap(ess) on the street could do and it would put them miles ahead of the competition instead of stagnating it.

JohnN , just my point.

I have written code in ObjectiveC for the iPad/iPhone and Java for the Android to enhance their photography features. It simply takes too long and takes a lot of effort. Just not worth it. These phones are not optimized for programmers using the camera.  I can do much more using LUA and the CHDK.

Nearly all the photographers that I meet in india and I meet a lot of them do not believe that technology can play a big role in what they do. They see their role in just being creative and they want no part either in post production like Photoshop or in the printing process. In fact a lot of advice that I read on the Net applies to film and not digital.

The Phone ecosystem of writing Apps did not exist till Apple allowed us to extend the phone and see what it did for Apples fortunes . When will the camera companies wake up and create a ecosystem that allows all of us to extend the cameras. I am surprised that the success of CHDK and ML has not opened their eyes.

By the way, most of the top 10 cameras companies are Japanese.

Hi guys
is there a specific link for 5d mark iii donation?

I'm willing to donate more euros for that  ;)

Cheers
Fabio

We just have one general donation option. The poll in the download section says 1/3rd of the community wants a 5Dmk3 port so we are determined to get one to develop on.

I have a 5DM3 and would loooooove to have ML!

I'm willing to help with ANYTHING.

I just read here that Alex has a 5D3 (here: http://www.canonrumors.com/forum/index.php?topic=8807.15) - is this true?

I hope so - btw Alex - great camera isn't it :)

Yes, the camera should be on its way as we speak

Quote from: nanomad on August 21, 2012, 12:42:49 PM
Yes, the camera should be on its way as we speak

The most frequently asked question in the Canon Rumors forum is "When will the 5d3 port be ready" and some people stated it won't be long, even that the first version will be out in October...

... can anyone please give some prediction about how long the port will take, or alternatively just make it clear that it'll be released when it's ready and any other statement is pure guesswork?

Quote from: Marsu42 on August 23, 2012, 01:19:31 AM
or alternatively just make it clear that it'll be released when it's ready and any other statement is pure guesswork?

That would be the answer right there. ML developments comes in leaps and steps. No one will be able to tell you how many leaps and how many steps until a stable 5d3 port until they have already taken those leaps and steps.

My 5D Mark III arrived today :)

Quote from: a1ex on August 29, 2012, 09:38:25 AM
My 5D Mark III arrived today :)

I'm so glad to hear it!!!! Good porting man! I can not wait to try it on my camera!

Low-level progress here: https://bitbucket.org/hudson/magic-lantern/changesets

Roughly half of the things are already working, as I did an early port without having the camera in my hands. However, before publishing some early betas I need to go through each menu and try everything. It will take a while.

Meanwhile you can suggest what things you are missing on 5D3 without ML.

I'll start:
- zoom button back to its old place -> very hard to do, as the old button shares the code with the other top buttons (I can't figure out which of the top buttons was pressed).
- Canon menu feels very cluttered (can't fix this :P )

Other things:
- HDR bracketing looks pretty nice in Canon's implementation (7 frames), do we still need ML HDR?
- I'm thinking to limit ML to CF cards only, anyone requires SD cards?

Just CF would be pretty much a show stopper, as I now a few, incl. myself, using the SD card for eye-fi. At least keep the support for writing the JPG files onto SD.

Otherwise, I am looking forward to see what you will bring to the 5DIII.

You can use both cards: the CF one loaded with ML, and the SD for recording photos/videos (just tried).

This has the advantage that you can keep ML settings when swapping the SD cards :)

That s a good thing, so you can record to several sd cards, even if ml is not on them.
in camera-hdr bracketing is nice, but it would be cool to combine it with interval, so you can do hdr timelapse.
the overlays or a clean hdmi out would definetely be cool, but the most important thing would be zebras and peaking.
I can t wait to test it on my camera! great work!!!

Right, so it's practically the same thing as if you would install ML in the camera (from a convenience's point of view).

Zebras and peaking are already working, even fast zebras worked from the first try :)

really cool :)
is it possible to keep the drive letters #define-able so users would be able to compile custom veriants if they need that.

I would be happy with a version with only peaking and zebras for the beginning, if it would come out fast ;)

CBR ALL-I implementation is a must have feature. The Magic Lantern ISO's sound cool too.

I can change max bitrate and quantizers, but that's all.

Awesome work on ML so far!

Besides what's already been mentioned, I personally miss the Intervalometer and the Bulb Timer :)

Jesper

Quote from: a1ex on August 29, 2012, 04:07:04 PM
I can change max bitrate and quantizers, but that's all.

That's all *yet*

It's not the same as in digic 4, it was researched from scratch. I've exposed all the H.264 parameters to Marvin and that's all he could control.

Those are the parameters for ALL-I. Most of them give ERR70 if changed.

Transform8x8Flag = 2
Profile = 100
Level = 51
BitRate = 90000000
EntropyCodingMode = 0
IntraPicInitQP = 20
InterPicInitQP = 20
QpOffsetForB = 0
MinQpI = 10
MinQpP = 10
MinQpB = 10
MaxQpI = 51
MaxQpP = 51
MaxQpB = 51
MinBitrate = 0
MaxBitrate = 0
SarWidth = 0
SarHeight = 0
AspectRatioIdc = 1
VideoFmtAndVspFlag = 81
VideoFullRangeFlag = 1
TimingInfoPresentFlag = 0
RateControlEnable = 2
ScalingMatrices = 0
pScalingMatrixAddr[0] = 0
pScalingMatrixAddr[1] = 0
pScalingMatrixAddr[2] = 0
pScalingMatrixAddr[3] = 0
pScalingMatrixAddr[4] = 0
pScalingMatrixAddr[5] = 0


Quote from: a1ex on August 29, 2012, 09:38:25 AM
My 5D Mark III arrived today :)

Excellent - great news indeed - its a good body isn't it?

Clean uncompressed HDMI output(like the D800) would be amazing though unlikely.
4:2:2 would be amazing as well but as I understand it's even less likely.
1080 50P would be a pretty nice feature
720 100P also cool

But somehow I got the feeling that all my wishes are almost impossible to implement.  :)

You having the 5D3 is great news! :)

Timelapse functions would be great, possibly combined with bracketing.
Advanced codec settings maybe

One highly appreciated feature would be video recording auto restart one the timelimit is hit.

Great to hear that zebras work :)

Woohoo I'm so looking forward to give it a try, keep up the great work! :)

Quote from: a1ex on August 29, 2012, 04:07:04 PM
I can change max bitrate and quantizers, but that's all.

Excuse my ignorance, what's a quantizer? Pushing the bit-rate should certainly help but VBR was a drama on the MKII. What's the situation with IPB?

Here you go: http://en.wikipedia.org/wiki/Quantization_%28signal_processing%29 and http://vcodex.blogspot.com/2009/04/h264-quantization-parameter.html

In all Canon DSLRs, the algorithm is VBR with a max bitrate limit. When this limit is low enough, the bitrate is almost constant in practice, so this combination of settings is labeled as CBR. When this limit is raised, some scenes will not have enough detail to increase the bitrate (in most cases because quantizers are at lowest level, so quality is as high as it can get).

There is hope for MJPEG 422 or clean HDMI out though :)

Quote from: a1ex on August 30, 2012, 08:39:47 AM
There is hope for MJPEG 422 or clean HDMI out though :)

Amazing!

BTW, is there a way to get 1:1 Crop?

Yes, record the 5x zoom image via HDMI - it's 1:1 crop on all Canon cameras ;)

Quote from: a1ex on August 29, 2012, 12:44:02 PM
- HDR bracketing looks pretty nice in Canon's implementation (7 frames), do we still need ML HDR?

... but Canon doesn't do *automatic* bracketing with as many frames as it takes, or weren't you talking about that?

Quote from: a1ex on August 29, 2012, 12:44:02 PM
- I'm thinking to limit ML to CF cards only, anyone requires SD cards?

... I think it should be the other way around (!): The sd card controller on the 5d3 is crippled and only writes at very slow speeds if you didn't realize yet - so many people will be using the sd slot only for backup purposes (like write jpeg to it while raw/video goes to cf). Thus, cf cards will get changed much more often, and ml might be better placed on the sd that stays in the camera.

I didn't play much with it, but it has an auto setting. Not sure what it does, I didn't read the manual.

Good point about ML on the other type card that you normally use. However, this complicates things a bit, as ML was designed to work with a single card drive, and it would require major code changes (those CARD_DRIVE"path/to/file" constructs would no longer work if CARD_DRIVE is not a constant).

Being all uppercase doesn't mean it has to be a constant  ::)
If, during the boot process and before ML reads its config, we can discover which card ML is on we can then simply set the static variable CARD_DRIVE to the correct value.
For example, we could use a simple fopen B:/autoexec.bin and if it fails it must mean that the card is on the other drive

CARD_DRIVE is used in string concatenation at compile time ;)

Fun stuff: the 5D3 has a headphone jack and it's possible to upload music on it and listen while taking pictures :)

On-topic: audio meters are working, but Canon has them too.

Ouch  >:(

Quote from: a1ex on August 30, 2012, 08:39:47 AM

There is hope for MJPEG 422 or clean HDMI out though :)

MJPEG 422 would be bloody fantastic in the 150-200Mbit/s range ;D No real need for ProRes then.

MJPEG 422... very exciting prospect! Hope it's possible.

I would love to see this new piece of hardware and processing power that the Mark 3 brings put to full use. I might be aiming too high here but bitrate and output like the GH2 hacked would be awesome! It would be great to see sharp video like that come out of the mark 3

thanks for all the work you have put in so far a1ex!

Quote from: a1ex on August 30, 2012, 11:06:01 AM
CARD_DRIVE is used in string concatenation at compile time ;)

Well, then the easiest way would be to do two compiles (at least for ml release versions), one for the sd and one for cf card slot? Imho that would be better than to force end-users to use one specific slot.

Hi all,

Thanks for your great job and really happy to hear that things are on a good way.

I used a couple of 60D in tv documentary production for one year with great results. I would never have tried that without ML. Now I would like to switch to my brand new 5D3 !

All you can do is highly appreciated but here is what is most important for my video use :

- Analog audio gain control with separated values for each channel.

- Audio graphic monitoring in the upper black part of the screen like others ML. Canon implemented one indeed but so badly located and small!

- Possibility to adjust the audio output level - essentially louden

- Same iso treatment as ML 2.3

- Expo override 1/25e

- Zebra, focus peak, histogram, magic zoom, discrete virtual horizon

- Possibility to flip the screen vertically and/or horizontally in order to use a small mirror system to compensate the lack of rotating screen.

All you can do to enhance video quality is also very welcome : higher bitrate, clean 4.2.2 on HDMI, HDR in 1080p25...

Just an idea/question : is it possible to make raid 0 using the 2 slots, with 1 sd and 1 cf of same capacities, to be able to record very high bitrate or fps?

Thanks again and hope to hear from you soon.

Pascal

Raid 0 seems like it would be unlikely. Raid controllers are hardware, not software. Raid software emulators are typically restricted to raid 1. Also you would have to figure out a way to mount both cards as a RAID 0 array on your computer to get the files off of the cards.  I would also imagine that the write speeds are not the same for the 2 card slots.

Hey Alex and crew!

Sad but true... I finally managed to make time this morning to load ML on my 5D2 - have been intending to check out the latest version for months but finally forced myself to make some time.

Have to say I'm incredibly impressed. Last time I tried it was about a year or so ago and it was good, but confusing to use... this latest version is absolutely amazing! I cannot believe what you guys have managed to do and now, I'm totally pissed at  Canon for their lack of foresight to implement some of these features! Geez, I mean really... why can't they at least include an intervalometer? Basic stuff.

Quote from: Francis on September 02, 2012, 05:24:25 AM
Raid 0 seems like it would be unlikely. (...)  I would also imagine that the write speeds are not the same for the 2 card slots.

This is true. There even was a big discussion o how the SD card slows down the CF one (in specific cases) because of the throughput differences: jeffcable.blogspot.com/2012/06/why-you-should-not-put-sd-card-in-your.html?m=1

Read your low level progress. Real time defishing is an interesting feature. Can it work on video too? Are all those features in the stock firmware and just disabled by canon or is it so we thing you write yourself?

Most ML features were written from scratch; there are very few features that were present in Canon firmware but are just hidden. Movie recording on 50D and Kelvin WB on Rebel cameras are some examples of unlocked features.

Digic effects (including ML ISOs or display contrast/saturation) could also be considered unlocked features: the image processing chip (seen as a library of routines) implements them, but they are not present in the main firmware. It's not something implemented and then removed from Canon menus, but a capability of the image processor which was not fully used.

Defishing is for preview only, to help with framing.

Regarding the CPU power: I went ahead and implemented a new display mode for focus peaking, with alpha blending rather than small blinking dots, which looks very nice but it's a bit slow (LiveView runs 15-20 fps with this enabled). I didn't think DIGIC 4 is fast enough for this, but had a big surprise: on 5D2, the same code runs just as fast as on 5D3. So, either the ARM chip from DIGIC V is just as fast (or as slow) as in DIGIC IV, or there's more CPU power used by Canon tasks (and less left for ML tasks). Maybe the speed-up in DIGIC V was only for the image processing chips?

Do you think you can do a alpha build to enable the community to provide you with feedback or is it still a bit too early for that?

In case you do not wish to publish a done build for the 5d3, is it possible to try and build it yourself or would you recommend to not do that because it's too unsafe atm?

Your work is greatly appreciated! Only today we were filming an event with a few EOS cams and i sooo wished for some of the ML features like focus peek and zebras on the 5d3 and not only on the 550ds.

It's a bit too early at this point. I've saved a ROM dump from my camera, just in case. Overall it works pretty well, but it doesn't feel as solid as it's on 5D2 (I've got some random ERR02 messages).

I'm thinking to start with a beta with few features (for example, start with zebras, peaking, histograms), have a few early testers run it for one week, and if it's rock solid, I can add some more things. Then repeat this process as many weeks as needed, until the port is complete.

There is an issue that's stopping me for publishing it: how to handle multiple cards. Right now it's hardcoded to work on CF cards only. As long as you don't use any features that access the filesystem (like movie logging, HDR post scripts or other files created by ML), you can also boot ML from a CF card and save pictures/movies on a SD card.

I could compile two binaries - one for CF cards and another for SD cards - and select one automatically. I have to find a way to detect which cards are loaded from bootloader stage. I'm afraid that letting the users manually choose the right version will create trouble.

Restoring ML after format doesn't work, so probably the best way to deploy it will be to load ML on a SD card (which will always be in the camera), and shoot on CF cards. Or viceversa (load ML on a CF cards and shoot on SD cards).

Handling multiple cards requires some major code changes, and I've already had trouble with the most basic file I/O calls ( http://www.magiclantern.fm/forum/index.php?topic=2528.0 ) .

Since my proposal of limiting it to CF cards was not welcome, I think we'll have to wait until these things are solved.

Quote from: a1ex on September 03, 2012, 07:38:28 PM
So, either the ARM chip from DIGIC V is just as fast (or as slow) as in DIGIC IV, or there's more CPU power used by Canon tasks (and less left for ML tasks). Maybe the speed-up in DIGIC V was only for the image processing chips?

As I understand canon changed the video "resize" method for the 5d3. They used to line skip but now, considering the absence of aliasing, they use a more advanced resize method. Not sure if that's true but I think they also enabled chromatic aberration correction for photo and video as well. I guess that uses some precessing power too. No wonder you're left with only a fraction of the DIGIC5+ CPU power.

I also wonder if the 5d can do 4k video as the 1D C does.

A beta with only a few features once you are satisfied with their stability sounds like a sane way to proceed.

Quote from: a1ex on September 03, 2012, 08:52:03 PM
Since my proposal of limiting it to CF cards was not welcome, I think we'll have to wait until these things are solved.

Personally I like the idea of using the SD slot as ~permanent residence for ML since as above stated it is slower than the CF slot when used and hence is absolutely uninteresting to me. That approach would also likely get rid of any issues resulting from a format of the CF card.

Depending on what cam you previously had there are obviously reasons for wanting to use the SD slot as primary slot, due to e.g. a already purchased SD card army, but CF cards aren't that steep an investment compared to the price of the 5d3. You can get a reasonable fast 32GB 600x CF card for under 80€ these days and that's one with 90mb/s read and write.

Heading for the CF slot as pic/video dump might also make more sense simply due to it's speed and possibly higher bitrate video output due to that fact?

I would be happy to have ML working with either card option - whichever works best. It will very difficult to please everyone in this regard so perhaps stability and function should be the overriding factor.

Quote from: csound on September 04, 2012, 03:57:20 AM
I would be happy to have ML working with either card option - whichever works best. It will very difficult to please everyone in this regard so perhaps stability and function should be the overriding factor.

Agreed - given what they're getting (most likely for free) surely they can stump up for a card they can use for images too!

Quote from: a1ex on September 03, 2012, 08:52:03 PM

Restoring ML after format doesn't work, so probably the best way to deploy it will be to load ML on a SD card (which will always be in the camera), and shoot on CF cards. Or viceversa (load ML on a CF cards and shoot on SD cards).

Handling multiple cards requires some major code changes, and I've already had trouble with the most basic file I/O calls ( http://www.magiclantern.fm/forum/index.php?topic=2528.0 ) .

Since my proposal of limiting it to CF cards was not welcome, I think we'll have to wait until these things are solved.

Loading ML from an SD card and recording to a CF card is the best option looking forward. If you can enable MJPEG 422 or push the ALL-I bit-rate then recording to CF cards makes much more sense. Media is cheap as chips these days so it's a very small investment for welcome new features. Spending days or weeks trying to get ML loading from both slots is a big waste of your time given that it doesn't improve on the MKIII's filmmaking ability one bit.

I'm up for being a bit-rate crash test dummy.

Quote from: squig on September 04, 2012, 04:27:56 PM
Loading ML from an SD card and recording to a CF card is the best option looking forward. If you can enable MJPEG 422 or push the ALL-I bit-rate then recording to CF cards makes much more sense. Media is cheap as chips these days so it's a very small investment for welcome new features. Spending days or weeks trying to get ML loading from both slots is a big waste of your time given that it doesn't improve on the MKIII's filmmaking ability one bit.

I'm up for being a bit-rate crash test dummy.

I agree.

Quote from: Lcrusher on September 04, 2012, 06:09:52 PM

I agree.

I agree as well !! Alex you're the man !!! If MJEP422 is doable, that would be huge and I think you should charge for ML on 5D3. I know I would pay for it.

The port is already becoming usable, and I went ahead and recorded the first timelapse with bulb ramping on 5D Mark III.



I'm thinking to start public testing pretty soon, maybe next week. First with a minimal version, then enable new features when the old ones are confirmed to be rock solid.

MJPEG requires more research, at this point I'm not even sure if it will work, so first I'd like to have a basic version working. I'll also publish some binaries for researching bitrate settings.

How about the clean HDMI?

Before researching new things I think it's better to have the basics fully working.

I'm just wondering if clean HDMI out on the Mark III is possible why it's not possible on the Mark II

Because the firmware is different ::)

Great News, a1ex!
I am up for testing!!

Quote from: a1ex on September 05, 2012, 09:20:25 AM
I'm thinking to start public testing pretty soon, maybe next week. First with a minimal version, then enable new features when the old ones are confirmed to be rock solid.

That is awesome news! :)

Great work a1ex. I have two 5Dmk3 would love to beta test.

There's not a lot on the 5Dmk3 that I'm not happy with, but one of the features I personally use all the time is the Multi-exposure mode. I use it like a Sony multi-exposure noise reduction. It would be nice to make it so it would just shoot 9 shots with a single shutter press rather than hitting it nine times.

I also find it interesting that you can stack 9 images into one RAW file, but you can't stack other stacked images into each other for more stacks. Ideally for astrophotography it would be better to have 30 stacks, and this would be really handy at the higher ISOs.

One of the features that I love on the Olympus OMD is Live Bulb. Again I use multi-exposure to simulate something very similar. Multi-exposure overlays the last frame captured in the live-view for a sorta psuedo live bulb exposure. I wonder if it is possible to make this not rely on multi-exposure and to have the exposure just slowly appear on the screen much like the Olympus does with Live Bulb.

Here, multiple exposures work with a single press if you hold the shutter button pressed (in continuous mode). So it shouldn't be hard to automate it to work on a short single press with self-timer.

I don't think I can change the number of shot in a stack, as they seem to be stored in memory and postprocessed when the sequence is finished.

Live bulb is technically possible only in movie mode, at 2 megapixels. But since the 5D3 does proper downsampling, there's probably no downside for this other than lower resolution.

Edit: it may be possible with intervalometer, but with large delays between the shots. Plus, it will increase shutter count a lot.

Quote from: a1ex on September 05, 2012, 05:40:03 PM
Here, multiple exposures work with a single press if you hold the shutter button pressed (in continuous mode). So it shouldn't be hard to automate it to work on a short single press with self-timer.

I don't think I can change the number of shot in a stack, as they seem to be stored in memory and postprocessed when the sequence is finished.

Live bulb is technically possible only in movie mode, at 2 megapixels. But since the 5D3 does proper downsampling, there's probably no downside for this other than lower resolution.

Yes, the continuos mode works if kept held down, as does the remote, but only if you keep your button pressed. Automated single press would be very welcome here.

I rarely do video work but I do quite a bit of long exposure. One of the other things that I wish and this is not exclusive to the 5Dmk3 is to be able to have either an on camera calculator or someway to calculate proper exposure with a 10 stop ND filter. It never meters correctly (usually maxes out at 13 seconds) so it's a guessing game. Now normally not a huge issue as I carry around an exposure chart, but I wonder if there's an easy way to maybe have something like DoF button combined with AE to give values for 10 stop (or whatever is set) exposure, and times that go beyond the 30 second. Be nice to meter, take the value down, then put the filter on, switch to bulb, program my remote for long exposure and expose correctly.

I'll share other thoughts if they come to mind, but that's all so far.

Quote from: a1ex on September 05, 2012, 05:40:03 PM
Edit: it may be possible with intervalometer, but with large delays between the shots. Plus, it will increase shutter count a lot.

Yes, this is how I've actually sort of dealt with it with a handheld remote. It's not perfect but it does work. I'm not too worried about the increased shutter count. It's worth it to me as it increases the usable dynamic range when I adjust images for shadow details. Shutters are consumables to me, just don't buy one of my used cameras off of me is all I suggest  ;)

Here's an example of how I use it:
http://www.flickr.com/photos/kinematic/7696561690/in/photostream

With current ML, you can already estimate the time for long exposures with display gain or FPS override or both. It's true, you have to do some math yourself. I try to find the limit where ExpSim stops working, then boost the exposure until getting a correct image, then increase shutter speed by the same amount.

Or, simply use HDR in automatic mode and let it run until it gets the right exposure.

This may also help: http://wiki.magiclantern.fm/faq#can_i_use_liveview_in_complete_darkness

Lastly.... I just donated $50 to the ML cause. Small contribution, but hopefully it helps some!

I just thought of another thing that drives me bonkers sometimes is the ability to see the AF points at times. I wonder if you can figure out how to make it so that it's always on the bright red for confirmation. There was word that Canon was working to fix this problem. I've since gotten used to it. I don't know if it is worthwhile to fix it or not, but just something to add to the 5Dmk3 list (also part of the 7D and 1Dx).

Thanks a lot!

Excellent news Alex!

I'm a very big fan of keeping ML on a single CF card and using my SD card collection for storage. I'm using a 5Dmk3 and a T3i and it's a pain when I once again forget that formatting the card on my mk3 also removes ML.

I know there are many people using multiple cameras and don't want to buy another set of cards for each camera while it's perfectly possible to share the cards between them.

SD cards are much cheaper than CF cards while the camera does not utilise the full advantage of CF cards anyway.

Keep it up!

Quote from: KAIT Labs on September 06, 2012, 03:06:44 AM
SD cards are much cheaper than CF cards while the camera does not utilise the full advantage of CF cards anyway.

That's untrue. The SD card implementation in the cam is way sllower than the CF slot. If you care about getting data out of the buffer and onto the card fast, the SD card slot will bite you hard.

Quote from: kinematicdigit on September 05, 2012, 06:27:50 PM
I just thought of another thing that drives me bonkers sometimes is the ability to see the AF points at times. I wonder if you can figure out how to make it so that it's always on the bright red for confirmation. There was word that Canon was working to fix this problem.

The problem according to Canon is that highlighted af points hinder metering (unlike the 1d4), it seems to be a design flaw with the many af points and Canon already stated that the upcoming solution "might not make everyone happy". On another forum it was already suggested that's because the solution might be "no solution at all" :-p

@alex: Now that you've handled both 5d2 & 5d3 extensively, maybe you could write something about your personal "is it worth it" opinion about the differences? I'm still unsure about which camera to get, and for the 5d3 I'd have to wait for a price drop anyway. But now that ml is really ported, I'm not so sure about the 5d2 anymore (worse af, more banding).

Hi guys
My 5d mark iii came yesterday, tomorrow i'll give it the first test shooting a wedding reportage... I really miss all the ML features..
I can't wait to see the first beta vers for this port.
I am up for testing too!!
Great Job, a1ex!

Hey a1ex, what does smooth ISO mean?

Something that will change the way you shoot videos. Or maybe not :)

Up for testing too!
If ML must stay on a single card I also prefer on the SD one to keep CF higher speed for data.
Tomorrow I'm going to US for a doc and I miss ML on my 5D3 :((

@Marsu42:

Actually, the only thing I've shot with the 5D Mark III was the timelapse above, so I can't really give a good advice yet.

For now, I can say that LiveView is actually a lot more usable in darkness on 5D3, compared to 5D2, probably a 2-3 stop improvement. Certainly a lot more than the 0.5 stops rumoured on some forums.

Also, if you shoot in burst mode, or if you care about battery life, go for 5D3. When shooting the timelapse linked above, I've measured 6 hours of battery life during 15-second exposures with intervalometer set to 20 seconds. That's impressive IMO.

Quote from: Lcrusher on September 06, 2012, 12:20:37 PM
Hey a1ex, what does smooth ISO mean?

Awesomeness, just tested it on my 1100D and it's beautiful. You can actually use it do an ISO-based iris pull. Until today you either had to use HDR video which sacrificed FPS or a manual de-clicked lens.

Quote from: nanomad on September 06, 2012, 03:05:53 PM
Awesomeness, just tested it on my 1100D and it's beautiful. You can actually use it do an ISO-based iris pull. Until today you either had to use HDR video which sacrificed FPS or a manual de-clicked lens.

Oh I see. That's what I thought. I wonder how it works.  So if I increase the ISO while shooting from 160 to 320 won't it give extra noise in the middle of the shot due to unnative ISO?

Noise on the Mark III?! Maybe if you shoot with a pinhole lens :)

That and you can still "ML" ISOs that can apply a negative EV to the native ISO thus masking noise a bit

Preview (1100D, no post-processing, ISO range from 75 to almost 1600) http://nanomad.magiclantern.fm/1100D/samples/ml_iris_pull_1100D.mp4

Quote from: a1ex on September 06, 2012, 01:31:48 PM
For now, I can say that LiveView is actually a lot more usable in darkness on 5D3, compared to 5D2, probably a 2-3 stop improvement. Certainly a lot more than the 0.5 stops rumoured on some forums.

Thx for the first impressions- it's valuable to me because I trust you to be more independent than the usual "I bought it for $3500, it must be stellar" vs "I cannot afford it, it has to be bad" forum talk.

Btw, the alleged 0.5 stops improvement concerns the iso noise in raw shots, and I must admit myself after comparing iso samples from 5d2 and 5d3 myself that up to iso3200, it doesn't make much of a difference. The one thing that is more of a problem on the 5d2 seems to be stronger banding, and this limits raising shadows much more than iso noise - the 5d3 has cleaner sensor readouts...

Good news: card autodetection is working pretty nice, so you can use any combination of cards. Recommended: install ML on a small SD card and shoot pictures/videos on CF cards.

Here's the proposed feature set for the first public version (alpha 0) - coming next week.

(http://a1ex.magiclantern.fm/bleeding-edge/5D3/5d3.png)

Sounds great, you are awesome! Looking forward to giving it a try. :)

That's awesome! I was really missing focus peaking and zebras. :P

There's been some talk elsewhere that even having an SD card in its slot also slows down the speed of the CF card, so would this affect any ability to record in higher bit rates?

http://www.canonrumors.com/forum/index.php?topic=7600.45

Seems to be a urban legend. I'll run some benchmarks.

Edit: ran benchmarks, it's urban legend. I'll include the benchmark code in the first alpha, so you can try for yourself.

Hello all !
if ML works on a mark3 is there a link with a possibilitie of installing it for the 650d or it's a totally another kind of development ?
Tell me if you know... and thanks for your work ! :)

Screen issues aside, the possibility is there but we can't do much without a firmware update or other means to fake it

Quote from: a1ex on September 07, 2012, 08:02:06 AM

Edit: ran benchmarks, it's urban legend. I'll include the benchmark code in the first alpha, so you can try for yourself.

Well that's nice to know - I'll put my SD card back in. Thanks!

For testers: here's what you will have to fill out: https://docs.google.com/spreadsheet/viewform?formkey=dFRxbGZlUHYyOHB6SDZWZFVpUlVRTUE6MA#gid=0

Please don't fill it right now, I've only posted it so you can review the questions and maybe come up with other suggestions.

the 1DX and the 1Dc run on twin Digic 5+ and only the 1Dc can do 4K MJPEG or 1080P60, I guess the real challenge is to get the firmware of the 1Dc and to see what is the difference ... they have reworked the 1Dc for massive heat dissipation, witch lead me to think that maybe they also run the processor at a higher clock speed.

I can have my hand on a 1Dc quite easily so if you explain me how to do a backup of the firmware I can try to send it to you... to see what are the difference that allow such cool things !!!

here they say that only one processor do the writing to both card :
http://thenewcamera.com/?p=8403

I dont know how accurate the schema is but, if it is correct, ONE digic 5 can handle TWO different card at full CF speed (2X150Mb/s) so technically the processor on the 5D MKIII writting data at 150 Mb/s on a UDMA 7 CF card is only doing 50% off it's ability. (after all a 5D MKIII can write on TWO separate card with ONE digic5+)

I am pretty confidant that the 5DMKIII can do 720P120, 1080P60 and 2K.P25. the matter is not what the camera can do but what the camera can write... Doing 422 MJPEG is way less intensive on processor power than H264 would be, but is doing heavier file.

Outputting 150 Mb/s for a long period will get the camera very hot quite fast.... but for small run it might not be an issue... and the one that need to record longer clip have the money to buy a 1Dc.

my main concern would be to get 1080P60 and 720P120 as it would just help me so much in action sport.
Event if 150 Mb/s is Si-Fi and 110-120 Mb/s is more like what real world fig gives you... that gives enough bandwidth to get good 1080P60

I definitively agree that ML should be on a small write-locked SD and the recorded video should go on CF.

just for fun and for those who like Time-lapse here is a Time-lapse of 140 000 tilt and shift stills that I have done for Disney with my colleague Daniel Meyer :
http://youtu.be/xFpSrXJWITY
I would love to get those time-lapse bulb-ramp fonction on the 5DMKIII.

Queep going : you guys rule !

I bet the issue with the 1Dc is the same as the 7D: there are two digic processors and we don't know how to handle them.
If you stumble across a firmware update for the 1Dc sendi it to a1ex anyway, you never know :P

Quote4K MJPEG

Would be really cool to back-port this even at 1080p or 720p.

Quotethey also run the processor at a higher clock speed.

And this too... I bet DigicIV has some overclock wiggle room.

The overclock idea is quite interesting, I'll dig out my DSLinux stuff and see if we ever investigated that area.

Overclocking? Ha ha, this is interesting :D

I've overclocked other arm stuff (openwrt, phones, soc) and haven't had too many problems with it. Just should make sure regular users don't go crazy and make the arm not boot. Also should try to raise clocks for the SD slot somehow. maybe can get more than 50mhz... shouldn't bother a UHS-1 card.  That extra 5MB/s from camera might be nice. Only problem I'd see is data corruption if it doesn't like it.

http://www.arm.com/products/processors/classic/arm9/arm946.php


Max Clock  441 (speed optimised)  /  230mhz (area optimised) wonder where we're at.

Quote from: EDGERIDER on September 07, 2012, 02:27:28 PM
just for fun and for those who like Time-lapse here is a Time-lapse of 140 000 tilt and shift stills that I have done for Disney with my colleague Daniel Meyer :

just one word: wow!

about overclocking: the last time i looked at the registers, they looked as if there was no chance to increase the cpu speed.
we might win more, if we were able to allocate enough ram for copying firmware there and the chance to remap flash memory address to this RAM.
a speedup up to factor 2 could be possible for code execution.

Shoot_malloc and patch out where canon messes with it.

yeah, but then still a way of remapping flash is missing :)

Alex do you think that is possible the implementation of the canon c log? Like the c100,c300 and 1dC

Quote from: 1% on September 07, 2012, 05:55:36 PM
And this too... I bet DigicIV has some overclock wiggle room.

This is proven by Canon: The 1dx uses the same af and cpu, but is faster than the 5d3 due to "higher voltage".

Quote from: EDGERIDER on September 07, 2012, 02:27:28 PM
my main concern would be to get 1080P60 and 720P120 as it would just help me so much in action sport.

... and hdr video! At least continuous 1080p/50 would be stellar, well for us PAL users that is :-)

Won't overclocking just shut down a camera due to heat more quickly?  :o

Quote from: EDGERIDER on September 07, 2012, 02:27:28 PM
the 1DX and the 1Dc run on twin Digic 5+ and only the 1Dc can do 4K MJPEG or 1080P60, I guess the real challenge is to get the firmware of the 1Dc and to see what is the difference ... they have reworked the 1Dc for massive heat dissipation, witch lead me to think that maybe they also run the processor at a higher clock speed.

I honesty think that the 1Dx and 1Dc are more alike then anybody thinks. I don't think the 1Dc processor is any more faster then the 1Dx. If you look at the spec of both cameras there exactly the same the only difference is the clean HDMI and the 4k mode. I think the main difference is the firmware. That why the 1Dx is out and has a firmware update and the 1Dc is not out yet. My guess is there still tweaking the firmware. You may be able to dump the 1Dc firmware with a modded 1Dx updater. You may also want to decrypt the 1Dx updater and see if you can find any trace of a mjpeg encoder. I've seen some raw 4k mjpeg .mov samples files and I can say its not true 4k is more like 2k footage. But again this was a pre-production 1Dc. Maybe if you can get a picture taking with a 1Dc a model id number can be parse from it.

I'd settle for 2k 4:2:2 MJPEG,I think it would be an improvement. Hopefully not limited to digic V only. 5dIII encoder already different.

One more thing about the 1Dc, the heat issue. The 1Dc is the first true video based dslr. All dslr have heating issues but there main use are for still pictures. The 1Dc is marketed as a video camera and there doing there best to eliminate this issue. The 1Dx should be able to do anything the 1Dc can do, the only thing would be it would have the same heating issues as all the others dslr.
Now back to the topic. 1%, I notice the different encoder I also notice there is no mjpeg decoder.

Alex, your truly a mad doctor. Dr. Frankenstein would be proud. Your creating a true beast.

I think mjpeg is new to 1dc so we need 1dc dump first. Hopefully its in software not in digic V itself... at the least we find out how they did it. Maybe canon is looking in on us, would be foolish of them not to....

more voltage = more heat...
the 1Dc and the 1DX are indeed different on a hardware basis. I've alredy played with pre-prod sample and i can tell you that there is some minor tweak on the 1DC (for example the flash synchronization PC port has been replaced by a stéréo headphone jack) also the same battery last at least 20% less time on the 1DC.
sorry for my low software knowledge...
next week I will have my hands on a 1DX and a 1DC for a couple of hour, how can i get the firmware out from them without briking the camera?
would that help you guys?

Eheh, good question. The answer is that you probably can't right now. Try getting in touch with a1ex. I don't even know if somone has ever tried porting ML to a 1D series camera.

Hi guys,
i've tried my 5d mark iii and i'm very impressed. Of course i'm missing the onscreen info and focus picking a lot but i'm loving the silent control for shutter iso and audio, so i can't wait to see the interaction between ML features and Canons.
When do you think it will be ready for few test?

This week, stay tuned.

would this be f*ing facebook, you would get a big like from me, haha.

https://www.facebook.com/magiclantern.firmware
::)

!

Donated !!!

this is gonna be Legen wait for it.... dary

we are indeed waiting :D

Me too~ Donated...

Hope I can use ML in Next week video shooting~

ML on 5D3? Finally, hallelujy, where's the donate button? Gonna donate immediately :)

Btw. what did you mean liveview is more usabel (2 stops more) then on 5D2 ?

Quote from: Marsu42 on September 06, 2012, 11:23:41 AM
The problem according to Canon is that highlighted af points hinder metering (unlike the 1d4), it seems to be a design flaw with the many af points and Canon already stated that the upcoming solution "might not make everyone happy". On another forum it was already suggested that's because the solution might be "no solution at all" :-p

I've never heard of this before? Do you have a reference to cite? I've never seen the meter change from the current conditions, even under the lowest light that I can still acquire AF with my fastest F/1.4 lenses.

Even if that was the case, the only point I would want illuminated is my active points and strictly for targeting. Once that has been acquired, it only takes a micro second for the illumination to shut off and the meter to accurate measure light. Regardless under my own tests under an EV of .01 with my handheld meter I saw no difference in the meter when it did light up.

You can now download Magic Lantern for 5D Mark III :)

http://www.magiclantern.fm/whats-new/78-articles/news/137-first-alpha-version-for-5d-mark-iii

Great, can t wait to test!!

YES! ML Mark III. Just got the message on DVXUser and headed on over. ML has been sorely missed after I sold my mark II

Woohoo! So exciting!!! Keep up the amazing work!

Now where'd that donate button go again...  ;)

 I can not download, and really want to ... I'm sad ...

You need to be a donor to access the download...and donations usually take up to 24h to process

How is the firmware guys? Anybody tested it? Got no paypal in my country  >:(

Quote from: kinematicdigit on September 12, 2012, 04:52:33 PM
I've never heard of this before? Do you have a reference to cite? I've never seen the meter change from the current conditions, even under the lowest light that I can still acquire AF with my fastest F/1.4 lenses.

... see http://www.canonrumors.com/forum/index.php?topic=6819.0

It would be really nice if the 5D mk3 would continue to record video past 29min59 sek. I recently used the 5D as a stationary camera to record a gig I was playing and had to have a friend stop and start the camera several times between songs to get the 1 1/2 hour concert. And he missed the last 20 minutes because he mistakenly only pressed stop, not followed by a start...

it's a default function in ml, so it can probably be expected to be there again.

I know its already a function in ML, but Canon 5D mk III already automatically starts a new clip with no gaps between the files when the file size exceeds 4 GB. As far as I understand ML produces a 2-3 second gap between the files.

What a great new to see developpement on 5D MIII  :), I can't shoot without ML anymore... Congratulation to all people working on it, I will donate again...
any possibility to have a usable timecode in 24fps (works only in 25fps) ? also, I don't understand on wich button I can modify value from ML
I'm going to shoot next week (documentary), no autoexec is almost unusable (too long to reload each time the camera is off, do you plan to make it soon ? I have an alphatron electronic viewfinder and the hdmi outpout from my "old" MII is so uggly :-\?
Sincerely
Yvan

The no-autoexec.bin thing is done on purpose for the test builds.

Thanks for your great jobs, I'll be testing this alpha after the 24h waiting ^^
Can't wait, I'll keep you posted about some issues

Is there anyway to donate other than Paypal? I really want to check this out (focus peek, and crops are needed) but cant use paypal

I encounter sometimes little bugs on the size of the frame when using external monitor (hdmi output)
Up and down of the frame, some ghost black lines go over the real size of the frame. Need to restart and not always clean... Also, difficulties when a card is full to be abble to insert a new one (need to remove battey).
Yvan

How to reproduce? (more details please)

I have a 4go CF with ML on it and by mistake, I forgot to insert the sd (for shooting). Then, after the full card warning, I try to insert the sd but can't remove the warning without pull out battery. (not sure it comes from ML or canon firmware, have to make test...
For the hdmi output, when I start the camera, the screen is not often clean, I found a solution by shortly shut off and on without loosing the ML loading.
Also, this morning, I had a freeze after the new 12mn splitting of the mark III, need to remove the battery to stop the camera...
Sincerely
Yvan

I still don't understand what the problems are or how to reproduce them.

http://freecode.com/articles/how-to-report-bugs-effectively

Just fill up your CF card until you get the no space warning and insert an SD card.

Does it happen with canon's firmware?

I'll check as soon as I find an SD card.

according to a very reliable contact @ canon, I was wrong : the only Hardware difference from a 1Dc and  a 1Dx is the sync pc port (for the flash).
there is no extra hardware for cooling or so...
It is a firmware limitation to go around the 30mn limit to a camera not to be taxed as a "video equipment" in europe (and surely also a way to make a good extra margin on top of an otherwise stock 1Dx) so it means a very good thing to us :
1 DIGIC V can handle 2K or 1080P50 if 2 DIGIC V can handle 4K. but even more = IT IS CAPABLE OF DOING CLEAN FULL HD THRU HDMI JUST LIKE A D800.... sometime I'm wondering what is wrong with those people who are limiting there own stuff on purpose.....

Any digic is capable of clean hdmi, the question is how to do it.

that is wher the 1Dc firmware should come handy  ;)

I see you guys are already discussing this argument :) http://www.eoshd.com/content/9044/exclusive-canon-confirm-1d-c-4k-dslr-is-same-hardware-as-the-1d-x

Yes 4k may not be possible on the 5D3 but maybe a firmware analysis of the 1DC will show how to make clean hdmi and maybe 1080p60/50 ?
Isn't the hdmi 4:2:2 on the 1Dc also ?

Quote from: AndreasK on September 21, 2012, 09:08:04 AM
Yes 4k may not be possible on the 5D3 but maybe a firmware analysis of the 1DC will show how to make clean hdmi and maybe 1080p60/50 ?

I'd be amazed if Canon didn't take some countermeasures to port 1dc features to the 1dx or even 5d3, they'll loose a lot of money if it would be done... though no harm trying I guess.

QuoteJust fill up your CF card until you get the no space warning and insert an SD card.

Did that a couple of times, with all ML options enabled, no problems.

a1ex .. have you begun exploring for increasing bit rates or clean hdmi out ?

Is stability less important than those?!

Quote from: a1ex on September 23, 2012, 08:45:40 AM
Is stability less important than those?!

At the moment, from what I've reading on "Canon Rumors" I'd definitely opt for stability before features before usability/beauty, many people still seem to be concerned that the ml "hack" voids their warranty (Canon dealer's fud) or bricks their investment. Usability should be the main focus when the new menu system/look is implemented (Magic Lantern 3.0?).

PS: Esp. the 5d3 and 7d are more professional cameras with a userbase that won't be very thrilled to play guinea pigs because they could loose money if it their camera breaks or doesn't do what they'd expect it to do.

That's what I'm thinking too. I have at least 5 lockup reports for 5D3, and I've experienced a few ones during development with the full feature set enabled, but nothing that I can reproduce.

To solve these things, I don't see other way than posting a few versions with even less features, and see which ones crash and which ones don't. This might provide a hint for what is causing trouble.

Quote from: a1ex on September 23, 2012, 12:54:03 PM
To solve these things, I don't see other way than posting a few versions with even less features, and see which ones crash and which ones don't. This might provide a hint for what is causing trouble.

I can't help because I don't have a 5d3, and even if I'd be hesitant to use a €3000 camera with alpha ml - with my 2y old 60D that has 100k shutters it's different now.

My opinion: Take your time, most people will understand debugging these things w/o a tethered software debugger or eos simulator is extremely time-consuming and annoying. There has never been an announcement for the ml 5d3 release date, and every time some posts "it's here soon" I reply "not necessarily".

Of course it should run stable at first!
We now have Peaking and Zebras with the Alpha, so there s no need for any external Monitor.
That s a big step for the mkiii!!!

I think there is a lot of room for playing with the bitrate and codec on the mkiii, so optimizing this would seperate it from all other dslrs. especially the gh3, imagine a canon dslr with almost the same sharp picture.
And a clean hdmi out for professional use.
I think these are the most important things to have a eye on after ml runs staple.

Like i postet, used the alpha for 3 hours on a job, it only hung up 1 time.

Quote...used the alpha for 3 hours on a job, it only hung up 1 time.

And I've used ML 2.3 on 5D2 for two weeks, around 3-5 hours daily, and had zero problems.

The infinite stress test seems to reveal something (sometimes it locks up after half an hour or so). However, without tester help, it will probably take weeks or months to diagnose this...

Thank Alex for the bug report manual, as I'm beginner on this forum, I'll try to be more precise on the problems I encountered when I'll finish my job. I'm shooting in that time a documentary on harvest and I can tell I can't work without an external hdmi monitor (alphatron evf 035 http://www.alphatron.tv/evf.html ) because the 5D is often at the level of my knees hanged on an home made "steady". The focus peaking of the alphatron is absolutely unusable compare to ML
Congratulation for your amazing work.
Yvan

I donated almost two weeks ago and I STILL cannot access the 5D3 ML link! What gives?

I was hoping to be able to have it up and running by this weekend.
:-[

Access granted.  Thank you!   :D :D :D

;)

Looks good, but in theory it's still ghosting when moving to fast, right ?

Of course. But afaik the 5D3 does proper downsampling at 720p, so with a little care, the results should be pretty good.

Its amazing whats been done so far with ml and the 5diii! excellent work everyone! I believe the potential for the 5d3 is great. my biggest strife with its video is h.264. I was messing with the s2 jpegs, shooting at 6fps the opening the files up as a jpeg sequence in a 24p timeline. if you shoot s2 jpegs in video mode the files are cropped at 1920x1080 and are only  .5 to 1 MB in size and were way sharper. could it be possible to somehow  shoot s2 jpeg sequences at 24p say for maybe shorter period of time? if so the sharpness and quality would be insane. i was using marvels cine and htp (which normaly makes uglys) and the quality was awsome. i dought this is possible but the jpeg downsampling was real sharp and so easy to grade. it would probably call for a data rate around 200mbs. so what if playback isnt there it would be worth the quality. thanks again for all your hard work!

Im sure this has been discussed and im sory if it sounds like a broken record but im just curious. in any case i cant wait for the ful ml on the 5d3!!! such exciting times! Thank you so much! The HDR LOOKS SO RAD! so awsome!

The HDR is VERY impressive!!

Does this mean HDR will be included in the next alpha build?  :D

Yep.

awesome .. any idea when alpha II will be available ?

No.

Quote from: hjfilmspeed on September 28, 2012, 04:00:19 PM
Its amazing whats been done so far with ml and the 5diii! excellent work everyone! I believe the potential for the 5d3 is great. my biggest strife with its video is h.264. I was messing with the s2 jpegs, shooting at 6fps the opening the files up as a jpeg sequence in a 24p timeline. if you shoot s2 jpegs in video mode the files are cropped at 1920x1080 and are only  .5 to 1 MB in size and were way sharper. could it be possible to somehow  shoot s2 jpeg sequences at 24p say for maybe shorter period of time? if so the sharpness and quality would be insane. i was using marvels cine and htp (which normaly makes uglys) and the quality was awsome. i dought this is possible but the jpeg downsampling was real sharp and so easy to grade. it would probably call for a data rate around 200mbs. so what if playback isnt there it would be worth the quality. thanks again for all your hard work!

Yeah, the more I read about Canon limiting the potential of their products in order to make more money, the more disappointed I get. I really hope that the amazing ML team is able to somehow increase sharpness/resolution of the 5D3, as unlikely as it seems.

Quote from: a1ex on September 28, 2012, 11:52:03 AM
5D3 does proper downsampling at 720p

Is it after ML implementation ?
In my case, 720p producing about 500 lines
I am running Firmware wer. 1.1.2
Is there a hope for true 720p ?

I couldn't see any noticeable moire on my test chart ( http://graphics.cs.williams.edu/data/images/star-chart.png ), maybe just a tiny bit more than at 24p. On 5D2, in FullHD, moire is clearly visible. So I guess it's proper downsampling.

Yes. 5dm3 is ok for moire, aliasing. But resolution is not real. 5dm3 is producing less lines then 550d. It is clearly visible in 720p mode.  http://www.graphics.cornell.edu/~westin/misc/res-chart.html
Increasing resolution in 720p would be a hudge step.
Check any thrailer in 720p: http://trailers.apple.com/trailers/
There is true resolution and 24fps. (Canon framerate in 720p is: 50 and 60 !)

True video resolution is what we all need in 5dm3

Then, sell the 5D3 and buy a 550D.

Quote from: a1ex on October 08, 2012, 03:03:23 PM
Then, sell the 5D3 and buy a 550D.

;D

Quote from: a1ex on October 08, 2012, 03:03:23 PM
Then, sell the 5D3 and buy a 550D.

Giving up alredy ? Do i write about 4k like the others?
You did so much amazing things with ML

Giving up on what? ML never changed sensor scanning modes and similar low-level stuff.

Quote from: a1ex on October 08, 2012, 03:54:16 PM
Giving up on what?

Trying to increase resolution. I was wondering if thats possible witch ML

It never was

ugg it just bothers me to see the camera can produce tack sharp 1080 jpegs (processed in camera). i guess it cant do it at 24p for any length of time. I was hoping this could be possible with silent stills but judging by these last few posts i guess not.

to be fair the 5d3 wasnt designed to be a full frame cine camera. it was designed for photos. you want cine from canon you better be ready to pay for it. It would be awsome if canon could make a 16mm version of the c300. then guys like me might be able to afford it (after i sell sum camera stuff ha ha) But ML is for making the most out of these dslrs for cine work thats for sure. love it so much! Thanks again!

Here is an intresting post from a differend forum about 5dm3 olpf:

Quotehow can this OLPF filter be strong enough that the video looks so soft out of the camera, yet weak enough that it doesn't affect stills? with such a strong filter, RAW stills should be a mush of non-detailed identical pixels, but they're not - which leads me to think... (you know I'm always on the optimistic side) that filter actually changes from stills to video mode, it is electronically controlled somehow... and Magic Lantern will give as a way to control it without tearing the camera or getting rid of the dust-removal mechanism

http://philipbloom.net/2012/04/01/a-drastic-solution-to-increasing-sharpness-with-the-5dmkiii/

hmmmm i dont think its that. Even with the filter 100% removed the 1080 vid is only a slight bit better but not nearly as sharp as the s2 jpeg. its deffinetly canons method of downsampling in vid mode for sure. You never know ML always surprises but this one sounds tricky.

Test is based on Neutral preset zero sharpness, | -2 contrast, | -2 Sats
Second similar filter was untouched

from the tests ive seen removing the olpf is not
the answer. if theres proof otherwise i think
the olpf thing was busted.

I dont know what kind of tests you have seen.

These tests. If they are true anyways.

http://www.eoshd.com/content/8201/canon-5d-mark-iii-without-optical-low-pass-filter-the-verdict

The results are very minor. There is a way bigger jump comparing the s2 jpeg shot in video mode to the all-i.

I realy think its like a1ex said. The 5d3 rez issue boils down to the downsampling/sensor scanning method and maybe codec. As alex has posted ML cant change the type of codec. He himself was very optimistic in saying that there might be a very very slim chance of mjpeg or realy short 422 clips but again that in itself would be a crazy tuff code to crack.

The company who did this modification replaced olpf with anoder piece of glass... Also there is a calibration issue.
I think Andrew's test is realible, but this was done diffriend way.

Well it would be awsome if this could be remedied by ML but dont get your hopes up to high and overlook the other sweet features of ML.

Yes. I am very greatful what Alex has been done witch Magic Lantern in 1 year. Will donate for sure.
The true about 5dm3 it that all it users suffer from low resolution. In my opinion this is Ahilles heel in video therms.
Each way is god to fix this.
Iam not an expert. All my knowledge i have, come from my experience and internet (information what i chose to believe).

Some time ago i did resolution test's using 5dm3 in 720p comparing prime to zoom lenses.
Main comparison was done between Canon 24-105 f4.0 at 85mm f4.0 and Falcon 85mm at f1.4
Conclusion is that prime lenses producing more lines (20-100 vertical pixels !) (5dm3 720p)
This also was visible during my work on source material i did.

I was asking myself why? From scientific tests done by "optyczne" Canon should produce more lines at 85mm f4 comparing to falcon 85mm f1.4. And this is true in photo mode. In video is not. It is opposite.

We know that prime lenses wide open produce strong chromatic aberration http://en.wikipedia.org/wiki/Chromatic_aberration
This is something to do witch light diffraction. Maybe chromatic aberration is a quality factor in this case? So maybe OLPF filter ?



It was not scientific test, but proper enough to see the difrience.

I will do more tests witch only Falcon 85mm comparing f1.4 to 11 and publish them in about 20-30 days when i find the time for this.

Chromatic aberration come out on strong contrast.

"Canon should produce more lines at 85mm f4 comparing to falcon 85mm f1.4. And this is true in photo mode. In video is not. It is opposite."

Canon L lenses are suposed to super sharp but you are comparing a zoom lense with a prime. Prime has less glass then a zoom so it should be sharper depending on the prime lense of course. Im not sure why its the oposit in video mode. Also are all your in camera lense profiles turned off?

I agree the resolution issue kills me especialy after you look at true 1080 or 720. I just did a test between the s2 jpeg and all-i 1920x1080 (i will post soon) and its realy strange what happeneds to the image comparing the video to the still (looks more like sampling methods to me). the difference was huge and I realy dought the olpf could fix this. Go for it and test the lenses but i think its the cameras default video smapling method.

even though removing the olpf did help a tiny bit
it still most likely wouldnt resolve 1000 lines like it
it should. again i think its deeper then that
unfortunetly. i also fear that the 5d3 might not
have the power to resolve to much more @ 24p

Canon: http://www.optyczne.pl/84.4-Test_obiektywu-Canon_EF_24-105_mm_f_4L_IS_USM_Rozdzielczość_obrazu.html
Falcon: http://www.optyczne.pl/178.4-Test_obiektywu-Falcon_85_mm_f_1.4_Aspherical_IF_Rozdzielczość_obrazu.html
Wide open, Canon is sharper. Settings were the same. Lens profiles off.
I did fast test on falcon 85mm comparing f 1.4 to 11. No difference in resolution. So is no chromatic aberration.

I found this interesting: http://www.eoshd.com/comments/topic/495-canon-5d-mark-iii-polarizer-improves-sharpness/

Quote from: Andrzej on October 10, 2012, 12:18:06 PM
Yes. I am very greatful what Alex has been done witch Magic Lantern in 1 year. Will donate for sure.
The true about 5dm3 it that all it users suffer from low resolution. In my opinion this is Ahilles heel in video therms.
Each way is god to fix this.
Iam not an expert. All my knowledge i have, come from my experience and internet (information what i chose to believe).

Some time ago i did resolution test's using 5dm3 in 720p comparing prime to zoom lenses.
Main comparison was done between Canon 24-105 f4.0 at 85mm f4.0 and Falcon 85mm at f1.4
Conclusion is that prime lenses producing more lines (20-100 vertical pixels !) (5dm3 720p)
This also was visible during my work on source material i did.

I was asking myself why? From scientific tests done by "optyczne" Canon should produce more lines at 85mm f4 comparing to falcon 85mm f1.4. And this is true in photo mode. In video is not. It is opposite.

We know that prime lenses wide open produce strong chromatic aberration http://en.wikipedia.org/wiki/Chromatic_aberration
This is something to do witch light diffraction. Maybe chromatic aberration is a quality factor in this case? So maybe OLPF filter ?



It was not scientific test, but proper enough to see the difrience.

I will do more tests witch only Falcon 85mm comparing f1.4 to 11 and publish them in about 20-30 days when i find the time for this.

Chromatic aberration come out on strong contrast.

"Yes. I am very greatful what Alex has been done witch Magic Lantern in 1 year."   

This guy is one of our heroes. He is very knowledgeable and always ready to help others.

Quote from: jplxpto on October 10, 2012, 11:12:25 PM

"Yes. I am very greatful what Alex has been done witch Magic Lantern in 1 year."   

This guy is one of our heroes. He is very knowledgeable and always ready to help others.

Pretty valuable post...
Glad to be your hero  8)

yes, Alex is doing an amazing work on Magic Lantern.
This project won't such a success without him!

Of course all other contributions are important too!

Indy

Quote from: Indy on October 11, 2012, 01:13:18 PM
yes, Alex is doing an amazing work on Magic Lantern.
This project won't such a success without him!

Of course all other contributions are important too!

Indy

Yes, this guy is fantastic ... next year he will win the Nobel Prize of hacking.

hehehe

Does any one know if the alpha release allows continuous video for 12 hours outputed on the hdmi or do i need a mk 2 and v2.3 as i know this will do it.

Will be being used to capture video onto pc.

Thanks

I really hope mjpeg will be possible. I am sure a lexar 1000x CF card is fast enough. I guess we still do not know if 5d mark III is able to do it or not until alex tries. 

I am thinking if someone not concern about shallow dept of field or low light performance a good camcorder might have to do for now for higher resolved lines of resolution.  I might look at Panasonic TM900 for 1080p @ 60p for now.  One review http://www.camcorderinfo.com/content/Panasonic-HDC-TM900-Camcorder-Review/Sharpness-Performance.htm and other http://translate.google.com/translate?sl=auto&tl=en&js=n&prev=_t&hl=en&ie=UTF-8&layout=2&eotf=1&u=http%3A%2F%2Fwww.ixbt.com%2Fdivideo%2Fmark-ii-vs-tm900.shtml. 

just a little question as I'm completely addicted to ML now(I can't imagine to work again without it).
Will the next release have the possibility to have the histogram under the frame as for the mark II to have a full clean frame ?

I also have a little dream : with ML informations, have some transparency above and under the frame (you can see the 4/3 full picture, as in mark II in normal view but it disapeared in mark III) to see the boom operator before being in the frame.

So what does everyone think? Can the 5d3 handle higher resolving video in 1920xwhat ever? Just wondering what everyone thinks. ;D

Quote from: hjfilmspeed on October 16, 2012, 01:17:09 AM
So what does everyone think? Can the 5d3 handle higher resolving video in 1920xwhat ever? Just wondering what everyone thinks. ;D

If Alex can get it recording uncompressed 1080p to CF cards then it should resolve more detail. It's the compression and the noise reduction that stunts the MKIII.

i think ur right. the rez is there. you can see it when
u digitaly zoom in to focus. its also in even
the lower quality jpegs. then on the same image
in video mode the rez is gone. =(

Quote from: hjfilmspeed on October 16, 2012, 03:52:15 PM
i think ur right. the rez is there. you can see it when
u digitaly zoom in to focus. its also in even
the lower quality jpegs. then on the same image
in video mode the rez is gone. =(

???

Quote from: ilguercio on October 16, 2012, 03:57:22 PM
???

Sorry maybe im wrong but if your in movie mode and your not recording and you zoom in using canons focus assist, there seems to be decent detail. Remember that spot you focused on. Take an s2 jpeg(it will crop out at 1920x1080 if you shoot it in video mode) and take a 1080p all-i video (with zero in camera sharpening) . Bring both up in you editor. then zoom in on that same spot on both the s2 jpeg(1920x1080) and your 1080 video. Youll see a hudge difference and youll see what 1080 is suposed to look like.

You also notice that the detail you saw in the canon "focus assist" is in fact present in the s2 jpeg and not in the video.

I think what squig said is what the solution could be but man would that be a task. Dont know how these ML guys do it. I wouldnt even know where to start.

Im sorry i deffinetly dont mean to beat a dead horse just wish it was possible to see why this is.

What are the odds of seeing more still shooting features in the next ML alpha?  I don't shoot much video, but would love to start testing out the still features.

The feature set is already announced.

Quote from: a1ex on October 17, 2012, 11:02:12 PM
The feature set is already announced.

Sorry, Kinda new here. I've looked all over the forum and on the mkiii alpha download page, and I can only find the feature set for the alpha1.  Am I missing something (obviously I probably am), please drop some knowledge on me.

It was buried in the forum.

Quote
Proposed feature set for Alpha 2:

- Magic Zoom
- Focus peaking with grayscale image
- HDR video
- Gradual ISO transitions (this is new feature, and 5D3 is the only camera where it works flawless... yet)
- Display adjustments (brightness/contrast/saturation)
- Clean HDMI out with pillarboxes
- UniWB display correction (bleeding edge)
- Zoom on old button or M-Fn (not quite reliable though, I may disable this)
- Display presets

None of these things require changing any permanent camera settings, so they should be pretty safe. Backend things being tested: DIGIC controls and state object hijacking.

Besides that, it will contain quite a few fixes for bugs found by the 7D guys (which were also present on 5D3).

Thanks for the quick reply a1ex (nice handle by the way).  So, any hints on when we can expect more of the stills features, since most of the new features slated for the alpha2 are video-centric?  I don't mean to pester, just really anxious/curious. 

I remember when a1ex first join the google mailing list. There was already an Alex in the mailing list, so he added the 1 so he wouldn't be confuse with the other Alex.

Clean hdmi? wait .... realy? Like external recorder clean or external monitor clean?

Alex said 5D MIII Alpha 2 should be out this week!  I am patiently awaiting.....

Why is 5D MIII Alpha 1 not listed in downloads in Bitbucket?  Just curios to know how many downloads so far..

3300 downloads so far.

Maybe it's a good idea to continue the discussion in the development thread. (http://www.magiclantern.fm/forum/index.php?topic=2602.0)