Messages

Wonderful, Greg ! Compliments !
Now Wolf should correct his 550D code by following your example, and refresh his pull request ! Great !

Now i can compile ! But what is the procedure to put my modifications online as a "pull request" ? Many thanks ! 

+1, I associate to the question. Even SD resolution will suffice ! 

Hi Greg ! Do your latest modifications works ? No more greenish color with zoom and full height frame ? 

It would be nice to have 1280x400 as 600d RAW DNG with 24 fps. It should be posible

Yes ! It would be great ! Let's pass the ball to Wolf...   

Some questions :

[1] Do the capture resolution can be selected ?
[2] Do the exposure time can be selected ?
[3] Do there is hope to run a little realtime movie (at least at 24fps) by tweaking something (resolution or exposure for example, or other things) ?

Many thanks !

Full resolution frame example on 550D (1736 x 1156 pixels) (1 second fixed exposure, independent of the exposure time you set) -> https://dl.dropboxusercontent.com/u/46130896/sample.jpg

Max speed is about a frame every 2 seconds on 550D with a 30 MB/s 8Gb Sandisk SD card

To take silent dng, go to camera settings on ML menu and enable silent pics (ON), then put the rotating knob of the camera into M (manual), then push the liveview button (the red one) then keep half pressed the shoot button to start silent-shooting. Release it to stop the sequence.

Great Wolf ! Many thanks ! You are great ! 

Do your mods are (or will be) integrated into the official unified builds ? Let me know ! Many thanks !

Just some think-tanks ...

5D3 is most promising for raw video... sure... but what's the point to squeeze out raw 1080p video (with so much efforts and sacrifices) from a camera that costs the same like a blackmagic, where blackmagic has a hassle-free (no single images to process one-by-one) 4K raw ? How many people will buy a 5D3 instead of a bcc for exclusive video purposes ?

5D3 is most promising for raw video... sure... but what's the point into pushing all the forces exclusively on this direction, when you can clearly see the results of the poll "what camera you have?" here in this forum, but neverthless it is continuously said "550d is too old...", "550d is not worth the efforts..." ... and so on ?

Sure, 5D3 is the main benchwork to concentrate on, in order then to port to the rest of the models. That's the right way.
Sure, 5D3 has a larger sensor so more light sensitivity than a bcc (not so much more, however). But as an advice: don't understimate the impact of even a SD resolution raw video achievement on the "poor" 550d ! 

News for 550d ? 

It looks like a waste of time trying to get RAW video on a 550D.

Even at SD resolution, it's not a waste of time... on the contrary !

and use fps override to reframe.

fps override is intended to change frame rate, not to re-frame a shot (changing the filmed area): it doesn't change the resolution of the movie...

+1, I associate to this question, and waiting for answer ! It is a great achievement 24fps 1080p RAW, but on a 5DMKiii ... a camera that only the body costs up as a leg and an eye... everyone is near to buy, instead, a natively raw-enabled video-cam ! The real achievement, the real breakthrough, the real bargain, the real stunning, the real amazing, the real useful, the real thing... is to port all this to a camera like 550D ! 

Many thanks Wolf !

But do the ML usb-output sources must be modified everytime the main ML graphic parts are updated ?
Or do it's automatic, so the PTP section don't need to be updated also ?
If PTP section must be updated to reflect the ML graphics, do it's kept up-to-date with the ML main graphics or it's left to his destiny ?

This is in order to know if it will be convenient, otherwise, to buy a HDMI field monitor and don't bother with the android tablet solution.

Many thanks for your next reply, Wolf !

It has be said to me that it is sufficient to enable a couple of switches in the makefile and then re-compile the latest sources.

Gerk.raisen : do you think it is true ? I still didn't tried this. I was thinking that it consisted in a simple instruction that puts out the pre-existing ML graphics to the USB: isn't it true ? Do the code must be modified every time the main ML code (or graphic and menu section) is changed ?

You need to compile ML yourself and enable it in Makefile.user.default

Can you give me a hint on where is and what is the correct variable, and the value to set for it, inside makefile ? Many thanks !

It will be useful and cheaper to use a tethered tablet as a field monitor, but ML graphics are not sent to it: only live video is.
Do this can be done ?

The last DSLR Controller version shows the live images from the camera (550D) but NOT the Magic Lantern (last version 2.3 stable) graphics and overlays.
What I'm doing wrong ? Do there are some options to enable/disable ? 

Do the porting of raw overexposure detection will be ever available for the 550D and other models ? 

The correct name of this fuction, in the audio field, is exactly : LIMITER

At least implement one of the proposed little templates I have done, because in the Others you cannot see if the color is inside or outside the "legal" area, because simply there isn't such an area drawn in the original template, but only a single dot.

Also: if you switch to x2 magnification you have implemented, you no longer can see if the colors are really inside the safe areas or not, because you have to re-scale also the underlaying grid ! You can say: "who cares ?"...but this way a vectorscope is useless for the majority of applications.

I hope you agree 

I can draw the templates, like I have already done with the improved vectorscope

This feature is a must for filming purposes, where a physical follow focus cannot be used, like on stock 18-55 lenses

People use vectorscope to calibrate colors... bigger=more precise evaluation if they are out or not, and about what quantity. If you know what a vectorscope is, you should know. I use it to evaluate if colors are right and if they falls inside the correct ranges. In a thumbnailed vectorscope nobody can see this.

Good ! Let me know when you implemented it, by replyng to this thread, thanks !