Author Topic: Magic Lantern for 5D Mark III - Alpha 3 (1.1.3) (Read 813682 times)

CaptainHook · « **Reply #75 on:** September 15, 2012, 10:45:47 AM »

I got slightly slower with one of my lexar 32gig 1000x's.. is the top right telling me there was only 14gig left on the card ? (haven't used ML much). It was at least half full so could that be a factor then?

This was using the 1.8gig firmware tester from page 2.

Put me down for testing uncompressed!!

Cineman · « **Reply #76 on:** September 15, 2012, 10:48:38 AM »

This is such great news! Any increase in bit rate / image quality would be my main request for your next addition. Also, the ability to de-compress 1.5x anamorphic images on the L.C.D. so that the correct aspect ratio is displayed while recording would be fantastic! When one or both of these features are added I'll definitely be donating more. I'm shooting a feature in mid October. Any hope I can get a sharper image out of this camera by then? Thanks for the amazing work!

CaptainHook · « **Reply #77 on:** September 15, 2012, 11:39:50 AM »

Hey Alex, a quick couple of things i noticed when playing back and having crop marks (2.35:1) showing;

When using built-in LCD if i press "info" to remove the 'clip location indicator' (whatever its called) top left of screen, the crop marks around that area will flicker on and off exposing the shot behind the cropmark.. not a huge deal but distracting none the less.

When outputting via hdmi to an external display, because it's playing back at 1080 (on my 24" monitor live view doesn't use the full screen so maybe just 720, and playing back clips goes full screen) the crop marks aren't scaled properly and don't cover the proper width etc.

Thanks!

joxxie · « **Reply #78 on:** September 15, 2012, 10:49:51 PM »

any idea when you might add the intervalometer ? I wanna start shooting timelapse and it would nice not to have to
buy one

wintix · « **Reply #79 on:** September 15, 2012, 11:10:34 PM »

same here, looking forward to a alpha 2 build with a bit more functions to toy around with.

btw, is it my imagination or is modifying the shutter speed causing redrawing issues with the aperture number? it's kind of setting me off each time i fiddle with the settings as i first think that i accidentally changed aperture and not the shutter.

vitafab · « **Reply #80 on:** September 16, 2012, 05:02:54 PM »

Hi guys,
I've test alpha 1 all day long during a wedding reportage and i had no problem with it at all.
It's great to have stuff back as i was used to. I didn't miss much the autoboot since most of the time i left the camera in photo mode with the autopower off. I've update the firmware with no problem except once when battery level was under 17% .
In very low light situation i've use 12800 iso with hard edge focus peacking and it does the job better then the other methods.
Thanks again alex
I'll keep donating

optik · « **Reply #81 on:** September 17, 2012, 07:26:23 AM »

Can't say how grateful I am you guys thanks. Everything seems to be working just fine no problems whatsoever (minor GUI glitch at the bottom when I change shutter or aperture) shot for about six hours today.
I primarily do a lot of green screen work I read somewhere that there was an option for achieving better green screen results in magic lantern what is that setting?

Francis · « **Reply #82 on:** September 17, 2012, 07:29:32 AM »

You can use the waveform display to see if your greenscreen is evenly lit. Aim for a horizontally uniform graph.

JohnN · « **Reply #83 on:** September 17, 2012, 04:37:52 PM »

Quote from: a1ex on September 14, 2012, 07:57:03 AM

Focus peaking is based on D2xy, so:
- biased for edges: that's exactly d2xy, and the algorithm is described here: http://www.luminous-landscape.com/forum/index.php?topic=56246.0
- biased for fine details: it's second derivative (d2xy) minus first derivative (what was d1xy). Rationale: strong edges (with high contrast) are very likely to be false positives, so this setting will try to filter them out and only look for textures.

So far so good - no issues at all for me

One question about focus peaking - I see there are two methods now as I don't recall edge from when I had it on the 60D, but in the article you pointed to there was this image (below) - do you think this sort of display is possible as it would be a lot easier to see at a distance or in sunny conditions.

a1ex · « **Reply #84 on:** September 17, 2012, 04:46:56 PM »

I'm afraid this display would require a lot of CPU power.

I have some experimental display modes with alpha blending, but frame rate is quite a bit lower (15-20fps). Probably not an issue for photo mode with slow action, but with fast action it really feels very slow.

JohnN · « **Reply #85 on:** September 17, 2012, 05:49:08 PM »

Cheers - would be interesting to see, although obviously as a lower priority.

vitafab · « **Reply #86 on:** September 17, 2012, 06:36:32 PM »

Hi guys,
there any chance to have the hdmi and lcd working at the same time?

itsskin · « **Reply #87 on:** September 18, 2012, 12:20:21 PM »

