Messages

Many thanks, tecgen !

I have just build the code from your repo, including latest commits resizing the icons, and tested it in my 500D. This is how it looks:





I think it's Ok this way.

They look fine to me.

Probably the word "TAP" would be enough?.  And "LV" for "liveview" on the 500D.

Nice improvement, thanks!

I have just tested it and works perfectly in my 50D.

But I have 2 other cameras, that also lack a Q button: A 500D (that uses the Liveview button) and a EOS-M (that needs tapping the touchscreen instead of pressing a button).

So, we still need more icons [emoji6]

50D can record 1080p raw at 20 fps continuosly.

Fixed both, hopefully.

Now it builds correctly for 50D.

I have just done a quick test in camera. Everthing seems Ok, zebras (RAW and LumaFast) work, and powersave settings in liveview photo mode work Ok also (turn off global draw, dim display).

   

Last nightly builds (2016-04-15 and 2016-04-13) are failing for 50D, with this error in the build log:

Code Select Expand


../../src/zebra.c: In function 'clearscreen_task':
../../src/zebra.c:3862:25: error: implicit declaration of function 'idle_kill_flicker' [-Werror=implicit-function-declaration]
                         idle_kill_flicker();
                         ^
../../src/zebra.c:3867:25: error: implicit declaration of function 'idle_stop_killing_flicker' [-Werror=implicit-function-declaration]
                         idle_stop_killing_flicker();
                         ^
cc1: some warnings being treated as errors
make: *** [zebra.o] Error 1



So it seems that functions "idle_kill_flicker()" and "idle_stop_killing_flicker()" are not well defined in /src/zebra.c

I do not see this error on recent nightly builds for other cameras.

There's something we have to test in order to have it fixed? Could be this error related to the recent stubs reformat? (perhaps some stubs missing for 50D?)


--------- Edit --------------------

Perhaps the problem is in this code:

Code Select Expand


#ifdef CONFIG_KILL_FLICKER
static void idle_kill_flicker()
{
    if (!canon_gui_front_buffer_disabled())
    {
        get_yuv422_vram();
        canon_gui_disable_front_buffer();
        clrscr();
        if (is_movie_mode())
        {
            black_bars_16x9();
            if (RECORDING) {
                fill_circle(os.x_max - 12, os.y0 + 28, 10, COLOR_RED);
            }
        }
    }
}
static void idle_stop_killing_flicker()
{
    if (canon_gui_front_buffer_disabled())
    {
        canon_gui_enable_front_buffer(0);
    }
}
#endif


That originally was on "zebra.c" but now has been moved to "powersave.c" (line 406). 

My C programming knowledge is very rusty now, after many years of not practising it, but it seems to me that this code contains the actual function definitions for "idle_kill_flicker()" and "idle_stop_killing_flicker()", so the definitions are missing in "zebra.c"

Yes, it seems that 80D's sensor includes on-chip A/D conversion, aproaching the DR at ISO 100 to the DR seen on Sony sensors.

But 80D is a Digic 6 camera. And ML has not been ported yet to any Digic 6 camera... and porting it seems a very difficult and time consuming task ... so don't expect to see ML running on a 80D soon.

It works for me in three different cameras; EOS 500D, EOS 50D and EOS-M.

So please, be more especific: why do you say "It doesn't work"? 

You can't activate Advanced Bracket when Dual-ISO is enabled? Or it does not take pictures at all? Does it work when you disable Dual-ISO?

Or the problem is with the flies? You cannot process them with cr2hdr? Or they are not properly bracketed?

We need more info to be able to help you.

You can bracket Dual-ISO exposures easily:

1- Find a static scene (landscape, etc) and mount your camera on a tripod.
2 - Set camera to M mode, chose the aperture value you prefer. Set Dual-ISO as active.
3- Enter LiveView, use A-ETTR to find the shutter speed value that maximizes exposure without clipping any highlights. This will be the base exposure for bracketing.
4- Exit Liveview, enter ML menu and setup Advanced bracket options (number of desired frames, EV increment) and choose as "sequence" the option "0 + ++". Setting the 2-second delay is useful also to avoid camera shake when starting the bracketed series.
5 - Press the shutter release to start taking pictures.
6- In your computer convert all Dual-ISO CR2 files to DNG with cr2hdr.
7- Process the DNG files corresponding to a bracketed series with your preferred HDR sofware.

