Messages

I was used to download the latest builds from MK11174 here : https://bitbucket.org/mk11174/magic-lantern/downloads/
But now it says it's a dead link ! Do we must now follow the normal nightly builds link for 550D ?
Many thanks in advance for the clarifications !  ;-)

Hi, all, I've started maintaining ML for the 50D, where one goal is to bring it up to parity with TL for the 50D.  So, it'd be really useful for me for those of you using TL, especially for RAW video, to try out the latest build of ML – the nightly builds are back! – and let me know what doesn't work as well, or at all, in ML.  You can provide feedback in the thread I've created.  Thanks!

Thank you very much Ayshih ! Just for me to understand better: do your maintained nightly builds contains all the Andy builds latest features here ? And will also contains more, when new TL features will come up and Andy will not keep updated with his builds ? Many thanks in advance for your clarifications ! 

Raw-rec.  Not mlv.  3x crop, yes. Dunno about half shutter.

WAO !

Now, in the last Andy release, 23,9fps and even 24fps works with 1920x1080 (full HD) continuous !
Double buffering and ML grayscale preview, 1Gb card warming-up option.
1000x 64Gb KomputerBay card (fully tested for uniform high speed >= 1000x and no defects, all this on all the addressable space).

What an achievement !

Many thanks and congratulations to all the people that worked on this !   

-- deleted ---

Hy Andy! I saw your last 50D build uploaded on your repository! What's new? Or I missed your whatsnew post? Many thanks!

a relatively simple POST production 'fix' for the dead pixel issue, if you have Adobe After Effects, would be to use the clone tool to have the dead pixel area replicate the area on one side of it. This isn't a true fix but may help mask the problem somewhat.
Though this would become very labour intensive if the dot is moving, it wouldn't prove difficult if the dot is stationary in the frame.

Do it propagate to all the subsequent frames automagically ? Or do you need to do this frame-by-frame for every frame ?

[Why not design a camera?]

Why not design a camera?

Yet discussed, and decided it's a too costly operation with no advantages.
Sorry but they are so great geniuses (like you said) that they yet thinked, discussed and rejected the idea ! Sorry !     

Some 18-55mm kit lens action  lot's of moiré but that's expected.
CinemaDNG grading done in Resolve with Dennis Schmitz' excellent Teal/Orange LUT: http://bmcuser.com/showthread.php?4929-NEW-Lut-TealOrange

At 0:15 the car is hiccupping ! What's the problem ? It's not my player...