Hi guys!
Great work!
Just tested Lexar 32Gb x1000 and got 85MB/s write speed. Read test was skipped.

dude · « **Reply #88 on:** September 18, 2012, 03:27:42 PM »

Maybe that s good news..
http://www.techpowerup.com/172369/The-CompactFlash-Association-Announces-CFAST-2.0-Draft-Specification.html

5DanielMIII · « **Reply #89 on:** September 18, 2012, 04:32:40 PM »

Hm, never done this before, so please, a step by step what to do!? =) hehe
Just unzip the folder and smack it on the SD card?
Or should the card be prepared in a way? Do I get to choose the ML on start up, or..

Aaah, so many questions, so many many possibilities!
Life is overwhelming now that ML on 5D mark III surfaced.

Or, might just be me, the technoobfool;-)

Regards

shiny · « **Reply #90 on:** September 18, 2012, 06:50:17 PM »

hi,
i don't have the mark3 but i will use it for a video shooting.
can you give me the right info to use the alfa version with camera?
i want to use the method the alex suggest.install ml on the small SD and using cf card for recording video.
so....is this what i have to do?:
1:copy ml in sd card
2:insert sd card in camera and press firmware update.
3.in now installed?
4.insert cf card and start to recording
5.i have missing something?

what is the button to have access to ml menù?is the same of the mark2?
thanks

Jason Montalvo · « **Reply #91 on:** September 18, 2012, 07:16:49 PM »

You have got the procedure right my friend. I would insert both cards at the same time and then do the firmware update, because if you waited to insert the cf card the camera would turn off and you'd have to run the firmware update again. No autoexec.bin on the Alpha firmware.

Hope this helps !!

agregory · « **Reply #92 on:** September 18, 2012, 07:21:14 PM »

I keep trying to load the firmware with my SD card and my camera doesn't see the file. Do I use the USB? I'm on the updated canon firmware 1.1.3.

a1ex · « **Reply #93 on:** September 18, 2012, 07:22:48 PM »

Format the card from the camera, and make sure the FIR is on the root of the card.

wintix · « **Reply #94 on:** September 18, 2012, 08:07:28 PM »

are you planning to release a second alpha to toy around with over the next weekend, alex? if so, what features do you consider to put in there?

a1ex · « **Reply #95 on:** September 18, 2012, 09:22:01 PM »

Well... with the 7D thing I didn't really work on the mark 3 lately.

I've tried it on a small event this weekend (1300 pics), had to pull the battery once and got 3 black pictures (but I had a larger feature set enabled). In the google docs, two users also reported lockups (happened once, they could not reproduce). Not that good.

On the other hand, I've seen some reports of 5D3/650D problems without ML ( http://www.canonrumors.com/forum/index.php?topic=8732.0 , http://www.learningdslrvideo.com/canon-t4i-650d-vs-60d-review/ ), so it's going to be hard to diagnose.

For next alpha, I'm thinking to add things that do not require changing any persistent settings. HDR video is one of them, also most DIGIC display tweaks. Also the zoom position on M-Fn.

wintix · « **Reply #96 on:** September 18, 2012, 09:52:52 PM »

yeah, saw the changelog was pretty empty and hence hoped for a second alpha soon as things seemed stable from the outside.

i just read the forum thread you linked and it seems that only people that are using the sd card slot with high speed cards are speaking up so far. my glass ball guesses that since the 650d and the 5d3 used with a sd card are affected that it has something to do with the sd card implementation in recent cameras. maybe you can do a release with a ~15G file benchmark (or something so configure the size) to allow specific testing of the sd card slot in the 5d3. maybe it's possible to crash the camera reliably with putting some heavy usage on the sd card slot for a longer period of time.

so far i threw at the 5d3 what i could think of, went through several hundred pictures with ml enabled and didn't experience any issues so far, despite the minor redraw issue in video mode i mentioned earlier.

nice work on the 7d as well, btw! also looking forward to anything testable there. kind of cute to have two cameras with a port in progress.

itsskin · « **Reply #97 on:** September 18, 2012, 10:11:41 PM »

Alex, how hard is intervalometer to implement in next Alpha?

a1ex · « **Reply #98 on:** September 18, 2012, 10:19:19 PM »

It depends on prop_request_change calls... the thing that I want to avoid for now.

wintix · « **Reply #99 on:** September 18, 2012, 11:01:56 PM »

how is that particular call dangerous? if i understand it correctly, it changes camera settings and can potentially lead to a non-booting camera if invalid values are written for whatever reason? - i do see why one wouldn't want to release something like that straight away but it probably doesn't get more safe than it already is with your testing so far?

News:

Author Topic: Magic Lantern for 5D Mark III - Alpha 3 (1.1.3) (Read 813682 times)