Messages

I'll have a drink in your honor then, kind sirs!

Yesterday I went to shoot a timelapse with FPS override and I was thinking: RAW video should be very much doable at low framerates, right? Because the camera has time to dump the buffer and the SD can receive it.

This feature should have an indicator embedded in the FPS override menu, which will tell you how much continuous time (frames AND real time in hh:mm:ss) you can record at the current framerate before the buffer gets full.

Just my 2p.


_{Offtopic, what ever happened to the 'scripts' tab? I found myself bored one day and I wanted to play sokoban, but then I remembered ever since 'modules' was implemented, the scripts were nowhere to be seen.}

If the 1100D has been abandoned it is sad - But please let us know.

Apparently Nanomad's at it again, he's trying to resurrect RAW video support for it, so, pretty much like punk, 1100D's NOT DEAD.

So is there a version I can download that would work on my 1100d?

The nightly builds are on the first page (http://builds.magiclantern.fm/#/). They work now.

However, since you've never had ML installed, you'll need to find a working .fir to "initialize" the first ML boot-up. (the .fir only tells the camera to search for the ML files from now on)
One can be found here http://nanomad.magiclantern.fm/1100D/magiclantern-v2.3.1100D.RC3.zip.

So, in conclusion, get the files from the first link, extract the zip to the card (root directory) and copy the .fir file from the 2nd link into the root directory of the card.

Good luck!

Yeah, Nanomad's nightly site is no longer accessible, instead, a "unified" download center has been put in its place.
The archive is gone (good thing I kept all my nightlies on the PC) to some extent, and all the present builds have failed to compile.

Just pointing it out.

If you don't care about it being clean you might get it to work with a tether or hdmi capture

You're a genius.
Thanks!

Not possible on the T3 but most other cameras have this capability built in, so it's not something that ML has has much motivation to implement, and would probably require a lot of work. I think there's some possibility of doing zoom on raw video on other cameras, but raw on T3 does not stand much of a chance with the tiny buffer and slow card reader

I know about the RAW capabilities being totally 0, but I just want regular recording of the zoom window, even if it's just the LV frame buffer (720xsomething). Still a nope?

_{Then again, I'm not a part of the dev team and I probably won't be for the following 2 years while I polish my C skills.}

I have searched for this on other threads as well and I had no luck.
Is the option to record video of a zoomed area (5x, 10x) possible on our camera? (There has been suspicious activity around my house and I need zoomed footage on the individuals as soon as possible.)

(i.e.: you press zoom, the image gets zoomed, then you press record and instead of zooming back by itself, the camera records the zoomed view)

Thanks either way.

[Bug]

Bug: I don't know for how much this has been an issue, but whenever I hold the EV button and scroll the dial (i.e. I change exposure), when I lift the finger from the EV button, it (the camera) automatically enters the ML menu, as if I'd just tapped the EV button. Now, I sort of understand the instructions behind the tap vs. hold, but I can swear I didn't have this problem until recently. It's as if after every click of the dial, ML registers a new press of the EV button.

Anyone remember of a time where changing EV didn't fly you into the ML menu?

I liked to know if ML has a function that a friend of mine has on his nikon to focus on a color, and then the picture is al in Black and White exept for that color... takes greate pictures that way.

Hope there is!
thanks!

In the Overlay tab, look for Focus Peak. Press Q. You should have a few settings, some of which are what you specified (namely, grayscale image and color).

And you need to have the .fir file in the sd too, u can extract it from older builds.

Or, you can just get it from here http://nanomad.magiclantern.fm/1100D/magiclantern-v2.3.1100D.RC3.zip instead of looking through some 2 hundred builds.

Well, enjoy your vacations everyone! I'll keep trying to crash the builds with every chance I get, as happily as ever!

Confirming the freeze continuing on the July 20th, 2013 build. Once the autoexec.bin is placed on the card and the card in the camera, the LED stays lit after closing the card door and the only fix is removing the battery and putting an older firmware (which, for me, is the July 11th build).

Possible bug: when using multiple LiveView presets and "Powersaving in LiveView" with the option to enable the powersaving feature via the DISP button - By pressing the DISP button, the camera cycles through the LV presets until the end and then the powersaving feature switches on. If you press again, the screen reverts to the original state (on/brightness restored), but the LV preset is stuck to the last one.
To switch LV presets, you have to go to the ML menu and press Q while highlighting the GlobalDraw setting.

I think it should revert to LV preset 0 and so on after having completed the preset cycle and the powersaving activation.

This "bug" is present in multiple nightlies, I am unable to pinpoint the build itself, so I'm thinking it's an error in implementation somewhere.

[Suggestion]

Suggestion(and this should be available for all cameras): an adjustable panorama-making feature (based on ghost image rendering method), which allows the user to choose the direction in which he/she'll pan the camera, overlapping percentage (how much of the previous image is shown), opacity and a greyscale option, which I imagine would be of great help in some contrasty scenes.

I am aware one user attempted in 2012 to create code for this kind of feature, but I found it a bit over-complicated for what it's supposed to be (it required a precise number of shots, focal length, etc.).

In short, it's about an addition to ghost image, which allows you to choose how much of the image is shown and where it is shown.
_{(maybe even the automatic creation of a special folder per panorama?)}

offtopic : 47 I would suggest that you go away for another week, really fast, so we get more things done, faster

offtopic: ;___; I'd better find 14-bit HDR (dual streams, not interlaced) RAW 1080p video with geolocation accessible via touch screen and voice control when I come back.

[UPDATE:]

Hi!

When I try to load modules i get an error:"tcc: error: undefined symbol 'ram_hist_get_overexposure_percentage' [E] failed to link modules" I am on last (Jul9.) nightly

Using the 9th of July 2013 version.
Mine can't even load the .sym file.
It returns some error among the lines of "MISSING SYMBOL FILE: B:/ML/MODULES" at the top, then the screen ends and on the bottom it says "ist Error loading 'B:/ML/MODULES/t3_105.sym': File does not ex" then the screen ends again.

I haven't checked for crashlogs or anything, I will in the morning when I will get to my card reader.

Offtopic: I've been gone for 1 week and you guys are already putting modules into the 1100D? Neat!

UPDATE: no crashlog seems to have been created

I just looked for it and couldn't find it.  If it is in there, it's hiding pretty well or I'm blind.

Well, damn, they took it out. It was quite useful for snapshots. I hope we'll have it back in some future version.

[Bug Report Update -]

Bug Report Update - Intervalometer - Okay, I reverted to the June 13th release and ran (am running) the intervalometer at 30 seconds with the shutter speed at 29 seconds.  No problem at all.  The camera has been running for over 2 hours and 20 minutes and it's up to 275 simulated shots.  Now time to recharge my only battery :-)

Aw, man, you should have used the save-to-422 so that you would have not wasted simulated shots for nothing.

(if we even have 422 anymore, I haven't checked in months)

[FPS override]

Relevant to the earlier issue of Av button pressing in LiveView during FPS override: it* seems to happen the same without FPS override as well.

*the Av button doing practically nothing for a good few pushes (around 20) until it shows you the ML menu.

I was with GlobalDraw active, but only with zebras (as opposed to my other, previous display presets which include focusing peak and other GPU-consuming tasks). Something happened after the release of the 13th/18th of June nightly which caused erratic behavior with the Av button (it used to only not respond in LiveView when trying to close the ML menu via the Av button)

_{(hope I didn't accidentally my whole English, but I've tried to formulate the sentences like 3 times)}

[have had]

Well, you need to have had a .fir at some point.  After that, I think you can just use the .bin.

Keep in mind that I'm new here, too.  If we could get an admins input here, that would be reassuring.

I think that the .bin replaces the .fir, but you have to have run the .fir at least one time in the past without reflashing your firmware back to OEM inbetween.

Precisely! The .fir tells the firmware upgrade system on the camera to look for the .bin file on the SD every time it boots up (if it's not there, i.e. another SD card, it just carries on with its normal Canon firmware, but it does the check every time). Holding down the SET button (it has to be at its default setting, so no DoF preview custom function setting, guys) while powering up the camera will bypass the ML boot-up sequence (the bootflag is still enabled, mind you) just that one time you're booting up.

Addendum: looks like ^_somebody enjoys formatting their text as well.

[Suggestion]

Uhm, the thing is...we use timers to check long/short presses but FPS override screws it (the check!), hence you cannot open ML menu. A quick suggestion is go out of LV mode which in turn should turn FPS override off...sucks...

Thanks for the suggestion, that's how I got out of it. I didn't panic, because worst-case scenario I would just have to replace the config file with a backup I do each time I get a nightly.

Also, I thought how the del button works, so I tried short, repeated pulses to sync with the frames (in case it can actually detect like a 0ms pulse), long pushes, nothing worked. Thanks for explaining the principle so that I won't mash the buttons off trying to fool the camera.
Oh, and exiting the ML menu by pressing del still doesn't work.

Suggestion: can you guys implement a P mode for Movie? (as in, I get to choose the ISO and the camera gets to choose Tv and Av) I love controlling the ISO, but that also means I have to adjust other settings as well, which is sometimes quite time-consuming. Thanks!

[Note]

Found some sort of a bug: while using FPS override, it is next to impossible to enter the ML menu from LiveView (it takes a lot more del key pushes than before the 18th of June nightly; and yes, it was tricky to enter the ML menu before because of this, but now it's rather impossible).

Also, in Movie Mode, using FPS override, if you open the Canon menu and close it, the screen will stay turned off (definitely off, not on and just black). Another scenario with FPS override is that if the screen turns off (at least while recording) (by adjusting the powersave settings from ML), there are many chances the camera will freeze upon trying to turn on the screen immediately (the screen stays off, the mirror stays up even after turning off the camera from the switch - all comes back to normal once you take the battery and put it back in).

If you do not try to do mess with anything, a FPS overridden movie is saved and nothing bad happens.

Random crashlog and COREDUMP.DAT while setting the FPS override.

Code Select Expand

[75] menu_redraw_task: NULL PTR (fe28,e1a00000)
pc=  cc7c8d lr=      4b stack=16a570+0x2000
entry=c84f50(0)
e1a00000 e59ff014 e59ff014 e59ff014
e59ff014 e1a00000 e59ff010 e59ff010


Magic Lantern version : v2.3.NEXT.2013Jun18.1100D105
Mercurial changeset   : 423f465af80b (unified) tip
Built on 2013-06-18 19:49:33 by [email protected].
Free Memory  : 240K + 1144K


There are 3 other crashlogs on the card, all from the same experimentation.
Note: the camera did not, at any point, report a crash or mention the crashlogs (as it did yesterday when reading the documentation in-camera).

[the .fir file is missing]

Hey, I just got the 18th of June nightly. This is probably on purpose (as stated on the nanomad site), but this time the .fir file is missing. Nice of you to finally put the documentation!

However, each page of documentation generates a crashlog, as such:

Code Select Expand

[75] menu_redraw_task: NULL PTR (dd88,e1a00000)
pc=  cc7c8d lr=      4b stack=16a570+0x2000
entry=c84f50(0)
e1a00000 e59ff014 e59ff014 e59ff014
e59ff014 e1a00000 e59ff010 e59ff010
[75] menu_redraw_task: NULL PTR (c55c8,e1a00000)
pc=  cc7c8d lr=      4b st

Magic Lantern version : v2.3.NEXT.2013Jun18.1100D105
Mercurial changeset   : 423f465af80b (unified) tip
Built on 2013-06-18 19:49:33 by [email protected].
Free Memory  : 198K + 1933K


and here is the COREDUMP.DAT    .
Also good job on freeing memory, I couldn't believe my eyes when I saw 2+ free MB!

Stay frosty!

Edit: apparently, there is as much free memory as before, but I guess crashing something freed up ~1.5 MB.
2nd edit: upon opening the coredump myself, I managed to see something within the jibberish string about an 105.fir. I am hereby stating that I do not have the .fir on my card, and have not had it for weeks. (should this change anything)

I'm not seeing the .zip file on the nightly page.  The last one I see is for the 12th.

I can confirm this. It has been missing the last time I've checked as well (est. 18 hours ago) and now the 15th build is only a few kB in size (as opposed to the regular ones at around 3 MB) as it's lacking the .zip itself.

_{i hope you guys didn't take out the README/manual file}

Yo nanomad is there anything we can do in assisting you with the possibility of RAW video for the T3? I will test anything and I mean anything LOL. Let us know what we can do. Is there a work around to address the low memory or small buffer issue?

Magic Lantern and you has taken our DSLR out of DSLR purgatory and has given it wings. 

I'm with you 120%. I'm on summer break and it's gonna rain for weeks, so I should theoretically be stuck to my PC, day and night, with an endless supply of batteries and internet, just good for testing new builds (that may or may not brick the camera, but hey, you gotta risk a little).

A little off-topic, how does the "format and keep ML" procedure work? Are the ML files stored to RAM (that would be interesting, since the camera says they're about 7 MB big and it takes some time to count (I think, but it could be just copying them very slowly to the RAM) them all)? _{Either that or you just move the files on the card to a sector that will be formatted lastly and then, while formatting, put them back to the top and... ah, I wish they'd teach me this in school already.}

Anyway, keep 'em strong guys! We appreciate the work.