That workflow will work, I see no problem in it (be careful to do not mix processed DNG files with original .CR2 files in your HDR sofware, as you were previously attempting).

But ... Dual-ISO files have a wider dynamic range at a expense of lower resolution. And they do not have better color.

So is preferable to use exactly the same workflow with Dual-ISO disabled, skipping number 6 and feeding your HDR software with regular .CR2 files. You will only need to increase the number of desired frames in Advanced bracket to cover the same dynamic range. And the resolution will be better. So I can't see any real interest in using Dual-ISO in this scenario.

I really do not understand what are you trying to do: merge Dual-ISO processed DNG's with regular CR2 files in an HDR software? What is the interest of doing this?

Dual-ISO is useful to get a wide dynamic range when bracketed regular pictures are not possible (moving subjects). But if you are already doing bracketed exposures to make an HDR, you can simply turn Dual-ISO off.

And yes, a DNG from a a processed Dual-ISO picture has a slighlty different resolution than a regular CR2 file, the outer lines are cropped. If you really need to merge both files, you can convert both to TIFF 16 bit, open them in an image editor (Photoshop, GIMP, etc.) and crop one of them to the exact size of the other one. After that, you can merge both TIFF normally in your HDR software.

And I do not understand how these questions are related with ETTR settings. And how ETTR settings could affect how Dual-ISO module makes more or less images ... Dual-ISO is a single shot, not a bracketed series. And as I already said, I do not see the point of using Dual-ISO if you are shooting bracketed series.

And focus-stacking Dual-ISO pictures is exactly the same as focus-stacking regular pictures, read the forum and try to master focus-stacking alone first.

M3 and M10 firmwares are based on Powershot series firmware, not on EOS DSLR's, so Magic Lantern cannot run on these cameras. In theory porting CHDK to EOS M3 is possible, and some initial work has been done, but there is no a completed CHDK port so far.

ef-m 11-22mm lens in this category need to unlock
If the advance has been unlocked before boot
Press the shutter results do not go
Necessary to unlock the lock and then press the shutter

Yes, this is a known issue, the shutter bug but currently the causes are not well understood and there is still no way to completely solve it. It affects all EF-M zoom lenses, but not the EF-M 22mm f2, and also does not affect EF and EF-S lenses mounted on the EOS-M using the lens adapter.

The bug can appear frequently or not, and this depends a lot on the brand and type of SD card you are using.  Currently we know that using a  SanDisk 32GB Extreme Pro UHS-I SDHC U3 (Class 10) 95 MB/s SD Memory Card in most cases can greatly help to reduce to the minimum the probabilty of experiencing the bug.

For stills: raw histogram and raw zebras, Auto-ETTR, spotmeter, Dual-ISO, automated focus stacking, intervalometer, full resolution silent pictures, ghost image (for panoramas), crop marks, focus peaking and magic zoom for easier manual focusing, advanced bracket, DOF info, motion detect, ....

Works for me also, on stills and H.264 video.

This has been already discussed, and it is not possible. The raw data cannot be processed at all by the DIGIC processor, even for discarding bits, the processor is not fast enough for such high data rate.

The 70D records full HD without ML? If you by continuous mean more than 4GB files thats not really an issue as it probably splits the file into multiple ones? At least my 7D2 does that.

I was talking about ML raw video recording, sorry for not stating it clearly. 70D can only record 720p raw, because the writing speed for the SD interface is limited to ~ 40MB/s, and raw video files are huge. A 50D, with a fast CF card, is able to record 1080p raw video.

I may be biased. But honestly I do feel like you could start phasing out some of the older cameras. I dont think too many people uses a 50D anymore, and if they do and ML is super important to them they can get a 70D realtively cheap when the 80D comes out. If not they can continue using a functioning build of ML.

Bad example.
I use a 50D with ML. This cam records Full HD 1920x1080 at 23 FPS continuous.  The 70D can't do that, because the SD interface is limited to 41 MB/S. And several ML functions for stills that work perfectly on 50D do not work on 70D (focus stacking, etc.)

