Messages

Without any module loaded, do you still get memory errors? (if so, what's the exact message?)

The error is the same:

Memory Error   alloc(12kB|TMP|DMA)
No allocator for 12kB|TMP|DMA at tcc-glue.c:70, module_task.

[EDIT:]

Could you be more specific about when you get the crashes?

• Whenever I try to load modules, they all crash, except for pic_view.mo.
• At times, I open the debug tab, it shows "Memory Error" instead of "Free Memory".
• Whenever I close the camera while the ML menu is displayed, it'll always hang until I take out the battery.

I'll try tomorrow's build. So far, both the 22nd and 21st have the same problems. (maybe others as well, but I have only tried these 2 so far). To my knowledge, the last one that worked exceptionally was the Feb14th one.

EDIT: it hangs when I'm in the Canon menu as well as when there's some overlay from ML (either a notification like "module loading was skipped due to etc." or the usual overlays in LiveView, although in LV, when you turn off the camera, the screen will hang, but the mirror will go back down).

[EDIT]

What's the complete error message?

That's it. It's in the debug tab, as an item with a red box to its left. The item's name is Memory Error and its "setting"/value is that error.


I formatted the card without keeping ML and I'll try another card reader in a few minutes.
EDIT: I updated to the Feb 22nd nightly, still the same problem

I forgot to mention, on the bottom bar while the error is highlighted, it says

Free memory, shared between ML and Canon firmware.
No allocator for 15kB|TMP|DMA at tcc-glue.c: 70, module_task.

Using 2014Feb21.1100D105, I managed to get into lots of problems:

• Memory Error  |> alloc(12kB|TMP|DMA)
  No module will load (except for pic_view, which is quite useless if file_man doesn't load).
  
• Even with all modules disabled, the error is still there.
• Closing the camera while in the ML menu causes it to freeze, until the battery is taken out.

Can anyone confirm this, or is this just because my card reader decided to die on me just as I was copying the new files on the card? (the version shown in the debug tab is the current one and I have noticed a new module, so I think all the important files (.bin and .mo) have been updated)

[Example:]

While driving to work today, (as always I'm wonder about enoumerous things...) I was wondering...

Is it possible CPU/MEM wise for our 1100D (T3) to process a 3 to 6 Frame HDR Picture Automatically via some module? Am I speaking some impossible nonsense or... Is it really possible?

Example: Select module_autohdr
Choose from 3 to 6 Exposure intervals, Point, Shoot and Process and Voilá! A HDR RAW! 

If I remember correctly, someone already asked this and the answer was something in the lines of: "we could, but we won't, because it's something you can do in post(-processing)"

However, anyone is free to write any module, so someone ought to get tired of manually creating HDRs.

That was for MAKING an HDR file. The auto-HDR sequence shooter (with frame number decider) already exists .

It seems this is quite a common problem (not everyone archives each downloaded nightly lol). Shouldn't we sticky/edit OP's post with the fonts.dat fix in red flashing text?

I have a full week, daylight, snow and some horizontal blinds, a perfect environment for RAW, so I'm up for any preliminary tests.

Wow, that's quite something.
I mean yes, I have been visiting this thread around every day since I decided to try ML, even in the long hiatus (sept - jan), but I've never thought we'd get dual_iso, especially this early. Now RAW implementation?
I predict you guys will make a "convert to 1Dx" function by the end of the year. (pretty much like "Don't click me")


As actual, useful feedback, dual_iso's works great on my end, having lots of fun with it.

One question though.. is it possible to take double exposures with the current Magic Lantern?

Nope, and from what I recall, it won't be possible in any version (unless someone makes a separated script/module) because it's something you can do in post.

Can you upload a cr2 of your test scene?

http://www.mediafire.com/download/2r415t2zc3khdxc/pre+and+post+ETTR.zip

EDIT:

edit: ETTR does not work in LV, even the menu item says so...

Yeah, otherwise, in Always ON and Auto Snap it seems to be working just fine, when not in LV.
Strange thing now, every mode of ETTR pushes my exposure to +5 EV in LV.
Also, I see no warning about ETTR not working in LV. Bear in mind that I am using the precompiled nightly.

Can you upload a video of you using auto ettr and showing the -5EV bug?

I'm afraid I don't have another camera, nor a decent phone, but it literally just goes like this:

LiveView.
I enable AutoETTR from the ML menu, set it to double half-shutter click.
I double-press the shutter halfway.
Message "ETTR..." appears in the top-left corner.
Exposure goes way down (-5.0), everything is underexposed.
Message "Expo limits reached" appears in the top-left corner.
(I get sad and manually expose to the right.)

EDIT: sorry for the twisted neck it gave you guys, I did rotate it in youtube, but for some reason, that takes longer than the upload itself

OK, I grabbed today's build and toyed with it. dual_iso works very well, silent returns a linking error (probably was to be expected, based on previous discussions), auto ETTR still does the -5 EV thing and that's about it. Still no overlays in PLAY, but I did notice it being mentioned in the Help tab of ML.

Now, let's shoot people in the snow with dual_iso!

We got raw overlays in playback mode btw. Willing to hear feedback on how they work . Remember to enable review after shot or it won't work

Haven't managed to enable the raw overlays in playback. Tried Canon's image review -> hold, tried ML's (already had set it like that, but it didn't hurt to try all permutations), neither would result in any RAW overlays. Maybe I'm doing something wrong, it's quite late here.
So I decided to see whether or not they're true RAW overlays in LV, by switching picture styles (cinestyle vs. a very high-contrast one) and the histogram definitely changed => not RAW. The zebras, I really can't tell, but they should work by the same principle.
Whatever should be RAW isn't on my end, or at least I can't make it work. They do, however, all state RAW RGB, if that's any help.

I kept toying with ETTR, set it to Always ON and it displayed this after taking an image without LV:

ETTR: next ISO 0 N/A (was ISO 0 N/A)

At least now it didn't affect my exposure for the worse.

Can you share a silent DNG? I fear the state transition that we target may not be the most correct one

(Hopefully, it's not one of my cluttered desktop.)

http://www.mediafire.com/download/zmu0tf9xur0kpvt/98870091.DNG

EDIT: The fact alone that it's only 33 kB is something to ponder in case of a 14-bit DNG

I just finished testing today's build. It's stable enough, but almost none of the new features work.

• ETTR just brings the EV down to -5 (more like ETTL, am i right? ), but it's nice to know it does something.
• Silent pic is working alright (at least  single and sharpest), except for when it comes to viewing the .DNG files, either in-camera (with pic_view) or with Lightroom or Photoshop (using 2 different versions of Camera Raw). But if I remember correctly from older threads, these can be opened by other software? Point is, they can't be viewed using standard means.
• dual_iso is dead ("Err"), but from what I've read, it is expected to run soon without any workarounds
• On a side note, pic_view managed to open the .422 file generated by the screenshot feature.

Keep rocking, guys. Given enough time, I have faith you'll turn it into a 1D X.

What is the max temperature to operate safely? I reach 68°C, the colour was red and I think it was too much, so I turn off. Any suggestions?

It should be alright; the camera will turn itself off when reaching critical temperature. (source: Canon's manual)

edit: all images are _MG_xxx.jpg named and not IMG_xxx.jpg, no idea why

That's what happens when you select the AdobeRGB color space.

... it seems like the manual aperture doesn't want to work for video mode. If I set it to f22 (using the kit lens) I can hear it swivel in and out but it doesn't stay in f22.   

Yeah, that's a (general, I think) bug with (zoom?) kit lenses. The aperture doesn't stay put for some reason. You could always just set the aperture (SET -> DOF Preview) and partially untwist the lens, as it seems to be the only work-around.
Good luck.

Thanks for that, but that sounds very hacky.
How is the stability? Any crashes or problems while using it?

It's quite stable, don't worry.

[however]

I know about the new fonts, I managed to test some recent nightlies with the new eye-candy, while having a bootable card and a booting camera.

I'm just saying that when you need to make the camera boot from the card, you need a .fir (which I've had for quite a while) . After the bootflag is enabled, you get a yellow-text screen (as opposed to the green-text success screen) saying the "bootflag is enabled", but "FONTS.DAT was missing, please copy all files (a few MB)", however, the camera refuses to load ML after restart.
My first (and so far only) solution was to copy the FONTS.DAT from an older nightly.

Guys, I think I just found a problem with the compiler:

FONTS.DAT is missing since the Sep12 build and it's making the fresh install process quite impossible without older nightlies (or a unified release).

They don't link because they require features in the core that have not been implemented on the 1100D, and so the symbols are missing.

Yes, but say, you load a couple of "working" modules and one "non-working" module and they all fail. I can understand if it's a safety precaution, but I don't get why.

Just picked up today's build (2013Sep19). The font change was a surprise, even though I'd noticed the extra "fonts" folder.

Both "file_man" and "autoexpo" still work (even both at once), the others don't (linking error).
While the font change is welcome, I'd much rather have visible font in the debugging dialogues (show tasks, etc.). I understand there's a lot of info to be shown, but that could be rendered at a higher resolution and then just zoomed in (I guess).

Keep it up guys!

PS: The arkanoid game works as well. That's weird, yo.

Quick suggestion: can we get more customization on the keys? For instance, I could really use the flash button for any other function (say DOF preview).

Speaking of which, is there any way you can fix the conflicts between SET (C.Fn. as DOF preview) during Live View and the ML menu? Whenever I press the SET button, the camera goes into DOF preview mode and closes the ML menu. I'm just asking if it's possible, because it seems really weird, since this only affects Live View.

Don't mention it brah, glad to help.

Copying the files through a USB cable (with the card in the camera) will probably never work, since the PC uses certain protocols to communicate with the camera, which exclude strange file transfers.

As for copying the files via a card reader, make sure you don't have the LOCK switch enabled on the card, as it might distrupt file handling.

If this doesn't work either, try copying some normal files to and from the card (jpegs, MOVs).

If this still doesn't work, try formatting the card (I would suggest using SD Formatter if you've never formatted the card from Windows https://www.sdcard.org/downloads/formatter_4/).


It has to work at some point.