I tried last Andy600 build (the "2 mb/s more speed, september 2013), 64Gb 1000x KomputerBay card, 64K clustered and aligned, with max around 5500 frames = 3.5 minutes ! Many thanks to Andy600 !
Big achievement! We are so close to continuous! ml say "continuous ok" but it maxes to 5500 frames... so close !!!! 

I then tried to slow down to 23.7 fps, and it's really continuous: only 2 bars (one green and one blu, travelling here and there) are displayed for some time... so I thinked "here we are!..." but... then something suddenly breaks and 5 green bars and 5 blue bars are constantly displayed for some time, then something breaks again... and so on, to the point where all the memory buffer is filled up. No more than 5500 frames also in this case...

If we manage to understand what is "breaking" the writing process at constant intervals, we perhaps can try to solve it ! 

https://bitbucket.org/andy600/tl50d/downloads/Tragic_Lantern_50D109-Andy600.2013Sep28.go_faster.zip

Great! Many thanks again! I reached your same results, with max around 5500 frames = 3.5 minutes ! Many thanks to Andy600 !
Big achievement! We are so close to continuous! ml say "continuous ok" but it maxes to 5500 frames... so close !!!! 

EDIT: I tried to slow down to 23.7 fps, and it's really continuous: only 2 bars (one green and one blu) are displayed for some time, then something breaks and 5 green bars and 5 blue bars are constantly displayed for some time, then something breaks again... and so on, to the point where all the memory buffer is filled up. If we manage to understand what is "breaking" the writing process at constant intervals, we perhaps can try to solve it ! 

I'm using the "2mb more" build on page 144(?) of the official 40D/50D thread.

Great! Many thanks for this info! Can you give me the link? I cannot find this build. Many thanks again!!!!

What's the status on this? Would the potentially released RAM could be used to shoot longer RAW recordings?

Before memory backend, I managed to record 1600 frames of raw video at 1920x1080 23,9fps on 50D, now I manage to record 2500 frames at the same settings ! 64Gb KomputerBay card. 81Mb/s - 82Mb/s boundary writing speeds, 81.5Mb/s mean value.But I don't want this to be a placebo effect...  ;-)

I got the Lexar 1000x 32gb for $114 on eBay.

While I wouldn't bother justifying the extra cost in order to get another ~2MB/s over the KomputerBay, I would like to say it CONSISTENTLY runs 81MB/s, which is definitely worth the difference. The extra speed is gravy to me.

With the GlobalDraw off, I'll run crop 1920x1080 until the card runs out. No drops or pink frames.

With 50d? With same camera and card, ml says 81mb/s is not enough for fullhd continuous, and infact i am able to record only 1900 frames. I disabled gd and all other ml and canon stuff and jpeg low resolution mode on canon setting and all ml hackering on, "small hacks" OFF, otherwise only few frames are recorded. I can reach 82 Mb/s with 2500 frames, and special CF preparation, but not at all CONTINUOUS. What are your magic settings? And what build you use? (I'm using the last nightly build at time of this writing). Many thanks!

Please, keep raw 1.0 (not .mlv) compatibility also! It permits more frames to be recorded! Raw 1.0 will never die and it is essential. The .mlv infos are not so essential to all shooters, and not so useful to everyone. Many thanks!

A short 'short' with the intent exploring Magic Lantern's RAW dynamic range on the 550d. ISO at 800.

Great ! What resolution ? Thanks ! 

Try latest andy build and let me know if hdr works here

Do you use nightly or andy's build or what ekse?

Same problem here...

Well got the point, what iso limits have you set?

If video isn't flickering, then all is ok, no?!? Why you want flickering video!?!

Too lazy to look through all 41 pages. Anyone who can be a nice boy/girl and link download for a full working RAW video ML for 550D? Also a quick little guide. Or is it just to install like the regular ML? Thanks guys

... Even too lazy to read the first post ? 

When I change the preview mode in RAW video on 50D, Tragic.Lantern-2.0-Andy600.Build.2013Aug19.50D109, whatever I choose the result is Always "ML Grayscale" when viewed on the LV as soon as the "SET" recording button is activated. Do this is normal ? 

Yup I red about this before somewhere in this forum but just to clarify, we cannot access the "black-box" via ML because its impossible to do so or it can be accessed but needs more analysis? If its accessible, I'm sure that our talented developers will find ways to do it in time..

Dunno, TBH. However, I can think than this procedure is done by an external chip, because the task is very cpu-intensive, and from the data about the power of the main processor of the cameras and from the results we can achieve re-programming it, we are sure it cannot cope with this task, so there must be an external chip, very likely if not for sure. So, we can re-program only the main CPU where the main core routines reside: a long long slower CPU than this dedicated H264 chip. The result ? We can only tell this external chip some few parameters, but limited, like a limited quality control over compression. We can also intercept the raw data coming into this chip and write it to the memory card (raw video, the great last achievement of Magic Lantern), but surely the on-camera processing of this raw data flux is too slow for the main CPU that we can control, so only 1 FPS (for example) can be achieved. More: there is no so much memory left for our CPU programmings, so it is sure that a complex video compression algorithm cannot be implemented. For sure.

I'm trying to better understand how the cameras works. The H264 encoding is done by a dedicated DSP, and the JPEG compression ?

Dunno, TBH. But even if we can rewrite it or modify it, it will be a procedure equally or longer than the original one, so no hope to squeeze out more FPS o Images Per Second. The faster method to write an image/type frame burst is the dng silent pics, but they last only few frames due to camera internal buffer capacity. JPG is compressed and it seems at first glance faster to write on memory card: true, but the processing time to compress it (by a DSP or a dedicated internal firmware routine) nullify this advantage, and also makes it worse in terms of "lost" time