And keeping ML running on older cameras is not as hard as porting it to new models, the initial effort to get it working needs much higher developing skills and a lot of time. And porting ML to Digic 6 cameras needs a much harder work, as already explained.

Posting hundreds of complains saying "Why there is no ML for my cam?" in this forum do not help to get to this job done automatically. We need more people coding, testing and debugging, no more people complaining.


I may be biased also, but biased to have fun experimenting with inexpensive second-hand cameras. But I think that if someone wants more features for the latest Canon cameras, he should ask Canon. The Canon guys can access ML code, it is public, and they could implement ML's features in their cams easily if they want.  It's very difficult for a reverse engineered and volunteer based project to catch up with latest commercial products, that land in the market at such fast rate.

I do not shoot video usually, but I have tested mlv_lite on my 50D, with a Sandisk Extreme Pro 160 MB/s 32GB CF card.

MLV lite allows me to record Full HD 1920x1080 at 23 FPS in crop mode during 1min 30 sec (global draw off). This is not possible with regular MLV, I cannot go beyond 20 FPS for continuous Full HD recording, it fails after 15 or 20 seconds if I try to increase FPS. And at 20 FPS MLV lite is more stable than regular MLV (no yellow camera icon during the first seconds of recording, the icon is always green).

The 4GB file splitting works OK now, with the latest raw_rec module posted here.

The drawback is that with MLV lite I get a magenta cast when extracting DNGs with mlv_dump. I need to correct the black level (sending  "--black-fix=1768" option to mlv_dump) to fix it.

If people donate, then stop whining, it's hard work, people pay, you do, there's no much philosophy in it.

You are wrong, what you are describing is one possible philosophy, the commercial way. But there is another philosophy, completely different: the open source, community driven projects, based on volunteer effort. The developers here, who have created ML, prefer the second model. And they are afraid that hiring a particular developer to improve ML with a paid job will negatively affect the whole community based project.

So please, do not insist in taking the commercial way, asking for donations, etc. This has been discussed many times, and the answer has always been "no".

   

No, as far as I know, for any Digic 6 camera.  Nikfreak's ports for 70D and 100D are the most recent efforts to expand ML support for new models. Some initial work has been done on 1200D, also, but then discontinued. But nothing for Digic 6 cameras, as I said, this is way more difficult.

5D Mark III, 6D, 70D, 100D, are still current Canon models, and they are all supported by ML. And 700D, 60D and the original EOS M probably are still in production, and are also supported by ML. So if you need ML you have plenty of choices.

And to get ML ported to the newer Digic 6 cameras (a huge task, as I said), probably the 7D Mk II will not be the best candidate: it's expensive to do bleeding edge experiments with it, and his dual digic processor makes the programming a lot more difficult. The only advantage it has over other Digic 6 DSLRs is that there is a firmware update for it already distributed by Canon, and this makes ML development easier.
   

Walter is not pessimistic, he knows what is talking about, and he is patient enough to answer to the same questions again and again.

Porting Magic Lantern is a very difficult and time consuming task, that needs a lot of reverse engineering and hundreds of hours of work by a highly skilled programmer. Nikfreak could tell you about it, it has done the most recent ports, for 70D and 100D.

But new Canon cameras need a lot more extra work: they use a different version of ARM code, so ML needs to be rewritten for them, and also most of the tools the developers have written during last years to do reverse engineering on Canon cameras need to be rewritten as well. And no developer here has started this huge task, and they say they have no time and interest to do it.

Deleted, sorry.

Many thanks to A1ex, Licaon_Kter, dfort, and dpjpandone for your efforts to improve ML for the EOS M, and making possible this new nightly build !

I do not shoot video, but I'm glad to see that an old issue with A-ETTR present in previous builds for EOS-M seems fixed now.

ETTR worked in previous versions, but the "ETTR ..." on-screen message during exposure adjust locked and did not dissapear until I pressed the shutter button.  So I needed to look at ETTR hint in RAW histobar to know if A-ETTR had already fiinished calculation or not. With the new build, this issue is gone, A-ETTR works fine.


Thanks again !