Canon 1100D / T3 Current state:
Release Candidate Danger, Will Robinson! Danger! (http://i.imgur.com/ML5SF.jpg)
The main issues that are holding ML are:(http://www.backmic.com/i/all-bills-red.png) Blindly maintained (development happens without a physical camera in our hands)
(http://www.backmic.com/i/all-bills-red.png) Lack of physical buttons (for menu, for example)
(http://www.backmic.com/i/all-bills-red.png) Lack of RAM (only 128MB (http://www.magiclantern.fm/forum/index.php?topic=5071.msg166988;topicseen#msg166988); most other Rebel models have 256MB)
(http://www.backmic.com/i/all-bills-red.png) Low resolution sensor: 4290x2858 => 1430x952 theoretical max in LiveView
(http://www.backmic.com/i/all-bills-red.png) Slow SD interface (20MB/s, not enough for raw video)
(http://www.backmic.com/i/all-bills-red.png) Low display resolution (1-pixel wide items may be incorrectly displayed or aliased)
Short-term Todo List:
(http://www.backmic.com/i/all-bills-red.png) Enable raw video and silent photo capture (almost there)
(http://www.backmic.com/i/all-bills-red.png) Enable Lua scripting (feedback needed -- what works and what not?)
(http://www.backmic.com/i/all-bills-red.png) Make sure the stability tests are passing (feedback needed)
(http://www.backmic.com/i/all-bills-red.png) Write down which features work and which ones not (menu walkthrough, for testers)
(http://www.backmic.com/i/all-bills-red.png) Update the user guide (http://www.magiclantern.fm/forum/index.php?topic=20455) (task common for all other camera models)
(http://www.backmic.com/i/all-bills-green.png) Done: Port 550D button hack to 1100D AE_COMP to open menu but retain the original long-press functionality.
(http://www.backmic.com/i/all-bills-green.png) Done: Start working on the fonts and display routines
Random bonus stuff:
(http://www.backmic.com/i/all-bills-green.png)Done: In-camera audio meters.
I will be posting updates here as I make progress -- Nanomad
The current version compiles and runs on 1100D.
RC 3: http://nanomad.magiclantern.fm/1100D/magiclantern-v2.3.1100D.RC3.zip Use development builds instead!! Use the included .fir (for 1100D 1.0.5) to enable the bootflag.
Source code: http://bitbucket.org/hudson/magic-lantern/src/tip/platform/1100D.105 (http://bitbucket.org/hudson/magic-lantern/src/tip/platform/1100D.105)
Main builds: http://builds.magiclantern.fm/ (some features not working)
Development builds: http://builds.magiclantern.fm/experiments.html (feedback needed)
Hi,
I'm (once again) trying to get the 1100D port up-to date. If you don't mind, I'll hijack your original post and use this thread as a work-log :P
Missing constants
- EVF_STATE (state-object.c)
Here you go:
#define EVF_STATE (*(struct state_object **)0x4C34)
#define MOVREC_STATE (*(struct state_object **)0x5720)
Tip: for AV button, you may want to look at 550D implementation, where it's used for arrow key shortcuts (tweaks.c). This button has different codes, depending on the shooting mode. I've only considered P, Tv, Av, M and Movie.
Just a quick question a1ex, as I hate eating pre-made foods...
How did you find these values :o
Those are state objects ( http://magiclantern.wikia.com/wiki/StateObjects (http://magiclantern.wikia.com/wiki/StateObjects), http://a1ex.bitbucket.io/ML/states/ (http://a1ex.bitbucket.io/ML/states/) ) - some sort of event-driven tasks which are pretty easy to hijack (that is, execute ML code at certain moments, like once per LiveView frame).
Most of those things contain strings with their name (for our example, we have EvfState and Evf\\EvfState.c).
ff5969ac: ff6db6d7 ; *'EvfState'
ff5969b0: 00000001 andeq r0, r0, r1
<state matrix follows below>
The state matrix (ff5969ac) is referenced from sub_FF0F73C8. So, with arm-console:
dec sub_FF0F73C8
[...]
CreateStateObject(name='EvfState', 0x0, addr=0xFF5969B0, inputs=14, states=10) => ret_CreateStateObject_FF0F73E8
*0x4C34 = ret_CreateStateObject_FF0F73E8
return ret_CreateStateObject_FF0F73E8
So, at 0x4C34, Canon firmware saves a pointer to EvfState object (see "struct state_object" in state-object.h).
For the fonts: on 5Dc we have used a trick to downscale the bitmap coordinates on the fly (its resolution is 720x240). On 1100D, the screen resolution is 360x240 if I remember well, but the buffer size is 720x480, and the firmware does some sort of interpolation (is it nearest neighbor or something else?).
The medium font has a width of 12 pixels, and the bottom help text in ML assumes this width (max 60 chars). Probably a very tiny font rendered at width=6px and with pixels doubled could work a bit better than current medium font.
If not, can we consider a larger font (maybe the current small font with doubled pixels, that is, width=16px), and use horizontal scrolling of help text, like in rockbox?
I'll have a look into fonts after making the ML menu button work reliably (shouldn't take too long).
Thanks for all the help!
Also: how much free memory do you have on 1100D? The 60D, 550D and 600D had some problems with this (but now there are solutions, only that I need to know which one to apply).
Free Memory: 26K + 865K
Oh, and the overlay isn't showing up in the idle screen (the one that says P, ISO AUTO, AWB, MF, ...)
Hm... not much. Can you try compiling without -mlong-calls with a 32-bit gcc?
I'll fix this (need to do the same on 600D), but it may take a while.
The overlay means clock and other small extra info from outside LiveView? It's ifdef'ed out (debug.c, around line 1800).
Uhm, dunno if I'm doing something wrong, but the memory usage stays the same (26K + 865K)
This time I've used codesurcery 32bit arm gcc (4.6.3)
Remove -mlong-calls from Makefile.inc .
I've done that as soon as I switched to a 32bit compiler. Maybe it's the codesurcery compiler, dunno :o
Here's the patch I've created to make 1100D compile again
http://nanomad.magiclantern.fm/1100D-compiles.patch (http://nanomad.magiclantern.fm/1100D-compiles.patch)
Applied memory fixes to 1100D (though you may need to double-check the addresses).
https://bitbucket.org/hudson/magic-lantern/changeset/17b0f20612c2 (https://bitbucket.org/hudson/magic-lantern/changeset/17b0f20612c2)
Well, it sure did something.
(http://i.imgur.com/8hz69.png)
I'll run the test suite you posted now
Not bad. And if the screenshot feature works, it's probably enough. If not, we may have to move something from the big buffer to the small one.
The 60D gives random ERR70 if the second buffer has less than 1MB free. Probably I should also display the maximum contiguous block.
This post contains current issues with ML
- [WONTFIX] Shutter and aperture working only in Exp Comp mode (applies to LV too)
- [L] Going from Exp Comp ON to OFF doesn't re-disable Shutter and Aperture
- [M] Focus peaking: peaks are off
- [M] Focus peaking - grayscale preview: Image is magenta
- [H] Magic Zoom: image is zoomed but it's being displayed wrong (weird aspect ratio, flickering)
Movie mode
- [H] ISO Stuff is not working
P Mode
- [L] Can't disable ExpSim
- [M] GlobalDraw - interaction with Canon graphics not working
I didn't finish testing as I have to go :P
Exp Comp - you mean expo override? So, the 1100D now has manual video controls, right?
Focus peaking and magic zoom off: this means that HD image buffer size is incorrect. You can take silent pics and use them to guess the right size. Howto: http://magiclantern.wikia.com/wiki/VRAM/550D
Magenta image: that's strange, on the 1100D even digic commands are different :)
The 600D has problems with ExpSim too, so it should be commented out in the 1100D too.
Yes, sorry, exp override. So we do have manual video controls as long as we activate it. Which is nice 8)
Hey there!
I'm want to help with the development for T3/1100D, I have a lot of experience with C/C++, but I don't have experience with reverse engineering, is it enough to help?
Also, I have experience with graphic design, so maybe I can help develop a special font that will look better on 1100D low resolution screen.
There is anyway to render ML menus in 720x240 natively, then upscale it using nearest neighbor to 720x480? I think that's how it is done on the official firmware. What would be required to change in ML in order to do this? or is it not possible due to it requiring to rewrite core parts of ML?
By the way, is 1080p video option really completely locked down on this one? Or did you guys found out anything? I remember seeng something about this on ML Google Groups last year.
Hi,
I'm glad you want to help. I suggest you start by setting up the toolchain to compile Magic Lantern and compile the latest release for the 1100D.
The 5Dc renders ML menus at 720x240, so you can inspire from there. All the changes required for this can be in bmp.c / bmp.h / vram.c IMO.
Ok, I'll setup the toolchain on my PC here,
Then I'll look into 5Dc source.
I've seen some 5Dc constants in bmp.c and vram.c (CONFIG_5DC), won't some of them work on 1100D?
It seems that Canon is using some tricks to get most of 1100D display, can someone send me some screenshots of the original firmware menus? I want to take a look how Canon is doing it.
By the way, there is any specific reason ML font is looks like a system font?
I'm thinking about creating a more rounded font, similar to the one in the official firmware, I can do it from the scratch, pixel by pixel (I have some experience with pixel art for games and stuff).
This is specially useful for extremely small text, so I can tailor it to look good in low resolution.
Hi, I'm glad you want to help. Leave me your skype/gmail address in PM and I'll get you started on the 1100D port and ML in general.
Hey nanomad,
the link to the .fir on the first page is not working
you forgot the ":" after https
https://bitbucket.org/hudson/magic-lantern/issue-attachment/1150/hudson/magic-lantern/1333128527.7/1150/ml-1100d-105.fir
We now have a menu button that's working very well. It works in every non-auto mode except A-DEP
Patch: http://nanomad.magiclantern.fm/1100D/menu_is_av_short_press.patch
autoexec.bin: http://nanomad.magiclantern.fm/1100D/autoexec.bin
edit: updated patch to work in LV too
Did anyone say in-camera audio level monitoring?
Patch: http://nanomad.magiclantern.fm/1100D/enable_mono_audio_meters.patch
Autoexec.bin: http://nanomad.magiclantern.fm/1100D/autoexec.audio.bin
Keep in mind this is HIGHLY UNSTABLE CODE
Your camera may explode
The 1100D probably uses the same audio IC the 600D does and has no AGC (the mic is kinda crappy though). Who's volunteering to tear apart his camera to find out?
Great work nanomad!
Updated the first post a bit.
All my efforts are logged here: http://nanomad.magiclantern.fm/1100D/
I usually upload "working" (NOT STABLE!!! JUST WORKING) builds only. If anyone wants to test them please get in touch with me before doing so
Try some of the audio code from TL. If it works and we have the same audio IC it will make reversing easier. The registers should be the same in that whole family of lapis ICs.
Will do.
You may want to backport this changeset: https://bitbucket.org/hudson/magic-lantern/changeset/63f5464711f5
to your repo. It should make things easier in the future when we'll have multiple audio IC around
I tried the tragic lantern code, but did not get any audio meters at all (while I can see audio levels with stock ML code)
Some random stuff i found in the firmware about Audio IC.
- Initialization is done at 0xFF06A388. This starts all the tasks needed by DryOS
- 0xFF06A2B0 is EnableAudioIC. It writes a bunch of 0xAxxx values to the AudioIC itself
Everythin related to audio is around there
- 0xFF069AAC is DumpAudioIcRegister. This function seems to dump all the registers somewhere, but it doesn't use the usual debug messages of dryos. Is there any other debug function?
Quote from: nanomad on July 15, 2012, 02:22:11 PM
Will do.
You may want to backport this changeset: https://bitbucket.org/hudson/magic-lantern/changeset/63f5464711f5
to your repo. It should make things easier in the future when we'll have multiple audio IC around
nice Ive added it in my fork, if someone want to check it.
Quote, but did not get any audio meters at all
I have everything skipped except for 600D stuff. Since the registers are different any ML writes to the "standard" registers change completely different things and interfere. I definitely had to neuter all of the writes and the override task.
Try some of the debug.c functions like power mic amp and unmute av. If they work that means you have the Oki/Lapis IC. Otherwise its a 3rd IC or something else. Also on 600D the registers are doubled, when you get a reg dump working you'll be able to see if its the same.
I should get audio remote shot working next...
Do you mind jumping on IRC? I could use your firmware dump :)
Is the audio ic read/write address right on T3? 600D register dump should work on T3 too even if registers are different.
The addresses are correct , the function I used to dump stuff isn't...
Looks like we have a new audioIC here :(
80 40
81 03
82 02
83 a9
84 6a
85 23
86 64
87 a4
88 d2
89 2d
8a 6d
8b 80
8c 92
8d 92
8e 0f
8f 00
90 92
91 92
92 92
93 92
94 92
95 92
96 92
97 92
98 92
99 92
9a 92
9b 92
9c 92
9d 92
9e 92
9f 92
a0 40 ; 00 on Enable (1,14)
a1 03 ; 00 on Enable (2,15) -> 00 on Disable (1)
a2 02 ; 02 on Enable (3)
a3 a9 ; A9 on Enable (4)
a4 6a ; 6A on Enable (13)
a5 23 ; 23 on Enable (12)
a6 64 ; 64 on Enable (5)
a7 a4 ; A4 on Enable (6)
a8 d2 ; D2 on Enable (7)
a9 2d ; 2D on Enable (8)
aa 6d ; AudioVolumeOUT - 6D on Enable (9)
ab 80 ; 80 on Enable (10)
ac 92
ad 92
ae 0f ; 0F on Enable (11)
af 00
b0 92
b1 92
b2 92
b3 92
b4 92
b5 92
b6 92
b7 92
b8 92
b9 92
ba 92
bb 92
bc 92
bd 92
be 92
bf 92
Hi,any news on this port? Thanks
I'd love to get Magic Lantern on my T3. I tried to use paypal and my bank account won't link up with it :/.
I may have a SUPER EARLY ALPHA for today. I'll probably disable some features that are 100% broken just to be on the safe side
Can you post link for that super alpha,Iwant to test on my T3? thanks!!!
Quote from: nanomad on August 13, 2012, 03:18:34 PM
I may have a SUPER EARLY ALPHA for today. I'll probably disable some features that are 100% broken just to be on the safe side
Sweet! Thank you so much :D
Quote from: nanomad on August 13, 2012, 03:18:34 PM
I may have a SUPER EARLY ALPHA for today. I'll probably disable some features that are 100% broken just to be on the safe side
i would go crazy if i had an alpha version of magic lantern for my t3 :) my best friend just got a t3i and i put magic lantern on his camera and i am so jealous.
Are you sharing the alpha version for the 1100D? I'd love to try it if it's possible :)
I'm having issues with the compiler at the moment. The source its ready but it won't compile and I can't figure out why
It keeps complaning about a menu txt file :o
damn. thats a shame. i would have loved to play with it while i was at the ocean tomorrow. at the very least to use the timelapse function
Well, maybe it's my setup. You can compile the 1100D from sources (get the 2.3 release source code, go into the platform/1100D.105 and type make). The autoexec.bin will work just fine but it will have some "useless" functions in it (which I had disabled in my code)
im sorry. you lost me at compile haha
so if i download everything from here http://nanomad.magiclantern.fm/1100D/ and then put them on my formatted sd card and update the firmware it will work?
the link to " this FIR" doesnt work. i think i need that
ok well i tried my best and it seemed to work except when its installing on my camera it says fonts.dat is not found. and im positive that its in the ml data folder
ok ive done it! but uhh.. how do i get into the magic lantern menu? haha. i can see the extra things when im in live view but ive pressed pretty much every button and i cant seem to get in to the ml menu
Lol, I forogot to update the first post. I wouldn't use that autoexec.bin :P
where can i get the better one? it seemed to work although i can only open the magic lantern menu in video
I've fixed the compiler issue (it wasn't the compiler actually, but my system using python 3 as default). The autoexec.bin should be coming shortly
awesome :)
Uploading ::)
Alpha 1: http://nanomad.magiclantern.fm/1100D/magiclantern-v2.3.1100D.Alpha1.zip
Use this FIR (https://bitbucket.org/hudson/magic-lantern/issue-attachment/1150/hudson/magic-lantern/1333128527.7/1150/ml-1100d-105.fir) (for 1100D 1.0.5) to enable the bootflag.
I DEMAND feedback if you try to run it.
Notes:
FPS override: Auto FPS selection doesn't work but you can increase the timerA to get the desired FPS manually
ML menu in Video mode can only be exited using half shutter press
As always, remember that is HIGHLY EXPERIMENTAL CODE , use it at your own risk. Read the Install.txt CAREFULLY and follow the optional/suggested steps too!
Alpha 2 HOTFIX: http://nanomad.magiclantern.fm/1100D/magiclantern-v2.3.1100D.Alpha2.zip
What's new:
- Fixed a typo in button detection
- Moved audio meters in audio menu
- Rebased against latest ML 2.4
Nanomad first thank for your hard work...I have shortly tested this alpha
1. ML menu is available only on P and movie mode(with short press on Av button)
2. In P mode-Expo if I change white balance from auto to any other number I cant reverse anymore to auto wb(or I dont know)
3. Movie mode-If I turn Exp.override to ON the shutter speed number are going somehow like 1.0.000 or 1/2941.2.3,I cant change to 1/50,1/60 etc
5.I can see the AUDIO tab but I cant go in
4.And for the end my camera crashed 3,4 times while the FPS override was ON,if I find the crash logs files I will send to you or upload here if u want :)
That was the bad side :)
From the options that I like are HDR is now in full potential because of working submenu button Q
Follow focus is really cool option also the rack focus
Font are much much clearer and also readable without glasses :)
PS: On image review zoom in function is not ok
I hope I helped :)
Update to my previous post... mow is alpha2 :)
ML menu now works on all modes exept on P
Camera is still crashing in Exp.override put to ON
Audio meters are now OK
Are you running the latest canon firmware?
Yes,1.0.5
Ok, I think I know what's wrong...
Get on irc.freenode.net channel #magiclantern so we can test quickier :P
1. ML menu is available only on P and movie mode(with short press on Av button) <- Fixed, sometimes you have to double tap the button ... especially in LV
2. In P mode-Expo if I change white balance from auto to any other number I cant reverse anymore to auto wb <- Just set AutoWB from Canon's Q menu :P
3. Movie mode-If I turn Exp.override to ON the shutter speed number are going somehow like 1.0.000 or 1/2941.2.3,I cant change to 1/50,1/60 etc <- ML Uses "exact" apertures. The LV bottom bar will display the corresponding "Canon" Aperture
5.I can see the AUDIO tab but I cant go in <- Fixed
4.And for the end my camera crashed 3,4 times while the FPS override was ON,if I find the crash logs files I will send to you or upload here if u want <- What were you changing? FPS override is super-hacked on the 1100D btw
*** Alpha 3 ***
http://nanomad.magiclantern.fm/1100D/magiclantern-v2.3.1100D.Alpha3.zip
** Beta 1 **
http://nanomad.magiclantern.fm/1100D/magiclantern-v2.3.1100D.Beta1.zip
Disabled stuff that caused many of the Err70:
- Defishing
- Magic Zoom
- Audio Remote Shot
- FPS Override (Compile it yourself if you want to fiddle with that since we have to figure out how to safely change it)
Known bugs:
- Exp. Override sometimes shows weird values
- Canon LV bottom bar sometimes messes up with ML bottom bar
I still have no idea why my camera is saying fonts.dat not found.. I did everything in the notes and still not installing.
[edit] Ok so it's working without having the fonts.dat found... I'll continue to test out.
There's an issue with the .fir, place it both in the root of the SD card and where is it now.
the timelapse feature works and thats all that i wanted :) also will we ever be able to change the aperture and shutter speed in video?
Yes we are able now,just put exp.override on and you have manual controls in video thanks to nanomad :)
oh thanks :)
Thanks nanomad...
Installed tonight and able to see ML menu/functions.
Will do some more testing tomorrow.
Great job nanomad and all the other developers who are helping out... now time for a test drive!
I've tested HDR bracketing and it seems that it is not working at Bata 1
It's working fine here, what options did you set?
I tested with several options:
Frames: 4
EV increment: 1EV
Sequence: 0 - +
ISO shifting: Off ->> Result: images with EV+5,+7... no image with EV-1
Frames: Autodetect
EV increment: 1EV
Sequence: 0 - +
ISO shifting: Off ->> Result: the camera stopped and i received a message like "HDR bracketing stopped"
Sorry - i tested yesterday late night and can't remember everything. I can provide detailed information later after work.
Can't reproduce, sorry :(
Make sure you didn't select only +++ by accident
edit: actually, try not using P mode if you were using that. It's a "known" bug. HDR works best in M mode
Thanks for the P mode info. I will test it once again in M mode later this evening.
Awsome work guys :) I hope you succsed in making a stable version.. :)
Quick question nanomad, are the features of exp.override supposed to be functional at all when I turn it to ON or Auto in any of the shooting modes, including movie mode? Bcuz it does not seem to be working at all for me in any mode certainly not movie mode, or am I doing something wrong???
Has anybody else had this issue?
Also sometimes when I press the display button on my camera to find out more about the exp.override feature (Very cool help function by the way) my T3 crashes.
I will keep you up on whats going on, thanks
T3 crashing on the help menu is due to the old memory allocator I think. The new one has some serious corruption issues and had to be disabled...
Exp override should work in movie mode only. You set it to auto (ON) then just hit set on ISO / Shutter / Aperture and use the dial to select your value. Sometimes it gives strange values but you can see the brightness change anyway...
In 1100D, the correct call is: AllocateMemory_do(*(int*)0x2B48, size);
This was found by decompiling AllocateMemory.
Thanks fellas, but how do I get to the ML menu in movie mode or how would one go about selecting Exp override for movie mode? Sorry if I seem a bit behind... Its Monday LOL
Press (or quickly double tap) the Av +/- button.
Quote from: a1ex on August 20, 2012, 05:58:12 PM
In 1100D, the correct call is: AllocateMemory_do(*(int*)0x2B48, size);
This was found by decompiling AllocateMemory.
Yep, found it too. Somehow the 60D address ended up in there :o
Bad news everyone >:(
- We don't have Mirror lockup available as a cfn
Maybe we can backport the two cfn from another camera, but it sounds hard :-\
** Beta 2 **
http://nanomad.magiclantern.fm/1100D/magiclantern-v2.3.1100D.Beta2.zip
Changelog
- Enabled the new memory allocation routine, less Err70 hopefully
- Fixed a bug in exp override that showed weird shutter values
- Fixed Focus stacking
- Fixed HTP in ML
- Disabled mirror lockup (not available on the 1100D)
FIXED: ML menu not closing with trash button while in Live View
Now is everything much stable compared to the previous version :)
Is possible to add some new functions which are missing in 1100d like some new resolution
for recording movie in 720x480?
Maybe to take that from other canon model because 1100d has only one 1280x720 :)
We did some tests but Canon code refused any resolution beside the native one >:(
The JPCore hacking thread may provide a new way but for now I'm focusing on making the FPS control work
I want from my 1100d to make markII :P,anyway thanks for you hard work ;)
Good news everyone, the latest revison has FPS override working again ;D
nanomad=mashine ;)
I just installed the beta 2..Now i just have to learn how to use it ;D
Well, beta 3 will be probably out by the end of the day ;)
Fixed: Bottom bar sometimes not redrawing correctly
you mean FPS override can go to 15 fps without problems??
Bottom bar sometimes not redrawing correctly? you mean you fixed the bug that the Canon LV Bar conflicts with the ML Bar?
Quote from: nanomad on August 22, 2012, 02:56:59 PM
Well, beta 3 will be probably out by the end of the day ;)
Fixed: Bottom bar sometimes not redrawing correctly
Awsome Nanomad ;D
Quote from: trettet on August 23, 2012, 03:00:00 AM
you mean FPS override can go to 15 fps without problems??
Bottom bar sometimes not redrawing correctly? you mean you fixed the bug that the Canon LV Bar conflicts with the ML Bar?
Yes to both. The only item that still conflicts in LV is the low battery indicator :-\
Is posible to add some functions on audio controls?
Only when we have pictures of the internal of the camera to discover the maker of the audio IC. We are pretty much in the same situation the 600D was not a long ago :(
On a side note, I may have just finished the 1100D port :o
My has stopped video after 10-20 sec of recording today 2 times >:(
I have manualy set shuter speed and aperture to 1/50 and F2.2 at 25 fps
I dont know why?
** RC1 is OUT **
http://nanomad.magiclantern.fm/1100D/magiclantern-v2.3.1100D.RC1.zip
Looks like audio meters stop working when recording, I've yet to figure out why.
I'll recharge my battery and look into those two issues in movie mode...
Quote from: wave on August 23, 2012, 05:44:52 PM
My has stopped video after 10-20 sec of recording today 2 times >:(
I have manualy set shuter speed and aperture to 1/50 and F2.2 at 25 fps
I dont know why?
try your sd card. it should be a class 10
Maybe it was a bug related to this:
[FIXED] Wrong Movie buffer address
New autoexec.bin to be installed on top of RC1 -> http://nanomad.magiclantern.fm/1100D/autoexec.bin
I've started the stability test, let's see if we are lucky :P
I have allready class 10 card so that not the reason :)
Well, I tested the video recording and it works here. Without more details I can't do much:/
Try the latest autoexec.bin and see if it happens again. If it does, check the color of the small box that tells the buffer level
Yeap,the recording is allmost fine thats hapened only two times for now,i wil test this new fir :-\
@ nanomad you're right, in movie my buffer meter is startin off green but it quickly turns red very fast and gives me a message about my recording stopping automatically. However, I began using ML with a class 6, 4mb SD card on the first Alpha test you released and had no prob with my photos or movie mode, but now with all the xtras like exp override and fps override etc, Im having this problem in movie mode. Even after you uploaded the new autoexec.bin. Am I having issues because I have a class 6 and I need a class 10 SD card?
Other than my movie mode rec stopping Im not having any audio meter issues. Im going to Wally World to pick up a class 10, 16mb SD card just in case LOL
If your buffer is turning red make sure that you didn't set a high CBR value. ML does not interfere with recording unless you override CBR or FPS
CALL FOR TESTERS
I feel like the 1100D port is almost ready for inclusion in the official unified tree. I'd like everyone to report every issue he has seen and how to reproduce it. I'll start:
- Stability test crashes (know bug, fix in progress. This affects all ML cameras)
- Audio meters stop working after going into play mode and before starting to record again (Needs pics of the internals of the 1100D to work out the audio section of ML)
My bug list:
Enabling under the shoot tab. Silent Shutter on burst under live view i've crashed twice but not on the third time.
thats pretty much all I can find so far
Upload the logs somewhere (they are both on the root and under ML/logs) :)
I'm not sure how to get it to save log when i am having the other problem but this happened when i tried to save cpu log.http://www.4shared.com/file/7nrsNEGp/LOG000.html (http://www.4shared.com/file/7nrsNEGp/LOG000.html)
[edit] here's the crash log.
ASSERT: FALSE
at Memory\Memory.c:188, task run_test
lv:0 mode:0
Magic Lantern version : v2.3.NEXT.2012Aug24.1100D105
Mercurial changeset : 7fcd1aa2b73c+ (unified) tip
Built on 2012-08-24 13:46:31 by
Free Memory : 347K + 353K
When the camera crashes a log is automatically created
The error in run_tests is known and a fix should be ready shortly. It's possible that you were experiencing the same memory allocation issue when shooting silent pics
bug i saw,
this happened to me twice, but after using fps override, it shows up an odd value, 3xxxx (i forgot those numbers, it starts from 3)when i want to change the value,. camera crashes,.
Confirmed
FPS override bug...
I set desired FPS 4
Optimize for: low light is default,when I set it to exact FPS camera blocked,I have to pull my battery out :(
Installed this today and it went smoothly and great. Had a few crashes as well as a few scares fearing that I had bricked my camera but all is good now. I have 7 crash logs to give you guys, I'll post them below.
Not sure if these will help at all at increasing stability but here they are. If I discover a way to make the camera crash thats replicable I'll be sure to post the steps and logs for it. For now I'll be happily testing away. Thanks for porting this, its really awesome.
Edit: removed monster post of semi- useless crash logs :D
Crashes alone are not enough without context ::)
I also installed the RC on my canon 1100d and I've had a few crashes. I will upload the logs, but none of them were replicable. The main problem I had is that it lost all my settings 3 times yesterday and I don't know why that happened.
ASSERT: 0
at Evf\EvfState.c:1190, task Evf
lv:1 mode:20
Magic Lantern version : v2.3.NEXT.2012Aug23.1100D105
Mercurial changeset : cd03042485bd+ (unified) tip
Built on 2012-08-23 15:50:45 by
[email protected].
Free Memory : 347K + 219K
ASSERT: FALSE
at Memory\Memory.c:188, task menu_redraw_task
lv:0 mode:2
Magic Lantern version : v2.3.NEXT.2012Aug23.1100D105
Mercurial changeset : cd03042485bd+ (unified) tip
Built on 2012-08-23 15:50:45 by
[email protected].
Free Memory : 345K + 187K
ASSERT: FALSE
at Memory\Memory.c:188, task run_test
lv:0 mode:2
Magic Lantern version : v2.3.NEXT.2012Aug23.1100D105
Mercurial changeset : cd03042485bd+ (unified) tip
Built on 2012-08-23 15:50:45 by
[email protected].
Free Memory : 347K + 302K
ASSERT: FALSE
at Memory\Memory.c:188, task menu_redraw_task
lv:0 mode:3
Magic Lantern version : v2.3.NEXT.2012Aug23.1100D105
Mercurial changeset : cd03042485bd+ (unified) tip
Built on 2012-08-23 15:50:45 by
[email protected].
Free Memory : 342K + 193K
I hope these will be helpful.
Nailed one of the issues as a possible buffer overflow in ML top bar. I'll try to fix it ASAP and push a release. It should fix FPS ovverride
** RC2 is out **
http://nanomad.magiclantern.fm/1100D/magiclantern-v2.3.1100D.RC2.zip
Known issues: ML still crashes when running stability tests
Shameless title bump :P
Nanomad there is one "small" issue
When I put my cable and turn ON the camera when connecting to PC,EOS utility refuse to start
But if I turn On camera first and then put my cable is OK,before it was not the case
Before when? With another ML build? Or without ML?
I never touched USB code so it shouldn't be anything I did :o
without ML :)
Yeah confirmed :o
** Please don't use RC2 for now, I've removed the download **
There's something wrong with it that needs further investigation
ASSERT: FALSE
at Memory\Memory.c:188, task MovieRecorder
lv:1 mode:20
Magic Lantern version : v2.3.NEXT.2012Aug27.1100D105
Mercurial changeset : eadcc24c289b (unified) tip
Built on 2012-08-27 17:53:44 by nanomad@camera-gio.
Free Memory : 346K + 288K
Thanks
link does not work!>>>>>>>>>>>> http://nanomad.magiclantern.fm/1100D/magiclantern-v2.3.1100D.RC2.zip
Quote from: nanomad on August 27, 2012, 07:48:31 PM
** Please don't use RC2 for now, I've removed the download **
There's something wrong with it that needs further investigation
^
** RC2.1 is out **
http://nanomad.magiclantern.fm/1100D/magiclantern-v2.3.1100D.RC2.1.zip
@nanomad cool, is it just me or did I see an option for Kelvin WB or WB.override or Kelvin exp.override in one of the ML builds that was posted for the 1100D? I apologize that I cant remember
ASSERT: FALSE
at Memory\Memory.c:188, task menu_redraw_task
lv:1 mode:20
Magic Lantern version : v2.3.NEXT.2012Aug27.1100D105
Mercurial changeset : eadcc24c289b+ (unified) tip
Built on 2012-08-27 19:06:21 by nanomad@camera-gio.
Free Memory : 347K + 183K
Low memory >:(
I guess we'll have to live with that ???
@nanomad, Ok Im using RC 2 and something weird just happened :o ... FPS override just completely disappeared from the ML menu. And it did not create a crash log. And Im still having buffering issues when I change the FPS in movie mode even after I did like u said and I left the bit rate at default
You hid the menu options ::)
Press the canon menu button while in ML menu to unhide them
As for the buffer issues, I can't do much. Either your card is too slow or you need to disable stuff from live view (like the graphs)
To whoever asked about the bottom bar, just press DISP a couple of times and the canon bar will go away (it will flash briefly when pressing half shutter)
What is maximum Fps number possible with 1100d with fps override?
I can set it to 65 but it is true or false?
hey guys, how do you take a 24p shot? only 25p and 30p is supported for this cam right?
The maximum FPS is 30 (or 25 if you're in 25p), of course. And you can go to 24, just use FPS override with Optimize for: exact FPS
using fps override disables the sounds right? ok, got it, thanks bud., keep up the good work, sorry cant help about programming, im 15 years old and planning to go programming in college :)) sounds cool
There's hope for audio with FPS override, or so i read
Damn >:( that mean that is not hackable to go to 60 fps ;) is good for slow motion :)
The camera simply crashes when resolution is changed, i didn't try higher FPS tough. Maybe it's worth a shot.
Oh, and there's no way we can record at full hd or lower res, the encoder is hardcoded at 720p
I took this yesterday with ML and exp override on
https://vimeo.com/48335401
Look how much I need 60fps :P
@nanomad, Thanks
@wave, Its still a nice video 8)
I'm working on a crazy project, more news tomorrow :o
Quote from: nanomad on August 28, 2012, 06:21:46 PM
I'm working on a crazy project, more news tomorrow :o
such a tease :P
It didn't work out very well :(
Anyway, I've enabled quick rate/protect images in play mode (use the LV key).
About quick shortcuts in Live View, what button do you prefer?
@nanomad is quick rate when we select how many stars to give an image/movie ??? ... Blame it on Thursday LOL, and maybe Q for the shortcuts :P otherwise its up to you, you've been on point on everything as usual 8)
Yep it is that. It is fully customizable so you can select wheter the LV button in play mode will:
- Rate the image (one star per click, then goes back to 0)
- Protect the image to avoid deletion (I prefer this one actually)
For now I ruled out Q since it's the only way to access canon's AF modes with LV. I'll try to see if any of the buttons has a PRESS/UNPRESS event so that we can connect shortcuts enable to a long press
Cool! 8) I agree, the protect image option sounds like a winner. I wonder what the other members think...
Oh, btw I just realized that ML reading of the exposure compensation value is screwed up :-\
Too bad there's no documentation on how to find the correct memory location
I would like to add more room for user picture styles,maybe on the place where are image effects in ML?
And one bug maybe is that hdr bracketing in autodetect mode is not working properly ;)
:o....... Hey nanomad, whats the latest on that crazy project you've been workin on
Come on give us a hint LOL 8)
We are waiting for that crazy project :P
IT was about porting other cameras's features to the 1100D. But it's on hold since the 1100D is the only camera I've got and I cannot risk bricking it (I got real close twice)
Right on! I hear ya loud and clear. But it sounds very awesome.
Sneak peak of the upcoming "Smooth ISO" feature.
http://nanomad.magiclantern.fm/1100D/samples/ml_iris_pull_1100D.mp4
Say hello to iris pulling without HDR video drawbacks
I cant find on wiki what is iris pull ;-)
Is that something related to continuos focus?
Or is this stupid question :-)
It is related to smooth ISO adjustment while recording so that you can smoothly transition from a bright to a dark scene and vice-versa (like when entering an house) . It is something that canon firmware already does if you leave everything on auto
Canon EOS 1100D Time Lapse
http://www.youtube.com/watch?v=2dfEuZTJ5bQ
Here (http://youtu.be/aPG7FvR-ioQ/)'s my T3 time lapse I shot the night RC 2 came out. That auto iris feature for videos sure will be nice ;)
Hey guys, Jon here.
Totally new to the forum, not new to Canon DSLR and have been using this RC for a few weeks now. I am also a long time video student who has a pretty good background so far (if I do say so myself.)
I wanted to join in and test features if still need but, I am having issues and confusion about certain features.
First of, does everyone else get the "purple lines" on screen when dropping down below ISO200 in video mode?
Second, is there any possible way to do 60FPS, or 48? I read the comments above but I just want to see/figure out if I can help in achieving this goal.
Thanks,
JM
Oh, we are showing out timelapses shot with the t3 now? i shot this when i had to compile magic lantern for myself for the t3. All thanks to nanomad :) http://youtu.be/-PGuaX3Mi3U
I just noticed the purple thing, I'll have a look at it ASAP
is it normal for the whites to have a purplish tint if you have a Digital ISO like ISO's 25 to 75??
Yes, you need to recover them in post-processing.
Hi Folks
Lee here, totally new to this forum, I have the Cannon 1100d (bought in UK) installing 2.3 will not brick camera, and i CAN take off if i wnated to (i would suppose i just format card?) thanks in advance
Lee, Scotland
Quote from: leeb9972 on September 09, 2012, 05:29:03 PM
Hi Folks
Lee here, totally new to this forum, I have the Cannon 1100d (bought in UK) installing 2.3 will not brick camera, and i CAN take off if i wnated to (i would suppose i just format card?) thanks in advance
Lee, Scotland
As I understand it magic lantern launches along side canons firmware every time you start up the camera. Magic lantern doesn't replace canon's firmware in the memory of the camera so it relatively hard to brick your camera. The most dangerous part is upgrading Canon's firmware to the current version which really isn't very hard. If you want to remove magic lantern just format the card from inside the camera. If anything watch some tutorials and read up on the wiki abit.
Keep in mind that the 1100D is still experimental so there's the possibility of actually screwing up things (although I've yet to experience it)
I installed RC 2.1 the other day, and I noticed that when I was recording, my exposure was changing at a constant rate, causing the movie to brighten and darken. Exposure override was set to on (auto), and I also had the same result in just on. I had my expsoure set within ML...but it seemed like the canon auto expsoure kept trying to override it. Any help is appreciated.
The easiest way is to actually delete ML config and try to reproduce the issue...you probably had HDR video on by the sound of it
hdr video was not on...I'll try and record a video and show you what I'm talking about. It seems like my shutter angle changes by real small increments, like if i set it in the ML menu to 56.5, it'll change between 56.5 and 56.3 for a couple seconds, then calm down.
Uhm, yes. Please upload a video
There's a shutter lock option in the settings, see if it helps you
I wonder is it normal whenever u took a photo/video, when return to the screen, those focusing peaking/magic zoom
goes hey-wired, this is not normal rite? wonder if this bug has been reported..
I actually need turn off turn on live view to get back normal.
I know it. I'm trying to find the culprit but it takes time
Keep up the gud work!! I know it takes take, feel bad tat I haven't got the knowledge to help out, I'll be patient.. peace!!
Thanks for your work nanomad ! Is there any chance we can get 1080p recording on the 1100d ?
there's hope but my tests so far resulted in semi bricks of the camera and are currently on hold
how bout 60p natively? is it possible?
Everything depends on how cheap canon wanted to be. The 1100D is a dumbed down 600D so everything that works there *should* work here minus hardware differences
So Nanomad we can soon expect from you 60fps on 1100d right? :P
You wish :P
Hey, Bug report.
The Magic Zoom is bugging out after a picture is taken. it freezes the little zoom box and wont work until restart.
The settings are:
Trigger mode : ZoomIn (+)
Size : Medium
Position : NorthWest
Magnification : 2:1
Focus Confirm : SplitScreen
Second bug/ problem is the Overlay.
the overlay gets slightly fucked up by the standard Fstops iso shutter speed all of those just randomly overlaps the histogram waveform and those reedouts from the bottom of the screen.
The first one is new, the second one it's not a bug, it's a stupid feature of canon's firmware .... even with "no overlays" it insists on drawing a couple of things
so wait, no 60 fps?? awww,. sad
Hello guys, great work!
I can't seem to find but what can work on the T3 with the latest (RC2) version for video?
Manual exposure for ISO, aperture and shutter?
FPS Control? Like up to 35 FPS and as slow as 5FPS?
Other resolutions? 1920x108030/24FPS?
Higher bitrate? I think the top is 40Mbps?
External mic via installing it?
Manual video exposure: Working
FPS Control? You can only go down
Other resolutions? Nope. ML never did that
Higher bitrate? Sure, as long as you've got a fast SD card
External Mic? No need for ML to do that, just open the camera and solder a female 3.5mm female Jack to the current mic wires.
Hey, I was using the cam today and I noticed that wwen everything went black small blue dots appeared and now they and small red dots keep glitch in on the screen
(red dots aren't the. ZEbra these dots are somthing else.)
Oh and btw is there in any way I can help this port to get integrated faster
?
You've got focus peaking enabled.
And if you can write C code you can help me fixing bugs
Sir i am dying for final version of Magic Lantern for canon 1100D. Sir i have Canon 1100D. I want to install magic latern on it but i am watching daily that you all genius are going step forward day by day in magic lantern hack issues. after RC2 release there are so many modifications have done so far. So where i can get a download link of latest magic lantern for 1100D?
could you release RC3 for those who are waiting for your final modifications in magic lantern?
please send me a download link for latest magic lantern for 1100D.
thank you very much all of you and i pray for you.
good luck
artstylish
unfortunately the rc2 is the current state of the art build of ml for our camera. I'm a bit busy with exams right now and i couldn't work on any bug fixes...
wow , you're a student? haha me too, high school :)) anyways i got that bug about video flickering, a very slow one though, i know its not about the shutter speed. this happens rarely though, but can be a problem.
Quote from: nanomad on September 18, 2012, 10:50:35 PM
Manual video exposure: Working (...)
Thanks, Nanomad! The thing is that I might get a T3 or a T1i and I wanna know which is better for video with ML, definitely no 1080p is a con for the T3, the T1i has 1080 but then max at 20FPS, I've read somewhere else in the forum that it can't be modified but at least I thought it was possible to tweak the codec to just add 4 more frames to make it 24FPS like with the 600D/60D at 35 FPS or as fast as the latter cameras. Do you think it might be possible in the future? Or nobody's working on it.
I've got no idea, honestly.
But if you are into videos I suggest to save some money and go for the 550D or the 600D instead of the 1100D
Cool, nanomad, thanks!
i would recommend getting a refurbished one from canon. you save a couple hundred bucks
I would like to say thank you to nanomad and the other people who made this 1100D ML version possible !
I have a few questions :
I know that the 1100d doesn't have "spot metering" option , is it a functionnality added by Magic lantern ?
Does magic lantern add control of the Bit Rate and in fact what is the maxium reachable on the 1100D with a fast SD card like a Class 10 ?
Thanks a lot and keep up this great work !
Bitrate control works, but the maximum depends on YOUR card.
Spot metering is missing. I'd love to enable it (I've got a 600D but I couldn't identify it in the firmware) but I'm still fighting with liveview image corruption....
Thank you nanomad :)
Yes spot metering is a big miss , if you can do it it will be a major add for the T3 8)
For the Bitrate ok i will test it for myself when my T3 will come .
And what is the problem with the liveview image corruption ?
I forgot to ask if there is a list of all options that work on the 1100d ?
The beauty of the T3 is that everything, except audio controls, is working.
The "liveview corruptions" happens when you have zebras (of focus peaking) enabled and you take a shot. After that the image needs to be cleaned up (e.g. by pressing display)
Can you check the value of DLG_SIGNATURE? (print it with a NotifyBox from zebra.c where it's referenced).
Quote from: nanomad on September 23, 2012, 07:42:32 PM
The beauty of the T3 is that everything, except audio controls, is working.
Sounds good ! but so spot metering is another thing that doesn't work , right ?
Quote from: nanomad on September 23, 2012, 07:42:32 PM
The "liveview corruptions" happens when you have zebras (of focus peaking) enabled and you take a shot. After that the image needs to be cleaned up (e.g. by pressing display)
Thanks for your answer and your great work :)
Dumping it here since it may come handy later on...
Dry> memmap
== ITCM ==
00000000 : DRY_VECTOR_ADDR
000004b0 : DRY_HANDLER_ADDR
0x00000214(532)
000006c4 : DRY_HANDLER_END_ADDR
000006c4 : DRY_IRQ_STACK_START
000006c4 : DRY_RESET_STACK_START
0x0000093c(2364)
00001000 : DRY_IRQ_STACK
00001000 : DRY_RESET_STACK
00001000 : ITCM_END_ADDR
== DTCM ==
400006F8 : DRY_VECTOR_FUNC
0x00000400(1024)
40000AF8 : DRY_VECTOR_ARG
0x00000400(1024)
40001000 : DTCM_END_ADDR
== ROM ==
FF810000 : text start
0x004106d4(4261588)
FF6DF858 : romdata start
0x00014BD0(84944)
FF6F4428 : romdata end
== DRAM ==
00001900 : data start
0x00014BD0(84944)
000164D0 : bss start
0x00067FA4(425892)
0007E474 : heap start
0x000854E4(546020)
00103958 : DRY_HEAP_END
00103958 : DRY_SYS_OBJS_START
0x000072A8(29352)
0010AC00 : DRY_SYS_MEM_START
0x00104000(1064960)
0020EC00 : DRY_ERREX_STACK_START
0x00000400(1024)
0020F000 : DRY_ERREX_STACK
0020F000 : DRY_EXCEP_STACK_START
0x00001000(4096)
00210000 : DRY_EXCEP_STACK
Uhm even after fixing the DLG_ the screen is kinda trashed. To me it looks like it's writing in the wrong vram buffer.
It happens with peaking but not zebras btw
Can you post some screenshots?
No need to, I've fixed it :P
Just used the 5D3 way of getting the HD buffers and it works like a charm
That method is so clean we should use it as a default IMHO
RC3 is OUT
http://nanomad.magiclantern.fm/1100D/magiclantern-v2.3.1100D.RC3.zip
What's new:
- Quite a lot of stuff that comes from bleeding edge ML code
- Fixed live view corruption
- Enabled compiler optimizations
Since this build has optimizations enabled I'd like you to test it properly and report any bugs, even the most insignificant ones.
About bit-rate: I've noticed that the 1100D buffers struggles to keep up with modest BR with audio on so I suggest you use an external source
hello,
I have canon eos1100d and i'm trying to install this RC3, but somehow when I try to update my firmware it shows me black screen and I have to remove the battery to restart. And I can't go any further. What could be the problem? Thank you
Uhm, that's a first :o
What firmware do you have on your camera? You need to update to canon's 1.0.5 first then use the "ML updater"
Nanomad for now is much better all about display problems
Ok, I've found 2 bugs
When your in live view mode while in a picture taking setting, if you try to change any settings in the magic lantern menu, they won't change and the menu closes.
Set camera to manual mode > click live view button > press av button to go to magic lantern menu > press ok on a setting > menu closes and setting isn't changed.
The second I haven't been able to duplicate reliably yet, but the screen likes to tint colors.
i can't reproduce any of them...
check that all files are not read only and make a video of the issues
huh thats odd, I formatted my card, copied over all the ml files again from rc3, and made sure the files/folder were not read only, but I still get the glitch.
Heres a video of it.
http://www.youtube.com/watch?v=34Ike5gQDJ0 (http://www.youtube.com/watch?v=34Ike5gQDJ0)
If you can mention the potential risks and current features that are working/supposed to be working I will be willing to help test.
The only glitch is defishing not working because I forgot to disable it. Everything else should work
About the video: weird, it doesn't do that here. I'll upload a test version without the warning screen...you may have stumbled upon a bug in it
Do you have any function assigned to SET?
It's not caused by the warning screen, that one goes away after first key press.
Defishing should work if you use shoot_malloc instead of AllocateMemory. Need to find out how to free it though.
Quote from: Grzld on September 26, 2012, 02:05:45 AM
huh thats odd, I formatted my card, copied over all the ml files again from rc3, and made sure the files/folder were not read only, but I still get the glitch.
Heres a video of it.
http://www.youtube.com/watch?v=34Ike5gQDJ0 (http://www.youtube.com/watch?v=34Ike5gQDJ0)
Did you clear the settings in camera before install ML?
I had depth of field preview assigned to the set button, disabling that cleared up the issue. ::)
New bug: focus peaking is off by a few pixels in video mode. Probably a bug in one of the coordinates transformations routines of ML (HD2LV?)
Check if the HD buffer includes the 16:9 bars or not.
Fixed the HQ silent pics in movie mode, we can grab (c)raw 1280x720 frames.
Too bad they are too big to be saved to card as a video stream otherwise we could do decent fullHD in post-processing. Here's how a 720p craw file looks like when upscaled to 1080p
http://i.imgur.com/IX06W.jpg (http://i.imgur.com/IX06W.jpg)
Let's hope in mjpeg 422 :P
Nice to see the 1100D is keeping up with the development.
Nice to see you're born in my same region as well :D
Lol :P
So, a1ex managed to fix the bug that was causing weird images with low ISO in movie mode (it was a bug in ML code that affected all cameras)
I'll go thorugh all the posts again but the only thing that should be left is the damn focus peaking while on standby in movie mode....
Quote from: nanomad on September 18, 2012, 10:50:35 PM
Manual video exposure: Working
FPS Control? You can only go down
Other resolutions? Nope. ML never did that
Higher bitrate? Sure, as long as you've got a fast SD card
External Mic? No need for ML to do that, just open the camera and solder a female 3.5mm female Jack to the current mic wires.
I just bought a Canon T3 and I was sad that there wasn't any manual settings for video. I installed ML with no problems but I still haven't figured out how to set manual video exposure. I tried finding a tutorial, but so far I haven't had any luck.
Pretty much treading on unfamiliar ground, can anyone help me out?
Open ML menu, go to exposure set manual exposure to Auto then change the settings from the same menu
Quote from: nanomad on September 29, 2012, 04:39:32 PM
Open ML menu, go to exposure set manual exposure to Auto then change the settings from the same menu
I read that on the user guide on the site too, but so far, every time i set the settings on the ML menu and switch to movie mode, the settings don't apply and the exposure settings are still automatic.
am i doing something wrong? or is it some kind of bug with the RC3 firmware
Did you clear camera settings before installing? You may have the SET button assigned to something else, if so, change it to "no function"
You guys are awesome. Saw the post about the low iso movie mode fix. gonna try it out! Thanks for all all the hard work!
So this is the issue I am having with any ISO below 200, in movie mode of course. Is there any reason it should do this? It happens whether GlobalDraw is on or off, and focus peaking/zebras etc.
http://youtu.be/rm12_HGqBu0
Hit the Q button in the iso option and turn off Highlight tone priority if you want to use ISO below 200.
Alex fixed this yesterday night so it's not in the 1100D build yet (I'd like to fix the offset of focus peaking while in movie standby first)
Wow, I had totally forgotten about HTP, sorry my bad! Thanks, I really appreciate that.
If there is anything you guys would like me to do, let me know.
Jon
Yes, test every single function and report any bugs I've missed :P
tnx for the help nanomad, i was able to get the manual settings to work in video. however a new issue sprang up...
i read earlier the someone's iso started to jump from high to low while in video mode. I was wondering if you encountered this problem too.
i've tried clearing settings and reinstalling ML. I have shutter lock on and HDR video off, but the iso still fluctuates.
Can you make a video?
Quote from: nanomad on September 30, 2012, 12:33:23 PM
Can you make a video?
heres a vid i uploaded concerning the issue
http://www.youtube.com/watch?v=Lo77dM6yoqo&feature=youtu.be (http://www.youtube.com/watch?v=Lo77dM6yoqo&feature=youtu.be)
Ok thanks, can you post the expo override settings you used?
Quote from: nanomad on September 30, 2012, 04:15:48 PM
Ok thanks, can you post the expo override settings you used?
ISO 1600
Shutter 1/61
Aperture f/16
Exp. Override set to Auto
Do you have Highlight tone priority on?
edit: I, again, can't reproduce it.... there must be some option I'm missing. Try deleting ML settings too (ML/settings folder)
edit: interesting, image buffer is 720x214 in movie mode, HD is 1280x720 fixed
And I've fixed the last reproducible issue, focus peaking in movie mode!!!!
Quote from: nanomad on September 30, 2012, 04:29:24 PM
Do you have Highlight tone priority on?
edit: I, again, can't reproduce it.... there must be some option I'm missing. Try deleting ML settings too (ML/settings folder)
i deleted ML settings, and i tried with highlight tone priority on and off, still get the fluctuating iso : /
Right now i'm trying to see what sets it off. so far the way i can get it to sure fire fluctuate is to put some sort of light source or bright area dead center. sometimes it does it, sometimes it don't. perhaps it depends on my exposure settings.
Quote from: nanomad on September 30, 2012, 04:40:06 PM
edit: interesting, image buffer is 720x214 in movie mode, HD is 1280x720 fixed
And I've fixed the last reproducible issue, focus peaking in movie mode!!!!
woooooh, yay., that was the problem i was talking about before, thanks nanomad. GREAT job!
and the focus peaking is fixed. sooooo, when is the next release ?and how do you use the smooth iso transition.?
I'm waiting for kapueblo to reproduce his issue. Then there will probably be one last RC.
To use smooth exposure you just need to set it to on and then it will kick in every time you change any of the exposure paramters in ML menu (aperture, speed or ISO)
Hello, sorry for my English.
Today install ML, all OK, thank you.
Just one question, some words are very small and low quality, is solved?
What else is there to improve?
Thanks for your great work.
Thank you, guys for all of your hard work. I, like many others, learned to live with the capped potential of the T3. Now my camera has new life, haha.
One question, though. I see that in the movie mode, Canon's Digital Gain can be pushed up one more stop of ISO (12800) instead of the native of just 6400.
Is this just exclusive to movie mode or can you make that available for the photo modes as well?
Also is the HDR bracketing not working for everyone? When i try to use it the camera starts cycling through menus and taking pictures on its own and i have to do a battery pull.
Quote from: kainpower on October 04, 2012, 02:38:28 AM
Just one question, some words are very small and low quality, is solved?
Unfortunately, no. The small fonts is due to the very low (and weird) screen resolution
Quote from: leviathan on October 04, 2012, 03:36:49 AM
Thank you, guys for all of your hard work. I, like many others, learned to live with the capped potential of the T3. Now my camera has One question, though. I see that in the movie mode, Canon's Digital Gain can be pushed up one more stop of ISO (12800) instead of the native of just 6400.
Is this just exclusive to movie mode or can you make that available for the photo modes as well?
Also is the HDR bracketing not working for everyone? When i try to use it the camera starts cycling through menus and taking pictures on its own and i have to do a battery pull.
Very high ISO is only available in movie mode since we are digitally pushing the ISO of the movie buffer.
HDR bracketing works fine here. Try clearing canon's settings, you may have something that interferes with it
Hi everybody,
I installed the RC3 on my 1100D monday and start testing it. It's my first try on ML so I'm quite uncomfortable with it, and maybe some bugs are not ...
I followed the install procedure in the zip file, and reset camera settings.
1) Strange value (-2147483) in FPS override submenu
http://imgur.com/a/V4huY#0 (http://imgur.com/a/V4huY#0)
2) Bottom help said Wheel to change value, but wheel change the menu section (Movie / Image / Display ...)
http://i.imgur.com/axrNJ.jpg (http://i.imgur.com/axrNJ.jpg)
3) In expo menu, the LV display values can't be changed
http://imgur.com/a/V4huY#2 (http://imgur.com/a/V4huY#2)
4) Despite Arrow/SET Shorcuts options set as in first image (defaults), when in video mode the up/down keys are moving the AF white rectangle, so I can't edit settings in LV mode.
http://imgur.com/a/V4huY#3 (http://imgur.com/a/V4huY#3)
http://imgur.com/a/V4huY#4 (http://imgur.com/a/V4huY#4)
5) Despite ISO set to 320, LV report a record in 6400 (auto I think). When I go back to M mode to check if value was saved, it still shows 320.
http://imgur.com/a/V4huY#5 (http://imgur.com/a/V4huY#5)
To access ML Menu I switch to M mode on the camera, and go back to video mode to see if values are set. Is it the nice way ? Are setting kept for each mode or shared ?
6) Several crash in help menu navigation, can't remember the error, but something like 70. Will try to find a way to reproduce.
7) Where I activated Exp. Override and staying on the menu entry, the value sometimes change in an strange way, showed 0.0000 and other values I don't remember. I'll try do get it repoduced and capture it.
Thanks for your help.
Thanks for reporting
1) Definitely a bug, probably related to the fact that the 1100D has a strange internal timer
2) That's because we don't have the back wheel :P... I'll remove it since it's useless
3) Somehow it shows the 3 buttons while it should only show one fixed value, I'll probably hide that menu option as it's useless on this camera
4) This is an open discussion. The camera lacks a free physical button to enable shortcuts....if you have any ideas please say so.
4) Checking it
6) The camera has a low amount of free memory so the help function isn't really stable.
7) Checking it
2) refers to the top wheel; the back wheel is always used for up/down navigation. The top wheel moves left/right normally, but in submenus and in the edit mode it changes current value.
Whoo, faaaast ! : )
I edited my 5), maybe I'm using it the wrong way.
4) 5dII 50d can manage long pressure on joystick. Should use this feature on the set button for exemple.
I always configure my video settings in video mode, I think you should do the same. And make sure you have exposure override to ON or Auto (otherwise it won't work on the 1100D)
Quote from: nanomad on October 02, 2012, 03:45:44 PM
I'm waiting for kapueblo to reproduce his issue. Then there will probably be one last RC.
hey nanomad. I've been tinkering around with the settings to see what causes the glitch, but so far no luck :(
it may be something in my settings, but i'm not sure what. I've already tried clearing my settings on both my camera and ML, but still no luck.
may I ask how you what are your settings on your 1100d? maybe if i set it to your settings the problem might disappear
- Canon + ML settings to default
- HTP Off
- ALO On
- High Speed Noise Reduction normal
- Auto ISO max 3200
- Exposure override Auto(ON)
- Smooth exposure on
That should be it
Hello nanomad. when the camera is in LiveView (video or photo), it is difficult to enter the menu of ML, AV must be pressed repeatedly to enter ML menu. But in viewfinder mode, always enters the ML menu OK.
thanks
Yes, it's a known issue. Guessing the state of the on-screen "AV compensation icon" is kinda hard and you have to press the button a couple of times to make it register properly
As a happy user of ML2.3 on my 50D I have RC3 running on my 1100D for two days. I'll report my findings and error logs here.
Thanks :)
When trying to change FPS I cannot change the values for the timers
Did you enable FPS override?
Hello nanomad. For when RC4. We dream of a final version?.
Quote from: nanomad on October 10, 2012, 06:38:47 PM
Did you enable FPS override?
Yes I did and pressed Q to bring up the submenu for it, and neither the timer values or the actual fps value change from 0, so when I close it the fps override value stays at 0
Weird, can you upload a video? (from the power up to the moment you try to change values)
Yesterday ml/1100D crashed. The log can be found here:
http://www24.zippyshare.com/v/97654330/file.html
I do not know which settings were active or what I was doing.
Sorry for that. I'll pay more attention next time.
Not really helpful, isn't it ::)
There are shorter (and more helpful) logs under ML/LOGS directory.
Maybe they should be moved back to root dir, so user notices them easier?
Canon logs (created with Canon code) can't be moved easily.
Minor (unimportant) issue: shutter count is not updated after taking a picture.
Turning the camera off and on shows the new shutter count.
Only Canon can fix that one.
You can now use nightly builds (http://nanomad.magiclantern.fm/nightly/) to evaluate the status of the port. You can keep using this thread to report bugs related to the 1100D if you want (but use the general bug reports area if you think it affects multiple models). I'll keep updating this thread every time me or someone else makes a 1100D-related change
Uhm, strange issue... the camera LCD stays off (and doesn't respond to any button press except for SHUTTER) if I take a picture outside of liveview...
Can anyone confirm?
It's my "improved" AV press detection code.... :/
I've managed to fix it :)
nanomad good afternoon. In P mode, you can not compensate the exposure. AV press eventhough faster, always enters the ML menu.
You need to HOLD the av button, not press it (press = ML menu, hold = exp. comp.), just like it works with canon's firmware
But in mode P fail
Oh wait, you are running the latest RC, right?
Yeah, it's broken in that version. Try the latest "nightly" build from http://nanomad.magiclantern.fm/nightly
Now, with the nightly, it works correctly.
thanks ;)
Installed the nightly build (2012Oct11).
Prefs --> Image review settings... --> SET+MainDial: Compare Images.
Take a few pictures. View a picture then press the SET button and turn the wheel. The screen turns green. The second time I tried the screen turns 'noisy'.
Prefs --> Image review settings... --> SET+MainDial: Exposure Fusion.
View a picture then press SET and turn the wheel. The screen turns whitewith a 'noisy' bottom.
Exposure Adjust works fine.
Enter ML menu, go to Help, scroll down to "Complete user guide" and press the Q-button. A pop-up menu appears and the ML menu freezes. Press LV or Zoom-in or shutter release to escape.
If the ML menu is frozen and you press the Menu button the camera is completely locked. Remove and re-insert the battery.
I haven't checked if this was the case in the RC3 release.
Quote from: Canon Amateur on October 11, 2012, 11:33:32 PM
Installed the nightly build (2012Oct11).
Prefs --> Image review settings... --> SET+MainDial: Compare Images.
Take a few pictures. View a picture then press the SET button and turn the wheel. The screen turns green. The second time I tried the screen turns 'noisy'.
Prefs --> Image review settings... --> SET+MainDial: Exposure Fusion.
View a picture then press SET and turn the wheel. The screen turns whitewith a 'noisy' bottom.
Exposure Adjust works fine.
Enter ML menu, go to Help, scroll down to "Complete user guide" and press the Q-button. A pop-up menu appears and the ML menu freezes. Press LV or Zoom-in or shutter release to escape.
If the ML menu is frozen and you press the Menu button the camera is completely locked. Remove and re-insert the battery.
I haven't checked if this was the case in the RC3 release.
Ops, not the same thing indeed. Sorry...
Thanks for reporting. The user guide thing it's not a bug but it's related to the fact that the nightly builds are missing the documentation files
I have no issues on my 50D with the official ML 2.3 release.
Haven't tried this nightly build on my 50D.
I will try that tomorrow.
Quote from: Canon Amateur on October 11, 2012, 11:45:23 PM
I have no issues on my 50D with the official ML 2.3 release.
Haven't tried this nightly build on my 50D.
I will try that tomorrow.
2.3 official is good, the issue shows up with the latest changes only.
Anyway, enough OT talking.... looks like the hardcoded HD buffer values on the 1100D are wrong :)
Should be fixed in rev 4fda002
The help problem is from docs not being compiled => empty menuindexentries.h generated.
Here's a good copy of this file: http://a1ex.magiclantern.fm/bleeding-edge/menuindexentries.h
and then modify menuindex.py to leave the autogenerated source file unchanged.
I have serious issue with this nightly build,when I take a picture camera is totaly off,only solution is pulling battery out
Everything is on default,i have clean camera settings before install of ML etc
Which nightly build are you talking about? I thought I fixed that bug :/
This from Oct 11
Try the latest Oct 12 build (http://nanomad.magiclantern.fm/nightly/2012-10-12-3aac88fc7992/magiclantern-v2.3.NEXT.2012Oct12.60D.550D.600D.50D.500D.5D2.1100D.zip): yesterday I built several nightly builds and you may have downloaded one of the old ones before I took them offline
Now is OK :)
great ;D
Copied the nightly build (2012Oct13) over the previous one (2012Oct11).
Switched on the camera and the camera crashed.
I tried to make a picture of the screen containing a message, but by the time I had my camera the message was gone.
The logfile is saved here:
http://www41.zippyshare.com/v/12066098/file.html
FWIW: camera; Tv, 1/1000, ISO400, One Shot, RAW, Cont. Shooting, Eval metering, 18-135 IS lens.
Switched off and switched on the camera and everything works fine.
Tested the "Compare Images" and "Exposure Fusion" functions and they work o.k.
Great work.
I will test the other functions in the coming days.
Keep up the good work !!
Can you post the log from ML/LOGS directory?
Quote from: a1ex on October 13, 2012, 08:42:25 PM
Can you post the log from ML/LOGS directory?
Here you go:
-----------------------------------------------
ASSERT: FALSE
at Memory\Memory.c:188, task MetaCtg
lv:0 mode:2
Magic Lantern version : v2.3.NEXT.2012Oct13.1100D105
Mercurial changeset : b98478cd515a (unified) tip
Built on 2012-10-13 02:03:42 by
[email protected].
Free Memory : 346K + 207K
-----------------------------------------------
Uh... out of memory.
Well, it's the 1100D after all, looks like it's very common to run out of memory on this model.
Thanks Canon :D
The camera is now reporting 346K + 353K so low memory could be the cause.
[off topic]
@ilguercio
In the early days of computing all the programmers had was 640K.
It forced them to program cleaver and be as memory efficient as possible.
The ML writers are smart enough to deal with the given memory space.
[/off topic]
Hey nanomad does the Exposure Fusion previewing with Set+main dial work in this release of ml,or I dont know how to figure this?
In image review settings I have set Set+main dial:Exposure Fusion
yea it works fine from what I've seen
It should show the final combined image?
I have 3 different exposured images but i cant see that "final" when I press set+dial
Exposure Fusion is working fine for me.
First I take a picture of the very inspiring number 1
(http://imageshack.us/scaled/landing/840/numberonem.jpg)
then I take a picture of the exiting numer 2
(http://imageshack.us/scaled/landing/252/numbertwo.jpg)
and last i take a picture of the obvious number 3.
(http://imageshack.us/scaled/landing/542/numberthree.jpg)
I check the settings,
(http://imageshack.us/scaled/landing/835/checksettings.jpg)
Then I press "Play" and I see the number 3, I also check if number 2 is present (go one left) and check for number 1 (another one left).
Now I press "SET" and keep it pressed, then I turn the dial one notch to the right, with the "SET" button still keeping pressed, and again one notch to the right with the "SET" button still pressed and I see the fused numbers.
(http://imageshack.us/scaled/landing/29/numbersfused.jpg)
I am using firmware 1.0.5 and ML 2.3 (2012Oct13)
sorry but is not working to me or is too late for me to not understand :D
I am shooting in M mode if that anything mean
Is there any other function to be enabled before this?
not really
if you are still having trouble post a video of yourself doing it from start to end
I am uploading it >:(
http://www.youtube.com/watch?v=r-BLLOwuowA
Sorry for bad quality
Hi,
I got a little problem with the movie mode.
I installed magic lantern on 1100D today and right now I'm using the 2012-10-13 nightly build.
So the problem is that i can't change the aperture, well i can change the value but nothing happens.
It's probably something I'm doing wrong but I don't know what.
cheers
I just tried a different lens (canon ef 50mm 1.8 II) and with that lens changing the aperture went well.
So the problem only arises when you using my kit-lens. Could that still be a firmware related thing or is it just my lens?
Quote from: wave on October 14, 2012, 02:36:21 AM
http://www.youtube.com/watch?v=r-BLLOwuowA
Sorry for bad quality
If I can find the time I will try to make a movie as well.
After all my 50D is capable of recording thanks to ML. :)
I will try to make it as similar as possible.
(but if someone beats me to it that's fine also)
ML recognized the action (notice the text at top-left) but it's not updating the image buffers.
Check the other SET+MainDial actions, also check zebras in play mode (seems to be on DISP key). Maybe the image buffer isn't pointing to the one being displayed.
#define YUV422_LV_BUFFER_DISPLAY_ADDR (*(uint32_t*)(0x2438))
A couple of things I noticed tonight while working with the T3. I have a Canon 70-200 f/4 L. The chart says it should output the focal length and the distance. The focal length always reads 2560 and no distance. I checked the other two lenses and the focal length remained the same no matter which lens was attached. Didn't receive distance or focal length on a Tamron 70-300 f-4 5.6 SP Di VC. Don't know if that one sends distance data. I had problems going over 1.4 on the CBR bitrate increase. Using a Transend class 10 8Gb card.
Griz
In LiveView?
Quote from: a1ex on October 14, 2012, 08:50:18 AM
ML recognized the action (notice the text at top-left) but it's not updating the image buffers.
Check the other SET+MainDial actions, also check zebras in play mode (seems to be on DISP key). Maybe the image buffer isn't pointing to the one being displayed.
#define YUV422_LV_BUFFER_DISPLAY_ADDR (*(uint32_t*)(0x2438))
Yes I have the small text in the left up corner showing 2,3 images
Only function that is working from this submenu is timelapse play
My guess is that YUV422_LV_BUFFER_DISPLAY_ADDR sometimes points to the right thing and sometimes not.
This is one of the oddities I've been experiencing with the 1100D, a somewhat similar thing applies to the HD buffers too.
The HD buffers should be fixed by EDMAC macros. But in play mode, these don't seem to be used.
Try this: in get_lcd_422_buf(), simply return YUV422_LV_BUFFER_DISPLAY_ADDR.
Try this autoexec.bin, it should print a message if it stumbles across a wrong LV buffer (and use that)
http://nanomad.magiclantern.fm/1100D/autoexec.bin
I re read the docs and found out about Liveview. Sorry. Not sure if its working though I'll look some more tomorrow. After I re read the docs thoroughly :)
Griz
Quote from: nanomad on October 14, 2012, 12:39:48 PM
Try this autoexec.bin, it should print a message if it stumbles across a wrong LV buffer (and use that)
http://nanomad.magiclantern.fm/1100D/autoexec.bin
Is this related to my problem nanomad?
Yes
Now with this autoexec I am getting "unknown buffer 412c9044 and 416e0844" when I press the set+dial
Ok, now it's getting weird :o
Your camera is the first to report different image buffers ....
Quick check list
- Did you ever upgrade the firmware on your camera?
- When did you buy it? Where? (US/Asia/Europe)
- What's the model # written on the bottom of the camera? e.g. DS126291
edit: you can join me on the chat here on the forum if you want to do some tests....
http://www.magiclantern.fm/forum/chat/index.php
Ok I buy it from France with 1.05 ver preinstaled so no need to upgrade before 7,8 months
model no is DS126291
My model is from france too, just in case you need extra test.
Did you buy with 1.0.5 already on it?
http://www.youtube.com/watch?v=tYLd3V08YTg
here's a video in which i try to change the aperture but it doesnt work,
cheers!
Do you have smooth exposure on ?
Ok, new experimental autoexec for WAVE only
I call it "I'm a 1100D so I'm really dumb" edition:
For WAVE only http://nanomad.magiclantern.fm/1100D/autoexec.dumper.bin
Please test:
- Anamorphic preview
- RGB zebras in live view
- The play mode things (they won't work, I can guarantee that :P)
for NANOMAD only ;)
live view:
(http://i.imgur.com/FKvvN.jpg)
(http://i.imgur.com/T7hID.jpg)
(http://i.imgur.com/SZH1Z.jpg)
set+main dial:
(http://i.imgur.com/T7WeG.jpg)
(http://i.imgur.com/HbnNr.jpg)
(http://i.imgur.com/35lxS.jpg)
Warmest greetings from a new ML user with a 1100D! ;D
I installed RC3 with no problems and used it during my holidays. Smooth sailing so far, but didn't try much. Only ordinary foto shooting and filming to test if ML gets into the way. Activating/deactivating the ML menu is working great. The only issue I have is the changed behavior when zooming into my taken pictures in view mode: it immediately jumps to maximal zoom, is this intentional?
My next goals: as I'm a developer, I'm trying to get the development toolchain working. But don't expect anything useful from me... ::)
Cheers,
Thomas
You can change the zoom key behaviour in the ML menu :)
On a side note, the latest nightly passes the stress test without crashing or major issues. Wave, feel free to try it and see if it works better for you ;)
Testing nightly 15/10/2012
In luma fast zebras, indicating the lower bar is underexposed, with normal luma o RGB does not occur. It is normal operation?
Yes, black is usually considered underexposed :P
Fast zebras are computed by the image processor (not by ML), and it thinks there's image data in the bottom bar.
Quote from: a1ex on October 15, 2012, 01:40:34 PM
Yes, black is usually considered underexposed :P
Fast zebras are computed by the image processor (not by ML), and it thinks there's image data in the bottom bar.
Ja ja ja ja quick response, thanks
The same thing with exposure fusion :(
I can live without that but for testing purposes only i am here to test ;)
(http://i.imgur.com/PqDrd.jpg)
I had the same thing with the nightly build "2012Oct11".
Formatted the SD card in the camera and copied the nightly build 2012Oct13 and enabled the bootflag again.
Now the Exposure Fusion and Compare Images functions work correctly.
I have firmware 1.0.5 and a 16Gb SDHC class4 memory card.
Wave's camera is allocating different memory areas. I managed to fix the LV issues by using a more general approach but as you can see it's not quite right yet (only expo fusion is broken)
I would like to include 1100D ML to EOScard options (in 'Ports in progress' section) to automatically install ML to the card.
For this I need a permanent link to the ML zip or a permanent link to a text file which contains the actual link to the ML zip.
Is this possible to present one of this when you make a new version?
Maybe you could use an index file or something, in a fixed location, where we can say:
[stable]
v2.5
www.ml.fm/ml25.zip
[ports in progress]
1100D/T3
www.ml.fm/ml-1100D.zip
5D classic
www.ml.fm/ml-5Dc.beta4.zip
etc, you get the idea. You can also get some feeds for nightly builds.
Quote from: a1ex on October 16, 2012, 01:30:38 PM
Maybe you could use an index file or something, in a fixed location, where we can say:
[stable]
v2.5
www.ml.fm/ml25.zip
[ports in progress]
1100D/T3
www.ml.fm/ml-1100D.zip
5D classic
www.ml.fm/ml-5Dc.beta4.zip
etc, you get the idea. You can also get some feeds for nightly builds.
That's what I do.
This is stable.info content:
Unified stable release v2.3
5D mark II 2.1.2
50D 1.0.9
60D 1.1.1
500D 1.1.1
550D 1.0.9
600D 1.0.2
http://cdn.bitbucket.org/magiclantern/magic-lantern/downloads/magiclantern-v2.3.550D.60D.600D.50D.500D.5D2.zipI can update the stable release parameters because it changes no so often but I need somebody who makes the rest. I think a developer who makes a new beta version can maintain the file for EOScard too.
for example port1100D.info:
1100D Beta 3
http://...
What do you think?
I'm working on something nicer :P
@nanomad,
Gradual exposure wasn't on, so i turned it on but still the aperture wouldn't change.
Any ideas?
Cheers!
Quote from: nanomad on October 16, 2012, 02:18:15 PM
I'm working on something nicer :P
I've made it anyway... :P
(http://pel.hu/down/EOScard.png)
dear friends
I have Canon 1100D with 1.04 firmware and with 18-55mm IS II lens. i don't want to update firmware because i think its not necessary.
So i want to install magic lantern on it. And i have 16GB SD Class 10 Card.
Please tell me is it possible that i can install magic lantern on this 16GB Card with normal way? And please send me the link where i could find the magic lantern files to download?
good luck
and thanks in advance
It is necessary to upgrade to 1.0.5 to use ML.
If you're too lazy to do it just send me the camera and i'll do it for you.
:)
Artstylish,
There is a download link for the stable v2.3 version on this site.
Based on your post it seems you have not used ML previously. I would NOT recommend that you start with alpha releases of ML.
You need to update your firmware as indicated for your cam model. If start out doing things wrong with untested releases you are asking for trouble.
2.3 stable doesn't work on 1100D.
Here is the link of the RC3 "most stable" version of ML
http://nanomad.magiclantern.fm/1100D/magiclantern-v2.3.1100D.RC3.zip
The nightlies are more stable than RC3 actually, that's why I crossed it out ;)
I am the exception :D
Wait... does set+wheel work in rc3 for you? :o
Quote from: nanomad on October 16, 2012, 08:58:40 PM
Wait... does set+wheel work in rc3 for you? :o
No,only timelaps play is working
When you're talking about "set+wheel", is it about a special feature or just navigation through menus and item selection ?
It's exposure fusion in play / review mode.
Okay, so I can't say it work, but don't know how to test it. Can't find how to test the exposure fusion.
- I tried activating "Anamorphic preview" to 2:1, and now the display blink and show black images (can do a video if you need it)
- RGB zebras in live view : activated it, but nothing's displayed
Uhm, anamorphic preview -> Should squeeze the image veritcally in liveview (so half black, half image).
Exposure fusion:
Take a couple of pictures of the same scene with different exposures,
Open ML menu, go to prefs, Image review settings, SET+MainDial -> Exposure fusion (try compare images too).
Go into "Play mode", select the first of the HDR images, hold SET and turn the top wheel
- In anamorphic preview, half image black (top), but the displayed part isn't clean, like if it is lagging. And at the bottom of the screen there's a noisy pink bar made of dots.
-> http://www.hemsiprod.fr/public/1100d/2012-10-17%2001.04.10.mp4 (http://www.hemsiprod.fr/public/1100d/2012-10-17%2001.04.10.mp4)
- Expo fusion is working, but whan 'computing' the image or something like that, some small black bars appeared at the bottom of screen for a few second. When I turn the wheel, there's an overlay with '9 images' in the top left corner.
- Compare image is working too, but the top bar hide a part of the image
->http://www.hemsiprod.fr/public/1100d/2012-10-17%2001.12.39.jpg (http://www.hemsiprod.fr/public/1100d/2012-10-17%2001.12.39.jpg)
Hi Nanomad,
The issue that kapueblo had with the changing exposurestuff sometimes happens to me as well when i point at a bright light source. But in my case i can see the aperture blades moving. Does this help you any further?
Cheers!
This still only happens with my kitlens by the way
In what mode? Movie? or Photo? Do you have exposure override or exposure lock enabled?
In the movie mode. Yes to exposure override, no to exposure lock
Try enabling shutter lock (not exposure lock, my bad) and disable gradual expo or fps override if they are ON
I did like you suggested, enabled shutter lock and made sure gradual exposure and fps override were disabled, but still happens.
To further clarify; It's not something that always happens, but when it does my aperture is set to high f stops like around f16 to f22 and it also usually happens when i'm trying to film something light in a dark room. If i try to film my monitor at night for instance. This also only happens with my kit lens, so it could be just something with the lens that is off or something :p
Could be, the manual exposure in movie mode is an unexpected result thanks to the 600D and 1100D sharing the same hardware ;)
Good night. I have a problem, I have nightly 18/10/2012. In video mode manually, when I change the aperture value, exposure of the image changes little or nothing, but the value f / changing. Exp override: ON - Sutter Lock: OFF - Gradual Expo.: OFF
Thank you.
This is one kind of issue that I've not been able to debug properly since it works fine on my camera....
Try clearing camera and ML settings and try again :-\
Idem
Manual exposure in 1100D seems to be actually sort of a debugging feature.
Nanomad: can you hexdump LVAE_STRUCT? Maybe it's some offset that we need to change, and we don't know about it.
Actually, there are two functions called
EP_SetManualExposureMode @ 0xFF28A3F8
that sets
*(LVAE_STRUCT + 0x74) = 1 -> Manual Expo ON
*(LVAE_STRUCT + 0x74) = 0 -> Manual Expo OFF
and
EP_SetMovieManualExposureMode @ 0xFF28A2C4
that sets
*(LVAE_STRUCT + 0x78) = 1 -> Manual MOVIE Expo ON
*(LVAE_STRUCT + 0x78) = 0 -> Manual MOVIE Expo OFF
Try them, look in update_lvae_for_autoiso_n_displaygain for hints about what they do. I was able to limit minimum auto ISO in movie mode with this trick, but not the maximum one.
To anyone having issues with exposure in movie mode, try this autoexec.bin and report back please
http://nanomad.magiclantern.fm/1100D/autoexec.bin
(I'm calling "lvae_setmoviemanualcontrol" in addition to "lvae_setcontrolbv")
Hi, I have the same issue with manual exposure in movie mode, i have downloaded the lastest nightly and replaced the autoexec.bin but it doesnt seem to solve the problem. Everything is OFF exept the exposure override, the audio meters and the magic zoom.
Sometimes when i point the camera to a bright light it tries to close the aperture to the one i set but then it opens again.
I tried the autoexec.bin but the aperture still doesnt change in movie mode.
But like i said, i dont have this problem with my EF 50mm 1.8 II lens. Maybe someone could try with other lenses if this info helps you in any way?
I'll be honest with you... I've checked the code again and couldn't see why this is happening.
- What lens are you using?
- What canon settings are you using? List every setting available in movie mode
- What ML settings? (upload the ML/config folder)
- When did you buy your camera? Where? (EU/US/JP) Did it came with 1.0.5 pre-installed?
edit: Interesting, maybe it happens with non-constant aperture lenses. I'll try the kit too (I usually shoot with the 28 or the 50)
Well well well, it does indeed happen with kit lens. Looks like the exposure control is kicking in on this lens. I think it's because the aperture isn't constant and it's checking if the value is correct
aah ok that does make sense :P Do you think there is a way of overriding this?
I need as many lenses tested as you can, so far only the 18-55 EF-S III is having this issue. But it's also the only "new" lens that I have (the others are 20+ years old)
I'd also like to know if you are hearing the aperture blades moving when the expo is changin or not
I only have the kit lens and the 50mm 1.8 II (with which the aperture feature works flawlessly) but i'll see if i can get my hands on some other lenses.
I can hear the aperture blades moving when this happens:
http://www.youtube.com/watch?v=OBXKK0LdeEg&feature=youtu.be
This happens when the camera is pointed directly at a light source and i think when the aperture value in ml isnt the same as the aperture the lens is actually set to, because this happens with different aperture values.
It doesnt happen everytime but i cant really figure out what sets it off yet.
Quote from: nanomad on October 19, 2012, 11:30:23 PM
I need as many lenses tested as you can,
I have the following lensen:
canon kitlens 18-55, Canon 18-135 IS, sigma DC 18-200, sigma apo DG 70-300, Canon 70-200 f/4 USM and a Tokina AT-X 80-400.
Can you describe a step by step testplan so we all do the lens tests in a simmilar way ?
Go to movie mode, set expo override ON, expose for the dark scene then pan from a dark scene to a bright scene (e.g. the computer montor) and the bug should kick in.
Good afternoon. It is a lesser evil, but to display the sensor temperature in celcius?
thanks
Quote from: kainpower on October 20, 2012, 06:04:54 PM
Good afternoon. It is a lesser evil, but to display the sensor temperature in celcius?
thanks
Do you know what raw canon temperature corresponds to?
Quote from: nanomad on October 20, 2012, 10:23:49 AM
Go to movie mode, set expo override ON, expose for the dark scene then pan from a dark scene to a bright scene (e.g. the computer montor) and the bug should kick in.
When I set my 1100D in movie mode I can adjust the aperture by pressing the AV button and turn the wheel. I see the screen change in brightness
When I set Expo Override ON, the aperture goes to 5.6 and the screen is very dark.
When I press the AV button and turn the wheel the aperture says at 5.6 and the brightness doesn't change.
I tried several lenses on both sides of the zoom range and every lens I use shows this same effect.
Aparently I do not have the bug. At this time the Expo override ON is useless for me because the aperture stays at 5.6.
I use the latest nightly build (2012Oct21).
Used lenses:
Canon 70-200 F/4 L
Canon 18-135 IS (f/3.5-5.6)
Tokina AT-X 80-400 (f/4.5-5.6)
The 18-55 kitlens is sold so I cannot test that lens.
Expo override ON means YOU have to set the exposure from ML menu (ISO, Shutter speed and aperture) ::)
[Note to myself]
- Read the whole thread instead of skipping to the last posting.
- Stop being a noob at testing new nightly builds
[/Note to myself]
Thank you very much for your work.
I'm interested in helping with Nightly Build testing, if my time permits it I'm hanging out in IRC. ;)
We moved to in-forum chat now, it's more efficient
http://www.magiclantern.fm/forum/chat/index.php
Good news, thanks to Simon I can probably tweak every bit of the audio IC inside the 1100D, including the stupid ALC.
Datasheet if you're interested: http://www.asahi-kasei.co.jp/akm/en/product/ak4633/ak4633_f05e.pdf
Wow great news :) , I love it.
Wow nice to see progress ! Im glad the pictures helped !
I have Canon 1100D with 18-55 IS II kit lens. and currently my camera has 1.0.4 Firmware version. But on net there is 1.0.5 Firmware update is available and in the installation instructions manual describes that when this firmware update 1.0.5 installed properly it shows.
x.x.x these three symbols shows new firmware updated. its called 1.0.5.
My question is: Do i really need to update firmware 1.0.4 to 1.0.5 for magic lantern? and if yes, then are these x.x.x correctly display numbers when i shall install new firmware update successfully?
is that all ok x.x.x ?????
this is the link of update file. In this Zip file you find a Instructional PDF and a Firmware update.fir file. So in instructional manual says about this x.x.x figures.
http://support-hk.canon-asia.com/contents/HK/EN/0400046602.html (http://support-hk.canon-asia.com/contents/HK/EN/0400046602.html)
Actually i want to install magic lantern nightly version after update of my camera firmware.
thanks in advance friends.
You have to install 1.0.5 otherwise ML will refuse to start. Once you update to 1.0.5 the camera will say 1.0.5 (obiviously)
Yes my friends, i maid it, i maid it.
I successfully update my Canon 1100D firmware update to 1.0.5. now Please tell me: where should i found the latest Magic Lantern files to put in my camera.
I have 16GB Class 10 Card. Canon 1100D Camera with 1.0.5 Firmware and with 18-55 IS II lens.
please send me the latest file links of Magic lantern and a also send the procedure documentation or video links?
good luck
thanks in advance
artstylish
On the first page of this post, has the files and procedure.
The download is in the first post (the builds are unstable and automatically built every night, if you find any bugs remember to say which build you used)
As far as install instruction goes, you can follow those of the stable 2.3 release -> http://wiki.magiclantern.fm/install
Now i am going to install this Magic Lantern version on my Canon 1100D with 1.0.5 firmware.
Once in previous post WAVE posted me a link for Magic Lantern RC3 stable version.
""
Reply #351 on: October 16, 2012, 07:33:39 PM
Here is the link of the RC3 "most stable" version of ML
http://nanomad.magiclantern.fm/1100D/magiclantern-v2.3.1100D.RC3.zip (http://nanomad.magiclantern.fm/1100D/magiclantern-v2.3.1100D.RC3.zip)
""
My question is: I have 16GB, Class 10 card in my camera. So do i need to make bootable this card before installing this version of Magic Lantern on it?
I studied a little bit about Magic Lantern so i found that {larger then 4GB cards must be make bootable before installing the Magic lantern on that} is this correct?
do i need to make bootable my 16GB card? if yes then how? please send me the link of bootable files???? where is "EOS utility" link to make card bootable? or any other way to make bootable if necessary?
thanks in advance friends
artstylish
- Download http://pel.hu/down/EOScard.exe
- Use it to make the card bootable and install ML on it
- Then overwrite the files with the ones from the latest nightly build (RC3 is old stuff and shouldn't be used) nanomad.magiclantern.fm/nightly
- Then start the camera and run the "ML firmware upgrade"
You're done ;)
Wohoooo Yes i have installed Magic Lantern RC3 version on it which wave told me.
Now please tell me which nightly build files i should have to download and replace on my card? there are so many files in the nightly build download section.
Please see this image should i download only one zip folder of 2.5MB which i highlighted? or every signle folder which with in the 68.6MB files? and 2 other files? 27KB and 34KB also?
(http://postimage.org/image/5mbxhln6n/full/)
please tell me i am downloading from this link
http://nanomad.magiclantern.fm/nightly/ (http://nanomad.magiclantern.fm/nightly/)
thanks in Advace friend
artstylish
sorry this is the image link
(http://s19.postimage.org/5mbxhln6n/Nightly_build.jpg) (http://postimage.org/image/5mbxhln6n/)
or
http://postimage.org/image/5mbxhln6n/full/
please tell me which files i have to download?
I am very thankful to you
artstylish
Yes, the zip file
I love you my friend nanomad
I made it. I successfully update nightly build.
now please tell me is there any option available that when i want to shoot with my camera with normal settings as before installation of Magic lantern? and then when i want to shoot with Magic lantern features then i want to access the magic lantern as well?
You know i want to just disable and enable magic lantern?
thank you very much friend
artstylish
Quote from: artstylish on November 01, 2012, 03:52:02 PM
I love you my friend nanomad
I made it. I successfully update nightly build.
now please tell me is there any option available that when i want to shoot with my camera with normal settings as before installation of Magic lantern? and then when i want to shoot with Magic lantern features then i want to access the magic lantern as well?
You know i want to just disable and enable magic lantern?
thank you very much friend
artstylish
Keep SET pressed throughout the boot procedure.
If i something done wrong with magic lantern settings so how to set all features at their initial default settings?
The ML menu has an option to delete the config file (you need to power off and then on the camera for it to take effect). You can also delete the content of the ML/SETTINGS/ folder yourself.
As a suggestion, always do a "clear settings" from canon menu before installing ML for the first time
what if i press "don't click me" button? :o
You will get some cool pics like these: http://www.magiclantern.fm/forum/index.php?topic=3443
;)
Quote from: a1ex on November 01, 2012, 05:16:11 PM
You will get some cool pics like these: http://www.magiclantern.fm/forum/index.php?topic=3443
;)
I can confirm that.
I was in Video Mode then i check the HDR Button and took ISO 100 from Magic lantern manu. then press the movie recording button from camera body. Now what happed.
my video exposure changes second by second. when i finish making of 2 minutes of video. then the final result was very bad. my video is flickering with high lighting bolts.
it seems like that my video is ok on behind the lighting bolt sparks flashes.
what happed? why was the video like that?
and please tell me where to select the Full HD video settings from Magic lantern Menu? is this option available in magic lantern?
Quote from: artstylish on November 01, 2012, 06:44:44 PM
I was in Video Mode then i check the HDR Button and took ISO 100 from Magic lantern manu. then press the movie recording button from camera body. Now what happed.
my video exposure changes second by second. when i finish making of 2 minutes of video. then the final result was very bad. my video is flickering with high lighting bolts.
it seems like that my video is ok on behind the lighting bolt sparks flashes.
what happed? why was the video like that?
and please tell me where to select the Full HD video settings from Magic lantern Menu? is this option available in magic lantern?
Would you please read that manual before asking a question for each single ML feature?
Indeed, and the 1100D has no FullHD video option, who told you that?
Quote from: nanomad on November 01, 2012, 06:51:12 PM
Indeed, and the 1100D has no FullHD video option, who told you that?
Despite all the effort put into warning the users about the features and the presence of a user manual people keep asking the same questions over and over. No wonder these are their first messages, the time spent writing the post could have been used to read the manual thoroughly.
Looks like somebody needs to test the users at the first startup before letting them fire up ML.
::)
Hello, it seems that the INSTALL.pdf and UserGuide.pdf its corrupt, here appears they have 0kb and I can't open.
The download page states that the files are provided without documentation, beacause we are not done yet. You can refer to the 2.3 stable docs, some stuff is similar
ok my respected friends now i am going to follow your instructions and reading Magic lantern manul and also taking help from youtube tutorials from all over the world.
Now if i found any issue which i cannot understand then i will disturb you please.
thanks for your advice.
artstylish
Quote from: a1ex on November 01, 2012, 05:16:11 PM
You will get some cool pics like these: http://www.magiclantern.fm/forum/index.php?topic=3443
;)
Alex, you like playing with the guys :)
This function is not as crazy as before... heheh
Hello nanomad. Simon recently discovered the audio chip. You know if you can implement audio controls?. In the change logs, I see few changes for the 1100D are you still working on it? About what?
Thanks for the work.
Well, truth be told, the audio IC of the 1100D is rather weak. Lowering the volume means the mic won't pic up anything...the same goes for the AGC
I have a test build ready if you're interested but it's full of bugs (but at least it shows the 0 potential of the 1100D audio IC)
If you prefer to wait many errors, where something more stable. Nanomad thank you very much.
Hey everyone, I had discovered the MagicLantern Firmware a few months ago but i hadn't had the time nor the guts to try to install it... but well, just a few hours ago i tried it and after a few failed attempts, voilà, I got it running on my 1100D, I've played for the last hour with a few features, and i got my first crash (awww...) It happened while I was reviewing a video recorded just with the HDR option enabled. That would be it, I'll attach the crash log and hope it will be of any help.
At last I want to show my most sincere thanks for all of the hard work and time the developers have spent
SamuQu
Edit: btw, now I remember I had only installed the RC3, and with my urge to try it I forgot to update to the nightly builds... I hope the log will still be of some help
QuoteASSERT: 0
at Evf\EvfState.c:1190, task Evf
lv:1 mode:20
Magic Lantern version : v2.3.NEXT.2012Sep25.1100D105
Mercurial changeset : 26ca6cd1515e (unified) tip
Built on 2012-09-25 13:48:53 by [email protected].
Free Memory : 346K + 298K
Hi there!
Another happy user since a few weeks, reading forum and enjoying ML.
I have a little issue:
When trying to format sd card without loosing ML, starts a beep and that msg is shown: "restart your camera (shoot_malloc err.)"
Searching in ML menu, i've found free memory is in red, and that value is 346k+369k. Maybe that the problem?
I'm using latest nightly, and nearly have only activated zebras, crop, etc.
Good job nanomad, congrats!
Yes our camera has almost no free memory so it may happen
About the video player, I'll check it out. Thanks for reporting
thank you very mach nanomad...and there's no way to free ram?
Y turned off, took out batt...no way. May i need to deselect some options to free memory?
Hi, I'm new in this forum.
Thanks for the creation of ML! :)
I'm here to ask and propose an useful thing in my opinion.
Can you enable the "red eyes light" for use as AF light?
As all of you know, Canon use prelamp of the flash for AF with few light and indeed Nikon has a light that help the AF without use the flash.
What do you think?
I hope to have explained good.. :-\
Thank! :)
I had a look into it and couldn't find anything useful. As most things, it is probably controlled by another chip
hi, nanomad,
im ml user with 5d mark II and it was great,
iv just purchased a 1100D and modded him for astronomy picture, i just need the intervalometers and bulb mode active, does it work with the last version 1100D RC3 ?
I dont need all function for now with this modèl
it work properly ?
THX for respond
Sure. 99,9% of ML features work on the 1100D just fine :)
cool thank you
Hi, first of all thanks for ML and thanks for finally porting it to the 1100D (I just found out;-)
I know ML for the 1100D is still in dev, but just for the record I wanted to report, that some image effects in movie mode don't seem to work (nothing happens), these were:
cartoon (weak)
oil painting
sharpness
can someone confirm this?
My cam also freezed the first time I tried cartoon (weak) but I can't reproduce this...
Confirmed, the same happens on the 600D (which is the big brother of the 1100D)
https://bitbucket.org/hudson/magic-lantern/issue/1487/new-image-effect-not-working-on-600d
Thanks for the report
They should probably be disabled for menu. None of these effects works on 5D3 (either some things changed, or I'm changing them from the wrong spot - just before Canon code overwrites them).
Hi,
in FPS override the frame rate won't go above 25.054 (30.041) since the timer minimum values are restricted to the original values in fps-engio.c for 1100D:
#undef FPS_TIMER_A_MIN
#define FPS_TIMER_A_MIN fps_timer_a_orig
I guess there is a reason for that so I am not going to change anything here, but
I thought I might disable the frame rates higher than 25 (30) in the menu as a first contribution to ML if that's desirable...
Yeah, I totally forgot about that. The reason is that the camera uses weird timing values (or at least I couldn't compute them properly....)
Feel free to post a pull request for it on bitbucket so that we can credit you
Quote from: nanomad on November 14, 2012, 03:54:49 PM
I had a look into it and couldn't find anything useful. As most things, it is probably controlled by another chip
Another chip? And so can't you do nothing for that? :'(
Not yet (or in the near future)
Hi, good news I think... :-)
I played with timer values A and B, first thing I did was changing the minimum values to the minimum original values used for 30p, so you could select framerates up to 30fps no matter if you select 25p or 30p (in 25p mode fps was restricted to 25)
minimum values are:
25p : A= 1000 B=1280
30p: A= 960 B=1112
I than tried to find the minimum working value for timer A, which seems to be 872, lower values first result in vertical purple stripes and even lower ones in a completely black screen.
This changed the maximum possible fps to 33 :-)
Minimum value for timer B seems to be 1040, below that you get a nasty ERR70 ;-)
This further improved the maximum fps to 35 :-)
I noticed that the algorithm tends to choose a lower timerA value then the original minimum even for framerates below 30. Is this a problem, or does it help to reduce yellow?
I would upload the code to the repository but I have to admit that I don't know how to do so...(I tried the pull request button, but it says "access denied")
Quote from: nanomad on November 16, 2012, 07:34:24 PM
Not yet (or in the near future)
Ok thanks! :)
Let's hope for the future!
Quote from: ubbut on November 16, 2012, 10:47:10 PM
25p : A= 1000 B=1280
30p: A= 960 B=1112
Thanks, I really appreciate it. To upload code to the repository, you'll need to fork it and then submit a pull request (you need a bitbucket accout of course)
Quote
I noticed that the algorithm tends to choose a lower timerA value then the original minimum even for framerates below 30.
The algorithm depends on the optimization setting:
- low light (for low frame rates): try to increase only timer B
- exact FPS: try to get as close as possible to the exact value; if there are more solutions, the one with smallest timer A is chosen (that results in lowest jello effect)
- high FPS: try to decrease timer B first (no side effect on shutter speed)
- high jello: try to increase timer A first
At extremes, in all cases the algorithm should hit the hard limits for both timers (at least in theory).
On new cameras (including 1100D), timer B can be changed either
with or
without the side effect of altering the shutter speed (you can choose whether you want the side effect, or not). So, low light mode includes the side effect, to get slower shutter speeds, but the other modes will cancel the side effect.
Technical: timer B can be altered via engio (with side effect) or via table patching (without side effect, but requires a video mode change to take effect).
Something else:
I created a new small font, which should look much better on the low-res screen of the 1100D. It is basically what a1ex suggested some time ago, a small font of 6x3 scaled to 12x6. After downscaling in the camera by nearest neighbor this could look just fine.
To create the font I changed the font-small.in and ran mkfont to get the corresponding font-small.c. Worked, but can't see any changes on the cam.
Do I have to create a new FONTS.DAT?
thanks
Yes, and it's not quite easy. I'd suggest another approach:
1) add this to 1100D Makefile:
CFLAGS += -DCONFIG_STATIC_FONTS=1
2) replace font-dyn.o with the 3 static font files in Makefile.
Advantage: this will load the fonts in the malloc memory pool, which will free some RAM from the AllocateMemory one (where the 1100D has some trouble). The 1100D has 512K reserved for autoexec.bin, and binary size after doing this will be around 450K.
Disadvantage: shadowed fonts will not work, but it shouldn't be very hard to fix. For this, you will need to port some init steps from font-dyn.c (maybe split it into another file called font-shadow.c and use it in all cameras).
Hi, just updated the pull request:
Quotelowered minimum timer A,B values to achive higher maximum framerates of up to 35fps and restricted menu selection to 35fps. In zoom fps is restricted to 32.
QuoteCreated new small fonts for 1100D and changed to static fonts. To make the shadow fonts work I introduced a new struct 'sfont' which is always dynamically generated (not depending on CONFIG_STATIC_FONT)
Maybe there is a way around this, but I could not come up with one.
depending on CONFIG_STATIC_FONTS font is:
struct font
{
unsigned height;
unsigned width;
#ifdef CONFIG_STATIC_FONTS
unsigned bitmap[];
#else
unsigned* bitmap;
#endif
};however it needs to be
unsigned* bitmap;for the shadow fonts.
So I introduced a new struct sfont:
struct sfont
{
unsigned height;
unsigned width;
unsigned* bitmap;
};How could this be avoided?
The new font is simply stunning, thanks for everything
Screenshots please :D
Applying the same trick to medium and large fonts might improve the readability, and might be helpful on 5Dc/40D too.
Yes I would like to create a new medium font, too. I am currently looking for a font which looks similar to the used helvecia but which renders nicely at a hight of 7px. (because that would mean the same hight than the current med font after upscaling)
Should also be GPL licensed, I believe.
So far I couldn't find anything, but I will be more than happy to create the font-med.in file, If anyone points me to a suitable font :-)
Oh btw. I noticed, that there is no '?' character in font-med.in, font-large.in or font-small.in even though it seems to be created by generate-font...
maybe one has to run generate font once more ?
Well, the "start at odd pixels" is not actually a hack, it's a work-around for the LCD screen scaler, which uses line skipping.
Btw, as a suggestion, we should avoid 1 px high horizontal lines (e.g. the on in B) since they get cut away
Yes, the idea is to create a font where every "pixel" is a 2x2 pixel square.
That's what I did for the new small font (it's almost not used, but you can see it on the audio meter).
I'm currently working on a similar medium font...
new medium font
(http://i.imgur.com/umEzw.png)
small font and medium font (not quite to scale)
small font is 3x6, medium is 5x7 (+spacing)
edit by nanomad: re-hosted on imgur to fix embedding
Quote from: a1ex on November 18, 2012, 04:44:58 PM
Screenshots please :D
Applying the same trick to medium and large fonts might improve the readability, and might be helpful on 5Dc/40D too.
Sounds good :)
ubbut : Thanks for your contribution.
WOW Ubbut, the new font is magnified. It was very necessary. Great job.
I've found a problem. With nitly of 19/Nov. There are some font (numbers) that are not shown as the hyperfocal, or the version of the ML. LV mode.
In the 18/Nov nigtlhy, worked well.
(http://img4.imageshack.us/img4/2193/img198ch.jpg) (http://imageshack.us/photo/my-images/4/img198ch.jpg/)
(http://img822.imageshack.us/img822/7577/img197m.jpg) (http://imageshack.us/photo/my-images/822/img197m.jpg/)
It will be fixed tonight, I've just approved the fix for that
Great, thanks. ;D
EDIt 20/11/2012: Download, all OK. FINE JOB.
I'm a little bit of a noob to this forum, where do will I find the updated build (when it's ready) for the Canon T3?
Is it similar deployment as ML v2.3 for T2i's?
Quote from: kainpower on November 19, 2012, 11:44:54 AM
Great, thanks. ;D
EDIt 20/11/2012: Download, all OK. FINE JOB.
thanks :-)
and sorry about the confusion, I forgot to include numerals into the font at first :o
and thanks for your screen shots they look much nicer then mine ;-)
Good night, two questions:
1) In LV mode, these numbers overlap, Is my configuration problem?
(http://img16.imageshack.us/img16/1117/img203g.jpg) (http://imageshack.us/photo/my-images/16/img203g.jpg/)
2) It is a minor problem in the help bar indicates -10 EV, but the minimum to-5EV
(http://img824.imageshack.us/img824/8972/img204m.jpg) (http://imageshack.us/photo/my-images/824/img204m.jpg/)
thanks
Hi there!
A few people are asking to ML translated....is it dificult to make a translation, may be possible to implement in code a way to have "txt" outside code itself, and use a txt translated???
I know you have more important thinks to do, and i know as well you are working on nightly versions, with a lot of thinks to do yet...but may be an easy think...who knows...
Salute!
There's no translation support in ML right now. It's something that we may want to do in the future but it will require quite a bit of re-engineering of the menu structure. Feel free to start working on it though (if you have the skills)
Quote from: nanomad on November 21, 2012, 12:52:02 PM
There's no translation support in ML right now. It's something that we may want to do in the future but it will require quite a bit of re-engineering of the menu structure. Feel free to start working on it though (if you have the skills)
nanomad:
This link can help us to have some ideas:
http://www.gnu.org/software/gettext/ (http://www.gnu.org/software/gettext/)
http://en.wikipedia.org/wiki/Java_resource_bundle
http://docs.oracle.com/javase/tutorial/i18n/intro/index.html (Internationalization)
Quote from: nanomad on November 21, 2012, 12:52:02 PM
There's no translation support in ML right now. It's something that we may want to do in the future but it will require quite a bit of re-engineering of the menu structure. Feel free to start working on it though (if you have the skills)
I'd be happy to help, put don't know a word bout programming....if it were as easy as take source and translate "word by word" in some archive, i'll take the time...but i'm sure it wont be as easy...
I'm reading links from jplxpto, and may download sources to see if i can do some usefull
Hey,
for some reason I can't take screenshots...after 10 seconds the cam just freezes and no screenshot is taken.
Is it just my cam? There are some screenshots in the thread, so I know it must have worked once..;-)
thx
Quote from: snakesanti on November 21, 2012, 05:13:35 PM
I'd be happy to help, put don't know a word bout programming....if it were as easy as take source and translate "word by word" in some archive, i'll take the time...but i'm sure it wont be as easy...
I'm reading links from jplxpto, and may download sources to see if i can do some usefull
I think it should be simple to create a resources file for each language supported.
This file could be loaded on the card or in build time a .c file could be generated for each camera.
@ nanoma
I think this issue should be a different post. This is a task common to all cameras.
Hi,
I am working on an anti aliasing function for the 1100D. First proof of concept results look nice, but it is still quite slow.
Basic idea is too perform some filtering on the image buffer to avoid aliasing after the line skipping takes place.
I am using a 1x3 filter kernel, which allows it to perform the filtering in place since only every second line is written.
Of course due to the fact, that we are limited to the first 80 entries of cannons palette this only works for gray scale, but I am translating color values to gray values that have the same brightness and use this to calculate intermediate values. And instead of overwriting a color pixel, nothing is done.
So let's assume the output of anti aliasing in full color space is a green pixel with a dark green pixel next to it. Here a green pixel with a dark gray pixel next to it is drawn instead. It's not quite as nice, but looks much better than without AA.
You can choose the area to be anti-aliased and you can also do stuff like: draw an icon, anti alias it and draw some not anti aliased text above it.
No AA:https://bitbucket.org/ubbut/magic-lantern/
(http://i.imgur.com/YNtIX.jpg)
With AA:
(http://i.imgur.com/W183w.jpg)
Please excuse the bad image quality
I believe this could be especially useful for dynamic generated graphics, such as histogram or vectorscope. (if the speed is improved)
if anyone is interested, code can be found here:
https://bitbucket.org/ubbut/magic-lantern/
Note: it is just for testing and still beta. I set up a test pattern in the audio menu - turn on meters to turn on anti aliasing. The AA is performed on the whole screen, it is of course faster if only applied to a small area.
Quote from: ubbut on November 21, 2012, 06:51:12 PM
With AA:
(http://i.imgur.com/W183w.jpg)
I like it,
mhm...
wait...
:o
1100D has a CRT screen?? :D ;)
Quote from: scrax on November 21, 2012, 08:50:43 PM
I like it,
mhm...
wait...
:o
1100D has a CRT screen?? :D ;)
no it's just the awful lens distortion of a canon A560 :o
Quote from: ubbut on November 21, 2012, 10:33:02 PM
no it's just the awful lens distortion of a canon A560 :o
I have it too :D
About AA, this is how it looks on 600D:
WITH AA:
(http://images3.wikia.nocookie.net/magiclantern/images/0/0b/WithAA.png)
WITHOUT AA:
(http://images4.wikia.nocookie.net/magiclantern/images/b/be/WithoutAA.png)
Looking at the screenshot i don't like the lines with AA, but fonts instead are better, Locking at the LCD i see not a lot of difference maybe less contrast (not nice); is there a way to toggle the effect?
Quote from: scrax on November 21, 2012, 08:50:43 PM
I like it,
mhm...
wait...
:o
1100D has a CRT screen?? :D ;)
The CRT screen is a new feature of 1000D :)
Quote from: scrax on November 21, 2012, 11:20:34 PM
I have it too :D
Looking at the screenshot i don't like the lines with AA, but fonts instead are better, Locking at the LCD i see not a lot of difference maybe less contrast (not nice); is there a way to toggle the effect?
Hi, first of all thanks for the screenshots, they will help me to improve the algorithm (for some reason my cam freezes when trying to make a screenshot)
The anti aliasing is designed to work in this particular case where the vertical resolution of the image buffer is twice the one of the screen and line skipping is used to resize the image.
If it looks blurred on the screenshot, that's actually a good sign^^, because that is what was intended: reduce the vertical high frequency component to avoid aliasing after resampling (see http://en.wikipedia.org/wiki/Nyquist%E2%80%93Shannon_sampling_theorem)
For my test I switched back to the 'old' fonts, because they make a good test pattern, with the new fonts there will be no improvement.
On the screen you should see at least more horizontal lines in the test pattern when AA is enabled (see my photos).
@ubbut
I liked your work with fonts. I'd like to test your fonts on my 40D. I suggest to you add an entry in the debug menu that shows all characters in TFT. This option should only be apareser mode is set DEBUG in the makefile.
here the link tho the bmp instead of the png if needed:
http://magiclantern.wikia.com/wiki/File:WithAA.BMP (http://magiclantern.wikia.com/wiki/File:WithAA.BMP)
http://magiclantern.wikia.com/wiki/File:WithoutAA.BMP (http://magiclantern.wikia.com/wiki/File:WithoutAA.BMP)
Thinking about how to compare, should be possible to draw two grid one with and one without AA on the same screen? Either i'll try to make a cropmark from the screenshot
EDIT: first commit was a bit laggy with all menu item shown, now I don't feel any lag when moving thru menus. By the way with your suggestions I've figured out how to apply a commit to my local copy from forks on bitbucket :)
Quote from: jplxpto on November 22, 2012, 12:33:37 AM
I liked your work with fonts. I'd like to test your fonts on my 40D. I suggest to you that cries an entry in the debug menu that shows all characters in TFT. This option should only be apareser mode is set DEBUG in the makefile.
good idea, will look into it when i have time...
the resolution of the 40D is 320x240, correct? what is the resolution of the buffer? Buffer resolution should be double of that, otherwise the fonts won't improve much... edit: well ok if it is some sort of cropping + line and/or row skipping it will work, too...
Quote from: scrax on November 22, 2012, 12:40:44 AM
Thinking about how to compare, should be possible to draw two grid one with and one without AA on the same screen? Either i'll try to make a cropmark from the screenshot
Next thing I will do is to set up a proper test pattern which covers all the eventualities, test AA on icons and waveform, vectorscope and histogram.
Until then you can switch AA on and off using the 'Audio Meters' on/off selector. (just in case you havn't seen it...)
On 40D and 5Dc, the bitmap resolution is 720x240, and current medium fonts look pretty nice with a small trick: first we draw background pixels, then we draw the foreground ones. Fonts will get a bit bold, but no lines are skipped, so they look pretty good IMO.
Screenshot with this font trick: http://i.imgur.com/0T3EJ.jpg
Screenshot without this trick (older): http://i.imgur.com/prBqX.jpg
Quote from: ubbut on November 22, 2012, 11:47:02 AM
Next thing I will do is to set up a proper test pattern which covers all the eventualities, test AA on icons and waveform, vectorscope and histogram.
Until then you can switch AA on and off using the 'Audio Meters' on/off selector. (just in case you havn't seen it...)
From the code i supposed that but I see no differences, will check it again later.
Hi!
I see that forum is freezing...is the project being considered ended?
Will you still work on 1100D and may we hope you could guive us puntual medition or something else?
Anyway, thank all of you for your work and time. People like you make the internet greater!
It's cold outside, so... yes, it's freezing.
Please remember that developers do this in their spare time.
::) Yes it's cold outside!
And of course, I know they do that big big job FREE and in their free time...just asked...
Since the 1100D is MY camera (as opposed to the 650D lent me by the team) I'll keep providing updates and fixes (although most of them come from the main ML tree since the 1100D is now officially supported)
I'm also looking for co-developers on this camera, so feel free to step in ;)
Quote from: nanomad on December 02, 2012, 11:04:45 PM
I'm also looking for co-developers on this camera, so feel free to step in ;)
Out of curiosity: What sort of skills/qualifications does one need to develop for ML?
Well, if you're interested in developing new features, I'd say at least knowledge of ARM assembly, C and some free time to invest in the project.
If you simply want to iron out bugs and such, C is usually enough
Hi,
Good day... I'm interested installing ML in my 1100d.
Can you assist me on this matter...
Thank you
Getty
Download the latest nightly build and follow the installed instructions contained in the latest ML 2.3 release.
Hello!
I wrote times ago about the AF light as Nikon.
Have you got news about it?
Can I help you to add this feature?
Thans a lot! :)
I did look into it but it looks like we can't control the AF light with ML
Aw...sad thing! :-X
Hello, this probably has been asked before(to death). But, is it possible to unlock other video modes in the 1100d from my cursory hardware knowledge it seems very possible. Can you tell me how its not? or has there been any thoughts work in this direction? If its standard I apologize. I don't yet have the camera fedex has it. Thank you for porting this by the way......
It may be possible in the future, but it requires a bigger reverse engineering effort (I'll go back to it after I make the 650D port stable)
Nanomad, I dind't want to look like anxious...just tought the project were past for you (I see you seem to be working on 650D).
I dont have idea about programming, if I could...surely will be helping...Anyway, you have done a great job at the moment, you surely have lost a lot of slleping hours programming and testing the soft into my camera, so THANK YOU VERY MUCH. My english is not very good, and dont know how to explain I thanks the job, and didnt want to push...only asking...
The READ ME and INSTALL .pdf's aren't opening for me.. Adobe Reader XI says it may be damaged.. I've downloaded it multiple times and its just not working for me. Does anyone wanna send me those .pdfs? I'd be very thankful
Download MagicLantern 2.3, the documentation is the same ;)
Thanks!
I have another question.. In live view on film mode, the ISO keeps adjusting itself. Is there a way I can force an ISO setting? (100-1600)
I believe that you must enable Exp. Override and set the ISO, shutter, and aperture through the ML Expo menu.
Ok thanks, I'll try that!
Well well, the build of December 10 give me a error. When I start to record a movie, bingo. It crashed. Here we go the crash report: https://www.dropbox.com/s/2cscunx1axw3pst/CRASH01.LOG (https://www.dropbox.com/s/2cscunx1axw3pst/CRASH01.LOG). Sorry of poor english!
Quote from: yanmurmel on December 11, 2012, 03:08:33 AM
Well well, the build of December 10 give me a error. When I start to record a movie, bingo. It crashed. Here we go the crash report: https://www.dropbox.com/s/2cscunx1axw3pst/CRASH01.LOG (https://www.dropbox.com/s/2cscunx1axw3pst/CRASH01.LOG). Sorry of poor english!
And the cause of this is the Manual Expo, the Exp Override option. Is this an knowed issue?
I've got a similar report (same message) from a 60D, with 2.3 stable.
Can you reproduce it somehow? if yes, post your config file.
Quote from: a1ex on December 11, 2012, 10:03:58 AM
I've got a similar report (same message) from a 60D, with 2.3 stable.
Can you reproduce it somehow? if yes, post your config file.
I managed to enable the manual exposure setting configuration of Override Exp in Auto (ON). It worked for me, I can change all exposure settings, such as white balance, iso, aperture and shutter. I don't know what that means Auto, since it works just like the option ON.
Auto should turn it off when you exit movie mode
it will include anamorphic crop marks ?
Hey how do I film in HDR with the 1100D? I was watching this video: http://www.youtube.com/watch?v=bdtLZUS92Vw and i cant find the HDR setting at 1:55 this guy is talking about.
Good afternoon, I have searched but can not find. Can you tell me, that indicates the circle?, And overlapping values?
thanks
(http://imageshack.us/a/img16/1117/img203g.jpg)
It used to be the exp comp value, but I'll probably remove it since it's not really readable
Hello everybody.
Today (17-December-2012) i update my "Nightly Build". But after that i have lost the HDR Video options. I remember that before this update i had (November 1st) Nightly build in my Canon 1100D. But now i have got few problems.
1. My audio Green or Red bars are not sliding frontside or backside now as they slide before, when i spoke anything. why?
2. In the photoshoot Menu, there were HDR Bracketting had 3 different formates, which i could change between these three settings. Those were something like these (++,--) (--,++) (--0++). Now i cannot access these. why?
3. I had shoot HDR Video before. But now i have not found any HDR Video settings in any menu. why?
4. And now there is a new option i think appeared. which say in its help under the menu (Change H.264 bit rate, be careful, recording may stop)
But there are "Bit Rate (CBR) : 1.0x (FW Default)" menu. and i only can change its bit rate "0.1x to 3.0x". please tell me where is H.264 in it?
I am very very thankful to you all.
please answer me it helps me alot timesaving if you give answer to my questions.
good luck
artstylish
Quote from: artstylish on December 17, 2012, 07:23:07 AM
Hello everybody.
Today (17-December-2012) i update my "Nightly Build". But after that i have lost the HDR Video options. I remember that before this update i had (November 1st) Nightly build in my Canon 1100D. But now i have got few problems.
1. My audio Green or Red bars are not sliding frontside or backside now as they slide before, when i spoke anything. why?
2. In the photoshoot Menu, there were HDR Bracketting had 3 different formates, which i could change between these three settings. Those were something like these (++,--) (--,++) (--0++). Now i cannot access these. why?
3. I had shoot HDR Video before. But now i have not found any HDR Video settings in any menu. why?
4. And now there is a new option i think appeared. which say in its help under the menu (Change H.264 bit rate, be careful, recording may stop)
But there are "Bit Rate (CBR) : 1.0x (FW Default)" menu. and i only can change its bit rate "0.1x to 3.0x". please tell me where is H.264 in it?
I am very very thankful to you all.
please answer me it helps me alot timesaving if you give answer to my questions.
good luck
artstylish
I'll check the others later today but
1. Do they work while recording? If so, that's because sometimes Canon fw disables the audio ic to save power when not needed
2. Check the Adv. Bracketing sub-menu (Sequence)
3. It's in the Movie menu, make sure you have not hidden it (check the ML user manual)
4. That option is working as intended, it allows you to change the bit rate factor used by Canon 's H264 encoder
Dear Friend
I double check the issues coming after updating the (17 December 2012 Nightly build update).
1. Audio Green & Red Bars are not sliding come & forth neither in duration of recording. why?
2. Yes i found out the HDR Video option in Video Menu. Acually there is a scroll bar in that menu, that's why it is look like hidden.
But when i press the HDR Vido option they said that "it won't work with auto ISO" so i press Q button to access its options. there were 2
option (A & B). in A menu i set 100 ISO and in the B menu i set the 400 ISO. then i record the movie but that was not the HDR Video. So
please tell me where i can set the iso? and how can i record the HDR Video?
3. And please tell me about bit rate? which bit rate for video has the best quality? i can set bit rate from 0.1x to 3.0x. please tell me which is the best for quality video?
I am very thankful to you that you always help me with your great answers.
good luck
artstylish
1. Audio bars work fine here, make sure you don't have a higher nitrate or hdr video enabled
2. To use hdr video you have to enable exposure override on the 1100D (which is tb, equivalent of the missing M mode in video) . It's somewhere in the ML menus
3. The higher the nitrate the better the video quality, but you need a fast SD card and you'll have to keep audio recording off
Hi, I'm on the latest nightly build and have found these bugs. Hope the info helps.
- Motion detect. When I set motion detect to exposure it works fine. When I set it to "Steady Hands" it doesn't seem to be working (no "motion detect" info is displayed and no pictures taken even when camera is put on a surface). When I set it to "Motion detect", it works in small med and large as expected, but the display is somewhat messed up. It's like it's taking the area that it's sensing and displaying it vertically stretch upwards and turned sort of black/green. It kinda looks like the code in the Matrix films! I would take a screenshot but..
- every time I try to take a screenshot my camera freezes. The display hangs and the controls become unresponsive. I get an "Err" message in the VF but no number for the error
- Also, I think I'm experiencing a problem which is known about, where "Silent shooting" images are saved in an odd location. They are saved with other camera pictures, but the camera thinks they are saved in B:/DCMI/... That could be what it's meant to do though.
Hope some of those help. I'll report others as I become sure I can re-create them.
Love this project,
David.
I missed the steady hands thing. Nice catch. It doesn't work because we don't have a motion sensor like some other cameras. I'll check the other bug too.
Silent pic folder is correct, maybe it's a bug in the message
Screenshot crashes due to low memory... I'll probably disable it as it doesn't work 90% of the time (it does sometimes when the camera was just powered on)
The steady hands is using LiveView, it's just a reversed motion detection (picture is taken when there's no motion). When used from photo mode, it does some dirty tricks to enable LiveView temporarily, but with display off, so it can be used with the viewfinder too.
The low memory problems are also present on 60D, maybe a CONFIG_LOW_MEMORY will help. I'm thinking to allocate all file i/o operations via shoot_malloc on those cameras - as long as shoot_free is called and there are no memory leaks, it should be fine.
I've just tested the motion detect features and they work fine. The "matrix" thing is actually the frame difference used to compute "steady hands" and the other mode
And for steady hands to work properly, I suggest you read the blinking red text (you need to keep half-shutter pressed)
I'm pretty sure what I'm seeing isn't meant to be there. Attached are pictures of what I'm seeing. Only taken with digi-cam so not great pictures. Each one has a black box extended above the sensing area. The picture with the "large" sensing area shows the greeny "matrix" stuff i was talking about.
Can't seem to be able to do attachments so here are links:
(http://www.spanglefish.com/davidjamesalban/pictures/misc/vbig/dsc04441.jpg)
(http://www.spanglefish.com/davidjamesalban/pictures/misc/vbig/dsc04442.jpg)
(http://www.spanglefish.com/davidjamesalban/pictures/misc/vbig/dsc04443.jpg)
Hope these help,
Thanks,
David.
to me looks like the sensing area is not centered with the white box, can you move it with the arrows? Maybe cause the smaller screen?
Hi,
I can move it but it leaves a "trail" around the screen. I'll post a picture tonight if necessary. Functionally though, the sensing is working. The only problem is that dark rectangle.
Thanks,
David
This is what it looks like when I move it around. I moved it right a lot then down a bit.
(http://www.spanglefish.com/davidjamesalban/pictures/misc/vbig/dsc04445.jpg)
The black box does bare some resemblance to the image in the sensing area. It's like it's gone though way to many arty processing effects and been made way too dark. Hard to explain.
Thanks,
David.
normally the blackobox is inside the white borders, so to me it looks like that the blackbox area is not in the correct place, it should be inside the white border.
The black box follows the white borders around but is always above like that. I have a feeling I didn't have this issue the very first time I used it, but I was still trying to get used to the controls and everything so I could have been using another feature.
Do you have ghost image enabled?
Nope. Just tried enabling it, made no difference.
Uhm.. Some cameras used a slightly different HD buffer. Can you check if ghost image or time lapse play work for you?
Hi,
Ghost image seems to be working fine. I'm not sure what you mean by "Time lapse play"? I've turned "time lapse ramping" on and started the intervalometer. It did a lot of checking screen gain and changing luma and ISO settings which I didn't really understand. After a few minutes of doing that, it has started taking shots at about 7sec intervals. If that's what's expected, I'd say it's working?
Thanks,
David
:( >:( :-\ :'( :P I've been waiting for this firmware to come out now for so long. Please Please Please work on it!! I'm gonna be stuck with this camera for quite some time and as you know it's capabilities are very minimal and limited so pleaaaaaaaase get this firmware up and running ! Thanks -Tony
email me @
[email protected]
It's already working, just download a nightly build and try it ;)
Hi,
Do we have a solution for the motion detection issue? Am I the only one that has the problem?
Cheers,
David.
Well, you may have an "unlucky" camera. Do you mind doing these steps?
- Re-download the latest firmware from canon
- Update the camera
- Re-test the motion detection
If it doesn't work, make a video of it (it makes debugging a little bit easier)
HDR video doesn't work for me, iso only changes back and forth when I don't record? I have exp. override: Auto (ON).
Did you check the recorded footage? We removed live view flickering to avoid seizures
Quote from: nanomad on January 03, 2013, 11:06:09 AM
Did you check the recorded footage? We removed live view flickering to avoid seizures
Yes I checked my recorded footage but it still does not work.
Quote from: lengher on January 03, 2013, 08:30:47 PM
Yes I checked my recorded footage but it still does not work.
Fixed, should be in today's nightly builds
Hi .
I am from Russia.
English I don `t know: (
The question whether it is possible to put the firmware now?
Does it not preneset damage the camera?
It is possible. I can't guarantee it won't do any damage to your camera, but no one has complained about it yet (this applies to ML as a whole)
Thank you!
I update the firmware to the lates Canon one. Then updated the ML firmware onto it, still got the same problem. Here's the video of what's going on. While shooting it, I discovered a related problem where the motion detection is triggered when the sensing square is moved to the top of bottom of the screen.
http://www.youtube.com/watch?v=1e9Z6LRX_dg&feature=youtube_gdata
hope this helps.
Hi Nanomad,
(sorry for my bad english)
I have tried "magiclantern-v2.3.NEXT.2013Jan03.60D.550D.600D.50D.500D.5D2.1100D" nightly build in my 1100D and
this is what happened:
You talked about this issue before in this forum, but I don't know if it was solved.
My lenses are Canon 18-55 III. Please, tell me how to remove the error.
Thanks.
Unfortunately it seems to happen with some lenses...the trigger conditions are not known but, from what i've seen, it happens if
- you have an EF-S lens
- the lens doesn't have a constant aperture
- the scene has a high dynamic range
Thank you nanomad, one last thing, will the issue be removed in the future?
Hello!
I tried ML 2.3, but Focus Peaking isn't work on my 1100d. Will it be fixed in the future?
Thanks!
Quote from: FluidMovementMovies on January 07, 2013, 08:34:57 PM
Thank you nanomad, one last thing, will the issue be removed in the future?
If we figure out what causes it, yes
Quote from: Xavierus on January 10, 2013, 11:50:02 AM
Hello!
I tried ML 2.3, but Focus Peaking isn't work on my 1100d. Will it be fixed in the future?
Thanks!
What version? One of the old releases on a nightly build? What do you see on screen? What algorithm were you using (check with Q while the peaking option is highlighted). Also: post a screenshot of the scene
Quote from: nanomad on January 07, 2013, 05:54:35 PM
Unfortunately it seems to happen with some lenses...the trigger conditions are not known but, from what i've seen, it happens if
- you have an EF-S lens
- the lens doesn't have a constant aperture
- the scene has a high dynamic range
Hi!
It also happens to me when i´m using EF50mm f1.8...
Could you come with a workaround?
I'm using the 11 Jan nightly
Interesting... I shoot almost exclusively with the 50 and never experienced it
Hi, couple of things:
First:
I tried to do a bulb-ramping timelapse today. When I set it going, it started doing the calibration stuff - It took a few pictures then tried to draw the graph thing, but soon it got stuck in a cycle of testing the display gain, changing the ISO, and the shutter speed, checking luma and stuff. It did this for ages. I've only had bulb ramping work form me once, on a previous build. However, when it did work that one time, it took ages and did something similar to this cycle of checks. So I decided to trust it and left it to do it's checks then hopefully start shooting the times lapse. However, over an hour later, it was still doing the checks and was nearly out of battery. This is the fourth time out of four tries that this has happened, though this is the only time I've left it for so long. The scene was well lit - I was shooting the sky, (ISO100, f5.6 1/200 was well exposed, though I tried other settings). The scene wasn't moving at all, it was on a tripod too. I've attached the log files from the two tries I did today. I stopped the first one after about 5mins but I let the second go for over an hour. Strangly though, both are only 1kb.
Second: Did you see my video on youtube showing the problem with the motion detection? I'm not asking for any results, just checking you saw it. I can provide more info on request, but if I'm the only one with this problem, it may not be worth it.
Third: I've notice something when viewing images. When I press the zoom button, it goes to full magnification, and when I press it again, it becomes unzoomed completely. Is there any way to turn this off? I find the standard zooming controls easier to use.
Thanks for the continued efforts. I might have a go at compiling myself, to at least see if I can understand it, though I'm not sure I understand the instructions :P
Happy snapping! :)
Edit: I can't seem to add attachments. There is not option for it. I've copied the log files bellow:
ML ASSERT:
ABS(bramp_last_exposure_rounding_error_evx1000) < 500
at ../../src/shoot.c:6087 (hdr_shutter_release), task shoot_task
lv:0 mode:2
Magic Lantern version : v2.3.NEXT.2013Jan04.1100D105
Mercurial changeset : 1f026f967e02 (unified) tip
Built on 2013-01-04 03:04:10 by [email protected].
Free Memory : 345K + 311K
ML ASSERT:
ABS(bramp_last_exposure_rounding_error_evx1000) < 500
at ../../src/shoot.c:6087 (hdr_shutter_release), task shoot_task
lv:0 mode:2
Magic Lantern version : v2.3.NEXT.2013Jan04.1100D105
Mercurial changeset : 1f026f967e02 (unified) tip
Built on 2013-01-04 03:04:10 by [email protected].
Free Memory : 346K + 334K
1) Can you post a video showing the calibration process? Normally it takes a couple of seconds.
2) It works fine, except for the misalignment problem, which is straightforward to fix (Nanomad did the same thing for magic zoom). The misalignment is probably the cause for bulb ramping not working well. Also check spotmeter whether it reads from correct spot.
3) Look in Prefs menu.
4) What steps did you do to get the logs? It shouldn't happen; it means something's wrong with my math...
Thanks for such a quick reply :D
1. I'll do that but it'll take a little bit of time. How long do you want the video? Like, I said, it did whatever it was doing for over an hour. I'm sure it was doing the same things in some kind of pattern or cycle, but I wouldn't know if that pattern or cylce was a minute long, or 10.
2. Spot metering seems to be working fine even with motion detection on. I'll include a demo of that in the video.
3. Got it, shoult have check, thanks + sorry.
4. The log files were just there when I looked on the SD card. Opened them with notepad. When I was shooting: set up scene, took a few test shots, went to "shoot menu", everything off, set timelapse ramping to "Smooth ramping"/"OFF"/"OFF", turned timelapse ramping on, set intervalometer to "16s"/"0s"/"Disabled", turned intervalometer on, pressed the delete button to come out of ML and it started it's checks.
Cheers,
David.
1. Just 2-3 cycles.
2. Check with a small black spot on a white wall, for example (this is how I test it on my cameras).
4. When you get that message, you should also see it on the screen. At which point does this happen? Also, are you in M mode?
1. Hard to tell what a cycle is so I'll just play it by ear.
2. I used my ipod on full brightness in a dark room, moving it into view. It changes from ~4% to ~50% when the screen is under the spot. Tried it both horizontally and vertically. I'll include it in the video.
4. Don't see any "error" message on scren, just things like "checking display gain", "increasing ISO" etc. I wasn't in manual mode, though it did change to manual mode. Just trying it in manual mode and it seems to be having the same problem. Video probably needed.
Hi,
Sorry the video took so long - lack of compatible cameras/memory cards/lenses - ended up shooting using an old screw on 100mm f2.8 + 1.4x converter + extended + adapter. Bizzar setup :p
Anyway, video is here: http://www.youtube.com/watch?v=LFuZxTgyaDc
Again, the camera generated a log file which is bellow. Hope this is useful.
Thanks,
David.
ML ASSERT:
ABS(bramp_last_exposure_rounding_error_evx1000) < 500
at ../../src/shoot.c:6087 (hdr_shutter_release), task shoot_task
lv:0 mode:3
Magic Lantern version : v2.3.NEXT.2013Jan04.1100D105
Mercurial changeset : 1f026f967e02 (unified) tip
Built on 2013-01-04 03:04:10 by [email protected].
Free Memory : 346K + 322K
Hopefully fixed, try again with tomorrow's nightly build. If it's still not working, record another movie just like this one.
Faster response than most things I've paid for, brilliant :D Look forward to giving it a try and will report back
Cheers
Given the bulb ramping a try and it seems to be working. Pretty dull grey weather here though, so can't test whether it is "ramping" correctly. It did the calibration though and started taking the intervaled shots, so looks promising.
The motion detection still has the image mis-aligned but that wasn't meant to be fixed yet was it? Will it planned to be fixed in the future or is it not worth it given the motion detection technically works.
Thanks, can't wait to use these things in anger :)
David.
Quote from: nanomad on December 02, 2012, 11:04:45 PM
Since the 1100D is MY camera (as opposed to the 650D lent me by the team) I'll keep providing updates and fixes (although most of them come from the main ML tree since the 1100D is now officially supported)
;D ;) Very glad to see the 1100D port is not dead and more glad to know it is officially supported. Thanks!
good evening, I found 2 errors, work with ML nightly Jan. 25:
1) The sound and focus icons are not displayed correctly. I understand that is produced by the low resolution of the LCD. Can you solve?
(http://imageshack.us/a/img716/1313/cam00027u.th.jpg) (http://imageshack.us/photo/my-images/716/cam00027u.jpg/)
(http://imageshack.us/a/img138/4707/cam00028k.th.jpg) (http://imageshack.us/photo/my-images/138/cam00028k.jpg/)
2) When trying to format a SD, gives this error
(http://imageshack.us/a/img404/2930/cam00029c.th.jpg) (http://imageshack.us/photo/my-images/404/cam00029c.jpg/)
Thanks, let's see if we can fix it easily
Tell please, what now the most actual version for EOS-1100D 18-55 IS II
In what version least errors.
Functions on landscape shooting are necessary to me basically, function blow \noise = foto is especially necessary
Thanks!
Excuse for my English
There are no "stabler" builds for the 1100D. The nightly builds contain the most up to date code
nanomad, ok
aha)) there it is necessary to press artfully)) hurrah!
How to remove ml?
format card/download original 105.fir/install?
thanks!
Re-run the firmware update you used to install magiclantern, follow the instructions to disable the bootflag then do a low level format of your card from the camera
I'm still unable to use timelapse ramping, also, it crashed when i tried to run it.
Had to remove the battery to make it turn off.
And, when i checked, camera had reached 38 deg. C, is it fine? (i tried to take a screenshot, but, it failed and had to remove battery)
I also got those today with night build:
ASSERT: FALSE
at Memory\Memory.c:188, task cls_task
lv:1 mode:3
Magic Lantern version : v2.3.NEXT.2013Jan27.1100D105
Mercurial changeset : 64e55f572bf9 (unified) tip
Built on 2013-01-27 03:03:17 by
[email protected].
Free Memory : 346K + 285K
ASSERT: 0
at Memory\Memory.c:568, task run_test
lv:0 mode:3
Magic Lantern version : v2.3.NEXT.2013Jan27.1100D105
Mercurial changeset : 64e55f572bf9 (unified) tip
Built on 2013-01-27 03:03:17 by
[email protected].
Free Memory : 346K + 339K
Some workarounds:
- disable HDMI support (saves 170K only 55K, not worth the effort)
- replace AllocateMemory with malloc wherever possible (saves 50-200K) [DONE]
Tomorrow's nightly should behave a bit better, let me know how much free RAM you have.
Other workarounds: disable waveform, vectorscope and cropmarks.
Hi! I installed magic lantern to be able to set manual exposure in video mode using exposure overrides.
However,i noticed a problem when setting custom aperture. The camera says that the aperture has been set correctly but the difference in light and DOF is not as big as it should be. The difference between aperture 3.5-22 looks like the difference beetween 3.5 and 5 (without exposure overrides) I wonder is this a bug? If not please tell me why it happens and how i fix it. Thanks :-)
There were some more questions:
1. How correctly to update nightly build?
I should remove and establish completely all on the new? Or it is necessary to rewrite only files on top of the old?
2. Whether possibility on 1100d will sometime begin shooting by means of a sound?
3. What temperature is considered normal 30с, 50с, 70с...???
thanks.
Very much it was pleasant: it Follow Focus, is a pity that is not present autolock focus and handlock focus!)
But I have already learnt a finger to disconnect an auto focus before shooting and to include back after shutter descent))
Has still found interesting application for Follow Focus+intervalometer:
For example we need to be photographed against mountains, and nearby who is not present that it to make...
By means of an auto focus we are focused on a proper place, Follow Focus focus on the necessary position is tightened very precisely, we include intervalometer, we go on a proper place and we wait shot))
Sorry for my English.
Hi
I'm new in ML and because my 1100D is my only DSLR camera i don't know if what i experiment is a miss understanding/setup from my side or bug.
I give try to timlapse ramping. It work at the end but with a lot of flickering.
For the calibration process sometime it was ok sometime not. it took me a while to understand that i should select from live view a part of the scene with good contrast, otherwise the calibration go in loop and never stop. I did all my test with smooth ramping.
I set up the ref picture for midtone 50%. I don't understand how i can setup the midtone,highlight and shadow from different pictures (bkt for example)
I'm little bit confused with the timelapse ramping submenu.
-What happen if i select everything (auto exporamp,Manexporamp,manfocusramp)
- Does the manexporamp overwrite the autoexporamp?
- can i use the man exporamp with the manfocusramp?
-Is the manfocusramp is linked with the focusendpoint of the focus menu?
-When should i use LRT instead of smooth ramping ?
I try as well to bracket my shot while using timelapse ramping, it works but don't forget to setup the number of frame you want to bracket. if you leave it in autodetect you'll never have the same number of bkt per shot. it start with 3 after a while (because of light change) he take 4 or 5 etc... So if you want to post process with enfuse or other TM tool you should have the same number of bkt (sorry i don't use linux and can't use the Bash script made from ML).
At the end of my test the best result i had was by using ADV.Bracketing with 5 bkt per shot in AV mode with the intervalometer. The result was much smoother and much less flickering.
I'm as well confused with the focus menu I don't get how to fix the start and end point of the focus (do i have to go to LV and back to menu?).
Do you know where i can get a good tutorial about follow focus, rack focus and stack focus? The online ML doc is little bit light....
I Try as well the motion detection feature, it work perfectly at night for lightning.
Sorry for all that questionws, but i'm using ML like crasy for the next 3 daysand i love it.
Thanks to all the team for this fantastic job.
I finally manage to get focus stack working. There is a strange behavior with it. i focus on the start point and then use the focus end point menu to setup my ending point with the wheel, When i run the focus stack it reversing the stack starting with my starting focus point. Let say that i'm focusing first in front of the subject and set up the end point 10 step behind, then when i run the stack the camera start with the first focus point but instead of going forward to the next focus point it goes backward. To bypass that problem i have to refocus my subject to the ending focus point of the stack and the the camera finish to the starting focus point. It's not easy to guess in live view if my new focus point match with the ending point of the ML Stack...
Think I've found a couple of bugs.
1. When shooting with auto-HDR. If you previously viewed images in grid view (zoomed out twice), the auto HDR routine seems to try to meter the whole 9 images, which leads it to take far too many (possibly indefinitely). To recreate: cold start, take a few pictures if the card is empty, press play to view them, zoom out twice (if not already) so you view 9 at once, then set up an auto HDR image, it will take pictures pretty much indefinitely. I need to turn off to get out of it. If you press play and zoom in twice, so as to view images one by one, then try and auto HDR image, it works.
2. I'm not sure about this one, but it seems to be repeatable. If you use bulb ramping with image quality set to JPG LARGE (smooth), it doesn't seem to change the exposure. It just takes photo after photo, even if they are completely blown out, or black. However, if I switch to shooting in just RAW, it works fine. If this isn't a bug, but is just how it's meant to be, it's very limiting, because it reduces the number of possible images in a single time laps by a factor of four. On an 8GB card, that means only about 30 seconds at 30fps.
Still loving ML and hope these things can be easily ironed out.
Thanks to the ML team :)
1. you need to display only one image
2. does it also happen with auto HDR?
1. Could it be set to work out if one image is being displayed and then change it or warn if necessary? It could test whether there is a black grid is present in the displayed image, or it could simply zoom out many times then zoom in twice, which would guarantee it's displaying only one image. It would only need to do that during the first test. Subsequent tests would be the same. It's probably not the most urgent or important thing, but it would be nice for a final "perfect" version.
2. No, auto HDR seems to be unaffected. I just tried and it worked with JPG large.
Thanks
Can you (or anyone else) record a video showing bug #2? I need to see the exact timing of events.
Hi, first of all thanks to Nanomad & A1ex & all the team behind Magic Lantern for this wonderful software.
The second, I got the same problem that fufuheo mentions above. When I change the aperture with exp.override on it doesn't change at all, Av values in the right always stayed between 2.9 and 8. It only happens when I'm using the exp.override in video mode, in the other modes the change of the aperture is fine.
Also in the video mode, when I set the f to a low value f36 for example and I focus to highlight the picture starts to flick, and become dark in some moments and then return to bright again, it seems that the camera tries to set the f correctly.
My 1100D is an spanish one with firmware 1.0.5, I 'm using the Nightly build of Dec 02.
The only lenses that I got is the Canon EFS 18-55mm f3.5-f5.6.
Thank you
Hi, the flickering that I was mentioning above is the same that FluidMovementMovies experienced, but I got only this when I set the f below f5.6
Quote from: FluidMovementMovies on January 07, 2013, 02:39:46 PM
Hi Nanomad,
(sorry for my bad english)
I have tried "magiclantern-v2.3.NEXT.2013Jan03.60D.550D.600D.50D.500D.5D2.1100D" nightly build in my 1100D and
this is what happened:
You talked about this issue before in this forum, but I don't know if it was solved.
My lenses are Canon 18-55 III. Please, tell me how to remove the error.
Thanks.
Update to the latest nightly and report back
Hi!
Thanks for your fast answer Nanomad
I updated to the last night build. And I still have the same problem.
This time (in Video Mode) I set the lens to 18mm with f3.5 in the begin, then I changed the f to 22 and move the camera into the sunlight, this time the flickering was bigger than previously and the motor of the camera started to make noise, opening and closing the diagram.
Later I move the lens to 55mm of focal lenght and set the f to 36, the flickering stopped and the noise too, but the picture was too bright and there were a shallow DOF.
After a few moments, and with camera in the same conditions (55m and f36, sunlight) I tried to autofocus, and I noticed that camera really close the diagram of the lens during the focus, but when it finished the camera outputs again a bright picture.
Thanks and I hope that has been helpful
awesome job guys...!! just installed ML on my 1100D and it works fine...!! (so far)
would like to know the chances of changing the video resolution to :
a) downsize small 640x480 (or similar sized) videos
b) upsized 1080p
thanks again for the great work you guys are doing, & i wish i could contribute somehow but am handicapped with no knowledge of programming etc...!! :(
regards...
I just installed ML on my 1100d
Sadly I came for the audio settings and shocked that I couldn't find the analog gain where i can reduce the hiss sound of the cam
Is their something wrong with mine or is it still in the process? :'(
I fiddled with audio stuff for a bit and come to the conclusion that Canon already did their best with this crappy chip. Turn down analog gain and you can't hear anything. I may put some research into it after I'm done with the 650D
Hi again nanomad,
I hope you can solve the flickering (the same as Arcanemon). Now it happens a lot more, and it's really annoying, I can't record anything with exposure override. I reinstalled ML, but it keeps happening. Please help, and thank you very much for your job and for your time.
Quote from: a1ex on February 02, 2013, 09:28:41 AM
Can you (or anyone else) record a video showing bug #2? I need to see the exact timing of events.
Been busy. Just tried to re-produce this and film it, and typically, it worked fine. (This is intervalometer with bulb ramping in JPEG). For now, I suppose we'll just assume I did something wrong before, and that it works fine. I don't think I did do anything wrong, but who knows. I'll keeo a look out for it, hopefully I'll have more opportunities to use it in the coming weeks.
Good stuff as always,
David.
great job here, just waiting for this porting since first known about ML after bought my 1100D...
been used for view week since magiclantern-v2.3.NEXT.2013Jan07 nightly build, really it boost this tiny entry level camera!
For some reason, I try to turn on Cropmarks (it turns green when it's off and vice versa), and Spotmeter in live view with no luck, I think, thats the feature I'll use alot since I shoot mostly with old manual lens.
Hope this won't take any hard effort to make it happen, since spot metering and WhiteBalance with Kelvin is the most prominent lack of feature of 1100D beside above models, and I allready got my adjustable Kelvin WB,,,, ;)
Wanna to join testing... Got some doubts about installing:
1. install properly the stable release of ML 2.3 on 1100d
2. after this delete this files on my SD card and replace with up-to-date nightly builts
3. run ML
Is that right? Am sorry for my low IT intelligence :P
With the 1100D you can go straight to the nightly since it's not supported in the stable release
Thanks :D Installation without problems... I appreciate your work over here. Need several days to test the focus stuff (for manual focus wide open aperture photography) and will report. For now I notice that zoom booton in regular play mode (to see and check photograph, its sharpness etc) is skiping the mezzo steps - after one touch immidiately to max. magnification.
Heehee, I fell into the same trap! 8)
Just have a look in the ML menu, there is an item to change zoom behavior to the old style.
I'm using some January snapshot now for some time without problems on my 1100D, but I still had not enough time to play with the features, too bad. So most of the time I'm assuming that it's just my fault/stupidity...
One issue: I sometimes come here just to check if there's something new. The first posting in this thread changes veeery rarely, and the changelog.txt is hard to read. Am I right that although the 1100D port will stay in state "release candidate" as long as the 650D port is in work, just because the 650D has prio over it? If so, I can stop checking the homepage and the first posting to not miss the release anouncement, right?
(Or is the main reason for not announcing the 1100D port really what the first posting is saying: "The main issues that are holding ML are: Lack of phisical buttons"? In this case, I'll carefully watch my 1100D if someday new buttons magically appear. ;) )
The status is RC until there's a new release of ML :P
Hi again!
This weekend I'd been in an encounter and I made a lot of pics and videos, so it was a good chance to test the flickering and the aperture issue again.
This time I have borrowed an 18.135mm IS Canon Lenses and I got the same problems with the video, I mean when I tried to close the aperture in the LiveView it never did it and if the camera tries then start to flicker, but when I used autofocus in LV the camera effectively close the aperture. Also I noticed that this happens also if I used Exp. Override in Manual Mode, but only if the LV is on.
I will try again a copy of the RC3 that I got of ML, cause as I remembered when I used before I didn't have this problems with the LiveView mode.
I'll report back
On the nightly build, it can't find the bootdisk flag. I don't know what's wrong, it's on manual, live view, etc.
Are you talking about the fir?
Never mind, forgot to make the card bootable. Actually reading the installation guide helps.
nanomad hello. After using avanced bracket, in the image review, does not work the option "image review --- canonMnu-> HoldPLAY".
and
ghost image is not working properly, a screen with noise
thanks
Hi! Finally I tried the RC1 version of ML on my Canon 1100D.
But the flickering/aperture issue stills there. There is no change of what I experimented before.
Finally I have to post a experiment that I did. With exp.override of, I move the Canon's exposure compensation system to a point where the aperture was at the lowest f point (f22 in 18mm I mean), then I blocked it with the * button.
After that I set exp.override on, and the exposition values to the same that I blocked before, it still doesn't work. The camera sets again the aperture to it's highest number (f3.5 in 18mm).
Are all of you sure that when you close the aperture of the lenses with the LiveViewon, it works correctly?.
Can you upload a video of it?.
Thanks
Hi Nanomad. I've been filming this weekend and i found a problem. In exp.override, I can't control the aperture. I change it but it does not effect, the exposure doesn't changes.
Also, when I want to format the SD card, the camera says "shoot_malloc_error. Please reboot" but I can format it.
Is this an important error? Please help.
All in magiclantern-v2.3.NEXT.2013Feb16.60D.550D.600D.50D.500D.5D2.1100D nightly build.
Hi everyone,
i have problems using the bulb ramping feature on my 1100D. It always says "The scene is not static" or keeps calibrating forever. Did anyone get this feature running?
Thanks!
Post a video of the calibration sequence.
I got this strictly for manual exposure in video and it works fine.
I don't know what you're doing wrong to get that exposure flickering, I only get that with HDR mode on. Try disabling everything except manual exposure and see if it still flickers.
Also, did you update firmware to latest?
Hi Criollo!
As I commented in another post, I got the latest firmware version of Canon (1.0.5).
Also I disconnected everything except exp.override, but the problem stills there.
It seems that the problem is refered with the LiveView, cause when I used exp.override in Manual Mode or in other photo modes( except video) with the LiveView on, and I set the aperture of the lenses in a low value (f22 for example) it doesn't do anything, the picture is too bright ( yes I checked the shutter speed and ISO too), but when I took a photo, the photo is taken correctly.
However in video this doesn't happen, I got what I see from LiveView, so no matter how I tried to change the aperture that it doesn't do anything.
The flickering issue that we are mentioning, is that sometimes the camera realises that the aperture that you set (f22 again) is not the one which is showing in the LiveView so it change is to the correct value, but then turn back again to high f number (f3.5 for example), of course while doing this, you can hear a loud noise of the lenses "crying" what is no good.
This flickering doesn't happen everytime that you set a low f value, it only happens ocassionally especially when you move the camera to a highlight.
I hope that I got explained
Greetings a1ex, nanomad and all Magic Lantern forum members. First off thanks to those whom make this brilliant firmware possible. To the administrators, If I may, I've got a quick question regarding the FPS override feature. Lets say I'd like to record a video clip at 24 fps with a shutter speed of 1/48 and a shutter angle of 180 degrees to help with the artificial interior light flickering, and to get that "cinematic effect"at an indoor event. Because internal audio will be disabled during the recording process when using the FPS override feature, I would have to use my external Zoom H1 microphone to capture audio. I would also have to use a clap board etc., to sync the video and audio in my NLE. My question is has there been any talk about enabling audio at the start of recording a small time frame of maybe 5 seconds or even less, then automatically disabling audio. That way the clap board sound can be used to sync the audio and video that will be captured internally into the Canon. I would then sync my internal captured Canon clap board sound audio and video with the clap board sound of my external Zoom H1 mic in my video editor. However, I would still have to use my external mic to capture audio for the duration of the video, but as you can see it will be a tremendous help to our editing workflow. If this has already been discussed in the forum I do apologize. Thanks. 8)
The only way I can recreate the flickering issue is set the FPS mode to low light instead of exact fps, or enable HDR video; I'm using a manual lens and not a automatic diaphragm lens so the camera cannot control the aperture.
I'm about to update to the latest build. Got some crash logs and some other logs (7 in total). They're from the 20th Jan build?
Do you guys want them or are they too old to be of any use? The crashes happened straight after boot. I took out the battery and started up again and all was well. Never a perminant problem.
Thanks for ML!
David
Post them; there were no startup changes that I can think of.
Just the crash logs (4) or the other "logs" as well (presumably for HDRs?). If the other .log files are for HDRs, I've had no trouble with HDR.
How do I attach them? When I click "Attachments and other options" I just get 3 checkboxes. If it's just the crash logs, I can probably just copy and post them.
You can use a file sharing service like https://mega.co.nz/
Easier just to hoast them on my server than create an account I won't use. Link is here: http://www.spanglefish.com/davidjamesalban/documents/ml/logs.zip
I'll take it down ina month or so. Should be enough time.
Cheers.
Canon code ran out of memory when indexing the photos on the card.
How much free memory do you have now?
I just upgraded my firmware now.
However, during the period I had those crashes, I had lots of memory most of the time (usually >3GB). However, I did shoot some time lapses every now and then which may have filled it up until I unloaded and deleted all the images. I can wait to see if it does it again, and then record how much memory is free on the SD card, then let you know?
Is it an issue with the Canon side of things than the ML side? Like I said, none of the crashes bothered or affected me. Just off/battryout/batteryin/on worked each time.
Btw, I've got some issues with the motion detect in the latest build. It's same as some I mentioned before. If the sensing area is "large" it always takes pictures. And if the sensing area (at other sizes) is moved to the top or bottom, it always take pictures. I'll get a video together when I have time and post it, but those are the same symptoms I had that I posted in a previous video.
... RAM memory, look in Debug menu.
Right now: "301K + 442K". But I've just upgraded, presumably you needed the figure from the time of the crashes?
Sounds a bit better. The 60D still has occasional trouble with 1 MB free in the second buffer...
Ok, well I just keep you posted, but record the figure at the time of any crash. Can it not add that to the crash log?
I'll work on the video too. Cheers,
David.
Can't seem to be able to use the arrows to control the aperture/shutter speed, has anyone else got this working or is it just not working yet?
massive thanks to all contributors, loving the firmware
Hey Folks,
Today I have tried out the latest ML Nightly-Built on my 1100d. It's a truly amazing piece of work... simply awesome! However, after playing around a bit I came to the point when the aperture and/or Iso began to flicker in a high dynamic range lightning environment. I tried out different things and found out, that the flickering stops temporarily, when you lock the lightning settings in the basic canon menu by pressing the *-button. (As long as the settings are locked).
Greets and Thumbs up, Eric
Hi, I installed ML again on my 1100D wednesday to record a live show so I needed the auto restart feature that worked fine on my 5DII.
On the 1100D when the 4Gb file limit was reached a popup appeared to say video has stopped ... but no autorestart.
Is it a known bug ?
Thanks.
MiK
Quote from: alband on March 17, 2013, 04:20:08 PM
Btw, I've got some issues with the motion detect in the latest build. It's same as some I mentioned before. If the sensing area is "large" it always takes pictures. And if the sensing area (at other sizes) is moved to the top or bottom, it always take pictures. I'll get a video together when I have time and post it, but those are the same symptoms I had that I posted in a previous video.
http://www.youtube.com/watch?v=pCM_nI7Fc0Y&feature=youtu.be
Aspect ratio has messed up when I uploaded to youtube which is odd. Still shows the issue though. It seems there are zones at the top and bottom, if the detection area is moved into them, it triggers (the trigger number shoots up too). When the detection area is big, it's always in those zones. That's my diagnosis anyway. The big detection area will be really useful for me if/when it works.
Thanks,
David.
Hi guys
I am a newbie in photography and recently bought canon 1100D as my first DSLR..I am planning to install magic lantern in my camera and I have some doubts regarding magic lantern port to 1100d,which i hope some of you can enlighten me on..
1.Once installed,does the exposure override mode in magic lantern allow user to manually decide aperture,shutter speed and iso when shooting video,with 18-55mm kit lens.?
2.How can i make my sd card bootable?
Thanks in advance..
Hi guys.. I want to ask about Trap Focus. When I watched the demo on vimeo... trap focus (continuous mode) works perfectly that every time a car passes by it takes a shot... In my case, I turned it on in cont. mode, it took picture when the subject gets in focus, however it didn't take any more pictures after that... The camera just beeps (focus confirmation beep) when the subject gets in focus... Do I need to change other settings?
I'm using Canon 1100D. I know ML on this model is not yet fully functional.. i just want to ask if this is why my trap focus doesn't work properly...
I installed latest nightly build in my 1100D..I'm really impressed with the features..My heartiest thanks to the team behind this amazing product..Most of the functions i tried worked flawlessly,except exposure override.
When i set the magic lantern to exposure override mode ON,everything appeared to be normal in live view mode-there were no flickering or frequent "dimming and brightening" experienced by some previous posters in this thread.Shutter speed and iso could be set as desired.But the trouble was with aperture-It didn't change as i expected..It didn't stay in the widest aperture as mentioned by some previous posters.I set the aperture to the widest 3.5 limit and increased gradually with live view focused on a lamp..There was incremental dimming of the lamp with each increase in aperture from 3.5 upto 28 but to a much much lesser level than originally expected level of dimming,ie increase from 3.5 to 28 seems like 3.5 to 5.6..It seems like the decrease in aperture with increase in f value is like about 1/10th of the original expected value..Could this be rectified in coding?
Does this happen in both movie and photo mode?
Sorry for late reply..It happen only in movie mode..not in photo
Hi!,
For me it happens in all the modes when the LiveView is ON; So I think that the aperture issue is only in LV.
If you try to focus when you are recording video, then the aperture changes correctly, but then it came back.
I recently made a video of it, I'll upload it this afternoon so you can see.
However, THE FLICKERING ISSUE APPEARS VERY SOMETIMes, BUT THE APERTURE ISSUE IS ALWAYS THERE.
I'll wait back for your answer.
Hi!,
Here is the video with the Aperture issue that me and others commented.
http://www.youtube.com/watch?v=xnSFDjDl9DU
I was using the video mode but as I said before it happens in every mode when the LiveView is on.
Other things:
- Build used: Nightly build from 26 March 2013.
- Lens used: Canon EF-S 18-55mm III non IS.
I added some annotations into the video that I hope clarifies this problem.
Thanks again to all the ML team for this wonderful software.
Hello.
I'm new here and first I would like to thank all the guys that are making ML possible on 1100D.
I'm not using much of ML features, but the one's that I'm trying to use - don't work.
1. Taking screenshot: when I want to take a screenshot of either ML or any Canon menu, the timer end and nothing happens except the camera freezes and I need to remove the battery.
2. When using FPS override (to make timelapse), droping it down to 0.2 FPS makes camera freeze (I can start recording, but when I end it, it freezes) EDIT: Looks like I set it to 2 fps but when I open a video on PC it's normally 30 FPS :/
3. ML sometimes resets itself after I start the camera up and I need to set it up all over again (SOLVED with exporting to script, EDIT: Can't run script, out of memory)
4. Will try more features when the weather changes, it's all grey and snowy now :S
Setup using: ML v2.3.NEXT.201 3Mar31.1100D105
Free mem: 303k+442k
Lens: 18-55 EF-S IS
1. just found a fix for the same problem on 60D
https://bitbucket.org/hudson/magic-lantern/commits/e5cf90d28d61
https://docs.google.com/spreadsheet/ccc?key=0AgQ2MOkAZTFHdFFIcFp1d0R5TzVPTVJXOEVyUndteGc#gid=2
2. read the user guide
3. how to reproduce?
1. I don't understand that fix...what should I do, where to find those files? Or you will update it in next nightly? EDIT: Ok, I see that the new nightly is out. Gonna test it.
3. Please define that, I can't really understand the question...How to reproduce what? The script? I just ran it...
EDIT: Deleted old ML, pasted the new one and turned on the camera...and ML crashed, I got this to send it to the devs
https://www.box.com/s/vg8945cdrjgyru2e8m8t
EDIT2: The April 02. version works (screenshot doesn't) but when I switch to LV I get "Null pointer error 0,100" writen with red letters in top left corner.
Reverted to 31.March.
Flickering is caused by broken aperture control - it always wide open, but if you set it to higher number - you will not change aperture, but you will experience flickering with changing aperture - from wide open to f-number, you set in ML, back and forth.
So, I recommend to always change your aperture value to your lowest f-number, to avoid flickering. (it's hard with zooms with variable max f-number - it will stick to highest f-number after your come back from tele- to wide- - you need to correct aperture accordingly if you don't want flicker).
Thank you Rush for your answer.
But there is any code-fix for that broken-aperture control?.
Is it possible to correct it?.
This aperture issue only happens in a few Canon 1100D? Or everyone else has the same problems?
I've double-checked the aperture constants and they seem alright. It only happens on 1100D.
Feel free to grab the source code and investigate it.
Ok, I got some C skills programing but no too much.
In which archive are the constants?.
Thanks
I'd checked the file consts.h in the 1100D source code, and in the video section I've seen this:
#define VIDEO_PARAMETERS_SRC_3 0x70C0C
#define FRAME_ISO (*(uint16_t*)(VIDEO_PARAMETERS_SRC_3+0x8))
#define FRAME_SHUTTER (*(uint8_t*)(VIDEO_PARAMETERS_SRC_3+0xa))
#define FRAME_BV (*(uint8_t*)(VIDEO_PARAMETERS_SRC_3+0xb))
#define FRAME_SHUTTER_TIMER (*(uint16_t*)(VIDEO_PARAMETERS_SRC_3+0xC)) // not sure
So, as I notice, there is not constant there for the APERTURE. After that I checked the same file but for the 600D. And I found this at the same section:
#define VIDEO_PARAMETERS_SRC_3 0x70AE8 // notation from g3gg0
#define FRAME_SHUTTER_TIMER (*(uint16_t*)(VIDEO_PARAMETERS_SRC_3+0xC))
#define FRAME_ISO (*(uint8_t*)(VIDEO_PARAMETERS_SRC_3+0x8))
#define FRAME_APERTURE (*(uint8_t*)(VIDEO_PARAMETERS_SRC_3+0x9))
#define FRAME_SHUTTER (*(uint8_t*)(VIDEO_PARAMETERS_SRC_3+0xa))
#define FRAME_BV ((int)FRAME_SHUTTER + (int)FRAME_APERTURE - (int)FRAME_ISO)
So you can see in the 600D:
#define FRAME_APERTURE (*(uint8_t*)(VIDEO_PARAMETERS_SRC_3+0x9))
there is a constant for the aperture, could be that the problem?.
Also FRAME_BV is defined different:
#define FRAME_BV ((int)FRAME_SHUTTER + (int)FRAME_APERTURE - (int)FRAME_ISO).
I hope that it has been helpful.
From these, you can override ISO (as in HDR video) and shutter (via FRAME_SHUTTER_TIMER). Aperture... I couldn't change it from there on my cameras, but it's worth trying on 1100D.
Aperture is changed via exposure override (CONTROL_BV constants). With expo override enabled, ISO and shutter are working?
Other things worth trying:
call("aewb_enableae", 0)
LVAE_MOV_M_CTRL=1
or... just unscrew the lens a bit :P
Tried the new nightly, ran some test and this is what I got...
CRASH DUMP >> https://www.box.com/s/vg8945cdrjgyru2e8m8t
Also, screenshot still doesn't work.
Hi good people, long time lurker here. Great job on the firmware!
On behalf of your 6th of April 2013 nightly, I am hereby dumping some crashlogs:
https://mega.co.nz/#!KcchmKIY!Enbsuk0kANdg1Br8MzFTvzN_bEMvvjmyY3QADi9wxJM
This is probably not any news, but the crashes don't
actually crash the camera (i.e. nothing freezes), but are mild nuisances, or they probably affect the background jobs. Again, another possibly known fact is that I've always been informed by the firmware that there is not enough memory (for malloc, not space on card), on every nightly since December (which is when I started testing ML).
Same as:
Quote from: zagi988 on April 06, 2013, 07:09:24 PM
Tried the new nightly, ran some test and this is what I got...
CRASH DUMP >> https://www.box.com/s/vg8945cdrjgyru2e8m8t
Also, screenshot still doesn't work.
Also, this seems to have been reported earlier by a gentleman, movie restart doesn't work. I've tried modifying the 'Powersave in LiveView' settings, under ML and the 'Auto power off', under the normal Canon menu (should they affect the restart in any way), but still no success: the movie ends at ~ 4GB (as it should due to the FAT32 limitations) and if left alone, the mirror flips back and the camera enters stand-by.
Again, though, marvelous job on the firmware, it's been a lot of fun so far, hopefully I'll be able to help out in about 2 years when I'll know enough C.
Peace out!
EDIT: I forgot to mention that the crashlogs are generated ONLY in LiveView in these cases: 1) when I turn on LiveView and 2) when I press the autofocus button (at first it was only the half-shutter, but then I decided to modify its function into AE lock and to autofocus with the former AE lock button).
Thanks for the reminder about movie restart not working ;)
For movie restart, one has to check ErrCardForLVApp_handler (or wait_for_lv_err_msg).
Movie restart fix pushed, wrong stubs found on the 1100D, 650D and EOSM
Nice, thannks. I hope current nightly-builds are stable enough for my basic use :)
Hi everyone, I'm testing the lastest nighty build on 1100d , 07 april 2013, the fonts are better than the "non nightly" version, and the user interface is more clear, and pratical, but I have a problem and a question:
The problem is:
It always crashes on liveview. The functions that works are the intervalometer and the bracketing, but everytime I launch liveview it crashes.
Screenshots doesn't work and get the camera mad, need to restart.
The question is:
Will it be an Audio Shoot trigger like is written in the manual?
I will find it very useful
I'm a student of New Tecnologies for Arts and I very appreciate your project! Keep on! my 1100d needs to "unleash the beast" :)
All the Best
astonealive
Canon Eos 1100d
Do you have logs on the card?
Hi, I'm here to report that the 2013Apr09 nightly does not work when updating.
Here's what happens:
I go to enable the bootflag from the menu, it manages to show the success screen with the green text and when I try to start the camera again, the red LED lights up and stays lit indefinitely, the screen remains black and no button seems to work. Turning off the camera changes nothing, as the LED is still lit, so the only option is to take out the battery and format the card externally.
For some reason, when I first tried the nightly, the camera refused to start even without a card (which is when I panicked), but for some reason the 2nd time worked just well.
I've used both the original Canon battery and a replacement, both fully charged.
No files have been created on the card after the incidents.
i had the same problem, luckily i had the last version of the nightly build that i put on my 1100D, on my computer and i put the files back on my card and it works again
Quote from: nanomad on April 08, 2013, 07:32:04 AM
Do you have logs on the card?
sure. it's in the spoiler
[spoiler]
[39] AeWb: NULL PTR (0,e1a00000)
pc=ff07dbd4 lr=ff07dbd4 stack=137058+0x4000
entry=ff1ee5d8(9b9680)
e1a00000 e59ff005 e59ff014 e59ff014
e59ff014 e1a00000 e59ff010 e59ff010
[39] AeWb: NULL PTR (0,e1a00000)
pc=ff07dbd4 lr=ff07dbd4 stack=137058+0x4000
entry=Magic Lantern version : v2.3.NEXT.2013Apr07.1100D105
Mercurial changeset : a70a44f9b6e8+ (unified) tip
Built on 2013-04-07 02:03:38 by
[email protected].
Free Memory : 303K + 364K
[/spoiler]
Alrite, should be fixed already. Try with tonight's build
Quote from: 47Crows on April 09, 2013, 07:24:46 PM
Hi, I'm here to report that the 2013Apr09 nightly does not work when updating.
Here's what happens:
I go to enable the bootflag from the menu, it manages to show the success screen with the green text and when I try to start the camera again, the red LED lights up and stays lit indefinitely, the screen remains black and no button seems to work. Turning off the camera changes nothing, as the LED is still lit, so the only option is to take out the battery and format the card externally.
For some reason, when I first tried the nightly, the camera refused to start even without a card (which is when I panicked), but for some reason the 2nd time worked just well.
I've used both the original Canon battery and a replacement, both fully charged.
No files have been created on the card after the incidents.
It has been the same! I almost died! I format the SD and the problem was solved. I dare you to try other versions in evidence until it is the final version.
Thanks for a great job!
(Sorry for the orthography. Google Traductor)
I'll investigate the issue, but I suspect it is related to all the NPE we are now catching (bugs in canon code)
OK, since my most recent post did not receive a response- on to the next one. This manual aperture control issue in video mode that has been a big topic for T3 owners, is really strange because for me since I own the 50mm prime lens, the exposure override ON option works perfect for me when I want to manually control the aperture when recording with the 50mm in use. The only time exposure override does not manually control the aperture is when I use the 18-55mm II or my other kit lens that is listed below. It seems to be just the kit lenses that seems to not work properly, at least for me.
I can confirm that. It works fine with the other non-kit lenses I have .. ... but they are all primes :P
Quote from: nanomad on April 14, 2013, 09:52:25 AM
I can confirm that. It works fine with the other non-kit lenses I have .. ... but they are all primes :P
Yes my friend, confirm indeed. It is peculiar. Is it not? 8)
Hi there
Have to report same bug.
Don't know why, a few weeks since last update in my camera, today i've downloaded latest nightly, and my 1100D do not start in any way.
When i close the batt door, red light goes on (with no blinking) and I cant do anything else. Tried with set button, in P mode....no way. I tried also formatting sd card in my pc, then, formatting on camera (starts well without ML), and then reinstalling ML: same problem; red light on, camera dead.
I had to ger off ML and use original firm with card formatted...
Any solution?
Quote from: snakesanti on April 14, 2013, 08:28:56 PM
Hi there
Have to report same bug.
Don't know why, a few weeks since last update in my camera, today i've downloaded latest nightly, and my 1100D do not start in any way.
When i close the batt door, red light goes on (with no blinking) and I cant do anything else. Tried with set button, in P mode....no way. I tried also formatting sd card in my pc, then, formatting on camera (starts well without ML), and then reinstalling ML: same problem; red light on, camera dead.
I had to ger off ML and use original firm with card formatted...
Any solution?
The latest nightly build that works for me without any obvious incident (other than exposure override option not working with my kit lenses) is the March 31st nightly build. Other than that all of the April nightly builds give me the same experience you have had 8)
QuoteThe latest nightly build that works [...] is the March 31st nightly build.
Maybe somebody did an April's Fools joke and forgot about it? ;D
That's actually a very valuable information. I can bisect and hopefully find the offending code
Hi!!
I've got a problem:
When I want to format the card, my camera says: "shoot_malloc error: Retrying" and it beeps. When it beeps 5 or 6 times, it says "Restart your camera (shoot malloc error)
If I format the card, (even choosing keep ML) it deletes Magic Lantern.
Free Memory: 301K + 442K and it says "Not enough free memory"
All in magiclantern-v2.3.NEXT.2013Mar08.60D.550D.600D.50D.500D.5D2.1100D
Thanks!
Quote from: FluidMovementMovies on April 16, 2013, 10:49:46 PM
Hi!!
I've got a problem:
When I want to format the card, my camera says: "shoot_malloc error: Retrying" and it beeps. When it beeps 5 or 6 times, it says "Restart your camera (shoot malloc error)
If I format the card, (even choosing keep ML) it deletes Magic Lantern.
Free Memory: 301K + 442K and it says "Not enough free memory"
All in magiclantern-v2.3.NEXT.2013Mar08.60D.550D.600D.50D.500D.5D2.1100D
Thanks!
Same here, for quite a while, I can't pinpoint the version.
Quote from: 47Crows on April 15, 2013, 08:19:50 AM
Maybe somebody did an April's Fools joke and forgot about it? ;D
Good one lol 8)
Not enough free memory :(
And the new boot method doesn't work on the 1100D :(
I'll probably disable that feature
It should be rewritten to use memory chunks, see g3gg0's test code. 50D also needs it.
1100D port is now working again :)
Next stop: Memory chunks :)
Thanks man/men, gonna try it in a few hours.
I'll push a new build then ;)
Quote from: a1ex on April 17, 2013, 08:48:37 AM
It should be rewritten to use memory chunks, see g3gg0's test code. 50D also needs it.
Looks like it's working ;)
A 0x45E00070 S 0x00AC8000 R 0x00AC8000
A 0x42AF16C0 S 0x0030C000 R 0x0030C000
A 0x45AE8100 S 0x00314000 R 0x00314000
A 0x44600070 S 0x00F18000 R 0x00F18000
If i got it right, I now can cycle the chunks and use them to store stuff. Right?
Yep. Add files to first chunk, and when it's full, move to next chunk.
I can confirm that the 21st of April works just fine.
Minor bug, though and I am not sure from when it is, I just noticed while testing today's nightly:
I activated Follow Focus and messed around with the settings and the focus, until it sort of broke. It said "Focus error :(", and from that point the autofocus, the autoexposure and the shutter was dead (I couldn't take a picture at all). I turned off the camera (it should be noted that I was in LiveView, so that I could mess with Follow Focus) but the mirror did not come down. I turned it on again, it started in the non LV Canon interface (even though the mirror was still up), I pressed the LV button, it went right into LV as if nothing happened, then I tried to turn LV off to get the mirror back down and it didn't work, so I turned off the camera again, still no mirror action. Now, when I turned the camera back on, the same happened, the Canon interface showed up BUT, when I tried to turn off the camera, the interface was still there (as if it had crashed), so I just took out the battery, put it back on and when I closed the battery lid, the mirror came down. (note: during the testing of autofocus and autoexposure and taking a picture I tried deactivating autofocus from the lens, which is a kitlens with variable aperture - the EF-S 18-15mm f/3.5-5.6 IS II)
Again, I am unsure as to when this became a problem since I always fiddled around with the focus and nothing went wrong before.
I tried to the problem, but it didn't work, the build continued to function without incident.
(No crash logs have been created, only 2 "ROMx.bin"s, of 16 MB each, way before the incient.)
The focus error is not really an error, more like the lens not responding to focus commands. It happens with a lot of lenses.
The bug you reported, instead, seems a lot more serious.
Hi everyone!
Is the EF-S lens flickering fixed in this new nightly?
Thanks in advance!!!
Hi,
do you have a clue why you can´t control aperture in video mode with the 18-55mm Kit lense? Is it possible to control aperture in fps override mode at for example 2fps with the 50mm prime lense? Would be great for daytime timelapse without ND-filter.
thanks..keep up the good work!
Is it ok, that I always see focus over time rolling (rolling "histogram" look like) in the bottom of screen?
I can't find the way to turn it off. I want to turn it off to save cpu cycles...
In 600D it shows only when trap focus is enabled.
ps: seems that it only appears in 4:3 screen layout.
BTW, there is still bug with aperture control and flicker. And in-camera formatting shows malloc error (auto movie restart don't work too)
Aperture control is still bugged, the focus stuff is due to the 4:3 layout, not much we can do (and it doesn't really use that much cpu anyway).
The malloc error requrires a new memory management library that I'm polishing up
Hi,
When i use bracketing in ML modus everything is working ok, i always use 7 pictures.
When i dont use ML (pressing SET and turn my 1100D on) the bracketing modus of 7 pictures is still working ???
I have to manually turn it of in ML modus before going to the normal firmware.
You are doing a great job with this firmware !
Uhm, what happens if you remove the card?
Without the card it is taking 1 photo.
Uhm, so some ML task is running anyway. Time to check the code
Ok, take the time you need for it :)
So I'm trying the May 2 nightly, and I can't get Focus Peaking to do anything. It seems that I can't enable GlobalDraw. The options under Overlay/Global Draw are either OFF or LiveView (a previous nightly from February had ON instead of LiveView, I think). Now OFF, I understand. But when I select LiveView, all of the other Overlay entries remain greyed out. If I select one, there's red text saying "GlobalDraw is disabled, check your settings". Well, that's the Global Draw setting right there, right?
Maybe Focus Peaking doesn't work on the T3? Do I have stale settings?
Thanks!
Go to liveview, hit DISP a bunch of times. ML only works when canon overlay are disabled
Ah! That's it. Thanks for that. Is is a bug that the config screen says "check settings"? It appears to grey out the settings when Global Draw can't be activated due to the Canon overlay.
It probably can be made better. Suggestions?
Hi Everyone,
I'm taking a DSLR Video class and the instructor has recommended we all download Magic Lantern, but my camera is the T3 and, of course, it isn't ready. Does anyone have an idea when it will be finalized? We're going into week 3 on Monday, and I just want to know if this is even option, or if I have to join the Nikoners and go without. I have already tried using the nightly, but, being a noob, it's lost on me.
Thanks,
Lena
It is available through the nightly. Follow the normal install instructions. Waiting for a proper release won't make that process any easier.
It's not the installation process that I want to be easier, I've done that. I don't see the menu buttons or any indication it's on my camera, except for some small yellow numbers in one of the indicators (can't remember which one now and don't have the camera with me.) I thought that was indicative of the 'no buttons' issue that the build is lacking? Or maybe I just don't know how to use the software...? :/
Press the Av button one time, and then one of your arrow keys, always works here.
Quote from: nanomad on May 05, 2013, 09:36:49 AM
It probably can be made better. Suggestions?
Well, the main thing that I'm seeing is that when going into the ML menus from non-LiveView mode, all the menu items are greyed out, and when selecting one, the help text at the bottom says (in red) that Global Draw is disabled. When I start the ML menus from LiveView, the menu looks right (not greyed out and no red warning text).
I think it would be better that when coming into the ML menus from the non-LiveView mode, the text wasn't greyed out when GlobalDraw is set to LiveView, and the red warning text didn't say "Global Draw disabled" in red, but instead said "Global Draw is only available in LiveView" in orange or yellow. If Global Draw is disabled, then the greyed out menu and current red text makes sense.
Does that make sense?
Wait a minute, red text was in a prehistorik version...
Well, I'm currently running a May 2, 2013 nightly build. The red text is way at the bottom of the screen, like a help text (not the menu text, if that makes sense).
Quote from: Urbexgamma on May 09, 2013, 08:04:53 AM
Press the Av button one time, and then one of your arrow keys, always works here.
Thanks! Duh. :/
Hi there.
My cam seems to be dead... :( :o
I didn't use ir along a week, and it doesn't swich on...
I let de battery charging during my work time....hope ML only ate batt...anyway, it isn't normal, i've charged it a week earlier....
Will tell you what finally happens (hope continue having a reflex)
The 1100D shouldn't be affected by the shutdown bug in theory... But this kind of stuff may happen. Let's hope it's not an hardware issue but just a flat batter
There is another kind of shutdown bugs, where DryOS state is corrupted. These are usually ML bugs, and can be fixed if you tell us how to reproduce it.
Tip: when the shutdown is not complete, the camera will not turn back on. This should help identifying the stuff that causes problems.
Finally the problem was empty battery 8) 8)
It should be because I usually forget swich off my cam, and it remains in standby mode...with ML eating all energy.
Anyway, my fear were big enought (and my girfriend's face too >:()...i'll be a time with original firm in my cam...
Thank you all guys!
So, since nanomad seemed to have a little bit more time on his hands and wanted suggestions, I thought of a thing, which might or might not have been said before.
Picture this if you will: I would really appreciate a ML function that allows the user to save a certain exposure preset (kinda like Expo. Presets, but not quite). At the user's choice, the exposure presets can be dumped into files (expo config files, whatever you want to call them) and/or sent directly to manual mode (M)'s exposure settings. (somebody likes to use formatting a lot)
I don't know how useful other people might find it, but I've had times when I wish I'd jotted down the exposure for certain places (say, a poorly-lit room, where you don't have access to a tripod, but have managed over a year to find a good exposure preset for it). True, you can note down the exposure settings, but what's the fun in doing that?
tl;dr, I wish I could have a "send exposure preset to manual/file(s)" function. I know, lack of buttons. Say... half-pressed shutter + the Q button, or the DEL (although you use DEL in conjunction with the wheel to compensate EV, but I doubt a quick tap will affect it).
I certainly had other ideas, way before I'd found out about ML, but obviously, they come and go. I'll be sure to come back if they do.
Peace.
There's a pull request pending called custom C-modes (google what a C-mode is on a canon camera). But it's so complex i didn't review it yet. I guess I could look at it after porting RAW stuff to the 1100D :P
Quote from: nanomad on May 19, 2013, 07:10:08 PM
There's a pull request pending called custom C-modes (google what a C-mode is on a canon camera). But it's so complex i didn't review it yet. I guess I could look at it after porting RAW stuff to the 1100D :P
Yep, kinda like what high-end Canons have, but it would be swell if they were unlimited (which is where the "dump to file" part comes in, but I guess you'd do that anyway).
Thanks for the awesome builds! Keep fighting the good fight!
I would like to try the ML on my brand new T3, but I'm afraid of. I almost don't know anything about programming, so i'm afraid i can't help you guys at all. but guess you can help me. Is there any reason for me NOT to install it, since i don't know how to solve any issue that i may have? If,in your opinion it's acceptably safe , (i'm not saying i want 100% sure, but I just don't want to lose the equipment that i'm still paying for) how do I proceed ? Is there any file that I just got to put in the memory stick to install ML, or I have to make any complicated process before having it on my camera? If it's not asking too much, i would like to learn how to do this process of installation safely, even if the software is still in development.
Hi,
Good day...
Is there any updates of ML for 1100d?
Hi, I just heard about ML and wanted to know when do u estimate 1100D would be supported?
The 1100D is in "maintenance mode", meaning everything that should work it's working right now. The only exception is RAW stuff but I'm working on it :)
Quote from: nanomad on May 28, 2013, 09:56:58 PM
The 1100D is in "maintenance mode", meaning everything that should work it's working right now. The only exception is RAW stuff but I'm working on it :)
So, do you think it wouldn't be dangerous? I mean, I know the possible risks, but overall it's ok to download this version even if I don't have much of a experience on programming and things like that?
Quote from: tomasmto on May 28, 2013, 10:56:52 PM
So, do you think it wouldn't be dangerous? I mean, I know the possible risks, but overall it's ok to download this version even if I don't have much of a experience on programming and things like that?
It should be just fine, don't worry about it. It's way past the dangerous part. I was like you a few months ago and I'm not quite well financially, so ruining the only camera I have is pretty much a one-hit-one-kill for me.
If anything goes wrong (if it freezes) , turn off the camera and then turn it back on.
If that goes wrong as well, take out the battery for a couple of seconds and then put it back in.
If all else fails, format the card and that should work. (note that it will still leave a tiny bit of information on the camera that tells it to look for ML on the card - this can be eliminated by installing ML on the card, then on the camera and then uninstalling it from the camera by the same process you use to install it. it should say so after having installed it, right there with all the green text)
(am i right guys?)
Anyway, just don't click the one function that says not to click it.
Enjoy.
In other news, I would like to report what seems not to have been fixed in a long time, nor it is really required:
I'm using the May 11th version, but I have a hunch these issues have not been dealt with.
When adjusting LV brightness, contrast (and probably saturation), cause strange behavior (the increase in brightness only affects the green channel of the screen and the contrast only the red/magenta).
Also, while filming with FPS override there are 2 issues:
-it takes a while (a few frames, which for timelapse purposes is a lot) for the autoexposure to figure out what exposure it wants from the scene (I'm guessing this is a Canon-defined algorithm that smooths the exposure changes in realtime video).
-while in exposure override, it takes quite a while to change the shutter value from the ML menu (the little cyan box with the grey vertical line moves realtime, but the numerical value change itself and the effect to the exposure are greatly delayed)
Otherwise, ML works great! Fewer crashes due to insufficient memory. The format-and-keep-ML function now works splendidly ever since you solved the malloc thing. Keep fighting the good fight and to all a good life!
Quote from: 47Crows on June 01, 2013, 09:17:26 PM
It should be just fine, don't worry about it. It's way past the dangerous part. I was like you a few months ago and I'm not quite well financially, so ruining the only camera I have is pretty much a one-hit-one-kill for me.
If anything goes wrong (if it freezes) , turn off the camera and then turn it back on.
If that goes wrong as well, take out the battery for a couple of seconds and then put it back in.
If all else fails, format the card and that should work. (note that it will still leave a tiny bit of information on the camera that tells it to look for ML on the card - this can be eliminated by installing ML on the card, then on the camera and then uninstalling it from the camera by the same process you use to install it. it should say so after having installed it, right there with all the green text)
(am i right guys?)
Anyway, just don't click the one function that says not to click it.
Enjoy.
Thanks a lot for the explanation,dude. I surely needed this little "push" to get me downloading it.
Hello, i am new to magic lantern, and a have a few questions:
Is it possible to manually control exposure using dial(like in 600d by default)?
Currently exosure changes are possible only via magic lantern menu with exp. override on.
Thanks!
Quote from: michbil on June 03, 2013, 07:49:26 PM
Hello, i am new to magic lantern, and a have a few questions:
Is it possible to manually control exposure using dial(like in 600d by default)?
Currently exosure changes are possible only via magic lantern menu with exp. override on.
Thanks!
Not possible :-(
Quote from: nanomad on June 03, 2013, 08:51:06 PM
Not possible :-(
Is there any hardware or software restriction to realize this feature?
Well, the dial is used to control canon's AV comp
how should I proceed with the installation? the files I have to download are not in the download tab, right? or those nightly builds are the correct way to go
You need to use the nightly builds
Hello,
I'm looking for it since 3 days but I didn't find how to make a HDR render on magic lentern.
My 1100D shows only bracketing and that's all.. No HDR function..
Thank you,
Kevin
Photo or video HDR? for photos you just shoot an extended bracket using ML and merge it in post
Yes, for photos!
I don't understand it should Be merging automaticly the three photos and it does'nt work with that bracketing.. can you explain me precisely how to do please ?
Thank you
Yea, it doesn't work if you don't read the manual or if you are afraid of Paintbrush ;)
http://wiki.magiclantern.fm/userguide#hdr_bracketing
It doesn't work. I've made what it was written. I took 3 pictures, bracketing, 3 differents exposure. Then I go back to playbackmode (What is that mode ? It's when you click on play and then you can see the last picture you took?) and I hold SET. I can hold this button 10sec or 3min, nothing appers. It just says : "Scrollwheel : Exposure Fusion." but there's no fusion..
Thank you again.
Quote...hold SET and turn the main dial (wheel)
If you can't follow these simple instructions, I'm afraid you have to go back to Canon firmware (or get a point and shoot camera?)
I understood sorry. And when I fusionned, what should i do next because my picture isnt saved..
Thank you.
@kevin.brun
the fusioned hdr won´t be saved..you have to combine those exposures yourself!
@nanomad
you said you´re trying to get raw video working on 1100d? Is it possible to get those high write-speed with sd cards?
Well, the thing is the 1100D has the same capabilities the 600D has, so around 960px wide images BUT we also have half the memory of the 600D available which means no RAW video. I'll enable all the other RAW-related stuff though (zebras, ETTR, spotmeter)
Quote from: cerbeld on June 05, 2013, 11:45:20 PM
@kevin.brun
the fusioned hdr won´t be saved..you have to combine those exposures yourself!
You mean on photoshop so? Oh well, HDR function on this custom firmware is usefull just to preview how will be the final HDR, made on photoshop?
Yes, you need to use photoshop or another software to do the final fusion, you can only get an approximate preview in-camera
too bad.. but i´m looking forward to try ettr :)
Hi Nanomad :D
So no RAW video on our 1100d model?
Most definitely not. We have close to no memory. I don't even know if I can mange to fit RAW stuff into the build tbh. I've made the camera lock-up a couple of times already .. :/
Oh, i really wanted RAW Video in my blacky
Buy a camcorder ?? lol
I tried to say that i want RAW video on my 1100d camera
Oh well, back to Flaats, Cinestyle and high bitrates I guess. At least you tried. :p
Minor bug detected on the June 11th build.
If you're in LiveView, you can't get out of the ML menu using the delete button (as opposed to earlier versions).
I've tried it with GlobalDraw on, off, on but with no "widgets" (i.e. zebras, focus peaking, etc.), nothing seems to work. You can get out of the menu using unconventional methods (half shutter only so far).
I realize you might have caught it, but it seems not to be posted so I thought you might want to know it's spreading.
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?
For some reason a lot of people look down on the T3 like its a nerdy, pimpled face, couldn't bust a grape in a food fight, virgin younger brother of the other newer Canon models, that just wanted to chill out with his bros. In some ways it is: its less expensive, its lighter in weight, its "feels" a lil different, and its lacks some manual features and functions fresh out of the box. However, its still a dang good DSLR out of the store.
You throw Magic Lantern firmware into the mix and hey, you got one helluva DSLR that does rival those that cost 2 to 3 times as much!
I don't know about anybody else but I believe the T3 has benefited the most from ML and still has the most to gain. Yeah, even more so than the 50D as far as in terms of practicality. I'm not taking anything away from the 50D engineering feat, cuz that ish was way super cool, but people at least considered it pro level before ML.
Magic Lantern and you has taken our DSLR out of DSLR purgatory and has given it wings. 8)
Quote from: 47Crows on June 11, 2013, 10:02:26 PM
Minor bug detected on the June 11th build.
If you're in LiveView, you can't get out of the ML menu using the delete button (as opposed to earlier versions).
I've tried it with GlobalDraw on, off, on but with no "widgets" (i.e. zebras, focus peaking, etc.), nothing seems to work. You can get out of the menu using unconventional methods (half shutter only so far).
I realize you might have caught it, but it seems not to be posted so I thought you might want to know it's spreading.
Yes, I actually noticed it yesterday. And I probably know what caused it
Quote from: Brand Brand on June 12, 2013, 07:22:57 AM
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. 8)
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.
Quote from: 47Crows on June 12, 2013, 09:00:11 PM
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.
Im with you guys, if i can help or test nightly builds
@nanomad, will it be possible with ML to manually change the ISO, shutter speed and aperture on the 1100D in video mode?
At the moment it is not possible to alter them manually, they are more or less chosen automatically.
It would be nice to choose them ourselves.
Enable exposure override :)
Yay! :D
I haven't installed it yet. My camera is quite new and I'm kinda afraid of bricking it.
Think I will wait for a stable version.
So I saw somewhere you had said there's no MLU for the 1100D. If I'm correct in my assumptions, Liveview serves as a type of MLU. If so, is there a way where you could have a feature, maybe on the display button, that would turn off the LCD during liveview? Most people would find that dumb, but wouldn't that effectively give us MLU without draining the battery so fast?
Cheers and thanks for all your effort!
Edit: I do see a powersaver that looks like it should work, but it seems to turn off the LCD and sensor when idle, but it doesn't seem to work during intervalometer use. I've tried the different settings with no luck. Dimming the LCD will probably help quite a bit, but actually shutting it down would be ultimate.
Yeah, today this topic has become 1 year old. Congratulations! :D
Liveview still flips the mirror when shooting so it's a bit useless
Quote from: nanomad on June 15, 2013, 08:28:49 AM
Liveview still flips the mirror when shooting so it's a bit useless
When I set it for time lapse, I can set it so that there's a second or two delay between the end of the last shot and the start of the next. The mirror is flipping up as soon as the exposure is over. I hear the tiniest noise when the picture actually starts, so I'm already getting the effect of MLU, but I
have to be in Liveview to do it. I'm personally using it for astrophotography and I have a homemade tracker to keep the stars at pinpoints. (I can use these sets I create for time lapse and/or for stacking.) Being able to flip off the LCD in Liveview would allow me to extend the time of my time lapse sessions dramatically. I shoot high ISO at 50mm with an f/1.8 lens, so that slap at the start of the pics can be hell when photographing the stars in the night sky.
Quote from: Windoze321 on June 15, 2013, 09:09:49 AM
When I set it for time lapse, I can set it so that there's a second or two delay between the end of the last shot and the start of the next. The mirror is flipping up as soon as the exposure is over. I hear the tiniest noise when the picture actually starts, so I'm already getting the effect of MLU, but I have to be in Liveview to do it. I'm personally using it for astrophotography and I have a homemade tracker to keep the stars at pinpoints. (I can use these sets I create for time lapse and/or for stacking.) Being able to flip off the LCD in Liveview would allow me to extend the time of my time lapse sessions dramatically. I shoot high ISO at 50mm with an f/1.8 lens, so that slap at the start of the pics can be hell when photographing the stars in the night sky.
I'm just starting to experiment with astro as well. I have a 50mm 1.8 but haven't tried it yet. What ISO do you recommend with the 50mm? I am assuming you use the aperture at 1.8? I was using the 18-55 at 18mm on the lowest aperture and a shutter speed of 30 seconds and ISO of 1600 (as recommended in the e-book 'Shooting Stars').
I'm still wondering what the best way is to combat noise. Do you do any stacking?
(Sorry for the diversion in the thread).
Quote from: Fletch on June 15, 2013, 09:32:41 AM
I'm just starting to experiment with astro as well. I have a 50mm 1.8 but haven't tried it yet. What ISO do you recommend with the 50mm? I am assuming you use the aperture at 1.8? I was using the 18-55 at 18mm on the lowest aperture and a shutter speed of 30 seconds and ISO of 1600 (as recommended in the e-book 'Shooting Stars').
I'm still wondering what the best way is to combat noise. Do you do any stacking?
(Sorry for the diversion in the thread).
Magic lantern has wonderful options for keeping your laptop inside where it's dry! Between time lapse and bulb settings, there's no need for the Canon EOS program with a USB strung between your camera and laptop just waiting for you to bring them both crashing down!
You'll want to stop the f/1.8 down a bit. Maybe f/2.5ish, give or take. (Most lenses seem to have better pictures stopped down.) As for ISO, it all depends on your equipment and your shooting conditions. I can get away with a lower ISO because of my tracking (Much longer exposures before star trailing). (Look up Barndoor tracker.) If you have a lot of light pollution, then high ISO will wash out your pics when doing long exposures. At 50mm, you're also going to get a lot of star movement on anything over 5-10 seconds. It's really a game of trial and error. Consider shooting in a fluorescent white balance, too.
Yes, I do plenty of stacking. I use Deepskystacker for alignment stacking and Photoshop for things like startrails. Here are some examples of what I've done. Most of these were taken with the Rebel XS. http://pinterest.com/pin/459437599456103974/ My T3 just got delivered yesterday and I've got almost 7k pics on it already. Check out my youtube for some of my time lapse videos. http://www.youtube.com/user/Windoze321
As for noise, there are various ways for combating it. One is to use a program like BlackFrame NR, but if you're wanting to remove them from 1,000's of pics at once (time lapse), then this guide will help you through Photoshop: http://www.foundphotography.com/2005/11/batch-action-to-remove-hot-pixels/ It's a bit complicated, but it worked wonders for me.
- Fixed ML menu not closing when in LV (it used to work but it shouldn't have :o)
- Freed up some memory
Thanks to alex work on the module system, the 1100D can now load them :)
Thanks. Your pics look great Windoze!
Yeh, I don't have a tracker. Plus it is hard to find clear nights here at the moment (it is Winter here).
I'll be looking to get out and trying to take some more pics when a clear night rolls around.
@nanomad and alex - thanks for all your hard work!
I haven't installed ML yet but I plan to when it is stable :)
Quote from: Fletch on June 15, 2013, 11:02:58 AM
Thanks. Your pics look great Windoze!
Thanks! The Orion Nebula was taken with my sisters' T3i with her 250mm and my tracker. The ones of the Jupiter and the Moon were taken with the XS while being held up to my telescope. (Oh how I wish
it had tracking!)
I installed ML the day I got my brand new 1100D. I couldn't resist, lol.
@nanomad - As far as testing goes: Last night I shot 4 straight hours of time lapse with it without a hitch at 1 pic every 7 seconds with 5 second exposures. Then today I shot for 2 hours straight at 5 second intervals (regular pics at 1/1000), so I think it's safe to say that that feature is pretty stable. On the next clear night I intend on using ML with the time lapse AND the bulb feature. I want a couple hours of 1 minute exposures of the Milky Way, so that should be a pretty good test. I'll report my results when I have clear skies.
I'm not seeing the .zip file on the nightly page. The last one I see is for the 12th.
Quote from: Windoze321 on June 15, 2013, 11:39:11 AM
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
There's a new build system on the repository. I'll fix nightly builds tomorrow morning
Quote from: nanomad on June 16, 2013, 02:26:21 AM
There's a new build system on the repository. I'll fix nightly builds tomorrow morning
Awesome, thank you!
Okay! I changed direction for my time lapse. Instead of using the intervalometer feature, I used the forced fps in video mode. Dropped it to .333 fps and forced changes to the ISO, shutter speed and f/n. The LCD cut off wonderfully using the power saver feature. I have taken a 1 hour and now a 2 hour time lapse. I don't know how long I can get, yet, I'll keep adding time along the way.
This is totally awesome because now I can do time lapse without adding 1,000's of shutter actuations to my precious camera!
Not only does it save my shutter, it save me HOURS of post processing!! It comes right out of the camera as a .mov file instead of 1,000's of pictures to resize and turn into a movie!
Thank you SO much for this and all of your work!! (That goes for everyone involved, including the testers!)
I have a question. What happens when the battery dies during video? Will it save the file 1st, or is all lost?
To view my results using Magic Lantern, check this out. It's a pretty great time lapse of a storm coming in. It gets better and better as it goes!: http://youtu.be/x-tYJTuigJ4
On a side note... I keep seeing people talking about restarting their videos. Maybe it's because of the dramatically reduced frame rate I'm using, but it's never stopped on me at up to two hours of straight recording!
Cheers!
Windoze, the video looks great!
I like the idea of saving the shutter from wear and tear - that is one of the reasons I hadn't done any time lapse work on the T3. It is quite new and I didn't want to just treating it like a workhorse.
What is the "f/n" you mention in the settings?
I'm looking forward to installing ML, but too scared just yet :-\
Quote from: Fletch on June 17, 2013, 02:55:48 AM
What is the "f/n" you mention in the settings?
Aperture or f/stop. I moved it up to f/11(ish) with a shutter speed of 1/240, I think. Also I set the ISO to 100.
This stuff works great, but you have to be real patient. When you set the fps to such a low # (.333), it takes awhile for everything to update. Changing the shutter (electronic) speed takes awhile. There's lag in the # actually changing and then more lag in it actually changing the liveview image to match. I don't know if this can be made to go faster or not. It works fine, though.
ps, I've been looking over the documentation -
Is it possible to get 60 frames per second filming with the 1100D?
Normally we are limited to 24fps or 30fps in the menu.
I see there is an override in ML, but it mentions that overcranking doesn't work very well.
Quote from: Fletch on June 18, 2013, 06:20:49 AM
Is it possible to get 60 frames per second filming with the 1100D?
The over-ride changes your shooting fps, not your playback fps. Your camera will play back at either 25 or 30/fps regardless of what you set the over-ride to. It will save the video file this way, too. If my brain is functioning correctly, anything above what the actual camera fps is set to would give you a slow motion video when being played back. (I haven't tried it, but based on my time lapse shooting, it would make sense.) I'm shooting 1/fps right now. When played back, it will be 30/fps. So in 1 minute, I'm shooting 60 frames which will be 2 seconds of video (1/fps*60s = 60 fames/30fps = 2s). If I were shooting 60/fps, it would give me 3,600 frames in 1 minute or 120 seconds of video (60/fps*60s = 3,600 frames/30fps = 120s). So now one minute of real time shooting would take 2 minutes to play back, giving you slow motion.
Someone please correct me if I'm mistaken.
Hi guys
I just got brand new 1100D, and I want sooo mcuh to put ML on it.. but if it dies or whatever happens and I want to send it back , and act dump, like I dont know what happen, will they know what I did and basically, what will happen ?
Will I get new one or they will know what I did and say its my fault, sorry.. bye.. ?
Quote from: TokraCro on June 18, 2013, 08:11:02 AM
Hi guys
I just got brand new 1100D, and I want sooo mcuh to put ML on it.. but if it dies or whatever happens and I want to send it back , and act dump, like I dont know what happen, will they know what I did and basically, what will happen ?
Will I get new one or they will know what I did and say its my fault, sorry.. bye.. ?
http://wiki.magiclantern.fm/faq#does_it_void_my_warranty
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:
[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 (http://wikisend.com/download/519518/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)
Quote from: 47Crows on June 18, 2013, 11:44:14 PM
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!
In that documentation are install notes. In the install notes it says:
There are two ways of running user code on Canon DSLR cameras:
1. Using the update process with a .fir file, which must be digitally signed.
2. Using the bootdisk process: the autoexec.bin file is loaded and executed. This file
does not have to be signed, but the bootdisk flag must be enabled in the camera.
If what I've read before is correct, then as long as you've already gotten it to work with a .fir file, then the flag has been set inside the camera and it should be able to execute the .bin file. If you haven't gotten it to work before, then I would assume you would need to find the correct .fir file first. (You can find one in the archives.)
nanomad, I downloaded the new build (2.3)
Not sure if I will risk installing it yet (I have never installed ML), but if I do, what version of firmware is required for the 1100D?
I looked on my camera, and I have 1.0.5 installed at the moment.
Quote from: Windoze321 on June 19, 2013, 12:35:51 AM
In that documentation are install notes. In the install notes it says:
There are two ways of running user code on Canon DSLR cameras:
1. Using the update process with a .fir file, which must be digitally signed.
2. Using the bootdisk process: the autoexec.bin file is loaded and executed. This file
does not have to be signed, but the bootdisk flag must be enabled in the camera.
If what I've read before is correct, then as long as you've already gotten it to work with a .fir file, then the flag has been set inside the camera and it should be able to execute the .bin file. If you haven't gotten it to work before, then I would assume you would need to find the correct .fir file first. (You can find one in the archives.)
So you definitely need a .fir file to run ML?
It won't just install via the autoexec.bin file?
Can anyone help me?
Im trying to use Focus Ramping on my 1100D with the 2013Jun18 Build
First, i set on manual focus to infinite, then move it to AF
Next open Magic Lantern menu, and go to shoot, and click on intervalometer, and i tried choosing -1, -25, +1, +25 on theManual Focus Ramp opcion, then i click Q to exit from the submenu, click on the LiveView button, and it starts to take photos, but the focus dont move.
Im doing something wrong?
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 (http://wikisend.com/download/375956/COREDUMP.DAT) while setting the FPS override.
[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).
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...
Huh?! FPS override does not affect ML's internal clock at all...
No what I meant is that it seems to me that with FPS override GUI events are being processed somewhat slower, which means a longer time between a press->unpress transition -> no shortpress detected -> no ML Menu
Nope, they should be faster because the CPU is idle.
And the error message shows a bug in ML this time, but I can't reproduce it.
Uhm, then i have to dig deeper
Quote from: nanomad on June 19, 2013, 12:14:40 PM
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!
Quote from: Fletch on June 19, 2013, 05:32:54 AM
So you definitely need a .fir file to run ML?
It won't just install via the autoexec.bin file?
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.
Quote from: Fletch on June 19, 2013, 05:27:29 AM
nanomad, I downloaded the new build (2.3)
Not sure if I will risk installing it yet (I have never installed ML), but if I do, what version of firmware is required for the 1100D?
I looked on my camera, and I have 1.0.5 installed at the moment.
You have the correct firmware. Look in the archives section for the June 12th release. That's the one I'm using right now and it seems to work fine. I haven't upgraded to the latest, yet. Partially because I'm not positive that I should erase the whole card including the .bin and replace it with everything from the latest release. I
think that is correct. I'll test it out by adding the new release to a separate SD card, I just haven't gotten around to it. There's a storm brewing as we speak :) Literally 8)
Quote from: Windoze321 on June 19, 2013, 07:32:30 PM
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.
All sounds a bit too complicated for me at the moment.
Maybe I'll just wait for a stable release that takes you through the steps.
Quote from: Fletch on June 20, 2013, 01:00:08 AM
All sounds a bit too complicated for me at the moment.
Maybe I'll just wait for a stable release that takes you through the steps.
If you want to do it easily, just go into the archives and get the one from the 12th. Unzip it and put everything you see onto your SD card (not in any folders). Then put it in your camera and turn it on. Go to your firmware update (Might have to be in Manual mode to see that option in your camera menu) and update it. It will tell you it worked and to restart your camera.
Edit: Once installed, tap the Av button to bring up the ML menu. Then hit your Menu button to bring up the Grid menu. (I like this way best, but you don't have to do that.) Highlight the feature you want to check out and hit your Set button to activate or the Q button to adjust the settings of the highlighted feature.
2nd Edit: You only have to do the 1st paragraph one time. After that, you're good to go unless you erase it off of your SD card.
As for ease of use... I've had my camera for 6 days now. Tomorrow will be a week. I've never used Magic Lantern before. It takes a bit to get the feel of it, but just work on one thing at a time. For me it was time lapse through the Video (FPSOverride) setting (along with exposure override), and when you drop the fps down as low as I do, then it lags pretty bad when changing the shutter speed. I wasn't sure it was working and it was a bit frustrating. Once I figured out I had to just be patient and wait for the changes to the readout of the shutter speed and wait a bit more for the changes to show up on the LCD, I was good to go. As for everything else I've tried, the changes are pretty instant. Hoping for some lightning so I can check out the Motion Detect feature! That should be fun!! 8)
And if you put a new, blank card in, the camera just won't use ML at all right?
Quote from: Fletch on June 20, 2013, 03:04:37 AM
And if you put a new, blank card in, the camera just won't use ML at all right?
Correct. The bootflag will still be set to look for software, but upon finding none, it just load normally. That's the only (and extremely tiny) change that occurs to your actual firmware when ML is installed the 1st tie.) I believe that can be undone by reflashing your camera with the OEM firmware.
You can also just hold the 'Set' button on your camera when turning it on and it will bypass ML as well.
Quote from: Windoze321 on June 20, 2013, 01:10:52 AM
If you want to do it easily, just go into the archives and get the one from the 12th. Unzip it and put everything you see onto your SD card (not in any folders). Then put it in your camera and turn it on. Go to your firmware update (Might have to be in Manual mode to see that option in your camera menu) and update it. It will tell you it worked and to restart your camera.
Edit: Once installed, tap the Av button to bring up the ML menu. Then hit your Menu button to bring up the Grid menu. (I like this way best, but you don't have to do that.) Highlight the feature you want to check out and hit your Set button to activate or the Q button to adjust the settings of the highlighted feature.
2nd Edit: You only have to do the 1st paragraph one time. After that, you're good to go unless you erase it off of your SD card.
So, that is the only thing I have to do to try it ? since I am noob here and just been reading, thats the one thing I have to do to make it work ? I am only interested in Intervalometer atm and thats the only feature I would explore atm
What about bugs and/or when I find some ? is there something I have to do then or what ? how does that part works ?
Quote from: TokraCro on June 20, 2013, 11:04:36 AM
So, that is the only thing I have to do to try it ? since I am noob here and just been reading, thats the one thing I have to do to make it work ? I am only interested in Intervalometer atm and thats the only feature I would explore atm
What about bugs and/or when I find some ? is there something I have to do then or what ? how does that part works ?
You just set up your picture for the exposure/aperture/ISO like you would normally do and then hit the Av button to open the LR menu. Then hit the menu button to bring up the grid style. Highlight Interval and hit the Q button. Adjust the time between pics and the delay before the 1st pic. After that I 1/2 press the shutter to start it. If you're looking to do time lapse without the shutter count rising, then do it the way I described by using Movie Mode on your camera and setting the FPSOverride and the Exposure Override. No need for the Intervalometer using that method. Make sure to use the power saving settings to cut off the LCD during recording to save on your battery.
Post bug reports right here. If something goes wrong, they say to turn off the camera and take out the battery for a minute.
I'm about to post a bug report on the Intervalometer. Nothing that will threaten the camera, but something that needs to be addressed.
Bug Report - Intervalometer - I was shooting some star trail pictures and ran into the same problem twice. I set it up on my camera to take 29 second exposures and set the intervalometer to take a picture every 30 seconds. (I have a fast Class 10 card with UHS Speed Class 1.) The first set took exactly 100 pictures perfectly. When I went to check it, the red light was flashing. I lit up the display it was counting down and was at 28+ minutes. The 2nd set went for 130 pictures. I went outside at the 50 minute mark to see if it was going to stop at 100 again, but it didn't. When I went out to check again later, the light was flashing again. This time it was counting down and at 42+ minutes.
This happened using the release from June 19th. This did not happen using the one from June 13th, but the setup was different. Using the one from June 13th, the setup was a 5 second exposure with the intervalometer set at 6 seconds. I took well over 1,000 pics without an issue.
So, I don't know if the problem cropped up between releases or if it happened because of the longer exposure time of the last attempt.
Cheers and thank you for all your hard work!
Compare the two releases under the same settings then :)
Quote from: nanomad on June 20, 2013, 12:38:27 PM
Compare the two releases under the same settings then :)
Okay, but it's morning time here, now. It will have to wait until tonight. (Not gonna waste 100+ long exposure shutter actuations on the daytime ;) )
The 130 pictures that it did take were great, though! http://pinterest.com/pin/459437599456549748/
You can enable a dummy shooting mode (snap simulation) and just let the camera blink and beep. It should be enough to reproduce the bug - of course, if it's not caused by some memory overflow when taking a picture.
There were some changes to timing backend, so it might be related. If the problem happens after exactly X hours/minutes/whatever after powering on the camera, I know where to look.
Quote from: a1ex on June 20, 2013, 12:52:19 PM
You can enable a dummy shooting mode (snap simulation) and just let the camera blink and beep. It should be enough to reproduce the bug - of course, if it's not caused by some memory overflow when taking a picture.
There were some changes to timing backend, so it might be related. If the problem happens after exactly X hours/minutes/whatever after powering on the camera, I know where to look.
Okay then, I'll try that out. Unfortunately, though, I only have one battery and I just set it to charge. I also need a couple/few hours of sleep. It will still be about 12 hours quicker than waiting till dark, lol.
Quote from: a1ex on June 20, 2013, 12:52:19 PM
There were some changes to timing backend, so it might be related. If the problem happens after exactly X hours/minutes/whatever after powering on the camera, I know where to look.
Now that I think of it, that very well could be. The difference between 100 and 130 shots is about 14-15 minutes at 29 second exposures. It did take me about that much longer to set up for the 1st shoot. For the 2nd shoot, I knew my settings and didn't have to take any test shots. I also didn't have to wait for my neighbors to go inside because I was setting up in a more secure location.
Edit: I will do the test on the old firmware if when I wake up I don't see a response saying you found it.
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)
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 :-)
Quote from: Windoze321 on June 20, 2013, 08:37:53 PM
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)
Quote from: 47Crows on June 20, 2013, 08:43:08 PM
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)
I just looked for it and couldn't find it. If it is in there, it's hiding pretty well or I'm blind.
If the skies are clear tonight, I'll be running the exact conditions as last night on the earlier release.
Quote from: Windoze321 on June 20, 2013, 09:02:42 PM
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.
Quote from: Windoze321 on June 20, 2013, 12:50:22 PM
The 130 pictures that it did take were great, though! http://pinterest.com/pin/459437599456549748/
Wow, that looks great!
How did you get the trees in there? Are they light painted?
Or did you start shooting earlier when it was lighter?
I'd love to try and get some pics like this.
Quote from: Fletch on June 21, 2013, 04:12:59 AM
Wow, that looks great!
How did you get the trees in there? Are they light painted?
Or did you start shooting earlier when it was lighter?
I'd love to try and get some pics like this.
Thanks! Yeah, they're painted by the carriage lights of the house.
Edit: ISO 400, 29s exposures, f/4.5, @20mm (Stock 18-55mm lens). I think I shot them in a Tungsten White Balance. Just set your manual focus to a bright star before hand (using the 10x magnification). Absolutely no editing besides reducing the size of them and stacking them in Photoshop. I left Blending for all the photos set to Normal.
I like your pic of the moon, too.
I tried shooting the moon using the kit 70-300mm (at 300MM) and could only get this close -
https://josb.jux.com/1234564
Quote from: Fletch on June 21, 2013, 04:46:33 AM
I tried shooting the moon using the kit 70-300mm (at 300MM) and could only get this close -
That's a great shot! Mine was taken through my telescope with a 12" mirror while holding the camera in front of the eyepiece. I only had the 2" 30mm eyepiece on it for a magnification of 50x. (I can go 545x, but the 30mm is the only one I have that fits the whole moon in it.)
Bug Report Update: Intervalometer - I ran it under the exact same conditions as last night except I used the release from the 13th and everything was fine. I stopped it at 2 hours and 40 minutes and it took 282 pics.
It should have only been 2 hours and 21 minutes, though (30s interval * 282 pics = 8,460s / 60 = 141 minutes or 2h 21m). I deleted all the setup pics and only counted the ones from the time that the intervalometer was running, so that wasn't it. I had written down the start and stop time of the intervalometer and it matched the time given for the 1st and last pics of the set. I see no gaps in the stars when stacked, though. Probably due to the combination of the bulb and intervalometer. I'm guessing that's why "There were some changes to timing backend".
Cheers and again, thanks for all your work!
Windoze, OK, so I installed ML and it seems to have gone alright. All the menus are there etc.
I just want to make sure I understand as to how to set shutter speed, Aperture and ISO for movie mode.
I have Exposure Override *ON* from the main menu and have set my aperture, shutter speed and ISO to what i want them to be.
This means that now when i am in movie mode it is using my settings and not the apparent settings that display on the bottom of the screen while in movie mode/live view.
This appears to be the case, as the brightness does not change whether I am pointing it to the window (very bright) or into shadow.
Quote from: Fletch on June 22, 2013, 04:59:39 AM
Windoze, OK, so I installed ML and it seems to have gone alright. All the menus are there etc.
I just want to make sure I understand as to how to set shutter speed, Aperture and ISO for movie mode.
I have Exposure Override *ON* from the main menu and have set my aperture, shutter speed and ISO to what i want them to be.
This means that now when i am in movie mode it is using my settings and not the apparent settings that display on the bottom of the screen while in movie mode/live view.
This appears to be the case, as the brightness does not change whether I am pointing it to the window (very bright) or into shadow.
Should be correct. I've only used it with the fps override, though.
Had some weirdness trying to use it today.
I had put another blank card in without ML and it worked fine (without ML running of course).
When I switched back to the card with ML on it, it wouldn't run when I pressed the AV button. I knew it was on there because of the little yellow numbers under 'ISO' on the screen, but the ML menu wouldn't come up, like it wasn't installed.
I had to press AV a few times in quick succession to get the ML to come up at all.
When it finally did, I couldn't seem to get the User defined Cinestyle to come up. It was like it had disappeared, but it came back a short time later.
So yeh, a bit weird.
UPDATE: I just put the card with ML on it back in (after having a non-ML card in it) and ML doesn't show up at all.
Check if the bootflag is still there with EOSCard. If it is, reset ML settings by deleting the files inside ML/SETTINGS
Just saw your post this morning now (after I tried below).
At first I thought it might be the battery, because it was getting flat, so I charged it overnight and tried again this morning.
I put the ML card in again but nothing. It didn't appear to be there. I know it was on there because when I put the card in the LED flashes once.
Anyway, I did the firmware update thing again (the ML installation) and it seemed to go OK. The green menu came up telling me ML was installed etc. So I turned the camera off and on, and again - nothing. I pressed the Av key a few times quickly and eventually the menu came up. I turned the camera off and on again, but this time no amount of pressing would bring up the menu.
Have to go to work this morning so will try again later.
(ps, am using build from the 12th)
[found answer - deleted :)
Is there an option to make numbers bigger when using Intervalometer ? I am talking about that numbers of taken pics . It happend to me few times that I was really low to the ground with my camera, and exp. was 10 sec with 12 sec betwen pics, and beside that I had to crouch to get to the camera, it was almost impossible for me to see the number of pics because whole process was really fast and the numbers are so small and with everything around them and it was (almost) impossible to see anything.
I dont want to bother too much, and you dont have to make adjustments because of me, I am just curious if there is option to change that or if you have time, somewhere down the road to add that option :))
Nomad, I had similar problems like Fletch, but I didnt change cards or even take the card out of the camera and my ML stopped working.
Did 2 sets of pictures the day before 2 x 300 pics and today I did 300 with no problems but after that when I moved to new location and set up everything I just couldnt get ML working. Pressing AV didnt do anything, turning on / off didnt help, battery was on half, I could see free GB in the bottom of the screen but ML woudnt come up. I have build from 13. The only way it would come up on the screen was if I pressed the button under AV Camera one with red dot.. then I would see all that things from ML, and pressing AV then worked.
Just recharged my battery and now ML comes on when I press AV every third time or something like that, but at least its working now.
Should I delete the files inside ML/SETTINGS like you suggested to Fletch or ?
Yeah try deleting the settings. I'll try to debug the button press code and see if I can spot an error somewhere
OK, I deleted that file, and not much changed. Now, I dont have that number that says how many GB i have left on card.. ML works ONLY if I press live view button and then AV to enter ML, that works every time, and if I am not in live view then I cant start ML.. is there any error file or something that I can send you to help you and that you can see that error ?
or something ?
I was thinking(Yeah i think)
Its possible to add mirror lock-up to 1100d?
I have a request. Using expanded HDR for photos, would it be possible to make the exposure margin higher than 5? I'd like to see options up to 15. Here's the thing. Even at 5, I have to take 3+ pictures to get the effect I'm looking for and everything in between is a total waste. What I'm trying to do is take a long exposure of the moonlit clouds. I would like to HDR it with a very short exposure that gives me detail in the Moon. So a broader range would allow me to do it with just 2 shots instead of 3-5. (I'm taking them in the mode that adjusts the shutter, not the other things. I want to keep a low ISO to reduce noise.) Having had a shutter failure in my last camera, I'm really trying to keep my shutter count down as much as I can without deterring my photography habits.
As always, cheers and thank you for this wonderful tool!
https://www.dropbox.com/sh/u6tx2jrid2h45y9/m_hsmhcxcS
Link with the files of my crash / error last night
It happened while I was transferring files from my camera to my PC via cable
Camera beeped and there was some message about not able to take pictures and something else.. I didnt see what really happened because I wasnt expecting anything while I transfer files. Battery was near end also, since I just got home from shooting
Hope it helps
Nanomad, any news about ETTR for the T3. It will be possible ?
I noticed in nightly change log that there is no more bulb ramping, is that going to change ?
Did something change after the June 11th build? Because with that one I can get into the ML menu from the live view every time. With the builds after that, I have to delete the settings every other boot, which is rather unpractical. :)
(Big thanks though to everyone involved in getting ML to work with the 1100D!)
I am using 13th build, and I dont have problem with liveview. not anymore.. Its not working any other way, just in LV.. but its working.. maybe sometimes I have to press 2 times, but its OK, at least for me
I'm on it. Fixing the menu has the highest prio right now
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
Quote from: stitzb on July 09, 2013, 06:19:09 PM
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
That was the idea, but as you can see it's not quite there yet :)
offtopic : 47 I would suggest that you go away for another week, really fast, so we get more things done, faster :D :P
Quote from: TokraCro on July 10, 2013, 05:39:36 PM
offtopic : 47 I would suggest that you go away for another week, really fast, so we get more things done, faster :D :P
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.
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?)
What about trying to press the arrow keys?
never really had problems with panoramas, even when I was in hurry, like standing in the middle of the road, click the liveview, lets says 30-50% of previous , click click , up, down.. and edit it later.. maybe it would help in the camera, but I always would trust more to the software on the computer, than on camera.. but thats just me, I guess
Please try tomorrow's nightly build, I've tweaked the button handling routine a bit
Tnx for the info, ill try it as soon as I am able to test it
The button now works on liveview :D Thanks
I have a query: What modules can do in MagicLantern? Can enable RAW Video?
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.
I got a problem with update ML. Please, help me. I can freely install/uninstall nightly builds up to 13 June (with 1100D-105.fir), but I cannot do that for any newer builds (without the 1100D-105.fir flie).
I do:
- unzip new build (from 16 July for example)
- overwrite files on my SD (which already contains June 13 build proper installed)
- insert card into the camera
- close the door and ...
The LED lights continuously and camera does not power on
What do I wrong? I see that you, guys, can update ML. Please describe how do you do that?
I'm following the instructions http://wiki.magiclantern.fm/install (http://wiki.magiclantern.fm/install) but
I cannot install any ML builds newer than 13 June on "clean" camera - Firmware Update just does nothing (It does not show the "green screen").
I cannot start camera with overwritten ML files on my SD - camera won't start.
I tryed to "reinstall" original Canon firmware 1.0.5 - it did not help.
Hey all,
I tried installing the latest build on my 1100d today. It said everything worked fine, but then when I powered down, the led light remained on, and now it won't power on. Something tells me this is really bad. Is there anything I can do?
(Thanks to everyone who worked on the builds by the way!)
I got a problem with the 2013Jul16 Build
I moved all the content to the SD Card
And then i put the SD on the camera, closed the cap
And the SD led turned on, without turning on the camera
I cant do anything, i removed the battery and tried it again and the same result.
Edit: I tried with 2013Jul17 and is the same thing
Quote from: Joseriul on July 17, 2013, 04:50:48 AM
I moved all the content to the SD Card
And the SD led turned on, without turning on the camera
I cant do anything, i removed the battery and tried it again and the same resuld.
Joseriul and mauflow
I had the same problem - the solution is just to put back all ML files from previous installed build (build 2013Jun13 works OK, thx TokraCro for advice)
Quote from: mhz on July 17, 2013, 06:23:52 AM
the solution is just to put back all ML files from previous installed build (build 2013Jun13 works OK, thx TokraCro for advice)
When you say put back, do you mean replace the ML files currently on the card with the ones from the earlier build?
Thanks for the help!!!
Bug noted, I'll work on it tonight
as the firmware for 16,17,18 July 2013 do not work, I checked for July 15, and there does not get out window magick zoom.
может быть что-то я не так перевёл, я из России ;D
I'm sorry (maybe something I have not moved, I'm from Russia) *
The last nightly freeze at the start. I tried format the card and update the ML, but didn't work :(
I've been using ML for 6 months now and love it! The HDR features are awesome! I do have a question though.
The 1100D/T3 does have a mirror lockup for cleaning only in the original firmware. But it won't let me shoot images with the mirror up. I shoot a lot of night photography and the shake can get pretty bad sometimes effecting the sharpness of the image. I've read a lot of the documentation and I've seen the mirror lockup feature on the other version of ML in the SHOOT menu but its missing in the 1100D/T3 menu.
It would be a great feature to have. If I have missed a post that it cannot be done or missing some info on it, please point me in the right direction.
Thanks again for making ML possible! :)
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).
The last nightly is start, but i get a message "Failed to allocate BVRAM mirror" and ML not work
Power-cycle the camera and see if it boots
Quote from: stitzb on July 23, 2013, 05:51:24 PM
The last nightly is start, but i get a message "Failed to allocate BVRAM mirror" and ML not work
I've got this error quite often too.
And I cannot use any feature in live view, I tried with many last releases, since months ago they worked well. Indeed my main goal is for focus peaking, too bad it doesn't work...
Quote from: nanomad on July 24, 2013, 01:31:44 PM
Power-cycle the camera and see if it boots
Not work. I also get this message
edit: The last nightly which works the 07.15
I can confirm that the 2013Jul27 still have the problem allocating vram mirror
FPSOverride: I can set it to 1 frame every 5 seconds but I seem to be restricted by the optimization setting. In low light mode, I can get the shutter speed as long as 4 seconds, but no lower the 3.9, I think. At the same FPS I can go to the High FPS mode and then my shutter speeds are 1/30 - 1/450 or something. Could we get a combination of the two? I'm using the gradual exposure (awesome, by the way!) but I want to start at around 1/450 and end around 4, but I've found no way to do it without changing the mode from high to low light. This would be perfect for the 'Holy Grail' if they were combined. I've played with the advanced settings, but can't seem to get it in there, either.
As always, thanks you for your work!
Confirming the message "Failed to allocate BVRAM mirror". I haven't seen ML in action yet, however I don't see any of the features working.
EDIT: talking about 2013/07/27 build.
EDIT2: Also, the set button doesn't do anything anymore at all.
I reverted back to build 2013Jun13, it seems to be the more stable one by now.
I'm trying to install on a 32g but when i go to firmware update, it doesn't see it. I was already on 1.0.5, but to be sure i updated to 1.0.5 but problem persists
edit:nevemrind
As someone who just wants the stablest build to try out ML for the first time, Which build should I use? I've heard good things about the june 13th but I was wondering if there was a newer one.
The 2013-07-31 build should be the one :)
Thanks a lot for pointing out that 13 Jun was a good copy while 16 Jul was broken. Made my bisecting muuuch easier
Quote from: nanomad on July 30, 2013, 11:08:27 PM
The 2013-07-31 build should be the one :)
Thanks a lot for pointing out that 13 Jun was a good copy while 16 Jul was broken. Made my bisecting muuuch easier
Thank you Nanomad :D
Edit: 2013Jul31 Works :D
Grazie a te nanomad, adesso sembra funzionare bene.
Thanks to you nanomad, now it seems to work well.
Booted up fine for me. I had to use the jun13 .fir file to install though. I'll play around with it a little while and report back if there are any problems.
Edit: There seems to be flickering between the ML and creating a user defined shooting style menus when adjusting settings in the ML video menu.
Still having problems with intervalometer and bulb exposure. The older build I was using from back in Apr just simply crashed when you tried to do a bulb override + intervalometer, I think I saw that others had reported this. I just recently put the Jul31 nightly on there and it no longer crashes, the only problem is that after the first shot it goes from being set on BULB back to 30", and so none of the subsequent pictures use the bulb override amount, they simply are 30 seconds.
I managed to make it crash by adjusting video white balance temperature in live view and hitting the disp button.
Crash log:
ASSERT: 0
at Evf\EvfState.c:1190, task Evf
lv:1 mode:20
Magic Lantern version : v2.3.NEXT.2013Jul31.1100D105
Mercurial changeset : aac317826b59 (unified) tip
Built on 2013-07-31 02:15:09 by
[email protected].
Free Memory : 240K + 400K
Note: I don't have the 1100D with me right now, I'll get back to it in September
Well, enjoy your vacations everyone! I'll keep trying to crash the builds with every chance I get, as happily as ever!
Hello Everybody,
i wanted to try out Magic Lantern on my Eos 1100D but i`m a littlebit confused by this line (in the first post in this thread)
QuoteRC 3: http://nanomad.magiclantern.fm/1100D/magiclantern-v2.3.1100D.RC3.zip Use development builds instead!!
Is this build unsafe or are there newer Builds with more features ? What build can you recommend as "relatively" safe ?
I have never been atacked by a build, so they are safe
Joking:P
I think the nightly build 2013jun13 is one of the more stable build, and u can find it on http://nanomad.magiclantern.fm/nightly/archive/
Quote from: Joseriul on August 07, 2013, 05:17:16 AM
I have never been atacked by a build, so they are safe
Joking:P
nightly builds can be dangerous when they come out at night.. they do strange things :D
joking also :D
Quote from: TokraCro on August 07, 2013, 08:40:56 AM
nightly builds can be dangerous when they come out at night.. they do strange things :D
joking also :D
Its that why they call them nightly?D:
hi everybody,
i just found out about magic lantern, and it really seemes fantastic!
also spend a time reading the forums, but i still got a question.
I have a canon 1100d, and at the downloadpage i don't see a stable version for my camera.
I did find the nightly builds, but it says you already need to have a stable version running on your camera.
what should i do? try to install the stable version, which i doubt will work on my camera, and then install a nightly version? or am i overlooking something?
thanks in advance for the help.
siegbert
Quote from: siegbert on August 09, 2013, 06:50:31 PM
hi everybody,
i just found out about magic lantern, and it really seemes fantastic!
also spend a time reading the forums, but i still got a question.
I have a canon 1100d, and at the downloadpage i don't see a stable version for my camera.
I did find the nightly builds, but it says you already need to have a stable version running on your camera.
what should i do? try to install the stable version, which i doubt will work on my camera, and then install a nightly version? or am i overlooking something?
thanks in advance for the help.
siegbert
Friend, there is no stable at all build, but there are nightly builds, and you can find them here:
http://nanomad.magiclantern.fm/nightly/archive/
And you need to have the .fir file in the sd too, u can extract it from older builds.
To install it
Make sure that u have the battery full
Put the .fir file in the sd
Put the last build files in the sd
And in your camera go to the menu, and click on firmware version, and click update
Wait a little, and there will be a screen with green words, read it and restart the camera
Quote from: Joseriul on August 09, 2013, 09:51:47 PM
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.
Hi everyone,
I'm trying to install ML on my 1100D but having troubles with launching it.
Here is the sequence of steps I tried:
1. take 2GB sd card, format it in the camera in low-level mode
2. restore defaut setting in the camera
3. copy contents of nightly NEXT.2013Aug12 zip to the root of sd card, copy .fir file from 1100D.RC3 zip to the root of sd card
4. start camera with the sd card, turn it to M mode and go to software update section in menu, update it with the data from sd card, reboot camera
After this step firmware version in menu is changed to 1.05-NEXT.2013Aug12..., in quick control screen now I see ML footer that shows its version and header with current date. But pressing AV button doesn't pop up ML menu as described in the manual. It just switches to another control in the screen and back.
Am I doing wrong or forgot something? How can I investigate why ML menu doesn't appear?
Tried the same sequence with NEXT.2013Jul13 version - the same results.
I will be grateful for any help.
Upd: Problem solved, the thing was that I pressed av button too long. It should be short press instead. And now it works!
hi, thank all for the work here! i just installed ML on my 1100d and works correctly, i instaled the 07/15 version that as i read was the most stable version.
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!
Quote from: uniextra on August 15, 2013, 09:11:06 AM
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).
1100d have RAW video?
It is will be in the future firmware?
Not enough memory for anything useful. Sorry
Quote from: nanomad on August 16, 2013, 01:18:36 PM
Not enough memory for anything useful. Sorry
Its possible to have silent DNG shot?
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 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.
Quote from: 47Crows on August 23, 2013, 09:30:23 PM
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.
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
Quote from: dmilligan on August 23, 2013, 09:57:51 PM
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.
If you don't care about it being clean you might get it to work with a tether or hdmi capture
Hi! I moved from a february nightly build to the 18th august one. Can anybody tell me why the silent picture option has disappeared? Also, has anybody fixed the bulb timer + intervalometer problem (exposure time back to 30s after first shot) on the 1100D?
Quote from: dmilligan on August 24, 2013, 02:01:24 AM
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!
In the end, which version should I install: 07/13, 07/15 or 07/31 ?
Thanks !
How about ETTR / Auto-ETTR (for timelapse etc.) on the 1100D / T3 ?
This would be a really useful feature on the 1100D, really hope it will be possible to have this soon!
Hello,
im new with ML,
Isaw a Video on YT where u can snap with the fingers and the Camera will take Automaticly a Picture : Sound Triger.
is that Possible on 1100D ?
I have Runnig the lastet Nightly and the R3 Firmware.
Quote from: 47Crows on August 15, 2013, 10:57:19 AM
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).
hi i found that... but i think i cant get it to work,... how is to be used?
this is what i see
https://www.dropbox.com/s/d9h79tzcz3euhor/2013-08-27%2018.41.38.jpg
https://www.dropbox.com/s/0hczrimt8b1dyht/2013-08-27%2018.41.45.jpg
i found the name of the function on nikon http://www.d5100dslr.com/tutorials/selective-color/
Quote from: nanomad on June 06, 2013, 12:25:09 PM
Well, the thing is the 1100D has the same capabilities the 600D has, so around 960px wide images BUT we also have half the memory of the 600D available which means no RAW video. I'll enable all the other RAW-related stuff though (zebras, ETTR, spotmeter)
As I see several are requesting this, I am sure I speak for most when I say we are thrilled to read that you are working on ETTR for the 1100D!! :)
The 1100D is a highly capable camera, 4K capable (timelapse) with very good low light performance.
With ETTR/auto-ETTR enabled on this camera, we have an affordable timelapse bad-a** 4K capable monster, that can produce flicker-free timelapses from dusk til dawn! ;)
Any news on progress on ETTR is welcome! :)
Your hard work is appreciated!
Quote from: uniextra on August 27, 2013, 07:40:33 PM
hi i found that... but i think i cant get it to work,... how is to be used?
this is what i see
https://www.dropbox.com/s/d9h79tzcz3euhor/2013-08-27%2018.41.38.jpg
https://www.dropbox.com/s/0hczrimt8b1dyht/2013-08-27%2018.41.45.jpg
i found the name of the function on nikon http://www.d5100dslr.com/tutorials/selective-color/
I think you and 47crows are having a little misunderstanding about what you are intending to do. You mentioned the word "focus" in your original post, but I think what you want to do has nothing to do with focus.
It appears that what you want to do is desaturate an image except for one particular color that you can select. This is not at all what focus peaking does. Focus peaking just draws colored dots on the live view screen to help you easily see what part of the image is in focus, and it only shows on the screen, once you take an image it will look normal.
What you are trying to do is very easy to do (and should be done) in post, but not in camera. Most devs don't want to waste time making ML do things that can easily be done in post (see the 4th item in this list: http://www.magiclantern.fm/forum/index.php?topic=950.0 ). If you would like to learn how to do this make a new thread in http://www.magiclantern.fm/forum/index.php?board=14.0 and myself or someone else will help you, but I'm not going to explain it here b/c it's off topic.
Hi A1ex/Nanomad,
the first post looks weird since the forum got a new layout. It's screwed, look at the bullet points! :o
Hi there!
I would like to help with the development of ML for 1100D. I have set up the toolchain, cloned the repository and played around with basic modules. I have a lot of experience in C, much less in reverse engineering/camera hardware. Is there anything I can do?
Quote from: thn-d on August 30, 2013, 09:44:48 AM
Hi A1ex/Nanomad,
the first post looks weird since the forum got a new layout. It's screwed, look at the bullet points! :o
Works again for me in IE, but still giant bullet points in FF. The page source looks unsuspicios, so I tend to believe the problem is on my side. Sorry!
Hi again!
I am trying to reactivate RAW stuff. First things first, so I've tried LV:
RAW_LV_EDMAC is 0xC0F26208
CAM_COLORMATRIX1 is
6444, 10000, -904, 10000, -893, 10000, \
-4563, 10000, 12308, 10000, 2535, 10000, \
-903, 10000, 2016, 10000, 6728, 10000
dynamic_ranges is {1099, 1098, 1082, 1025, 965, 877, 784}
I have defined CONFIG_RAW_LIVEVIEW and a RAW histogram appears when I switch to LV. But LV freezes, the camera seems to take a picture and crashes with a nice Err 70 (assert 0 in evf). I am not quite sure to understand what is going on. Any ideas?
EDIT: And about Photo mode, I think we need a SSS_STATE (which should be easy to guess considering addresses of other cameras). How can I generate a state diagram from the firmware? And how do I use the interception code to find RAW_PHOTO_EDMAC?
not perfect like a true ettr mode but I find uniWB in Av get similar results. Guess you could experiment with turning up EC+/- if shooting scenes where the correctly exposed pics histogram is shifted right (eg. predominantly/exclusively sky compositions at dawn).
YMMV but I found this works well enough for me as there is less bias and underexposure than vanilla WB (as far as raw goes obviously) since there is no RGB multipliers and histo clipping mirrors raw much closer than vanilla wb which is jpeg data made with multiplier values in the channels to generate a jpeg which often means good looking exposures are actually a stop under in cr2.
I only use timelapse for star stacking (dss and registax) so always in M never Av so no experience of how it may work out for long timelapse stuff on night to dawn/dusk transitions where obviously some semiauto exposure may be more useful but thought I'd mention it in case not tried that approach.
I can help you to test them
Hi.
Is it possible to set the ISO to "auto" when you are in Exp. Override?
Thank you, and sorry for my bad english :-\
Any idea how close we are to a stable build?
I have to say, it feels like the old 1100D has been forgotten :-\
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.
Oh no, I hope it will be fixed. Please keep a working download link for the 1100D! :(
Edit:
Latest build failed. As a workaround, navigate to http://builds.magiclantern.fm/ , select the 1100D and click on the "Show Older Builds" button.
Edit2: All listed older builds have failed, too, so Where is the last downloadable build?
Edit3: All builds fail after
make[2]: Entering directory `/var/lib/jenkins/jobs/1100D.105/workspace/modules/raw_rec'
Since raw_rec isn't supported for 1100D anyway, isn't it a problem that it enters that directory and tries to build there?
Here are the words of wisdom from the master himself (regarding why the 1100D builds fail):
Quote from: nanomad on September 10, 2013, 09:16:34 AM
The 1100D is undergoing work to support raw if possible. The builds will resume shortly
See reply #244 here: http://www.magiclantern.fm/forum/index.php?topic=3072.225
I am a complete ignorant of anything concerning Magiclantern and everything discussed in this thread.
I just want to download Magiclantern on my 1100d for the intervalometer function (I live in Egypt and can't find a physical intervalometer device so Magiclantern is my only chance of timelapse.)
So is there a version I can download that would work on my 1100d?
P.S: I am aware of the danger and know there isn't an official version for the 1100d.
Quote from: Ebrahim Saadawi on September 13, 2013, 01:29:13 PM
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!
If the 1100D has been abandoned it is sad :( - But please let us know.
I am hoping for auto-ETTR for the 1100D for timelapse usage..
Quote from: Northernlight on September 13, 2013, 08:58:51 PM
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.
Truth be told, I'm just helping out a new dev with it :)
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.
Quote from: 47Crows on September 13, 2013, 08:11:11 PM
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!
Thank you, Sir. Very helpful.
But I faced a strange problem when trying to copy the files to the root of the SD card. The card wouldn't let me copy anything onto it, and gives me a message saying "you don't have permission to perform this action".
I tried putting the SD card straight into the computer's card reader, and tried an external card reader, and also tried accessing the card through the USB cable with the card inside the camera.
I am using windows 7. Is there anything I can do to be able to copy the ML files to the card?
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.
Quote from: 47Crows on September 14, 2013, 04:23:28 PM
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.
Thank you a lot. The SD formatter worked and I copied the files to the card.
Thank you again.
Don't mention it brah, glad to help.
I have been using ML on my 1100D from long time now. But I have used only few features of it which I use almost daily. Like custom focus point selection, trap focus, one click zoom etc. I must say it really helps me. Thanks a lot dev.
Now I was wondering about video features supported on 1100D. Is there a list of supported features for video? I have no idea about it so far but I would like to test and help reporting bugs if I can.
Thanks.
I just downloaded and started using ML on my new 1100D. I have one thing to say, THIS IS FREAKING BRILLIANT! It's almost too good to be true (not to mention free)!
I now have full manual control over video, ISO, Shutter speed and aperture. (which wasn't in my wildest dreams for the 1100d)
I can shoot at 24fps with framerate override and even do timelapse at less than 1 fps without wearing out the shutter.
HDR video is absolutely incredible.
Other small things like rack focus, magic zoom, histogram, peeking and zebras are very helpful and easy to use, just like on my old professional camcorders.
I just can't say how grateful I am to you guys at ML and I think you should start charging for this. It's only your right.
I'd be glad to help with funding or testing to help the development.
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.
Hey there, I'm a curious guy, looked all over the internet to no avail, and didn't get a response in the IRC channel. Because of that, I feel that maybe I might have just enough justification to post here:
Is it possible to shoot 1080p with the T3 using Magic Lantern?
Consider me a silly dreamer or something - I was just wondering.
No, the camera is lacking the encoder path for full HD
I've got to say how much I love magic lantern and how it just helps us who can't afford the expensive dslr's out there and without magic lantern I wouldn't have more work space with my videos!
But I was wondering I just got a nightly build and most of the modules don't seem to work like the raw and dual iso module it says that it will load on next reboot but when I turn off then turn on with the on and off switch my camera just says error linking failed on the bottom of the screen. I know it is just a nightly build but i was wondering if I missed anything? Or if there is a way to reboot my camera with working modules ,is there a link where i can get working links for the modules?
Somebody should fix the build system and do not bundle the modules that are not working (nanomad?)
The new builds don't have them, simply delete the old ones from the card
The latest successful 1100D build (sep17) does have them.
Bug found: make clean only cleans configured modules while zip just bundles all the mo files it finds. Fix coming
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.
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.
Quote from: dmilligan on September 19, 2013, 06:50:19 PM
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.
hi everybody,
i am planning to get a 1100d, using ml specially for sound and light trigger.
i ve been looking for a list of what is and is not working in the current night build, no luck
where can i find it?
thxx for your help
best regards
herve
Someone generated a document from the source code showing the state of all features on all of the cameras, but I don't remember where I saw it, so I'd just go straight to the source:
https://bitbucket.org/hudson/magic-lantern/src/ce9fb256205c0b850ca7209b26973f0788e49447/platform/1100D.105/features.h?at=unified
lines that start with #undef means that feature is disabled (b/c it's not working yet) on the 1100D
Basically everything that has to do with audio and stuff that depends on RAW image buffers (like raw_rec and ettr) are not working (yet)
thxx a lot, so no audio trigger i guess :/
well wait and see then :)
There is the features page, idk if it is being actualized
http://nanomad.magiclantern.fm/nightly/features.html
thxx a lot, very promising!
wich parameter is the motion trigger using the light?
(btw how come i never receive email notification when you reply?)
thx for your time
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).
New font backend. FONTS.DAT was removed. You don't need it.
http://www.magiclantern.fm/forum/index.php?topic=8142.0
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.
You should only use the fir file with the build it came with and then after the the install is complete update to the nighlies. The fir files were not intended to be used with the nightlies.
Nightlies are not working for me, when I want to install ML my camera says I need a firmware update. What happened?
How are you installing ML? I can't see why it asks for an update....
Please upload a video
I download the nightly build, then I extract the zip and I can see 4 files: "ML", "autexec.bin", "INSTALL.pdf" and "UserGuide.pdf". I copy all the files in my low-level formated SD card but when I try to install, my camera says "to update you need a memory card with firmware". I realized that in old nightlies there was also the flie "1100D-105.fir" and I can install these nightlies.
If you still need a video tell me and I will upload it.
Thanks for your time.
Got it, the bootflag enabler is missing. I'll let you know once it gets back in the builds (hopefully tomorrow)
I seem to have a recurring issue when going into playback mode. It looks like cached Photoshop XMP files from processing RAW pictures just crashes the whole thing. Removing them from the image directory fixes it.
Crash Log:
QuoteASSERT: FALSE
at Memory\Memory.c:188, task CtrlSrv
lv:0 mode:1
Magic Lantern version : v2.3.NEXT.2013Oct05.1100D105
Mercurial changeset : 4380d31e6230 (unified) tip
Built on 2013-10-05 00:25:14 UTC by [email protected].
Free Memory : 281K + 300K
Anybody else have this issue?
trying to load ML for the first time
getting FONTS.DAT not found
BOOTDISK flag is disabled
Magic Lantern is not installed etc
was hoping somebody can advise how to fix this issue, I've been reading this thread can see a couple of people having same issue but getting confused as im very new to ML and need a step by step idiot guide can somebody please help? :)
best regards,
Zorgan
Quote from: zorgan on October 05, 2013, 07:48:37 PM
trying to load ML for the first time
getting FONTS.DAT not found
BOOTDISK flag is disabled
Magic Lantern is not installed etc
was hoping somebody can advise how to fix this issue, I've been reading this thread can see a couple of people having same issue but getting confused as im very new to ML and need a step by step idiot guide can somebody please help? :)
best regards,
Zorgan
Try another Nightly Build.. e.g. Sep17!!
Any updates on progression on auto-ETTR etc?
Nope, seems like the 1100D has been crippled in the RAW section. This is probably the side effect of the stuff Canon did to the camera software to lock out other features (like 1080p recording)
So what you are saying there will be no ETTR on the 1100D/T3, Oh that is sad! :(
Thanks for you reply though!
Why does Magic Zoom keep flickering when activated? It's an awesome feature but I can't use it due to that flicker. Too distracting :S
Because it needs a better vsync algorithm . Feel free to come up with one :)
Okay I am really a noob to installing ML on cameras. I own an 1100D (soon to upgrade to 70D) and want to modify my current camera. I tried following the instructions that were on the main website. If this thread is still active, it would be much appreciated if someone could help a brother out and help me with proper installation of this wonderful software on my POS camera. (I say that with the utmost endearing context)
Today's build failed. Do you have any idea when the stable build will be ready and if there is any chance of 1080p video? Thanks
I submitted a patch to fix the 1100D build but it has not yet been merged. 1080p is impossible. Asking about when a stable build will be ready is a bit of a troll question (http://www.magiclantern.fm/faq.html#q45)
I'd also like to report a crash every so once in a while during playback. Granted I am running the older version from august. There does seem to be a freeze up randomly in video live view. Here's the crash logs.
ASSERT: 0
at Evf\EvfState.c:1190, task Evf
lv:1 mode:20
Magic Lantern version : v2.3.NEXT.2013Jul31.1100D105
Mercurial changeset : aac317826b59 (unified) tip
Built on 2013-07-31 02:15:09 by [email protected].
Free Memory : 240K + 400K
ASSERT: FALSE
at Memory\Memory.c:188, task MetaCtg
lv:0 mode:1
Magic Lantern version : v2.3.NEXT.2013Jul31.1100D105
Mercurial changeset : aac317826b59 (unified) tip
Built on 2013-07-31 02:15:09 by [email protected].
Free Memory : 231K + 256K
ASSERT: FALSE
at Memory\Memory.c:188, task MetaCtg
lv:0 mode:20
Magic Lantern version : v2.3.NEXT.2013Jul31.1100D105
Mercurial changeset : aac317826b59 (unified) tip
Built on 2013-07-31 02:15:09 by [email protected].
Free Memory : 232K + 214K
ASSERT: FALSE
at Memory\Memory.c:188, task MetaCtg
lv:0 mode:20
Magic Lantern version : v2.3.NEXT.2013Jul31.1100D105
Mercurial changeset : aac317826b59 (unified) tip
Built on 2013-07-31 02:15:09 by [email protected].
Free Memory : 232K + 213K
Update your build
Have the new nightlies the file called "1100D-105.fir"?
Last build avaiable (4/11/2013) seems not downloadable (build failed), any info?
I've just found time to start using my 1100D again, so I came here looking for the latest and greatest. The last build that didn't fail seems to be on 20oct13 - is that (relatively) safe to use, or do I need to go farther back? Is there a list somewhere of which features the 1100D port currently supports (or tries to)? Does a month of failed builds suggest that the 1100D port is currently sidelined or abandoned?
http://nanomad.magiclantern.fm/feats.html
1100D - Magic Lantern - video mode.
I can do a Shutter Lock 1/50 and ISO lock?
No such option without ML...
I can lock ISO with * button but this is not a good way
...
1100D support became outdated. :(
(UP)
Yeah, too bad.
Is the version of 20 october usable?
Another 1100D user here.
Are there any usable builds right now?
Has this been abandoned?
It was really hard to install Magic Lantern in my Canon T3. So here we go:
- Download the last build from Oct 21: Download (http://builds.magiclantern.fm/jenkins/job/1100D.105/90/artifact/platform/1100D.105/magiclantern-v2.3.NEXT.2013Oct21.1100D105.zip)
- Unzip it into the memory card.
- Download the build from Sep 17: Download (http://builds.magiclantern.fm/jenkins/job/1100D.105/33/artifact/platform/1100D.105/magiclantern-v2.3.NEXT.2013Sep17.1100D105.zip)
- Extract only the file "ML/data/FONTS.DAT" to the folder "ML/data" of your memory card.
- Download the Magic Lantern firmware: Download (https://bitbucket.org/hudson/magic-lantern/issue-attachment/1150/hudson/magic-lantern/1333128527.7/1150/ml-1100d-105.fir)
- Copy it into the memory card's root.
- Insert the memory card on your cam and turn it on. Update your firmware.
Magic Lantern should install with no problems!
Quote from: pauloup on January 01, 2014, 08:28:20 AM
It was really hard to install Magic Lantern in my Canon T3. So here we go:
- Download the last build from Oct 21: Download (http://builds.magiclantern.fm/jenkins/job/1100D.105/90/artifact/platform/1100D.105/magiclantern-v2.3.NEXT.2013Oct21.1100D105.zip)
- Unzip it into the memory card.
- Download the build from Sep 17: Download (http://builds.magiclantern.fm/jenkins/job/1100D.105/33/artifact/platform/1100D.105/magiclantern-v2.3.NEXT.2013Sep17.1100D105.zip)
- Extract only the file "ML/data/FONTS.DAT" to the folder "ML/data" of your memory card.
- Download the Magic Lantern firmware: Download (https://bitbucket.org/hudson/magic-lantern/issue-attachment/1150/hudson/magic-lantern/1333128527.7/1150/ml-1100d-105.fir)
- Copy it into the memory card's root.
- Insert the memory card on your cam and turn it on. Update your firmware.
Magic Lantern should install with no problems!
Thanks for that, but that sounds very hacky.
How is the stability? Any crashes or problems while using it?
Quote from: davicorn on January 01, 2014, 04:15:57 PM
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.
My camera doesn't let me install ML. It says FONTS.DAT is missing, but I followed your instructions.
Hi,
I am very new but bery interested in magic lantern for my 1100d. I admire the work devs have done to enable these awesome features and I am forever gratefull. I really like the idea of recording raw video on these relatively cheap camera's and it is sad that it appears to be too locked out to do on this one. I did come across this chart that looks similar to the one on the raw section of the forum(perhaps a newer/older version) detailing what cameras do raw at what settings and in this chart the 1100d does appear to be working. (http://news.doddleme.com/equipment/magic-lantern-raw-how-canon-cameras-perform/)
I presume this was an error but I am crossing my fingers and hoping someone did manage to get it working somewhat. I would love to help out in any way I can. I don't know any of the C languages so that would be testing only. I read nanomad's posts here and it seems like development towards raw on this camera is pretty much dead, which honestly is sad but understandable. Is this the case?
Quote from: littlebobbytables on January 02, 2014, 09:24:03 PM
Hi,
I am very new but bery interested in magic lantern for my 1100d. I admire the work devs have done to enable these awesome features and I am forever gratefull. I really like the idea of recording raw video on these relatively cheap camera's and it is sad that it appears to be too locked out to do on this one. I did come across this chart that looks similar to the one on the raw section of the forum(perhaps a newer/older version) detailing what cameras do raw at what settings and in this chart the 1100d does appear to be working. (http://news.doddleme.com/equipment/magic-lantern-raw-how-canon-cameras-perform/)
I presume this was an error but I am crossing my fingers and hoping someone did manage to get it working somewhat. I would love to help out in any way I can. I don't know any of the C languages so that would be testing only. I read nanomad's posts here and it seems like development towards raw on this camera is pretty much dead, which honestly is sad but understandable. Is this the case?
Hi I am a beginer in the magic lantern scene as well but I believe that that was a mistake indeed. But lets keep our fingers crossed ;)
Hello,
I am quite the beginner in this but I have a question that I would greatly appreciate if someone would answer it. If I am not mistaken there is no manual exposure adjustment in the video mode. Would this ever be able to be changed? Is it possible that we one day may have a way to manually adjust exposure? An answer would be awesome.
PS I am willing to test any proto-builds so feel free to email me! :)
Quote from: theEmoboy on January 02, 2014, 11:12:03 PM
Hello,
I am quite the beginner in this but I have a question that I would greatly appreciate if someone would answer it. If I am not mistaken there is no manual exposure adjustment in the video mode. Would this ever be able to be changed? Is it possible that we one day may have a way to manually adjust exposure? An answer would be awesome.
PS I am willing to test any proto-builds so feel free to email me! :)
Hey there,
I'm pretty sure you can actually do so. What I did to accomplish this is to go to the ML menu, Expo tab, turn on Exp. Override and then changing the settings in the same tab. I hope this helps!
Quote from: pauloup on January 01, 2014, 08:28:20 AM
It was really hard to install Magic Lantern in my Canon T3. So here we go:
- Download the last build from Oct 21: Download (http://builds.magiclantern.fm/jenkins/job/1100D.105/90/artifact/platform/1100D.105/magiclantern-v2.3.NEXT.2013Oct21.1100D105.zip)
- Unzip it into the memory card.
- Download the build from Sep 17: Download (http://builds.magiclantern.fm/jenkins/job/1100D.105/33/artifact/platform/1100D.105/magiclantern-v2.3.NEXT.2013Sep17.1100D105.zip)
- Extract only the file "ML/data/FONTS.DAT" to the folder "ML/data" of your memory card.
- Download the Magic Lantern firmware: Download (https://bitbucket.org/hudson/magic-lantern/issue-attachment/1150/hudson/magic-lantern/1333128527.7/1150/ml-1100d-105.fir)
- Copy it into the memory card's root.
- Insert the memory card on your cam and turn it on. Update your firmware.
Magic Lantern should install with no problems!
Okay, I got ML installed on my 1100d. The fonts thing didn't really want to work, so I sprinkled the fonts.dat in multiple places. I think putting it in the
root did the job though.
Before being able to install ML, you need to
format your card (low level) through your camera,
reset camera functions and
reset custom func while your setting is set on
manual.
Rest worked completely fine. Thanks for that.
Now some time to play with ML ~
Quote from: littlebobbytables on January 02, 2014, 11:46:10 PM
Hey there,
I'm pretty sure you can actually do so. What I did to accomplish this is to go to the ML menu, Expo tab, turn on Exp. Override and then changing the settings in the same tab. I hope this helps!
Wow! Thanks! this changes alot! You sir have hade my day ;)
Quote from: littlebobbytables on January 02, 2014, 11:46:10 PM
Hey there,
I'm pretty sure you can actually do so. What I did to accomplish this is to go to the ML menu, Expo tab, turn on Exp. Override and then changing the settings in the same tab. I hope this helps!
could you possibly explain it to me?
i cant seeem to figure it out :'(
Quote from: theEmoboy on January 03, 2014, 07:59:38 PM
could you possibly explain it to me?
i cant seeem to figure it out :'(
I will be making a video/tutorial explaining some basic stuff on ML on the 1100D in the near future.
Wow thinks that would be great!
If you dont mind email me the link ;)
Quote from: theEmoboy on January 05, 2014, 06:15:28 PM
Wow thinks that would be great!
If you dont mind email me the link ;)
The audio sucks, man I wish I had another proper camera, but here it is: /watch?v=uQHNYSWI6qg
Hey man thasnksss!!! ;D it still is understandable and you showed me what i needed im leaving a like
Quote from: pauloup on January 01, 2014, 08:28:20 AM
It was really hard to install Magic Lantern in my Canon T3. So here we go:
- Download the last build from Oct 21: Download (http://builds.magiclantern.fm/jenkins/job/1100D.105/90/artifact/platform/1100D.105/magiclantern-v2.3.NEXT.2013Oct21.1100D105.zip)
- Unzip it into the memory card.
- Download the build from Sep 17: Download (http://builds.magiclantern.fm/jenkins/job/1100D.105/33/artifact/platform/1100D.105/magiclantern-v2.3.NEXT.2013Sep17.1100D105.zip)
- Extract only the file "ML/data/FONTS.DAT" to the folder "ML/data" of your memory card.
- Download the Magic Lantern firmware: Download (https://bitbucket.org/hudson/magic-lantern/issue-attachment/1150/hudson/magic-lantern/1333128527.7/1150/ml-1100d-105.fir)
- Copy it into the memory card's root.
- Insert the memory card on your cam and turn it on. Update your firmware.
Magic Lantern should install with no problems!
So this must fix the problem of the text not displaying correctly, right?
Hi,
ML for 1100D is dead? :-[
regards
starbase64
Quote from: starbase64 on January 12, 2014, 02:05:55 AM
Hi,
ML for 1100D is dead? :-[
regards
starbase64
I'm also quite interested in the current state of things regarding development. I hope nanomad sees this.
It will be back soon, thanks to dmilligan.
Quote from: a1ex on January 12, 2014, 03:16:03 PM
It will be back soon, thanks to dmilligan.
Praise the lord for he has spoken!
Quote from: pauloup on January 01, 2014, 08:28:20 AM
It was really hard to install Magic Lantern in my Canon T3. So here we go:
- Download the last build from Oct 21: Download (http://builds.magiclantern.fm/jenkins/job/1100D.105/90/artifact/platform/1100D.105/magiclantern-v2.3.NEXT.2013Oct21.1100D105.zip)
- Unzip it into the memory card.
- Download the build from Sep 17: Download (http://builds.magiclantern.fm/jenkins/job/1100D.105/33/artifact/platform/1100D.105/magiclantern-v2.3.NEXT.2013Sep17.1100D105.zip)
- Extract only the file "ML/data/FONTS.DAT" to the folder "ML/data" of your memory card.
- Download the Magic Lantern firmware: Download (https://bitbucket.org/hudson/magic-lantern/issue-attachment/1150/hudson/magic-lantern/1333128527.7/1150/ml-1100d-105.fir)
- Copy it into the memory card's root.
- Insert the memory card on your cam and turn it on. Update your firmware.
Magic Lantern should install with no problems!
I just tested this, and I can confirm that it works. However, I ended up placing the
FONTS.DAT into the card's root. It was not recognized in
ML/data for some reason.
A much easier way to install ML for the first time is to simply
- Download the RC3 (http://nanomad.magiclantern.fm/1100D/magiclantern-v2.3.1100D.RC3.zip) from the OP, and extract it to a clean (format in camera) SD card.
- Run the firmware update procedure in the Canon menu, the ML fir will set the boot flag when you do this and you should get a green screen. Turn off camera and remove SD card.
- Now update to the latest nightly by deleting all ML files on the card and replacing them with the most recent build.
No need to mess with fonts.dat.
Quote from: a1ex on January 12, 2014, 03:16:03 PM
It will be back soon, thanks to dmilligan.
When it comes back, I will need everyone's help to keep it maintained and up to date. I do not have time to test every feature, but if you submit
good bug reports and do good testing (http://www.magiclantern.fm/forum/index.php?topic=9516.0), it should be easy for me to fix issues and keep this port up to date.
The 1100D port seems to be quite stable atm (I've been just compiling it myself). I haven't had a crash in months, and all of the features I use regularly work as expected. I'm not aware of any enabled feature that doesn't work as advertised, but I also don't use every feature regularly which is why I need your help testing.
Quote from: dmilligan on January 12, 2014, 10:30:58 PM
A much easier way to install ML for the first time is to simply
- Download the RC3 (http://nanomad.magiclantern.fm/1100D/magiclantern-v2.3.1100D.RC3.zip) from the OP, and extract it to a clean (format in camera) SD card.
- Run the firmware update procedure in the Canon menu, the ML fir will set the boot flag when you do this and you should get a green screen. Turn off camera and remove SD card.
- Now update to the latest nightly by deleting all ML files on the card and replacing them with the most recent build.
No need to mess with fonts.dat.
When it comes back, I will need everyone's help to keep it maintained and up to date. I do not have time to test every feature, but if you submit good bug reports and do good testing (http://www.magiclantern.fm/forum/index.php?topic=9516.0), it should be easy for me to fix issues and keep this port up to date.
The 1100D port seems to be quite stable atm (I've been just compiling it myself). I haven't had a crash in months, and all of the features I use regularly work as expected. I'm not aware of any enabled feature that doesn't work as advertised, but I also don't use every feature regularly which is why I need your help testing.
confirmed tester
Made a video comparing base and higher bitrates: /watch?v=Pwhm1g3VQfA
Hi guys. I am an user of your ML software on my 1100D from 1 year. I follow this forum often but I never writed into.
If it's possible I want to contribute in some way, subitting crash reports. Do you know how I can do that? Should I send any file to a mail address? Could anybody explain a procedure?
Thanks
https://bitbucket.org/hudson/magic-lantern/issues/
before submitting, please:
- check for duplicates
- detail the exact steps to replicate the issue*
- include logs/screenshots/video if applicable
- include raw data files (.CR2 or .DNG) if applicable
- include your magic.cfg
- include build/version information
- make sure it's actually a ML bug and not Canon (hold set on startup to boot to regular Canon firmware)
- try the most recent build to see if the issue has already been resolved
- try and isolate the issue to a specific build (try older builds to see if you can figure out exactly when the bug was introduced)
- try different settings (ML and Canon) to determine the full scope of the bug (e.g. is it just in M or does it happen in Av and Tv too?)
*a bug can't be fixed unless it can be replicated, so a bug report is useless if you don't describe steps to replicate it.
I'm interested in trying and testing this out. Just have a few questions. Is it possible to brick, break, ruin the device? Is the firmware reversible? If I wanted to go back to the original firmware? Also, how do you dl the latest builds? For every build it says "This build failed"
Quote from: cinco312 on January 16, 2014, 09:48:51 AMIs it possible to brick, break, ruin the device?
Top of page -> User Guide -> F.A.Q.
Quote from: cinco312 on January 16, 2014, 09:48:51 AM
Is the firmware reversible?
ML is *no* firmware!
Top of page -> User Guide -> F.A.Q.
The only change done to the camera is setting a bootflag and that is reversible but not for all cameras as of today.
Quote from: cinco312 on January 16, 2014, 09:48:51 AM
If I wanted to go back to the original firmware?
Because it's no firmware but an additional software running on top of Canon's firmware: Yes
Top of page -> User Guide -> F.A.Q.
Quote from: cinco312 on January 16, 2014, 09:48:51 AM
Also, how do you dl the latest builds? For every build it says "This build failed"
Read some of the last posts. And ML manual. And F.A.Q.
Is there a way to lock the exposure in the video mode? I seem to have some issues with it changing dramatically, like its trying to capture the blown out highlights and under exposed shadows while filming. Also, 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.
Quote from: True-shot on January 19, 2014, 11:49:01 PM
... 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.
Quote from: 47Crows on January 20, 2014, 12:17:06 AM
Yeah, that's a (general, I think) bug with (zoom?) kit lenses. The aperture doesn't stay put for some reason.
The reason: http://www.magiclantern.fm/forum/index.php?topic=9776.msg94338#msg94338
Quote from: True-shot on January 19, 2014, 11:49:01 PM
Is there a way to lock the exposure in the video mode? I seem to have some issues with it changing dramatically, like its trying to capture the blown out highlights and under exposed shadows while filming. Also, 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.
Tried this?
Go to the ML menu, Expo tab, turn on Exp. Override and then changing the settings in the same tab.
I hope this helps!
1100D nightly builds running again!
Thank you very much! I have been following this thread for about a year now and i thought this was the end of Magic Lantern updates for the 1100D. I really appreciate this and I would like to help with nightly build bug testing.
Thank you very much, I also appreciate this!
Was this due to merging the fixes from dmilligan? Thank's also to dmilligan anyway!
Yes it was. Kudos to him for sorting everything out
Thank you guys!
Quote from: littlebobbytables on January 20, 2014, 06:59:33 PM
Tried this?
Go to the ML menu, Expo tab, turn on Exp. Override and then changing the settings in the same tab.
I hope this helps!
That's what I was talking about, I set the Expo manually but sometimes (possibly when its too dark) it changes back and forth and I don't seem able to lock it with out setting it brighter or focusing the center away from that spot.
Hi,
post script "align+enfuse" dosen't work, cant find output HDR_xxx.jpg.
settings: manuel mode with ML advanced braketing 3pics 1ev sequenz 0 + ++
regards
starbase64
can you post the script that was generated and any output from it?
also, OS version?
Hi,
here is the content of HDR_9547.sh
latest ML version and canon 1100D with Firmware 1.05
edit: all images are _MG_xxx.jpg named and not IMG_xxx.jpg, no idea why
regards
starbase64
#!/usr/bin/env bash
# HDR_9547.JPG from IMG_9547.JPG ... IMG_9549.JPG with aligning first
align_image_stack -m -a HDR_AIS_9547 IMG_9547.JPG IMG_9548.JPG IMG_9549.JPG
enfuse "$@" --output=HDR_9547.JPG HDR_AIS_9547*
rm HDR_AIS_9547*
Hi,
completely reseted my camera and now all pics named as IMG_xxx.jpg but no HDR_xxx.jpg.
regards
starbase64
#!/usr/bin/env bash
# HDR_9559.JPG from IMG_9559.JPG ... IMG_9561.JPG with aligning first
align_image_stack -m -a HDR_AIS_9559 IMG_9559.JPG IMG_9560.JPG IMG_9561.JPG
enfuse "$@" --output=HDR_9559.JPG HDR_AIS_9559*
rm HDR_AIS_9559*
and what is the output from the script (like the text output from the command line when you run it)? what OS are you using, mac or linux? do you have enfuse installed correctly and on the path?
Hi,
not on pc, directly on camera. created hdr directly on the camera.
(http://www7.pic-upload.de/thumb/24.01.14/an9eb75zgjwz.jpg) (http://www.pic-upload.de/view-22050788/VRAM1.jpg.html)(http://www7.pic-upload.de/thumb/24.01.14/e7kvgzyetlj4.jpg) (http://www.pic-upload.de/view-22050789/VRAM2.jpg.html)
regards
starbase64
The scripts are called 'post scripts' because they are made to be run 'in post' on the computer. They cannot be run on camera, there is no support for in camera HDR creating. This script is a bash shell script meant to be run on a *nix operating system (mac or linux) and uses the open source program called enfuse to merge the photos. These scripts are mostly just for convenience to allow easier batch processing of HDR brackets in post.
Also, you should be using raw for HDR not jpeg, raw's already have way more information and DR in them without stacking. Simply using raw instead of jpg you may find covers the DR of your scene without the need to take extra shots.
Ok, iv'e installed photoshop on pc.
Quote from: starbase64 on January 24, 2014, 03:50:34 PM
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.
Thanks to nanomad we now have photo raw (raw data in image review), which means we can use AutoETTR! I've tested it and it appears to be working. This is fantastic news for timelapse.
Also, I just took the first 1100D dual iso picture with adtg_gui, yay! (hopefully dual_iso support coming soon)
dual ISO 100/1600:
(https://bitbucket.org/dmilligan/magic-lantern/downloads/IMG_2910.jpg)
ISO 100:
(https://bitbucket.org/dmilligan/magic-lantern/downloads/IMG_2908.jpg)
Nice work. 0.4EV from the ADTG tweak is handy too :)
I have a telescope arriving later today and I'm super keen to see what dual_iso can do.
Have you looked at the other commits (https://bitbucket.org/hudson/magic-lantern/commits/a8bef7be9543b1c59edb6ad99607676f97776b0d) for camera (https://bitbucket.org/hudson/magic-lantern/commits/e01c19c45239edc83d464d93c6eeb86dba8e6425) support to dual_iso.
Quote from: Audionut on January 29, 2014, 03:22:00 AM
I have a telescope arriving later today and I'm super keen to see what dual_iso can do.
Nice! What is it?
Quote
Have you looked at the other commits (https://bitbucket.org/hudson/magic-lantern/commits/a8bef7be9543b1c59edb6ad99607676f97776b0d) for camera (https://bitbucket.org/hudson/magic-lantern/commits/e01c19c45239edc83d464d93c6eeb86dba8e6425) support to dual_iso.
I've got most of it figured out, I PM'd a1ex about the rest.
Quote from: dmilligan on January 29, 2014, 03:54:22 AM
Nice! What is it?
130mm with tracking mount. I absolutely wanted tracking mount, and anything larger (scope size) was double the price. It's an EQ2 mount with motor drive on the RA axis, and I think I should be able to remove the scope and attach the camera directly to the mount with wide angle too.
I live in the country and have easy access to dark skies. If I have my calculations right in stellarium, I should be able to take some wonderful photos.
I've never had tracking before, so sitting here twiddling my thumbs waiting for the postie to arrive so I can setup it up and become acclimatised. It's windy and cloudy here atm, but I'll (hopefully) put something up in the photo section tomorrow.
It's something I've wanted for a long time, and your photos were the last little bit of inspiration I needed to make it happen :)
Does this mean that the dual iso feature will be ported to the 1100D?
Yes
Thank you nanomad and dmillgan! That was awesome!
I have latest nightly build and writing me "FONTS.DAT NOT FOUND". Any help?
read this thread starting at reply #914
thx, now it works. :)
Looks like another camera got dual_iso. Nice work dmilligan.
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?
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? :D), 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.
Quote from: andreadoore on January 31, 2014, 08:04:18 PM
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)
Can you share a silent DNG? I fear the state transition that we target may not be the most correct one
Quote from: nanomad on January 31, 2014, 08:58:58 PM
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
Ugh that's nasty..... I'll see if I can spot something weird
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
Of course, silent pics need raw LV ... which the 1100D hasn't ....
Quote from: nanomad on January 31, 2014, 11:00:04 PM
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.
Did you compile ML yourself?
Quote from: 47Crows on February 01, 2014, 12:04:49 AM
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.
The fix was committed to the repository minutes before you posted this message, so you need to wait for the next nightly build (IDK when this happens), or build yourself from source.
Many of the other things you report as not working I believe have something to do with the fact that many of these things have just reached the repository today, and so probably are not in the builds yet. ETTR and dual iso are working just fine for me, so I'd say you just need to wait a day and try again. I appreciate your eagerness to help though. You can always check the commit history (https://bitbucket.org/hudson/magic-lantern/commits/all) and compare that to the hash or timestamp on the build.
Quote from: 47Crows on February 01, 2014, 12:04:49 AM
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.
There is no raw data available for LV. The histogram and zebras fall back to YUV data. It would probably be helpful if there was at least a warning about this in the menu, but this is expected behavior.
You can also hit the "changelog" button on the nightly download page. This will show you the latest commits in that build.
Quote from: dmilligan on February 01, 2014, 03:49:17 AM
It would probably be helpful if there was at least a warning about this in the menu, but this is expected behavior.
I believe all you have to do is:
a) return 0 from can_use_raw_overlays_menu() on the LiveView photo branch if there's no CONFIG_RAW_LIVEVIEW.
b) add a meaningful message in menu_set_warning_raw (like raw is not working in LiveView on this camera).
This code will be used whenever there's something that requires raw support (assumming it calls menu_checkdep_raw from its MENU_UPDATE_FUNC).
The warning is there. It even disables the whole ettr menu when in lv
... we were not talking about ETTR ;)
Oops I'll check dual iso too
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!
Can you upload a video of you using auto ettr and showing the -5EV bug?
Quote from: nanomad on February 01, 2014, 11:29:52 AM
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
Can you upload a cr2 of your test scene?
edit: ETTR does not work in LV, even the menu item says so...
Quote from: nanomad on February 01, 2014, 11:51:49 AM
Can you upload a cr2 of your test scene?
http://www.mediafire.com/download/2r415t2zc3khdxc/pre+and+post+ETTR.zip
EDIT:
Quote from: nanomad on February 01, 2014, 11:51:49 AM
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.
Just don't use ETTR in LV.. We will figure out a way to block it
Quote from: a1ex on February 01, 2014, 08:29:05 AM
I believe all you have to do is:
a) return 0 from can_use_raw_overlays_menu() on the LiveView photo branch if there's no CONFIG_RAW_LIVEVIEW.
b) add a meaningful message in menu_set_warning_raw (like raw is not working in LiveView on this camera).
This code will be used whenever there's something that requires raw support (assumming it calls menu_checkdep_raw from its MENU_UPDATE_FUNC).
The problems is more complicated than this and will require more significant refactoring to make the menu items logical in the situation that raw is not available in LV. Basically all the menu items are currently setup to assume that if raw is available at all, it is available in LV. We have the 1100D where this is not the case, and the menu items are extremely confusing even if I just add a warning here.
Here's what I mean:
The Histogram menu item will say:
• Histogram RAW RGB, Log, Dots
Even if I'm in LV where the histogram is not RAW, it is RAW during QR, so which histogram are we talking about? One of the histograms will be RAW and one won't. How do we convey this logically to the user? We can't say RAW histogram isn't working, it is working, sometimes...
I think this merits a complete rethink of the entire Overlay menu. Maybe there should be three separate overlay configurations: Movie, LV, and QR (maybe even a 4th MovieRaw). Currently the Overlay menu is very nonsensical for anyone who is not extremely familiar with how it works, in terms of what settings apply in what particular situations.
I also don't think there's any particular reason to even give the user the choice of what type (RAW vs. YUV) of overlay to use. The particular situation totally determines the type that should be used:
h264? - always use YUV overlays
raw_rec/mlv? - always use raw overlays
photo?
picture_quality_raw? - use raw if available, otherwise warn that YUV is being used instead
picture_qualtiy_jpeg? - always use YUV
thoughts?
Will answer after you try it.
Quote from: a1ex on February 01, 2014, 11:21:55 PM
Will answer after you try it.
I did:
--- a/src/raw.c
+++ b/src/raw.c
@@ -1690,6 +1690,13 @@
MENU_UPDATE_FUNC(menu_checkdep_raw)
{
+#ifndef CONFIG_RAW_LIVEVIEW
+ if(lv)
+ {
+ MENU_SET_WARNING(MENU_WARN_NOT_WORKING,"RAW LV is not working on this camera");
+ }
+ else
+#endif
if (!can_use_raw_overlays_menu())
{
menu_set_warning_raw(entry, info);
it's still quite confusing
Did you try to do like I said here?
Quote
a) return 0 from can_use_raw_overlays_menu() on the LiveView photo branch if there's no CONFIG_RAW_LIVEVIEW.
b) add a meaningful message in menu_set_warning_raw (like raw is not working in LiveView on this camera).
The logic is extremely confusing due to all the macros (sometimes I think ML could win http://www.ioccc.org) :P
is this what you mean?
diff --git a/src/raw.c b/src/raw.c
--- a/src/raw.c
+++ b/src/raw.c
@@ -1662,13 +1662,11 @@
return 1;
}
else
-#endif
{
/* outside LiveView: only pure RAW is known to work */
if (can_use_raw_overlays_photo())
return 1;
-#ifdef CONFIG_RAW_LIVEVIEW
/* in LiveView: we can display the raw overlays no matter what */
/* so use them also for sRAW and mRAW, even if this may not work in QR mode */
int raw = pic_quality & 0x60000;
@@ -1682,10 +1680,19 @@
MENU_UPDATE_FUNC(menu_set_warning_raw)
{
- MENU_SET_WARNING(MENU_WARN_NOT_WORKING,
- is_movie_mode() ? "[MOVIE] This feature requires you shooting RAW." :
- "[PHOTO] Set picture quality to RAW in Canon menu."
- );
+#ifndef CONFIG_RAW_LIVEVIEW
+ if(lv)
+ {
+ MENU_SET_WARNING(MENU_WARN_NOT_WORKING,"RAW LV is not working on this camera");
+ }
+ else
+#endif
+ {
+ MENU_SET_WARNING(MENU_WARN_NOT_WORKING,
+ is_movie_mode() ? "[MOVIE] This feature requires you shooting RAW." :
+ "[PHOTO] Set picture quality to RAW in Canon menu."
+ );
+ }
}
MENU_UPDATE_FUNC(menu_checkdep_raw)
Looks like Nano did half of the job, so it should work as I expect it to (which is basically exactly as you described).
So, in LiveView, histogram should print RAW only if the LiveView histogram is RAW. In photo mode, it should print RAW only if the QR histogram is RAW.
And this is auto-chosen based on picture quality.
Movie:
- H264 => YUV histogram.
- Some sort of raw recording => RAW histogram.
Photo:
- in LiveView, if pic quality is set to some sort of RAW => RAW histogram (if there is backend support), otherwise YUV
- in QR, if pic qualty is set to pure RAW (the only setting that works on all cameras), you get RAW overlays
So, with default settings, it tries to use RAW overlays whenever it makes sense. Try them on 60D, it should work like this.
The option for zebra (photo vs always) is there for speed reasons. Raw zebras are slow.
Adding a bunch of new menus doesn't sound like simplifying things to me.
Quote from: nanomad on February 01, 2014, 12:11:05 PM
Just don't use ETTR in LV.. We will figure out a way to block it
would this work? not sure if it will screw something else up (why is raw_lv_is_enabled() currently only checked for movie mode?):
diff --git a/modules/ettr/ettr.c b/modules/ettr/ettr.c
--- a/modules/ettr/ettr.c
+++ b/modules/ettr/ettr.c
@@ -728,7 +728,7 @@
if (lens_info.raw_iso == 0 && is_m) return 0;
if (lens_info.raw_shutter == 0 && is_m) return 0;
if (HDR_ENABLED && !AUTO_ETTR_TRIGGER_BY_SET) return 0;
- int raw = is_movie_mode() ? raw_lv_is_enabled() : pic_quality & 0x60000;
+ int raw = raw_lv_is_enabled() && (is_movie_mode() || pic_quality & 0x60000);
return raw;
}
Quote from: a1ex on February 02, 2014, 12:43:00 AM
Adding a bunch of new menus doesn't sound like simplifying things to me.
what I have in mind should make the menu simpler, I'll try and code something up so you'll have a better idea of what I mean
With global draw off for example, it won't work (because it won't be able to request the raw mode - it will give up before trying).
Hiding the option from the menu should be enough (only show auto snap and always on).
in 'always on' ettr still tries to run when you enter LV (and completely screws all the settings) even if raw data is not available, that is the bug. there's no separate option for 'only after you take a pic'. so basically until this is fixed you can't use ettr for QR and still use LV, i.e. I should still be able to use LV and have ettr work from QR data after the pic is taken, but I can't because ettr still tries to run
perhaps this is the problem
raw_lv_request();
int corr = auto_ettr_get_correction();
raw_lv_release();
the return value of raw_lv_request() is not actually checked by ettr
should it be:
if(!raw_lv_request()) return;
int corr = auto_ettr_get_correction();
raw_lv_release();
EDIT: okay, I now realize that is void function so that won't work
Correct, good catch.
You could even disable it completely in auto_ettr_polling_cbr: if (raw_lv_request == ret_0) return.
Quote from: a1ex on February 02, 2014, 09:38:13 PM
Correct, good catch.
You could even disable it completely in auto_ettr_polling_cbr: if (raw_lv_request == ret_0) return.
brilliant, that was what I was really looking for: check if the WEAK_FUNC is actually weak
okay, so 'raw_lv_request == ret_0' gives a compiler warning and doesn't actually work (ettr is still trying to run), this is used elsewhere to give menu warnings, and the warning don't work either
Weird they do work here...
well, now it works, that's weird... there's still a compiler warning though, maybe there is a more 'correct' way to do this, but I don't know, I'm not familiar with the specifics of weak functions in C
How this works: you are comparing two function pointers. You get the warning because the two functions have different prototypes, but since ret_0 does nothing, there are no side effects. The ABI takes care about compatibility.
You could cast the two pointers to thunk or void* or intptr_t for example, to get rid of the warning.
I'm tempted to write "if (&raw_lv_request == &ret_0)". It's the same thing for some historical reasons, but I feel it's a little more explicit (it's more obvious that you are comparing two function pointers).
I'd agree &raw_lv_request == &ret_0 seems more correct at least to me (I actually have to write some in C89 at work and this would be the syntax I'm used to), but when I tried it, it gave the same warning, so I wasn't sure what was going on. I didn't realize the functions had different prototypes. I guess then the most correct thing to do would be define a ret_void and use that instead of ret_0 or make raw_lv_request return something.
(I was actually more curios how the 'weak' stuff is implemented. How does it actually switch the symbol references dynamically like that, it's pretty cool and I didn't realize you could do it in C. I've done similar stuff but only in higher level languages)
Quick question: does motion detect with frame difference work on 1100D?
No, it says Motion level=0 even when moving the camera a lot. I am not able to get it to react at all
Got it, having the same problem on 5D3 123 and I bet on the 6D it doesn't work either.
Whenever i try to install the nightly build it says that FONTS.DAT not found?
EDIT: solved..
One question though.. is it possible to take double exposures with the current Magic Lantern?
Quote from: iDoggie on February 07, 2014, 02:45:52 AM
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.
1100D will be recording raw video. 640p @ 30 fps, but it's raw video nonetheless, right? 8)
Plus all the fancy stuff that comes with access to raw data in liveview (auto ETTR in LV, silent pics, ...)
That's great news! Thank you! :)
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.
Wow, Awesome. I was happy about the dual iso function, and a couple of weeks later. The 1100D will get RAW video recording, Thank you!
Awesome. Thank you so much for all your work.
Only one question: when I download a nightly build, the .zip only contains 2 files - ML folder and "autoexec.bin". Do I have to take "1100D-105.fir" from old nightlies to install it?
It's not needed
Thanks. For updating ML, can I just delete de files from SD card (from computer, not formatting) and placing the new files on it?
Sure
@nanomad: How long will we have to wait for access to 1100D raw video functionality? I hope you can get a version for us ASAP - it would be awesome!!
Thanks for bringing RAW VIDEO to the 1100D!! :)
It will take a while.
OK, thanks anyway!
Maybe you can supply us with a test/debug version...that would be nice to :)
I have a full week, daylight, snow and some horizontal blinds, a perfect environment for RAW, so I'm up for any preliminary tests.
Hi. I've been a long-time user of ML for the 1100D. Got a new camera and have been using that instead, but now I'm back on the 1100D.
My problem is, I can't seem to get ML on my 1100D anymore. I've followed the instructions as per http://wiki.magiclantern.fm/install to a tee, but I can't use the in-camera "Firmware Update" feature, as I'm lacking a firmware file.
I tried digging up an old .fir file from the "magiclantern-v2.3.1100D.RC3.zip", but when installing then, the install-process informed me that "fonts.dat" was missing.
I'm at a loss. Do you have any ideas on how to proceed?
In any case, thank your for the tremendous work you've put into maintaining this program. It is very much appreciated.
Don't mix the old fir file with the new build, use it with the build it came with, then update to the nightlies by simply copying over the new files to the card.
Quote from: dmilligan on January 12, 2014, 10:30:58 PM
A much easier way to install ML for the first time is to simply
- Download the RC3 (http://nanomad.magiclantern.fm/1100D/magiclantern-v2.3.1100D.RC3.zip) from the OP, and extract it to a clean (format in camera) SD card.
- Run the firmware update procedure in the Canon menu, the ML fir will set the boot flag when you do this and you should get a green screen. Turn off camera and remove SD card.
- Now update to the latest nightly by deleting all ML files on the card and replacing them with the most recent build.
No need to mess with fonts.dat.
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?
Will do
Thanks a bunch :)
Thank you for the time you take developing this. Really appreciated.
Hi,
How does this work > raw video and raw data in live view?
can i make timelapse without shutter?
regards
starbase64
Quote from: starbase64 on February 15, 2014, 04:51:35 PM
Hi,
How does this work > raw video and raw data in live view?
can i make timelapse without shutter?
regards
starbase64
Yes, when the raw function is developed, you will be able to combine it with FPS override and create raw timelapse (at 640p only I believe).
Anyway you can do that now but without having raw, just use the FPS override function and you can go down to 0.2 fps= frame each five seconds, with a five second shutter too if you want. But the results are of course 1280/720 frames, which I found very sufficient quality for video.
(PS: cool tip, use 35fps in FPS override and it gives quite good slowmotion when rendered to 24p!)
Hi everyone,
I am new here, but have been a ML Nightly Builds tester for about 2 weeks now (yup, still a noob). Anyway, does anyone else experience a screen freeze situation in Live view while using movie mode on ML?
I would also like to thank everybody who have participated in this project, especially the hard working developers! Count me in for testing! ;)
Had this error: overflow[54575/54544] shoot_malloc(53kb) at module c:357, task module
Solved it by deactivating some modules and just leaving the double_iso module ON.
I can also see a white pixel flickering in the middle while watching the movie :|
But still, in movie mode, when I turn off the camera the screen freezes where I was pointing... :| Have to take battery out and put it in again :|
When I benchmark the memory I get a "malloc error :( " message ... Is it my SD card?
shoot_malloc(16mb|TMP|DMA) failed at debug c:812, run_test
Can you post the list of modules that when enabled make the camera crash? I think it's just due to the memory on the 1100D being so low but it's worth double checking
Thanks Nanomad,
But even with NO modules loaded as I tried the benchmark after resetting ml, it still gives me this error and then screen crash while in video mode. Picture mode is fine, I can have about 5 modules on. What is malloc anyway? If the 1100d has low memory, can't we use the SD card for cache? Maybe I'm speaking nonsense, just putting it out there ;-)
Quote from: mad.eos on February 18, 2014, 09:22:36 AM
What is malloc anyway?
http://en.wikipedia.org/wiki/C_dynamic_memory_allocation
Quote
If the 1100d has low memory, can't we use the SD card for cache?
Not possible AFAIK
Thanks for sorting that out dmilligan! :)
So... What is the sollution? Not using Live View in Movie Mode? :-\ ::)
Quote from: mad.eos on February 18, 2014, 01:19:49 PM
So... What is the sollution?
Finding the problem and fixing it. You can help find it.
Reset all canon settings, custom function settings, and ML settings (and disable all modules). Does it still happen? If not, then you should be able to narrow it down to a spefic set of settings and/or modules that are causing it. Start enabling things one by one until it happens. Please be as specific as you can, some small thing that you think is too insignificant to mention could be just the clue that a dev needed to diagnose/solve the problem.
If it still crashes with everything reset, try older builds and see if you can find one where this doesn't happen and then try to narrow it down to a specific build (use binary search).
Okay!
Thanks once more, I'll try later on resetting ALL Canon and ML settings. Yesterday I just tried to reset the ML setting and the problem persisted. As I said, this only happens in Movie Mode. ::)
Found something kinda interssting. Shoot_malloc is the only one with 0 blocks allocated. Don't know if this helps or if it's normal. I've reset all settings and even uninstalled ml and installed again, still persists, am I the only one? ::)
Show us the screenshot.
Yes, shoot_malloc is used as a last resort.
Hi alex, we finally meet! ;D
Screenshot not working :-( it hangs...
You may use a second camera in this case.
Here we go!
(https://imagizer.imageshack.us/v2/870x652q90/191/3zxd.jpg)
(https://imagizer.imageshack.us/v2/836x628q90/401/j3xp.jpg)
Taken by our old sx100is
Ah, so the benchmark routine expects 2x16MB blocks, but you probably have only one.
I'd say limiting it to 8MB would have more chances to run the test.
Sooo... It's dev time? :D Will this solve the freezing problems? And also, have you ever detected a flashing white pixel in a video which was recorded with cbr mode at 1.2x ;-)
Does it freeze in movie mode with global draw OFF?
Just tried it out, and yes, it freezes with global draw off as soon as I turn the camera off, shutter closes and screen freezes :-(
I've uninstalled ML for the time being, will be trying out everyday new Nightly Builds though ;) So still in the testing mood as allways, just don't want it to freeze on me in the field if you know what I mean ???
Cheers and keep up the EXCELENTE work!! :D
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! :D
Quote from: mad.eos on February 19, 2014, 04:30:15 PM
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! :D
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 :D.
You could implement the ZeroNoise algorithm, which is really easy (simply take the pixel from the brightest shot as long as it's not clipped). I expect it would take around 30 seconds or so on the camera (based on raw_diag processing times).
Or you could just batch-process with CeroNoice: http://www.magiclantern.fm/forum/index.php?topic=9581
The main idea is to have a preview of the HDR Picture in the field without going later on, on the PC and Post-Process it. I don't mind doing PP, it's just to not have the kind of situation that you get home from a photo shoot, after PP you see one or two pictures and go "Damnn... I Should of..."
You guys know what I mean, I don't want to be lazy, just precise! ;)
Do you guys also notice a white pixel flashing in video mode using the CBR method? :-\
Quote from: mad.eos on February 18, 2014, 10:57:01 PM
I've uninstalled ML for the time being, will be trying out everyday new Nightly Builds though ;) So still in the testing mood as allways, just don't want it to freeze on me in the field if you know what I mean ???
Just press SET on startup to not load ML
Have you tried older builds to see if there is one without this problem?
Thanks for the tip dmilligan! ;) Will do!
How far should I go back? January? I'll try later on then and see if I can find which Nightly is the culprit, I'm just amazed that it only happens with me ::)
Quote from: mad.eos on February 19, 2014, 05:42:14 PM
"Damnn... I Should of..."
Taken 2 exposures 4 EV apart and called it a day.
Quote from: Audionut on February 19, 2014, 07:04:51 PM
Taken 2 exposures 4 EV apart and called it a day.
LOL! Good one Audionut... I have no argument to counter attack on that one!! :-X :P
But, wouldn't it be nice to have a preview? It was just an idea ;)
Quote from: mad.eos on February 19, 2014, 07:04:10 PM
How far should I go back? January? I'll try later on then and see if I can find which Nightly is the culprit
If you do a binary search (http://en.wikipedia.org/wiki/Binary_search) you should be able to go back 6 months and only have to check at most 8 builds.
Quote from: mad.eos on February 19, 2014, 07:15:08 PM
But, wouldn't it be nice to have a preview? It was just an idea ;)
Not really. Raw histograms/zebras provide all of the exposure feedback needed. These don't lie. JPG based rendering on the LCD only looks pretty, it adds nothing useful with respect to exposure.
The highlight exposure is super easy, ETTR with raw based exposure feedback
The shadow exposure is simply a matter of increasing exposure 4 EV.
Okay, I'll analyze carefully my silly me ideas next time ;-) anyway, I'll go back a few months and check if I can find the nightly culprit ;-) i have to ask this again, sorry, white pixel flickering using cbr movie method, anyone else?
Quote from: mad.eos on February 19, 2014, 08:42:07 PM
i have to ask this again, sorry, white pixel flickering using cbr movie method, anyone else?
Yes, I've noticed you are flooding with the same question 4 times.
Sorry alex, felt that it kinda got lost in the middle there amongst other topics. 4x is a charme, sorry for the flood.
Okay then, in an attempt of being some what productive, I can say that the Nightly build from February 1st down, doesn't freeze anymore. So, these problems may occur on more recent Nightlys! I'm staying with this one for the time being, startup even seems snappier and the whole "messing around" seems more stable! :)
Interesting facts:
.shoot_malloc now has 1 block and detects memory
.benchmark still shows shoot_malloc error (but who cares now that it won't hang anymore? still a fact though)
.screenshot works (yeeey)
.no freezes when I turn the camera off (got so happy I jumped up and "woohooed!")
.movie mode that I used was CBR @ 1.7x with a Cinema "effect" FPS @ 23.976 ;D
Video test can be viewed here: http://www.youtube.com/watch?v=BRTPvZpHd1M&feature=youtu.be
(http://imagizer.imageshack.us/v2/800x600q90/802/3isj.png)
Feast your eyes on ye' screen shot! arrg! ;D
Edit: AND ... No flickering white pixel of death in movie! FWPOD be gone!! :o
PS: Thanks for everybodys Help! ML Back online for me! :D
Cannot reproduce the bug, can you upload a zip of the ML folder on your card?
Even now that it's working? Only the benchmark doesn't work. But I can upload it. No problem ;-)
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)
47Crows, exactly what happened to me with other builds and with that nightly so... Back to the old version for me again :-( something went terribly wrong from Feb 9th and up, more or less...
With latest build(s), the camera freezes a lot, more than ever, and the only way around it is to take the battery out. Should I go for older builds?
Sure should, at least for now until the devs start debugging and find what's up with the new builds. Shouldn't be long though... Although it's Friday so they must be recharging their coding juice ;-)
Thank you. it truly freaked me out because I have a shoot tomorrow and I wouldn't be able to work with a camera freezing every couple if minutes! Good news is I downloaded an old build (4-feb) and the problem is gone. Thabks again.
Quote from: 47Crows on February 21, 2014, 11:39:32 PM
Memory Error |> alloc(12kB|TMP|DMA)
What's the complete error message?
Quote from: a1ex on February 22, 2014, 07:21:14 AM
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.
(http://i.imgur.com/4MK8t6m.png)
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.
No fake screenshots please. I know how it looks like, I want to know what it says in the help line.
Hello! How's the raw video module coming up Alex? :-)
1) why me? (I don't have a 1100D)
2) why rushing it?
3) I think we were trying to troubleshoot an important bug
1) Sorry, thought it was you who launched the good news, my bad. 2) Not rushing anything, a rushed code is a dead one.
3) You are right, sorry for the off-topic, just trying to make some convo while 47Crows gives us a screenshot.
Must be careful trying to be nice next time...
I don't have any issues on d3a8d0ab746b (about 2 days ago) and I just tried the latest (6bf65b482c71), also seems to be working fine with modules loaded. Could you be more specific about when you get the crashes?
Hi,
also no problems here with latest build.
Where can i find a module overview and description? The text on camera is too small for my eyes.
regards
starbase64
http://builds.magiclantern.fm/ -> click on Features -> then click on README.
thanks, cool
Tried again the latest build for the benefit of a doubt but... It hangs, freezes the display when I turn off the camera, shoot_malloc block value is zero, as I mentioned before, same ol' same ol', back to older build (01.02.14), for now... ;)
Quote from: dmilligan on February 22, 2014, 03:29:28 PM
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).
Yup! Same with me, exactly the same... The shoot_malloc on these later builds don't have any data allocated, don't know if this helps but it's one of the ways I can promptly detect that it's going to hang.
If you don't load any modules, do you get any crashes?
(besides that benchmark)
Yes, still hangs with zero modules loaded and if you record a video there shall be the white pixel flashing too. Screenshot function hangs as well.
Without any module loaded, do you still get memory errors? (if so, what's the exact message?)
I'm not at home atm but if 47crows or somebody who also has these problems could post the error ide be thankful. It's weird that it's only happening to the both of us, that I know of. :-)
Quote from: a1ex on February 22, 2014, 09:41:56 PM
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.
Getting close; do you have a screenshot of the free memory menu when this error appears?
#drumrolling. ;-) fingers crossed
Getting late; added some small changes that might help, let me know if it's better (post screenshots and complete error messages if not).
edit: the build bot got stuck somehow...
Here you go, took quite a lot to make it have a memory error. For some reason, while trying to take a snap of it, everything ran smooth. But I managed to break it, don't worry.
It seems almost random to me.
(http://i.imgur.com/HZU9Z4z.jpg)
EDIT: left at the original resolution, for your viewing pleasure
If shoot malloc is used=0 then it's going to crash, at least, happened with me every time.
Tried the latest build and here are my conclusions:
Good news:
shoot_malloc already has memory allocated, don't know if it's associated in any way but hey... It doesn't freeze anymore when we shut down the camera!
Bad news:
Screenshot does freeze the camera (hence the picture taken with my phone).
Memory benchmark still gives the "malloc error :("
(http://img.tapatalk.com/d/14/02/23/8uma6eva.jpg)
A thanks to alex in any case for partially solving this issue which, for me, was a great step for stability ;)
Hi,
screenshot doesn't work on latest build, here is a dump after freeze:
https://www.dropbox.com/s/epxypwtqte3hxw4/LOGS.zip
i hope this helps.
regards
starbase64
No problems with memory...
(http://www7.pic-upload.de/23.02.14/8s1r6v65y5j.png)
(http://www7.pic-upload.de/23.02.14/s74zbuulurom.png)
Screenshots and benchmarks are requesting more memory than you actually have on the camera.
So, as long as the error is handled nicely (without crash), don't worry about them. Look for crashes in normal usage (when you take photos, record videos, review them, browse menus and so on).
Screenshot is Canon code, so it's not aware of the memory backend. The only solutions are:
1) use shoot_malloc for everything (which is not exactly ideal, because when changing some stuff in Canon menu, they expect shoot_malloc to be 100% free)
2) rewrite the screenshot with ML code (described here, anyone would like to code it? http://www.magiclantern.fm/forum/index.php?topic=10540 )
Feb23rd works great for me.
Just noticed the QuickReview overlays and I have to ask, are they really RAW in the review stage?
Maybe offtopic, but I thought I should let you know, yesterday's build hung while entering stand-by and the LED turned on and remained that way. All because of one "if()" regarding memory?
If the histogram has the EV bars on it, and slides with exposure without changing its shape, it's raw.
If not, it's YUV.
Hi, i'm new here. First of all, great job!!
When I try to record at 60 fps, I put this value in Movie Menu in override in ML. It takes the value, but when I make the video, it is at 30 fps (maximum). Nothing happens. :( I've checked this with After Effects and it shows 30 fps.
Can I record at 60 fps? What values I need change?
PS: sorry for my English
1100D cannot do 60fps (FPS override is really only for making the FPS lower)
Since we're talking about video modes, what cbr setting is best for the 1100d with a class 10 SD card ;-)
dmilligan thank you for your fast answer
Quote from: mad.eos on March 01, 2014, 12:30:28 AM
Since we're talking about video modes, what cbr setting is best for the 1100d with a class 10 SD card ;-)
The highest one you can find that doesn't cause recording to stop. Use a high ISO and a lot of movement to test this.
Oki doks! Thanks! I get a flickering white pixel sometimes, that's also why I asked, will test later ;-) recording also stops if I zoom, if the cbr is too high. I'll post some results soon.
I don't get it, it stopped at 2.3x CBR but I went up and up until 3.0x lot's of movement high iso zoom in and out constantly and... All ok. What's the considered "over kill" value? ;-)
I have a Canon 1100D and have been trying to download the nightly build. The most recent build (and all of them) don't have any .fir file. I was able to find a .fir file in one of the discussion forums. Every time I try to install it on my camera it can't find "fonts.dat" and will not proceed with installation. Any help you can give?
Thanks!
See reply #1064 of this thread
Hi! Does anyone else experience the following bug with AETTR? Whenever i try to take a picture with AETTR the Shutter Speed decreases to the point when the picture is almost black and then it says " Expo limits reached". I tried different scenarios..some with low, high dynamic range, some in dark rooms or bright daylight.
What is it i'm doing wrong?
Thanks!
Quote from: cerbeld on March 02, 2014, 09:03:28 PM
Hi! Does anyone else experience the following bug with AETTR? Whenever i try to take a picture with AETTR the Shutter Speed decreases to the point when the picture is almost black and then it says " Expo limits reached". I tried different scenarios..some with low, high dynamic range, some in dark rooms or bright daylight.
What is it i'm doing wrong?
So far, autoETTR is NOT yet supported in LiveView, because we're still lacking LV RAW support. However, you can do just that by using either of the first 2 modes (always and autosnap, NOT during LiveView): take a RAW pic and then the exposure will be automatically set as far as it should be to the right, after an "offline" analysis is done on the previously-taken image.
(Am I doing it right, guys?)
Seems legit! ;-)
We are currently on the production phase of a short film, and just wanted to say that without you guys, this wouldn't have been possible. Manual exposure control brought life into our 3 1100D bodies available. So again, thank you! (Little Donation left- wish I could give more however)
Screenshots should be working now (there should be no more memory issues here); have some fun stressing this function :D
Tip: you can see them in the camera with file_man + pic_view.
Cool! Thanks a1ex for your dedication, I shall try the new nightly right away! ;-)
Thanks so much! That fixed the problem and it's working perfectly. :)
Works like a charm! ;-) I sense we are very close to a stable version for the 1100d, RAW video is next. :-D great work guys!
Well, it's just a tiny step towards a solid code base.
I chose 1100D for testing this one because it was one of the most troublesome regarding screenshot (lack of memory, low resolution, pixels not square), but all other cameras will benefit from it.
Can you post an image from LiveView focused on some fine print? (just curious to see how it handles the lower resolution)
Sure can a1ex, as soon as I get home! ;-)
Quote from: a1ex on March 04, 2014, 05:54:21 PM
(just curious to see how it handles the lower resolution)
There was a fair amount of aliasing when I tried it (at work, so I can't upload anything for you ATM), I wasn't sure if it was just the camera's LV feed or not (it's a lot easier to see the effect on my huge on my computer screen than on that tiny camera screen)
The LiveView buffer on 1100D is 720x240, and the screenshot code upsamples it to 720x480.
Sure, I could have used the HD buffer, but this one is just a feature useful mostly for debugging, research and tutorials (so I don't see the point in doing extra effort for squeezing more resolution).
Quote from: a1ex on March 04, 2014, 06:37:02 PM
(so I don't see the point in doing extra effort for squeezing more resolution).
agreed
Oh snap! It hangs in LV mode, can only take screenshots in menus etc... ::)
https://bitbucket.org/dmilligan/magic-lantern/downloads/VRAM0.PPM
https://bitbucket.org/dmilligan/magic-lantern/downloads/VRAM3.PPM
Quote from: mad.eos on March 04, 2014, 11:45:46 PM
Oh snap! It hangs in LV mode, can only take screenshots in menus etc... ::)
Perhaps you the build you are using doesn't have it yet (check the changelog or just try again tomorrow)
Hello nanomad,
I referred your youtube video and installed magiclattern for my 1100d.
It is great, however my liveview screen is now green.
Is there any option i clicked by mistake?
No magician here. Reset Canon settings and restore ML ones. Also make sure you are using the latest nightly builds
Quote from: Trion on March 05, 2014, 06:50:46 AM
...my liveview screen is now green.
Is there any option i clicked by mistake?
That usually happens when you tamper with brightness/contrast in the Display tab.
By definition, brightness and contrast should not change the hue. If this happens, it's a bug.
Ok, then, I've had this bug since around october 2012, when I got my first nightly.
Everything is when using LiveView, as suggested by the name of each feature:
- LV DIGIC peaking set to anything other than "off" or "slightly sharper" will result in a crisp, greener image.
- LV brightness results in a green tint.
- LV contrast results in a purple tint.
... but at least LV saturation and display gain work as expected.
Do you have some images to show it?
Quote from: a1ex on March 05, 2014, 05:43:43 PM
Do you have some images to show it?
(http://i.imgur.com/eNm80Su.jpg)
To what I can observe, it seems only the green channel is affected by these changes. If you mix equal parts of brightness and contrast adjustment, the image tends to balance itself out, color-wise.
EDIT: I tried taking a screenshot, but it crashed (apparently this happens in LV) and the PPM that resulted didn't have any changes in color/contrast/brightness, like the screenshot was taken pre-effect.
Yes the contrast and brightness features don't work since first build ever made (colors shift just like previous post) Though Digic Peaking works in the "slightly sharper" setting, and Saturation works in all settings.
Quote from: 47Crows on March 05, 2014, 10:09:32 AM
That usually happens when you tamper with brightness/contrast in the Display tab.
Thanks.
The pic above helped me sort it out.
Hey guys!
I've just installed Magic Lantern on my EOS 1100D. Works fine. It's very impressive, what functions this piece of software brings to the camera.
Everythink seems to work (But why are Screenshots taken as .ppm??)
(http://s14.directupload.net/images/140306/u72p2y6o.jpg)
lol? :D
(http://s7.directupload.net/images/140306/c7ki4ean.jpg)
So, uhm, could anyone give me a crash course in ML? There are some very interesting features, like ETTR and Dual ISO, but i seems that this is a little bit... complicate. Are there some tutorials or so I can use?
Thanks. Great work.
PS: Are there any other games for this? :P :o
http://www.magiclantern.fm/forum/index.php?board=15.0
Quote from: 47Crows on March 02, 2014, 10:15:48 PM
So far, autoETTR is NOT yet supported in LiveView, because we're still lacking LV RAW support. However, you can do just that by using either of the first 2 modes (always and autosnap, NOT during LiveView): take a RAW pic and then the exposure will be automatically set as far as it should be to the right, after an "offline" analysis is done on the previously-taken image.
(Am I doing it right, guys?)
thanks a lot! it´s working now :)
Quote from: Audionut on March 07, 2014, 03:32:50 PM
http://www.magiclantern.fm/forum/index.php?board=15.0
Thanks.
Any news on RAW video module?
If there's news you'll read about it here, but the absolute best you can hope for even if we do get it working is a couple of seconds of low resolution. The very small buffer and very low write speed makes recording raw quite impractical on this camera. The real practical uses of the raw buffer would be silent pictures and ETTR/Raw overlays in LV
OK...it sounded like nanomad got it recording continously in raw.
Quote1100D will be recording raw video. 640p @ 30 fps, but it's raw video nonetheless, right?
That was what he wrote like 1month ago...so I was just wonderin about the release.
So you don't think the 1100D will record raw video continously?
And what exactly is silent pictures, does this mean raw video without audio?
Thanks...
Quote from: EVZML on March 14, 2014, 06:21:57 AM
So you don't think the 1100D will record raw video continously?
And what exactly is silent pictures, does this mean raw video without audio?
http://magiclantern.wikia.com/wiki/Unified/UserGuide#silent-pictures
As for actual RAW video, I don't think it generally records sound. Someone correct me if I'm wrong, but as far as I know, it's a series of DNG files, written very quickly on the camera, right up to the moment when the buffer gets full. Recording sound as well will fill up the buffer prematurely, so it's probably disabled.
Silent pictures are single frame captures. Think photos but captured with the LV buffer, so no shutter actuation is needed.
Nothing to do with video.
I think it eventually will. It's just a matter of time for someone to catch up with the CONFIG_EDMAC_RAW_SLURP bits for LV mode.
There are two issues right now.
1. It's not easy for a developer to grab the raw frame size as the 1100D likes to crash as soon as you enter LV with "old method" for RAW on. Easily solved by turning FPS override on
2. We can't use the DEFAULT_RAW_BUFFER allocated by canon as it seems to be used for something else. Right now ML code expects the opposite so one should write a routine to allocate a buffer to write to (and free it when not needed anymore)
Found a bug while testing Trap Focus: when the focus indicators light up, the camera takes 3 pictures. I've tried both modes, with the C-Fn AF button configuration at default and otherwise.
HDR bracketing is off (even tried to set the number of frames to 2, just in case), the drive mode is single.
I'm using the 18Feb2014 build, but I haven't used this feature in a long time, so I don't know when the bug appeared.
edit: once in a while, it just takes 2 pictures. :-X
Forgot I had set Pics at once to exactly 3 (Shoot tab, Shoot preferences).
In the first nightly build I remember we had the option to set Exp. Override to ON in movie mode while leaving it OFF for photo mode. It really is a pain having to turn it manually everytime I use Live view for taking pictures. Could that be implemented again? Thank you.
Huge request that I'm hoping you'd implement, although I'm not sure how many people would use it. I'm thinking the screenshot function would be fine for this, but if it could be worked into video, that would be cool, too. I see I can take a screenshot of LV and it even works at 10x!! You have no idea how awesome this is to me and I thank you for it! I'm trying to get good pictures of Saturn, but to do that, you really need to take many photos and stack them. Is there any way that we could have the screenshot feature with an added option to take as many pics as we want? The 10 second timer is a must for the 1st picture, but after that, they can be back to back. Up to 1000 would be ideal. I can easily see me doing 100's at a time like this. The attached image is what I got from stacking just 4 images in this manner. It's hard to push all the buttons and also have time for the camera/scope to stop shaking in 10 seconds, but with up to 1000 pics, by the time the 1st few were complete, all shaking from the telescope would be dampened out and the majority would be useable. https://www.facebook.com/photo.php?fbid=10152312439213701&set=a.143037638700.112356.566973700&type=1&theater (https://www.facebook.com/photo.php?fbid=10152312439213701&set=a.143037638700.112356.566973700&type=1&theater)
Thanks for your time and effort, it's really appreciated!
Bill
(Windoze321)
You can use the built in Magic Lantern intervalometer but you will have some mirror shake.
The proper alternative would be using raw silent pictures but they are currently not supported on the 1100D. I can hack a module to do 422 as we used to if there's interest
I bet hacking a 422 module will take longer than doing a malloc/free for the raw backend, and also the old 422 code has major problems with vsync (raw silent pics have it solved, unless you are really unlucky to get pink frames).
True that. I'll see if I can code something useful. The buffer should be as big as the largest raw resolution, right?
Quote from: nanomad on March 21, 2014, 08:36:55 AM
You can use the built in Magic Lantern intervalometer but you will have some mirror shake.
If this was directed at me, I use the intervalometer all the time, but it doesn't allow me to take pics at 10x in liveview like the screenshot does.
Bill
Yes it was directed at you. The thing is, I don't see what advantage taking pictures at 10x would give you. If anything, the CR2 and jpeg offers more resolution and bit depth. You can still frame and focus at 10x then batch crop everything in post production. A quick shell script or a photoshop action will suffice.
The pictures I get doing it this way (with 10x ) are actually viewable. When I take a regular picture, yes, it's higher resolution, but it's so small (even when cropped and shown at 100%) you can't tell what it is.
I see, that's because the live view is showing a cropped and upscaled image.
Could you post a 10x bmp along with a jpeg shot of the same scene?
I'll try to do that in a bit. The link I posted above is the LV shot. I also forgot that I'm using a Barlow right now, and that makes it much bigger. Maybe the regular pics will end up being good enough. I'm in the process of taking a few dozen pics with 12s in-between, so it will take a few, but I'll post it asap.
Not sure how to upload actual photos, but here's the one taken normally without liveview. This is a stack of 20 pics. If you click it to scroll to the next image, you'll see the Liveview image at 10x. When I upscale the regular one to match the same approximate size, the regular one starts to pixelate. https://www.facebook.com/photo.php?fbid=10152312620288701&set=a.143037638700.112356.566973700&type=1&theater (https://www.facebook.com/photo.php?fbid=10152312620288701&set=a.143037638700.112356.566973700&type=1&theater)
So that's 20 pics stacked Vs. 4 stacked. Looking at a single frame of each of the pics (untouched and unstacked @ 100%) on my PC, the 10X is about 2.5x the size of the of the regular pic. (Of course we're only talking about Saturn itself, not the actual picture size.) So it is something I'd like to dabble with. I saw modules somewhere where someone has it taking a screenshot after every push of the button, so maybe an add-on or something like that instead of playing with the source? It's not a must, but it could be something nice if enough are stacked. Hard to tell at this point.
Bill
Hi,
I know many people have asked this before but the answers they recieved have not been as completely in depth as I would like. So here it goes.
Can someone please tell me if 1080p will ever be possible on the 1100d? I have heard some things about it being locked up so the reason I'm making this post is so I can please get a nice big paragraph on all the information about this topic :P someone please help.
I have this camera. Is the release for ML a nightly build then? Is it safe to use for the auto reset for video recording?
Quote from: killem2 on April 02, 2014, 03:10:05 AM
Is the release for ML a nightly build then?
Yes.
Quote from: killem2 on April 02, 2014, 03:10:05 AM
Is it safe to use for the auto reset for video recording?
Yes.
Awesome, can't wait to use it!!! 8)
can someone please tell me if it really is safe for my Canon EOS1100D?
Yes it is
if anyone has tested it, please post a video or something
Of what?
Quote from: akashdua on April 10, 2014, 05:35:16 AM
if anyone has tested it, please post a video or something
You can either trust us or not. You don't see some angry guy spamming the forum with multiple accounts after having his camera bricked, so I'd say it's safe to run it.
Speaking of which,
try force yourself into going through the entire thread before running ML, to get an idea of what happened with our build. Also, reading the rules and FAQ (http://www.magiclantern.fm/faq.html) should help clear some stuff up.
Quote from: akashdua on April 09, 2014, 12:28:53 PM
can someone please tell me if it really is safe for my Canon EOS1100D?
Quite frankly dude you're not loosing much if your 1100d breaks. But it wont! Read the Magic Lantern Website before making posts about this! Magic Lantern only exists on your sd card and it bootstraps to run in the background on the normal firmware. As long as you don't do anything stupid in the developer options you will be fine!
Hi,
ml works on Toshiba Wifi Card "FlashAir"?
http://www.amazon.de/32GB-Toshiba-FlashAir-Wi-Fi-CL10-Speicherkarte/dp/B00GX5EX18/ref=sr_1_6?s=computers&ie=UTF8&qid=1397721348&sr=1-6&keywords=Toshiba+flashair
regards
starbase64
No idea, I don't have one to test
Hi,
I am looking for SPOT Metering in 1100D for Night Sky-Star photography.I know ML has Spot metering.
Is there a way to fix to x% and continue shooting?
Suggest me please. ::)
when is someone going to work on a released version of ml for the rebel t3?
What does that mean? The nightly builds are released publicly.
Quote from: wert on April 20, 2014, 09:38:10 PM
when is someone going to work on a released version of ml for the rebel t3?
I think he means a Unified/"Official" version, like with the 5D and all those that are fully supported. I'm no developer, but I doubt that will happen anytime soon, mainly because of the limitations this camera has and the bugs that are caused by said limitations/differences.
Offtopic, but it's been driving me insane: whenever I shoot in LiveView, I hear a
short, mechanical, friction-ridden sound at the beginning of the exposure, from within the camera (which is not the mirror going up, obviously). Up until now I thought it was the shutter, resetting the sensor or something, but I took the lens out and repeated the experiment. The shutter does not come down, but the sound is present. It is not produced by the speaker. Can anybody please tell me what it is? It's keeping me up at night since I can't explain its existence. Thanks.
EDIT: apparently, the shutter "resets" the sensor, which means the shutter travels right at the beginning of the exposure.
Quote from: starbase64 on April 17, 2014, 09:59:23 AM
Hi,
ml works on Toshiba Wifi Card "FlashAir"?
http://www.amazon.de/32GB-Toshiba-FlashAir-Wi-Fi-CL10-Speicherkarte/dp/B00GX5EX18/ref=sr_1_6?s=computers&ie=UTF8&qid=1397721348&sr=1-6&keywords=Toshiba+flashair
regards
starbase64
Hi. I think it should work since it is not 64gb. But don't quote me on that. If you had a 64gb version or for that matter I would suggest using the eos card tool for magic lantern. http://chdk.wikia.com/wiki/EOScard . It is chdk but i think the setting allow you to flash ml too.
Completely off-topic, but I figure someone might want to look up this info, let it be found on a 1100D forum:
I opened up my focusing screen ensemble. Just a heads-up for anyone who ventures there,
IT (the focusing screen)
WAS NEVER MEANT TO BE REPLACED, so make sure you understand the risks.
(http://i.imgur.com/1gXypSY.png)
- Put the camera on its back. (preferably, tilted at a 45° angle toward the top side)
- Open the outer frame (3) by pushing inside on its tab. Try to avoid touching the mirror at all times.
- Pick up the screen (2) by any of the north "ears" (those facing you). Try to avoid touching the central part of the screen. Don't worry, there is only one way of putting in the screen (check the south ear that should fit in the bottom slot to the right). If all goes wrong, try to install the screen as the number 20 (seen on the east ear) is facing you.
- If done correctly, you shouldn't even deal with the other frame (1). If you do, however, dislodge it, don't worry, like the screen, it can only be put in one way (check the cutaways in the frame and compare them to their counterparts on the camera). At the time of writing I am wondering why this frame even exists since it's completely flat and very thin.
I hope someone finds it helpful.
Im using ML on a 1100D, i find that bulb ramping feature is missing. Is it a problem with my installation, or is this feature not available for 1100D?
Quote from: vadithiyan on April 29, 2014, 05:17:18 AM
Im using ML on a 1100D, i find that bulb ramping feature is missing. Is it a problem with my installation, or is this feature not available for 1100D?
You clearly didn't do a search of the forum. The feature was removed and the first dozen or so search results for "bulb ramping" lead to posts that indicate this.
You have two alternatives:
AutoETTR (http://www.magiclantern.fm/forum/index.php?topic=5705.0) for automatic ramping and deflicker with this (http://www.magiclantern.fm/forum/index.php?topic=8850.0) or this (http://www.magiclantern.fm/forum/index.php?topic=10496.0)
adv_int.mo (http://www.magiclantern.fm/forum/index.php?topic=8431) for manual ramping
or a combination of the two
Hi. I have two questions. Is possible to find change log for night builds just for 1100D and is there some list with all change not just for one day? Because I don't want check change log every day. I try find, but I didn't. Thank you :-)
Quote from: LeXXiii on May 06, 2014, 02:19:00 PM
Hi. I have two questions. Is possible to find change log for night builds just for 1100D and is there some list with all change not just for one day? Because I don't want check change log every day. I try find, but I didn't. Thank you :-)
I believe this (http://builds.magiclantern.fm/#/features) is the closest thing to your request.
Also, https://groups.google.com/forum/#!msg/ml-devel/hgaMKPUYctI/LZnOzMVgVcoJ ; https://bitbucket.org/hudson/magic-lantern/src/tip/platform/1100D.105/ to check what's happening with development.
Quote from: LeXXiii on May 06, 2014, 02:19:00 PM
Hi. I have two questions. Is possible to find change log for night builds just for 1100D and is there some list with all change not just for one day? Because I don't want check change log every day. I try find, but I didn't. Thank you :-)
Almost all changes are to common source files or modules. These changes will also affect the 1100D. The only reason they wouldn't is if they were changes to features that are disabled in the 1100D build, or if they are changes in modules you don't use. For modules, the commit comment typically begins with the module name. For disabled features, there is no automatic way of figuring this out. You'd have to inspect the source code and the actual changes.
View the full commit history on bitbucket: https://bitbucket.org/hudson/magic-lantern/commits
Thank you! I think, I found answer for my questions. :)
i have a eos 1100d and some questions about which magic lantern version to use.
the 2.3 stable version has no .fir for the 1100d.
can i copy it from the latest nightly build or rc3 version, because i want to use a stable version?
thank you!
You can but it won't work.
You can't just pick the binaries you like to get a running system will all the pros but no cons. It will not fit.
will there be a stable version for the 1100d?
if yes, when?
Quote from: ml138 on May 09, 2014, 12:38:10 PM
will there be a stable version for the 1100d?
if yes, when?
http://wiki.magiclantern.fm/faq#when_will_you_release_the_next_version
ML gives 1100D Manual video exposure?
is there any problems / bugs with the Nightly Build of 1100d?
if there is can i be of service? i own one if you need testing done so we could make it go faster!
as long as it won't ruin my camera i wouldn't mind testing it out!
by the way is there any harm in putting on the latest version of ml on my camera?
I own both an 1100D and a 650D and have latest working nightly builds of ML for both. I use them frequently, even did a short time lapse using the 1100D while out shooting a sunset on Oregon Coast. Appreciate all the work that people put into developing Magic Lantern! I know many Canon users that are suddenly taking an interest in the features the little 1100D does that their pro bodies do not.
Hi,
Quote from: fufuheo on February 06, 2014, 08:59:42 PM
No, it says Motion level=0 even when moving the camera a lot. I am not able to get it to react at all
Is it solved since February?
Thx :)
Hello everybody,
I would first like to thank you for the development of Magic Lantern which is really great. I would have a question for you, I would be interested in using PicoC to run scripts on a Canon 1100D, and if I understand correctly, PicoC is no longer available in the Nighly builds. Would you have a link to a previous version which supports PicoC ? That would be very helpful to me. When I click "Show Older Builds", the earliest build available is "Date: 2014-02-13 19:40:35 +0000", and I don't think that PicoC is available since this date.
Thanks in advance for your help,
Cedric
Hi again,
47Crows has sent me an older version of ML which supports PicoC, which perfectly matches my requirements. Thank you again for your help, and long life to Open Source and Magic Lantern !
Cedric
Somebody got RAW Video function running on the 1100D yet?...
No, it crashes with err70 as soon as you enter LV.
Here's the experimental branch, if anybody feels like coding: https://bitbucket.org/hudson/magic-lantern/branch/allocate-raw-lv-buffer
If you can compile ML, you can try writing down the resolutions, run some tests, take a silent picture, check whether it can record and so on.
It seems to touch some other core areas though (because 1100D doesn't have fixed LV buffer addresses, like most other cameras), so I think it's a good idea to finish this one first: https://bitbucket.org/hudson/magic-lantern/branch/new-lv-buffer-detection
Just noticed the 1100D build was broken for about one week, and nobody reported the error.
Is there anybody still using this camera, or should I discontinue this port?
Quote from: a1ex on June 22, 2014, 06:09:14 PM
Is there anybody still using this camera [...]?
Yes, just doing bimonthly updates since there's no activity on the forum, thus having no new features with which to experiment.
Quote from: a1ex on June 22, 2014, 06:09:14 PM
the 1100D build was broken for about one week
I try to submit patches as soon as I see stuff get broken, but I also don't always have to time to do this on a
weekly basis.
Quote from: 47Crows on June 22, 2014, 08:59:28 PM
Yes, just doing bimonthly updates since there's no activity on the forum, thus having no new features with which to experiment.
Same here. I got used not to panic when builds get broken for some time. The bug reports will eventually come imho.
I have time to test the nightly builds , I think it would be very usefull to have the RAW video function for timelapse video.How can I help?
I tried to dump the image buffers , in P/Tv/Av/M/A-DEP the camera just locks-up but it dumps the data , but if I zoom in the live view it does not lock up.In movie mode when not recording and not zoomed in its the same like in the other modes , it just locks up , but vwhen zoomed in or recording it does not lock up.
The resolution in the photo modes is 1056x704 , in movie mode it is 1280x720.
I also tried diffrent photo sizes (S2,S3,L) and also RAW.
Here is the folder https://mega.co.nz/#!f0xCAQZS!WlPkGrYK8jB_0i1P_Z5cchkwmFU0n3983W8pn5BSt5U
Crash hopefully fixed, can you confirm? No need to redo the dumps.
Can you show a screenshot of the Free Memory dialog, in one of those video modes where it was failing?
If I dump first in P mode there is a error but i can dump again it doesnt freeze.If I dump in Movie mode first there is no error even if I change to P mode and dump.
https://www.dropbox.com/s/xg5s26pln4b62td/dumping.zip
It was freezing in all photo modes and in movie mode if I didnt start recording before trying to dump.
It wasnt freezing when zoomed in.
PS. Sorry for my bad English I'am not a native speaker
IT WORKS!!!!
I have compiled https://bitbucket.org/hudson/magic-lantern/branch/allocate-raw-lv-buffer and it works , I have got 14 frames.It showed some error but not a Canon error a ML error.
Here are the first frames https://mega.co.nz/#!v4I11Z7S!cl6thSrdhHt6PArrpZnWUMQ-7EfHw4H2JVXl7YUhkq4
Here are two other samples https://mega.co.nz/#!HkJQSZYJ!AXm7vnvd5GLRq9vxIeorrgDXKSYesE_wQ9j9jlbpKcQ
Where is the debug info from the raw recording , I cant find it.
I tried the raw_rec , should i try the mlv?
mlv works also , I run the buffer test but I didn't let it complete because my cards is clearly to slow , only 7.8MB/s , it is a SanDisk 8GB class6 20 R 7 W
Here is the video https://mega.co.nz/#!nwpnXDCR!FTkU5F7WrMdFbSja6PVyN4PgTjN1EWF2ZmzyXX48SaY
And here is the build I compiled https://mega.co.nz/#!KowGFCIK!r4MaIcZRpiiHQGdaqM-0jgfAyrjZYV-6wgNjqUWFrcM see post #1257
PS. I am not responsible for anything that happens to your camera , just to be secure.
WOW! :) I will try it, my card is a Lexar Premium 32GB 200x CLASS 10.
Sounds like it's working soon...
PS: Have you noticed that aqua/cyan point on your .dng's ? Starting on this file:
M26-220600004.dng
that are some stuck pixels , that is normal , there are guides how to remove them. I dont know if the build will work in your camera , I just copied my folder and files. I had the 25th nightly installed on my cam and I didnt unistall it , just deleted it from the card and then I compiled it to my card directly.
Try to do a benchmark of your card.
OK. I will test it now. Where shoud I find the raw video files (if it works) ?
-> tried it now. it says:
Hack error at 0:
expected e3a00032, got e1a00000
Tested RAW VIDEO and RAW VIDEO (MLV), both same errors. But it looks like it does record, because when I press play button, it plays back the raw file!
there is a 30MB file in DCIM , then you need a program to convert it to cinema dng so you can open it in Adobe CC
http://www.phreekz.de/wordpress/2014/04/magiclantern-raw2cdng-1-5-0/
Looks like RAW VIDEO (MLV) doesn't work for me. But RAW VIDEO worked, got a 54MB .RAW file! I will try to open it with the program...
Nice results , I will try FPS overide tommorow , it's 2 AM here :p
Played around - first tests.
(RAW video, no MLV)
-768x400 continous
-864x450 recorded 83 frames (second run did 245 frames ???)
-960x500 recorded 75 frames
...
Card I used was Lexar (Premium Series) 32GB 200x (Class 10).
Maybe you can get better resolution with faster card...
Notice: When I turn on camera and record directly, sometimes 768x400 mode crashes after some frames. I think the problem is that the SD card is not warm enough....
So overall I can say it's nice play around, but nothing I can work with right now...maybe with some faster SD cards ;)
But still...NICE JOB! Thanks to the developers :)
-> UPDATE: RAW VIDEO (MLV) works on the 1100D ! You just got to take "Test mode" OFF, it even plays back the mlv files! Can record 960x500 continuous with fps override changed to 20fps...
again: maybe my card is too slow, I think you should get 960x540 24fps continous recording, because the 1100D has the same write speed as the 60D/600D/550D/500D...right?
https://docs.google.com/spreadsheet/ccc?key=0AgQ2MOkAZTFHdFFIcFp1d0R5TzVPTVJXOEVyUndteGc#gid=5
Nice!
Things to fix:
- find skip_left and skip_top in raw.c (take a silent picture - not video - and count the pixels in the black borders) - this will also fix the weird colors
- hack error: lookup the context in the source code, then follow this tutorial to find it: www.magiclantern.fm/forum/index.php?topic=12177
- check the Free Memory dialog for errors (some crashes might be buffer overflows)
- other error messages: document them properly, so I can give further advice
Skip left 68px , skip top 16px https://mega.co.nz/#!u8YGAYSC!w4MJMhVp6SgvMK8FuZLq3IeFTA5liYhXHFegQQsSCLU
There are no memory errors , shoot malloc 4.1MB used always.
There are at least 3 LiveView modes: 720p movie, 5x zoom, and photo mode (and skip values may be different in all these modes). Does the 1100D have other modes?
I tried to add the missing timer that was causing the error but I got this
Building module mlv_rec...
REBUILDING
[ README ] module_strings.h
[ CC ] mlv_rec.o
mlv_rec.c: In function 'hack_liveview':
mlv_rec.c:1556:13: error: 'cam_1100d' undeclared (first use in this function)
mlv_rec.c:1556:13: note: each undeclared identifier is reported only once for each function it appears in
make[4]: *** [mlv_rec.o] Error 1
Here is the strings file https://mega.co.nz/#!m94mia4C!MmCjuJoN4bY_xtG90oNt6-NsojXBf3GwhSKaed6AqRI
I compiled it but I get the hack error again when I start raw recording , I set StartDialogRefreshTimer
cam_1100d ? 0xff373654 :
EDIT:
0xff47e9bc also didn't work
i am still unsure if its safe to install the current build on my camera are there no bugs? or problems that can't be fixed and will ruin my camera?
Quote from: 1k738 on June 27, 2014, 06:23:22 PM
i am still unsure if its safe
There are no reports of anyone being injured by ML :P
There are plenty of bugs, but they are very unlikely to permanently damage your camera. There is still a chance, and there will always be a chance, nothing is going to change about that.
I'd say the likelihood of damaging your camera has much more to do with your technical knowledge, critical thinking, and ability to read and follow instructions, than anything to do with how stable ML is, or how many bugs there are.
dmilligan can you upload the ROM1.bin from your 60D so I can fix the hack error
At 5x the skips are the same skip left 72px , skip top 16px , but there are also about 200px at the bottom
https://mega.co.nz/#!74Y0hLjS!a0dH5Qi3EDSzzFLP9q9ku2ejLsmEDri87hHQg9m0tC8
Here is a clean build https://mega.co.nz/#!294TkDZK!cPxupx6zZ_1gc_t-iXemeAVj0e4UWAXap1ffRgRXizM
EDIT:mlv_snd seems to freeze the camera
Can you also check photo mode 1x?
Also, can you create a pull request with your changes?
I couldn't find the memory address but I added the strings file you can find it.
At 1x in both video and photo mode skip left is 68px and skip top 16px
https://mega.co.nz/#!HxoSTIpZ!5z3tSAoivI07-pixu-XCmcequpa5GLg_4BlcTvXMALs
The error is related to the extra hacks.
0xff373384
Quote from: dmilligan on June 27, 2014, 11:05:29 PM
0xff373384
Nope , this address also doesn't work .I think the hack error is more complicated.For now you can disable extra hacks.
Well it's the right instruction and in exactly the same place in an identical function in the 60D disassembly, so my guess is the 60D probably doesn't work either.
I'm on vacation and I forgot the charger for my notebook.I have tested the RAW video a lot , recorded about 10GB of footage , all with FPS overide , the longest about 13 minutes at 2.5fps.There is the hack error but everything works.
Tried Auto ETTR today , works great. I had a nice twilight scene , it started at ISO 100. 30 min after it was at ISO 2000 , shutter speed 1/15 at f3.5.Exposure is pretty constant.
you guys are awesome! breeding life into a dead camera
-Just downloaded latest build and for some reason Focus peaking and Magic zoom both are greatly improved! Thanks!
Feature request: would it be possible to assign buttons to change the exposure settings without opening the menu? Like 550/600/60Ds.
Up and down for ISO, dial for shutter, AV button + dial for aperture, that would be killer!
I got the RAW video working at 960*
[email protected] continuously with a Sandisk Extreme 45 MB/s. Thanks a lot!
Quote from: fufuheo on July 01, 2014, 11:59:24 PM
I got the RAW video working at 960*[email protected] continuously with a Sandisk Extreme 45 MB/s. Thanks a lot!
How do you make it work? I downloaded the latest build and there's no Raw module... Would love to try it and help developing this
you need to compile (http://www.magiclantern.fm/forum/index.php?topic=991.0) this branch yourself: https://bitbucket.org/hudson/magic-lantern/branch/allocate-raw-lv-buffer
This is heavily compressed for the web and the difference is even much bigger and artefact-free but here:
H.264 720p
(http://i.imgur.com/hb9EyMW.jpg)
Raw 540p
(http://i.imgur.com/ff3Orix.jpg)
The image is taking a HUGE leap on the 1100D, much much more detail, extremely fine noise structure, and of course very thick colour palette (14 bit) for grading to the point of being able to change WB in post!
Works very well with Fast cards at that resolution,
---Edit:
Another low-light test:
H.264 at 6400 ISO
(http://i.imgur.com/5CYZxCL.jpg)
Raw at 6400 ISO (@540p)
(http://i.imgur.com/zM1Esud.jpg)
As you can see, much higher detail, finer grain structure, and more accurate color palette
From my test, the 1100D's low pixel count at 12, with large APS-C sensor, gives it an edge over the 600/700D in terms of low-light.
Did somebody try full res silent pics?
Apperture size doesn't change in video mode during Exposure override when the value is changed, it's adjusting itself when it's changed from the lowest F number. Am I doing anything wrong or it's a bug ?
Quote from: RevinFilms on July 10, 2014, 06:56:57 PM
Apperture size doesn't change in video mode during Exposure override when the value is changed, it's adjusting itself when it's changed from the lowest F number. Am I doing anything wrong or it's a bug ?
It's a bug available only while using zoom lenses
[citation needed]. It will work fine on a fixed-focal length lens.
EDIT: as corrected below, the problem is with the 18-55mm f/3.5-5.6 III and with the 18-55mm f/3.5-5.6 IS II so far.
Quote from: 47Crows on July 10, 2014, 11:13:04 PM
It's a bug available only while using zoom lenses[citation needed]. It will work fine on a fixed-focal length lens.
Will for me aperture control works perfectly with:
-Canon 50mm F/1.8 II
-Canon 85mm F/1.8
-Sigma 70-300mm F4-5.6 APO zoom
-Sigma 10-20mm F4.5-5.6 zoom
Doesn't work with:
-Canon 18-55mm f/3.5-5.6 III non-IS
I'll get the newer regular IS II (non stm) version tomorrow so we'll see how it does with that one.
Will this bug get a fix ? That would be so awesome as I don't have other lenses :(.
Quote from: Ebrahim Saadawi on July 11, 2014, 04:14:40 AM
I'll get the newer regular IS II (non stm) version tomorrow so we'll see how it does with that one.
I have the IS II version and it doesn't work. It's the lens specs themselves.
dmilligan (at least) once explained what's the deal with it and why it won't work with this focal length range and aperture range setup. It simply had something to do with ML's values not syncing with the minimum F-numbers at each end of the focal length range.
Had to dig my 18-55 out of the dumpster to confirm this one. Doesn't work in video or photo LV. This isn't exactly a priority for me, I don't record video and never use the kit lens.
Quote from: timelapseHD on July 08, 2014, 09:44:22 PM
Did somebody try full res silent pics?
Currently using #1257's Experimental_build_1100D.zip (https://mega.co.nz/#!294TkDZK!cPxupx6zZ_1gc_t-iXemeAVj0e4UWAXap1ffRgRXizM) , which was posted
June 27th.
- Silent pics of ANY resolution result in a blank (0 bytes) DNG for each session (i.e.: the time between power up and power down of the camera); a message is printed briefly each time I "take" a silent pic, with the location at which the DNG was supposed to be
- RAW video works like a charm, except for when you zoom in (Canon's zoom, not magic zoom): the LV picture freezes, but the recording continues normally (action following the freeze is recorded seamlessly)
- this one is a bit tricky: in LV, while having silent pics enabled (with half shutter press as trigger), if I snap a picture (full shutter press), the image gets written to the file, but the camera beeps; a second time this is attempted, the shutter can be heard doing its job, the mirror comes down, but it never comes up. The camera then prints out a Canon message "BUSY" on the screen, the LED stays lit. When trying to power down the camera, the Canon image saving screen appears (blue circle thingy stating how many images it has to save) and it stays there indefinitely. When opening the card/battery door, the camera prints out a Canon message among the lines of "Close the door. Do not remove the battery." No image is saved this time.
Hope I've been of some help.
tl;dr: there are plenty of bugs, but the camera is very much alive, with no sign of being bricked; AETTR works like a charm and I quite dig the RAW histogram and zebras(which are more like false colours)
I will compile a new build tommorow.
Quote from: RevinFilms on July 11, 2014, 11:43:09 AM
Will this bug get a fix ? That would be so awesome as I don't have other lenses :(.
Confirmed. Doesn't work with either the 18-55mm f/3.5-5.6 III or 18-55mm f/3.5-5.6 IS II.
I actually love the kit lens as an 18mm f/3.5 wide angle prime. It's the only wide angle option at that budget.
You can still use it. It's actually not that much of a problem as I use it wide-open all the time anyway and adjust exposure with ISO and Shutter angle and Variable ND.
Quote from: Ebrahim Saadawi on July 13, 2014, 12:51:06 AM
It's the only wide angle option at that budget.
Not any more: http://www.bhphotovideo.com/c/product/1051476-USA/canon_9519b002_ef_s_10_18mm_f_4_5_5_6_is.html
Hi guys,
I am new to ML, and would like to try it on my 1100D, but I am not sure about HOW to install, since the directions are given to V 2.3, and the 1100D uses V 1.05. I am really sorry if there is another place I should be asking this, but I could not find any up-to-date discussion about this.
I believe I only need to format my card, extract ML there and turn on my camera, is it so?
Thanks,
Caio
Quote from: caiokv on July 15, 2014, 06:17:36 PM
Hi guys,
I am new to ML, and would like to try it on my 1100D, but I am not sure about HOW to install, since the directions are given to V 2.3, and the 1100D uses V 1.05. I am really sorry if there is another place I should be asking this, but I could not find any up-to-date discussion about this.
I believe I only need to format my card, extract ML there and turn on my camera, is it so?
Thanks,
Caio
V 2.3 is refers to the Magic Lantern version, not the camera firmware version (1.0.5).
To download Magic Lantern for the 1100D, go to http://magiclantern.fm/downloads.html (http://magiclantern.fm/downloads.html), scroll down to Nightly Builds (No stable version is availible for the 1100D yet) read the text and click the "Browse Nightly Builds" button, select 1100D.105 (1100D with firmware version 1.0.5) and download.
Once it is done click this link: http://wiki.magiclantern.fm/install (http://wiki.magiclantern.fm/install) scroll down to "First install guide" and follow step 1 and 2.
Hope it helps!
Any news about 1080p video recording ?
It will never happen
Hello,
I am currently trying to install Magic Lantern onto my Cannon Rebel T3i. I have formated the memory card and put the downloaded files onto them. When I went to update the firmware it says loading. It has been loading for at least 10 minutes now. Do you guys know what the problem might be?
Thanks,
Yara
Do you see this?
(http://a1ex.magiclantern.fm/bleeding-edge/new-installer.png)
Looks like 1100D has the updated firmware installer. dmilligan, interested in starting a fresh topic?
Quote from: Yara on July 21, 2014, 11:23:03 PM
Hello,
I am currently trying to install Magic Lantern onto my Cannon Rebel T3i. I have formated the memory card and put the downloaded files onto them. When I went to update the firmware it says loading. It has been loading for at least 10 minutes now. Do you guys know what the problem might be?
Thanks,
Yara
Did you install the t3i version? Take notice all the talk and files throughout this thread is about the T3, not the T3i.
In the latest builds, I am not able to format the memory cards in-camera anymore. When done, the magic lantern restoration process freezes at "writing bootflags", and you have to remove the battery, lose magic lantern until installing the fir. File and upgrading the firmware again.
Quote from: Audionut on July 22, 2014, 12:15:14 AM
Looks like 1100D has the updated firmware installer. dmilligan, interested in starting a fresh topic?
sure, I'll start getting some things together and writing something up (btw, right now it doesn't appear I have permission to start a new thread in this section)
Cool. Just start it somewhere else and I'll move it.
Quote from: Ebrahim Saadawi on July 22, 2014, 02:31:19 PM
In the latest builds, I am not able to format the memory cards in-camera anymore. When done, the magic lantern restoration process freezes at "writing bootflags", and you have to remove the battery, lose magic lantern until installing the fir. File and upgrading the firmware again.
Did this ever work? When exactly? (which builds?)
Quote from: a1ex on July 22, 2014, 05:38:20 PM
Did this ever work? When exactly? (which builds?)
Formatting in-camera always worked no problem with ML. Now constantly freezes at "writing bootflags". Not sure exactly when the issue began but I found it in the latest couple of nightly builds.
If you answer my question, I might be able to fix it. If not... not.
I apologize if this isn't the place and I have literally no knowledge on how magic lantern is created- so I unfortunately cannot contribute to the code. However, I was wondering if it is possible to add 1080p recording capabilities to the 1100d with maybe a lower bitrate? I know this seems very far fetched and it probably has something to do with the capabilities of the sensor itself- but I know the 50d cannot originally record any video at all, however, magic lantern allows you to record 1080p video (although it is very buggy and has no audio). Thanks for reading this.
note: I'm not begging for someone to add the feature. I'm just wondering if its possible at all.
Read this thread or just search, I'm sure it has been asked more than once.
Need help guys.. can you point me in right direction :)
I need to uninstall magic lantern from my camera.. I just sold it and need to remove it before I can give it to this guy
and I have no idea how to do that or where to read how to remove that specific build
Can anyone give me a link or something how to remove that one so I dont mess up my camera
2.3.next.2013jun13.1100D105
built on 2013-06-13 by nanomad
Format card using a cardreader, insert card into cam, format it again. Download latest nightly build. Copy extracted contents to card's root (cardreader again). Insert card into cam, run firmware update and wait until timeout occurs.
Camera's bootflag will be removed.
do I need to run some other CANON firmware or something or thats it ?
Quote from: TokraCro on August 03, 2014, 10:51:52 PM
Need help guys.. can you point me in right direction :)
I need to uninstall magic lantern from my camera [...]
Here (http://www.magiclantern.fm/install.html) you go.
Quote"[...] Uninstalling Magic Lantern
Don't just delete the Magic Lantern files from the card! If you do, the camera will freeze at startup and you'll have to take the battery out.
Uninstalling ML from one card
Format that card from the camera (select this option: Format card, remove Magic Lantern) and reboot. Your camera will load the original firmware when you use that card.
Uninstalling ML from the camera
With a Magic Lantern card, launch the Firmware Update process and follow the instructions on-screen.
Re-installing Canon firmware will not remove Magic Lantern."
Thank you everyone
Hey Nanomad did you ever get a chance to revisit adding Gain Control? I added an external mic jack and am trying to use a Rode Videomic, but even with the -20 db disabled I can barely hear any sound. Thanks
The 1100D does not have any way to input audio through an external microphone. What are you refering to?
Quote from: Ebrahim Saadawi on August 09, 2014, 11:24:27 AM
The 1100D does not have any way to input audio through an external microphone. What are you refering to?
From what I understand, he spliced it.
My guess is that instead of using the embedded microphone, he rewired the circuitry (2 wires, one cold, one hot) into a mono input, in which he can plug a microphone.
worked wonderfully for me. thank you so much
to make the card bootable, i used macboot (http://www.zenoshrdlu.com/macboot/macboot.html (http://www.zenoshrdlu.com/macboot/macboot.html)) and it's macbootcommand script, as described on their site. I added the magicLantern files to the card, then ran the update firmware process on the camera.
now when I hit the Av+/- button, I get all the bad-ass stuff, like time-lapse, and crazy stuff I don't yet understand.
thanks!
Hi,
the latest nightly is 20 Aug. Problem on nightly server?
regards
starbase64
Nightly Builds are complied as changes are made... no changes no need for a new Nightly.
ten days without changes on all cameras. wow
Since I can't code myself I don't worry about the frequency of the updates or new features...
New update is available: http://builds.magiclantern.fm/#/
Hey all,
I'm new and want to install magic lantern. The home page says it is compatible with the t3, but download page doesn't have a listed version. Do you use a version for another model?
http://builds.magiclantern.fm/#/
Thanks. Is this stable?
Top of page -> Downloads
and read disclaimer there.
Hello I'm new to this forum, I was just wondering if there will ever be raw video shooting capabilities for the t3
thanks in advance ,Jess
Quote from: Hosenborg on September 29, 2014, 09:16:51 PM
Hello I'm new to this forum, I was just wondering if there will ever be raw video shooting capabilities for the t3
thanks in advance ,Jess
There is raw shooting at the moment for 1100D, search on this topic for the latest build by an user
I have tried and i can shoot, but only 3-5 seconds
Hello,
I've just tried the last build for our camera. (Wanted to try dualISO).
DualISO - works fine, the previous build was somehow slower on my camera. This build is ok, BUT: using the motion detect made some trouble. It works great but it didn't let me return from liveView to normal view, after pushing the LV button it exited the LV and after a second returned to it. Turning off the camera worked. But that's the issue I had.. I'm very thankful for your work guys! If ML used Python I would try to help :)
Hello Transformers!
I am using nightly build Magic Lantern software of dated 27-7-2012, in my Canon 1100D Dslr. And now i want to update new magic lantern of 2014, so should i copy and replace new files with old ones?
And second help i needed from u is that please tell me how can i remove magic lantern from my camera. please send me link, Actually i forgot, but I once did that.
Good luck to all
And please send the latest Magic Latern of October 2014 download link for Canon 1100D. and its installation method.
Take care all
Can we get someone to flash a per-page, flashing-red sticky that says "READ THE FAQ, THEN THE WHOLE THREAD"?
Ontopic: read the instructions that flash on the camera when you install ML. Or, you know, the faq/manual.
1100d raw
Hello guys! I'm pretty new to Magic Lantern on 1100D, but since i have got it, i love it, love the expposure controls, focus peaks... But could someone do a full-on tutorial how to install the RAW video module?, i'm not sure if i even said the proper thing, but i'd like to see someone make a tutorial for "How to get RAW video on 1100D". Thanks.
Not available for 1100D:
https://builds.magiclantern.fm/#/features
It is, i suppose(Reply #1266;1267;1268 on this thread)
You have three options:
- Compile that branch on your own
- Ask Audionut to compile it for you
http://www.magiclantern.fm/forum/index.php?topic=12608.0
- Wait until this branch has been merged into main branch
I remember reading of a custom built that enabled full res silent pictures. Is that something that the 1100D can run?
photo on live view (without mirror) is important for me, i've made many time lapse.
What is the latest "most stable" nightly for the 1100D / T3?
The latest Nightly (magiclantern-Nightly.2014Oct07.1100D105.zip) crashs really often.
Hope someone can give me some recommendations.
Greetings
Mark
I'm using the "magiclantern-Nightly.2014Oct07.1100D105" build. It's quite stable.
Quote from: Mark Hähnel on November 05, 2014, 02:29:46 PM
crashs really often.
That's not helpful. http://www.catb.org/~esr/faqs/smart-questions.html#beprecise
QuoteThat's not helpful.
I haven't looked deeper into it. Just wanted to know about a nightly thats stable for others.
I saved the logs and will look into them and upload them as soon as i have time for it.
Hi.
I´m new here and i installed today the Nightly.2015Jan15.1100D105 on my eos 1100D.
Works great, but i don´t found the audio menu. first menu point is expo.
any help? sorry for my bad english!
https://builds.magiclantern.fm/#/features
audio features are not available on 1100D
Thank you! :( hope it comes in future or is it technical not possible?
Can anyone tell here what is the best last stable nightly build?
Thank you! :)
the answer to that question will always be: the most recent one
Quote from: dmilligan on February 06, 2015, 03:14:18 PM
the answer to that question will always be: the most recent one
I installed the last one but sometimes it have some visualization problem.
Are you able to reproduce them?
Not really well.
Sometimes the ML menu flash anc you can see the camera menu or display.
Quote from: ans86 on February 06, 2015, 04:46:02 PM
Not really well.
Sometimes the ML menu flash anc you can see the camera menu or display.
Don't worry, it's been occasionally doing that since at least 2013 with no ill effects.
Maybe a proper bug report will help to address this? Just saying ...
https://bitbucket.org/hudson/magic-lantern/issues?status=new&status=open&version=1100D/T3
hey guys i'm new to magic lantern and DSLRs in general just wondering why my videos are coming out dark. I have great lighting my settings are 24 fps, 50 shutter speed, iso 640, and aperture 3.5 (18-55mm kit lens). I'm not sure whats going on bc when I shot a test video with my iphone its perfect. Is there a feature I need to enable somewhere.
Increase your exposure parameters or get brighter lights
Thanks once I increased the ISO to 1600 it was good. I probably need a better lens to utilize the settings I was trying to film at.
Hey guys, i recently installed ML on my 1100D, first day everything was working fine and no problems. Yesterday, when i turned the camera off, the red light kept blinking, when the camera was off. It stopped when i took out the SD card. Is there any problem with this or can i just keep the SD card in it? I've read that a blinking red light meant that the SD card was busy (or something like that) when the camera is on. But mine even keeps blinking when the camera it shut down.
I also switched from video to M mode, to take pictures yesterday, but the shutter wouldn't open, and there was no liveview on. It was like it was in video mode, except i saw nothing on the screen (only the information about settings you always have when you press Q when in manual mode). After pulling the battery, the shutter went up again and i could take pictures. I haven't had this before and this was the only time i had it. Are these problems known or is it something new?
Thanks!
Quote from: TweeMeter on March 12, 2015, 09:24:43 AM
Are these problems known or is it something new?
Thanks!
This is definitely new.
Hi,
Not sure if this is the best place to post this but feel free to correct me!
I've been using ML for almost a month now, but it has been the most enjoyable month of using my T3 ever.
However, I was wondering if a new feature could be implemented? I think focus limiting would be extremely useful. The best it could possibly be is to have two focus limits, a near and a far, so the focus would only bounce around between the two points.
I'm saying this because I recently just started using it for bird shots, by leaving it right up close to a bird feeder and setting it to motion detect. I get a lot of cool shots, but the focus is often off, even shooting at f/11. If I could set the focus limits to either (or maybe both) just past the feeder and just in front, I could leave AF on for the shots.
Sample shot I've taken using this method: http://imgur.com/FEbBz5t
This would be so cool if you could do this!
We don't know how to control Canon AF algorithms. Most of the AF stuff is on a separate chip that we have no control over.
Cool.
Just out of curiosity, how then do you control the focus for focus racking and stacking?
In LV we can make the motor step. That's about it.
hi there! is there any risk in installing ML that cant be fixed by taking off ML?
Quote from: asdfg on April 02, 2015, 07:50:03 PM
is there any risk in installing ML that cant be fixed by taking off ML?
Yes
to what extent like could it ruin your camera completely?
http://wiki.magiclantern.fm/faq
Why is there a new version for 1100D.105 where the only entry in the changelog is for 700D.113?
Robot at work.
Change in code (Pull request confirmed) -> Build all. Only exception is 5D.123 which is a1ex's own.
I've noticed something fishy in the FPS override implementation. Can you help me check it?
1) With FPS override turned off, open the FPS submenu, enable the Advanced mode and write down the two timer values. Repeat for all video modes, and also for photo mode and 5x zoom.
2) Set FPS override to 35 and try all video modes. Write down timer values and make sure the image is normal.
•magiclantern-Nightly.2015May03.1100D105.zip
•Built on: 2015-05-03 02:25:03 +0200
1.Format the card from the camera.
2.Make sure you are running Canon firmware 1.0.5.
3.Copy ML files on the card and run Firmware Update.
and then appears to me firmware is not found
You downloaded a single zip file containing all ML files needed to install and run ML. I suppose you copied a single file and not - as requested - all ML files (= extracted content) to card.
I unpacked all files on card
Is there a file 1100D105.fir in card's root directory?
yes
Format card in cam, copy extracted nightly contents to card and retry.
If it doesn't work: Make a screen snapshot showing card's root directory contents.
not work
(http://www.bilder-upload.eu/thumb/4fc59d-1431241189.jpg) (http://www.bilder-upload.eu/show.php?file=4fc59d-1431241189.jpg)
EOS 1100D Firmware-Version 1.0.5 firmware is on the camera
http://www.canon.de/support/consumer_products/products/cameras/digital_slr/eos_1100d.aspx?type=firmware&firmwaredetailid=tcm:83-901719
(http://www.bilder-upload.eu/thumb/577ce8-1431241245.jpg) (http://www.bilder-upload.eu/show.php?file=577ce8-1431241245.jpg)
(http://www.bilder-upload.eu/thumb/9ba572-1431241269.jpg) (http://www.bilder-upload.eu/show.php?file=9ba572-1431241269.jpg)
Reset cam to factory defaults (including Fn), make sure to be in photo mode M (Liveview off) and retry.
If it doesn't help:
@nanomad: Do you have an idea what is going wrong here?
is still the same even after factory defaults
http://www.bilder-upload.eu/show.php?file=577ce8-1431241245.jpg (http://www.bilder-upload.eu/show.php?file=577ce8-1431241245.jpg)
Does it help if you rename the .fir in uppercase?
How large is your card?
that was it .fir in uppercase and the card is 16 GB
it is now running
(currently on the magiclantern-Nightly.2015May03.1100D105 build)
Has anyone tried RAW zebras/histograms lately?
I'm fairly sure I've seen them work on the 1100, but they seem to have stopped working at some point, since all I see are normal zebras(fast Luma-style over and underexposure red-blue patterns)/histograms (no ETTR hint, no EV bars), both in LiveView and image review. I am positive they are set to their RAW mode.
Also, screenshots might not be saving properly, since not IrfanView, nor GIMP can open .PPMs generated by the camera anymore. The header seems to be missing; here's the screenshot (https://drive.google.com/file/d/0Bx1Bmq9idHp1YURvSUw4OFE1dUE/view?usp=sharing), anyway.
Edit: According to dmilligan, we'll just wait for round 2 of RAW testing when the time's right.
Raw data in LV is disabled in the nightly build branch so histogram/zebras revert to YUV. It is working in another branch that hasn't been merged (and requires some manual work to merge it). Raw data is available in QR though, so you should see raw histogram and zebras there.
I've managed to take LV raw DNGs using the other branch (as well as FRSP), and the zebras and histogram work, but the EDMAC stuff for raw video I haven't managed to get working (I always get weird garbage data and/or crashes when I try), some of that is a little beyond my current level of knowledge.
@a1ex wrote:
"I've noticed something fishy in the FPS override implementation. Can you help me check it?
1) With FPS override turned off, open the FPS submenu, enable the Advanced mode and write down the two timer values. Repeat for all video modes, and also for photo mode and 5x zoom.
2) Set FPS override to 35 and try all video modes. Write down timer values and make sure the image is normal."
Strange!
One time in M mode in ,,FPS override" menu I was seeing ,,Rolling Shutter": 214748364.7 us, what is 2147483647 (2**31-1) with point.
One time I was seeing ,,Shutter range" 1/-214748... .. 1/-214748...
One time it was impossible to go into ML menu from ,,live view", without switching off camera.
When I was trying to do video (1280x720 – 25) with FPS override to 35 it was every time video withoud sound.
With second video mode (1280x720 – 30) with FPS override to 35 video was with sound.
I wrote everything what is changed during test exactly, f.ex. '-', '+' and 'x'.
1.1 Video mode (1280x720 – 25)
Shutter range: 1/25.. 1/4000
FPS Timer A: 1000 (+0)
FPS Timer B: 1280 (+0)
Main Clock: 32.07 MHz
Aktual FPS: 25.054
Rolling shutter: 31.2 us / line
1.2 Video mode (1280x720 – 30)
Shutter range: 1/30.. 1/4000 blinking with 1/30.. 1/3226
FPS Timer A: 960 (+0)
FPS Timer B: 1112 (+0) blinking with 1114 (+2)
Aktual FPS: 30.041 blinking with 29.987
Rolling shutter: 29.9 us / line
,,Shutter Range" is with connection to ,,FPS Timer B" (1/4000 with 1112 and 1/3226 with 1114 (+2)).
,,Aktual FPS" is blinking without connection to ,,Shutter Range" or ,,FPS Timer B".
1.3 Video mode (1280x720 – 25) with 5x zoom
Shutter range: 1/30.. 1/4000
FPS Timer A: 956 (+0)
FPS Timer B: 1116 (+0)
Aktual FPS: 30.059
Rolling shutter: 29.8 us / line
1.4 Video mode (1280x720 – 30) with 5x zoom
Shutter range: 1/30.. 1/4000
FPS Timer A: 956 (+0)
FPS Timer B: 1116 (+0)
Aktual FPS: 30.059
Rolling shutter: 29.8 us / line
1.5 A-DEP, M, Av, Tv, P
Shutter range: 1/30.. 1/4000 blinking with 1/30.. 1/3226
FPS Timer A: 960 (+0)
FPS Timer B: 1112 (+0) blinking with 1114 (+2)
Aktual FPS: 30.041 blinking with 29.987
Rolling shutter: 29.9 us / line
,,Shutter Range" is with connection to ,,FPS Timer B" (1/4000 with 1112 and 1/3226 with 1114 (+2)).
,,Aktual FPS" is blinking without connection to ,,Shutter Range" or ,,FPS Timer B".
1.6 A-DEP, M, Av, Tv, P with 5x zoom
Shutter range: 1/30.. 1/4000
FPS Timer A: 956 (+0)
FPS Timer B: 1116 (+0)
Aktual FPS: 30.059
Rolling shutter: 29.8 us / line
2.1 Video mode (1280x720 – 25) with FPS override to 35
Shutter range: 1/29.. 1/4598
FPS Timer A: 872 (x0.87)
FPS Timer B: 1050 (x0.82)
Aktual FPS: 35.026
Rolling shutter: 27.2 us / line
2.2 Video mode (1280x720 – 30) with FPS override to 35
Shutter range: 1/33.. 1/4414
FPS Timer A: 872 (-88)
FPS Timer B: 1050 (-62)
Aktual FPS: 35.026
Rolling shutter: 27.2 us / line
Can I post ML errors here for the 1100D?
Quote from: andreadoore on January 31, 2014, 08:04:18 PM
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?
I remember being in the mid 40's but it seems to have increased to the 50's now after one or two minutes of recording and it's gone yellow. There is this though: http://farm3.staticflickr.com/2810/11716975195_31bbf4be57.jpg from the post: http://www.magiclantern.fm/forum/index.php?topic=9673.0
can download since days no nightly
https://builds.magiclantern.fm/#/
when going back
Date: 2015-07-01 02:24:24 +0200 (failed)
Build Details
This Build Failed!
•Changeset: 3b95943
Changelog Build log
Date: 2015-06-25 02:25:02 +0200 (failed)
Build Details
This Build Failed!
•Changeset: 349e775
Changelog Build log
Date: 2015-06-24 02:24:59 +0200 (failed)
Build Details
This Build Failed!
•Changeset: 700da8c
Changelog Build log
Date: 2015-06-23 02:25:02 +0200 (failed)
Build Details
This Build Failed!
•Changeset: c46b607
Changelog Build log
Date: 2015-06-20 02:24:38 +0200 (failed)
Build Details
This Build Failed!
•Changeset: db3ebdf
Changelog Build log
Date: 2015-06-09 17:18:29 +0200 (failed)
Button "Show older builds".
What does "Build has failed" mean? Hard brick? Did someones camera explode?
Broken with intent, I suppose. See reply #1365. Same goes for EOS M.
a1ex hasn't commented artur_d's findings yet. Don't press, please, he wrote about lack of spare time ...
WTF why that? :/
I wanted to update my version to the latest working one (May 03). I downloaded and copied the folder to the existing folder on my sd card. Now ML does not start anymore. I remember there were some files I need to copy extra but I don't know what it is and I fear I've overwritten them. Somethings I the fonts folder I guess...
Can someone help me?
Quote from: Myxir on July 18, 2015, 03:44:40 PM
WTF why that? :/
Preventing things like exploding cameras.
Quote from: Myxir on July 18, 2015, 03:44:40 PMCan someone help me?
Delete Autoexec.bin and ML directory and copy extracted nightly build contents to card.
Quote from: Walter Schulz on July 18, 2015, 04:09:30 PM
Preventing things like exploding cameras.
Wouldn't it have been easier just to remove the "Don't touch this" feature?
Hey.
Yup, ML worked again after that.
all-clear: The C.FN #7 was set to set AE/AF. I did not do that. WTF...
But now my AF is broken. I cannot use Af in PASM modes. In all other modes it works.
It seems like the "Is in focus"-bit is set to "yes" all the time. With my 40mm STM I can use the MF even when the AF is activated and did not hit. I've tried different lenses, removing the SD card and the battery. I've installed 1.05 stock from canon.com com but it did not help.
I repeat: AF _does not_ work for me, even _without_ Magic Lantern on the SD card! o.O :(
A constant that is used for FPS override is wrong, so a1ex simply deleted the constant, that caused the compiler to fail b/c something it expects to have a value, doesn't. Rather than just disabling FPS override altogether, he intentionally allowed the build to fail, the idea being to encourage others to fix the problem. I normally try to fix stuff like this, but this particular issue requires more time than I have at the moment (it's also work that is not very interesting to me :P )
Both the 1100D and the EOSM are currently in the same situation with the wrong FPS override values. I looked up the code, fps-engio.c, and found where the code was intentionally broken to prevent these platforms from being compiled. It is rather easy to change it so these platforms do compile but of course the point is to fix it. a1ex asked for users to run some tests and report the results which was done on both platforms but sadly for users of these cameras the developers that know what to do with these numbers are too busy and not that interested. This isn't to criticizes, they are unpaid volunteers and this is just the way free and open source software is developed. You want something, you have to figure it out.
This is the header to fps-engio.c and it has some clues. Unfortunately the link goes to an outdated Google spreadsheet which points to a newer spreadsheet but it is rather cryptic and I can't see where the values reported need to be plugged in to get the correct timer values.
@dmilligan - is there any hint at all where to look for some sort of documentation on this? Apparently the 1100D and EOSM use different methods to change timer B but I can't get much further than that.
/**
* FPS control with engio calls (talking to DIGIC!)
* This method is portable: works on all cameras.
*
* https://docs.google.com/spreadsheet/ccc?key=0AgQ2MOkAZTFHdEZrXzBSZmdaSE9WVnpOblJ2ZGtoZXc#gid=0
*
**/
/**
* fps_timer_b_method
* Notes by g3gg0:
*
* okay i found how to directly change the sensor frame rate without patching and copying memory areas.
* it doesnt matter which mode is selected.
*
* on 600D v1.0.1 it is calling engio_write() with a buffer that writes the rate.
*
* unsigned long frame_rate[] = {
* FPS_REGISTER_B, 0xFFFF, // timer register
* FPS_REGISTER_CONFIRM_CHANGES, 0x01, // coherent update
* 0xFFFFFFFF // end of commands
* };
*
* void run_test()
* {
* void (*engio_write)(unsigned int) = 0xFF1E1D20;
* frame_rate[1] = 0xFFFF; // timer value as usual [Alex: timer value minus 1 on certain cameras]
* engio_write(frame_rate);
* }
*
*
**/
This might be better discussed in a development topic but broken nightlies keep coming up in the user topics. Besides, I'm not a developer--I know just enough to get myself into trouble.
I would like ML on my Canon T3 is it still being developed and not available for my model yet? I have tried almost all the Versions of firmware for the 1100D-105 and I keep getting the same message on my camera that the update file cannot be found.
1) Format card in cam, copy extracted nightly build contents to card and run firmware update. Follow instructions as described on page 1 of this thread.
2) If it doesn't work: Format card again and copy extracted FIR file (Canon's FIR, not ML FIR) to card and run firmware update. If done, proceed with step 1.
I am super new on doing this and I don't want to make any mistakes I may need a step by step walk through...I tried what you posted for me to do but this is the result I got. Autoexe.bin not found Please copy all ml files.
Quote from: Walter Schulz on November 05, 2015, 07:06:53 PM
1) Format card in cam, copy extracted nightly build contents to card and run firmware update. Follow instructions as described on page 1 of this thread.
2) If it doesn't work: Format card again and copy extracted FIR file (Canon's FIR, not ML FIR) to card and run firmware update. If done, proceed with step 1.
Format card in cam, copy extracted nightly build contents to card and run firmware update.
Autoexec.bin is contained in nightly build zip file.
Is it there in card's root?
Again I am very new....cannot stress enough I am not sure how to do this.. I have used the main download page and selected the 1100D-105 and it clearly states build failed... I went to top of page and followed link and got this file...ML-SETUP.FIR....the only one I could save and loaded it into the camera...that is when I got the error message I got.
Top of page -> Downloads -> Download Nightly Builds -> 1100D.105 -> Show older builds -> 2015-05-03.
Extract ZIP. Copy AUTOEXEC.BIN and 1100D105.FIR and ML directory to card.
Run firmware update.
there is no 2015-05-03
Date: 2015-05-02 19:25:03 -0500/Date: 2014-05-05 19:25:01 -0500
those are the closest to what you recommended
https://builds.magiclantern.fm/jenkins/job/1100D.105/
Thanks works great! ;D
Hi.
2 short questions.
Is it possible to use manual exposure, iso and shutter speed, when filming with the 1100D on Magic Lantern?
And is 720p still the highest (H.264, not RAW) resolution - no 1080p?
I'm mostly shooting with my 50D and sometimes use my 1100D only as second camera.
Thanks!
1. Yes
2. Yes
@dmilligan
1.Can you please tell me how to set it from automatic to manuel? I can't find it.
2.Has somebody ever tried implementing a 1080p video modus? Maybe it works, even if only for a few seconds/minutes.
Thanks!
Quote from: EVZML on November 09, 2015, 05:57:21 PM
@dmilligan
1.Can you please tell me how to set it from automatic to manuel? I can't find it.
2.Has somebody ever tried implementing a 1080p video modus? Maybe it works, even if only for a few seconds/minutes.
Thanks!
1.In the ML menu make sure you are in the "Expo." tab and make sure "Exp. Override" is on. Then, in video mode, you should be able to adjust iso, shutter, etc. from that same tab (in magic lantern's menu).
2. I asked about 1080p before and they said it couldn't be done.
I have 7D and EOS M - both with ML installed, sure. Great addon to Canon.
Friend of mine ask me about video crop mode ability on his 1100D. I tell him to look into ML "Video" menu and enable Video Crop Mode in it. But he give me answer "I havnt this item in menu".
So, want to ask here. Have 1100D ability to write mp4 at crop video mode? As I know, current 1100D ML build havnt RAW video ability in. Crop mode also off?
It feels soooooo good to be back. Positive people.
Quote from: oleg_milantiev on November 11, 2015, 08:32:23 PM
I have 7D and EOS M - both with ML installed, sure. Great addon to Canon.
Friend of mine ask me about video crop mode ability on his 1100D. I tell him to look into ML "Video" menu and enable Video Crop Mode in it. But he give me answer "I havnt this item in menu".
So, want to ask here. Have 1100D ability to write mp4 at crop video mode? As I know, current 1100D ML build havnt RAW video ability in. Crop mode also off?
No crop mode for 1100D.
Shooting raw, the crop function works. However, the 1100D is basically unusable for RAW video after too much time tying (too slow card slot and very low resolution with lots of bugs)
Short answer no.
I hope someone is still interested in this little large-pixeled APS-C camera.
Are there really no updates between May 3rd and October 1st?
I'm sorry guys IF my question maybe offends you, BUT I just have to find out somehow.
I'm not a coder, but would study it in order to make ML work on Canon 1200D.
Does anyone know IF the 1200D is the replacement for the older 1100D Canon?
If so, would the 1100D ML work on the 1200D?
If not, is there somebody who would create ML for the Canon 1200D, PLEASE!!???
http://www.magiclantern.fm/forum/index.php?topic=12627.0
Hello there!
First things thanks for your time.
I've spent a good part of my evening here trying to install ML on my 1100D but without success, I get the update file error :
Update file error.
Please check the memory card and reload the battery and try again.
I've :
* Formated my sd card (low level)
* use a 4Gb sd-card
* Executed the make_bootable script
* Tryed with three different build (latest, april and one from march).
* Updated my canon firmware to 1.0.5
* Re-downloaded firmware and try again.
My guess is that maybe there have been a new sub-build from canon for the 1.0.5 which is not compatible with ML (?) if so maybe did someone still have the canon firmware he used to upgrade before installing ML ?
Thanks in advance.
Excuse my engrish. :-X
Format card in cardreader.
Format card in cam.
Copy extracted nightly build contents to card.
Run firmware update.
Report back.
Wow it works, thanks very much!
Hello everyone :) I have one problem with ML.
I can't see ML's HUD on the LV, but this problem is new, I do not have it a week ago.
I need your help someone
I have the last bluid(magiclantern-Nightly.2015May03.1100D105.zip) for information
Hi everyone
I just downloaded ML on my 1100D and it works fine :)
Now i really want to use a external monitor but my monitor only supports that old AV.
I can order that AV-400 cable for eos but on all sites the specifications says that 1100D is not supported.
Do you guys think that ML gave my camera the option to use AV output. Or can software don't change things like that ?
Greets
just installed magiclantern-Nightly.2015May03.1100D105 - a build from over a year ago. the current builds are "BUILD FAILED". any word on a downloadable executable that will work?
i would try but am terrible in C and cygwin
thanks
ejfuhr
try it with other memory card.
if same error ocurrs the problem is hardware not ml
Hey 1100D / T3 ML users. Saw this in another topic:
Quote from: a1ex on December 16, 2016, 09:41:16 PM
- the raw buffer is not allocated all the time (as it's done on the new models) -> easy to fix, see the 1100D raw branch
There's a working branch of the 1100D? I thought it has been broken for over a year!
Nobody ran this test yet?
http://www.magiclantern.fm/forum/index.php?topic=1009.msg146321#msg146321
I thought the 1100D development was dead, too. I missed the earlier request from a1ex; here are my results:
(magiclantern-Nightly.2015May03.1100D105, clean fresh install)
First, 5x zoom had no effect on the timer values I observed.
In photo mode: after a fresh boot, timers were 0 (-1), 0 (-1). Switching to photo mode after being in video mode, timers remained as they were in the video mode.
FPS override off:
1280x720@30: 960 (+0), 1112 (+0)
1280x720@25: 1000 (+0), 1280 (+0)
FPS override @35:
1280x720@30: 872 (-88), 1050 (-62)
1280x720@25: 872 (x0.87), 1050 (x0.82) <- this was the only setting that showed 'x' instead of '+' or '-'; also the only one with decimals
Let me know if there are other tests to be run, and I'll try to help. I'd love to see a new version.
Great. Don't know what to do with that but hopefully we'll have 1100D back on the nightly builds.
I made some test builds for testing 10/12bit raw and included a build for the 1100D. Nothing is fixed yet and the new features are probably not working but we need to start somewhere. Let's see if we can breath some new life into this camera.
For brave testers only:
https://bitbucket.org/daniel_fort/magic-lantern/downloads/magiclantern-raw_video_10bit_12bit.2016Dec18.1100D105.zip
Sorry -- needs some more work on it before it is ready for testing.
How did you make this build? Raw video does not work on 1100D except on a very old experimental branch. That branch no longer cleanly merges with current unified or other recent developments like 10/12 bit.
The 1100D nightly build was intentionally disabled because a1ex noticed some incorrect values for FPS override timers. I've never cared enough to try and fix it (the Maths involved hurt my head :P ), I just compile it with the old incorrect values.
Well if it the math hurts dmilligan's head then it must be way over my head!
I just compiled it with the incorrect FPS timers and didn't notice the missing modules. However, I was following this lead:
Quote from: a1ex- the raw buffer is not allocated all the time (as it's done on the new models) -> easy to fix, see the 1100D raw branch
So it looks like I need to hunt down an old branch to find out what he means. Do you happen to recall the approximate vintage of that branch?
It's not hard just very tedious.
This is the branch you are looking for:
https://bitbucket.org/hudson/magic-lantern/branch/allocate-raw-lv-buffer
@dmilligan
Thanks -- again! :D
As I understand it: 1100D is still intentionally broken by undefining TG_FREQ_BASE as it seems.
But this also breaks "unified" (?) build, because reboot-all.c needs 1100D.105/magiclantern.bin.
As for now, I put
#undef FEATURE_FPS_OVERRIDE
in
platform/1100D.105/features.h
and I re-enabled the wrong
#define TG_FREQ_BASE 32070000
in
src/fps-engio.c
in my sandbox in order to be able to build "unified".
Basically, I wanted to try a unified build for two models I have, 60D and 550D. Am I correct that this is not possible at the moment?
Any suggestions where I can put in some work? I am willing to help and I know C and make.
I am still working my way through the build process - as for "unified" - that should possibly be another thread...
Quote from: dmilligan on December 19, 2016, 02:41:02 AM
The 1100D nightly build was intentionally disabled because a1ex noticed some incorrect values for FPS override timers. I've never cared enough to try and fix it (the Maths involved hurt my head :P ), I just compile it with the old incorrect values.
Hi dmilligan,
being both a software developer and an owner of the 1100D, I would be willing to help here. However I have no idea what exactly needs to be done with the values found by Floont in Reply #1410. You mention something about complicated maths. Is there some formula that we need to compute certain values with? Could you please point me in the right direction about what needs to be done? Then maybe I can figure out a way how to do it.
Study the FPS code and understand how it works (the ML code itself is basically the best documentation we have on the hardware). That's what I don't have time to do.
@Straight_Shooter
Wow, another developer with a 1100D. There are multiple issues going on that platform. Here's one we're trying to solve but keep getting lost tracing lv_raw_dump:
http://www.magiclantern.fm/forum/index.php?topic=5601.msg176935#msg176935
a1ex hinted that solving the 1100D might help with other platforms:
http://www.magiclantern.fm/forum/index.php?topic=5601.msg176545#msg176545
The math problem headache we're talking about here is:
src/fps-engio.c
#elif defined(CONFIG_1100D)
#define NEW_FPS_METHOD 1
#undef TG_FREQ_BASE
// #define TG_FREQ_BASE 32070000 - incorrect, see http://www.magiclantern.fm/forum/index.php?topic=1009.msg146321#msg146321
#undef FPS_TIMER_A_MIN
#define FPS_TIMER_A_MIN (ZOOM ? 940 : 872)
#undef FPS_TIMER_B_MIN
#define FPS_TIMER_B_MIN 1050
#define SENSOR_TIMING_TABLE MEM(0xce98)
#define VIDEO_PARAMETERS_SRC_3 0x70C0C
We had a similar issue with the EOSM that was resolved. I'm not a developer so I can't tell you exactly how it was figured out but the discussion starts around here:
https://www.magiclantern.fm/forum/index.php?topic=14959.msg148768#msg148768
From what little I know about this issue, I seem to understand that the value for TG_FREQ_BASE is not correct. To solve this, somehow a better value needs to be obtained. But I have zero idea what exactly needs to be done to achieve that, hence my question.
What kind of computation is needed here? Is this explained at some point in the code, maybe in a comment?
I guess I'll try having a look at the file: fps-engio.c
Check Reply #1429 (http://www.magiclantern.fm/forum/index.php?topic=1009.msg176584#msg176584). It points to a test a1ex asked to be run which someone did run and posted the results. How to calculate the correct TG_FREQ_BASE is beyond me but last time I said that was because I didn't look at the code carefully enough.
FYI, there is an experimental build for 1100D with raw video support over here: https://builds.magiclantern.fm/experiments.html
It is incomplete, so you are welcome to fill in the missing bits. Some of them can be found in this thread, just follow dfort's links.
With this build, please check whether the FPS values displayed by ML match the value selected from Canon menu, in all video modes. Also check whether selecting 35 fps in ML menu gives valid image in all video modes.
Hi. First timer here.
I updated my 1100D firmware to 1.0.6 (14 Nov 2016 release). I just want to ask if the latest ML build for 1100D "magiclantern-Nightly.2015May03.1100D105" will work with the latest 1.0.6 firmware? Or is it strictly for 1.0.5 only? Thank you.
1.0.5 only. You can find an archived firmware on Pelican's website (http://pel.hu/). The 1100D.105 is here:
http://pel.hu/down/eos1100d-v105.zip
Quote from: a1ex on January 13, 2017, 12:44:04 PM
With this build, please check whether the FPS values displayed by ML match the value selected from Canon menu, in all video modes.
1280x720 @ 25 fps selected:
ML displays a steady fps rate of 25.000
1280x720 @ 30 fps selected:
ML displays one of two different values. The fps value changes between 29.976 and 29.922.
This behavior is reproducible, but the time after which this happens seems to be random? I have seen it happen like after half a minute, or sometimes earlier (after ten seconds or so). It seems that the value 29.976 is shown for noticeably longer periods of time than the other value.
Quote from: a1ex on January 13, 2017, 12:44:04 PM
Also check whether selecting 35 fps in ML menu gives valid image in all video modes.
Desired FPS: 35 (from 25)
Actual FPS: 34.949
Desired FPS: 35 (from 30)
Actual FPS: 34.949
Hi, I updated ML today to tha latest version (2017Feb12.1100D105). But when I start it, it still says May 2015May03?
BTW if I turn the camera of it crashes. The red light is on and the camera wont do anything until i remove the battery.
Okay, autoexec and/or(?) ml-setup.fir were missing.
Quote from: Straight_Shooter on January 14, 2017, 09:38:35 PM
1280x720 @ 25 fps selected:
ML displays a steady fps rate of 25.000
1280x720 @ 30 fps selected:
ML displays one of two different values. The fps value changes between 29.976 and 29.922.
This behavior is reproducible, but the time after which this happens seems to be random? I have seen it happen like after half a minute, or sometimes earlier (after ten seconds or so). It seems that the value 29.976 is shown for noticeably longer periods of time than the other value.
Desired FPS: 35 (from 25)
Actual FPS: 34.949
Desired FPS: 35 (from 30)
Actual FPS: 34.949
Okay, so... does anybody know what to do with these values?
I tried looking at the code, but I can't really make heads or tails of it.
Looks OK, so the 1100D build was re-enabled a while ago.
Some more useful tests: stubs test (from selftest.mo) and Lua API test, both with the latest experimental Lua build.
Quote from: a1ex on March 05, 2017, 05:11:30 PM
Looks OK, so the 1100D build was re-enabled a while ago.
Ah, that is great news! I hadn't noticed that yet. Thanks for your good work a1ex.
Hello,
I'm new here.
So, I installed ML on my Rebel T3 (1100D) - onto two SD cards.
Both work well.
Now, the question is, when I try to record HDR videos - the video flickers like crazy (one frame at one set ISO, second frame the other set ISO, then it repeats).
Am I missing something or is that a slight glitch/bug thing?
(BTW, I'm running March 30th nightly build, 1.0.5 FW)
That's exactly what HDR video is supposed to do.
If on Mac -- use @Danne's cr2hdr.app or MLP (depending on if shot in RAW or H264) to convert and render out ProRes w nice looking HDR effect.
It is also recommended to shoot in 50/60p when shooting HDR videos as the process will be halfed w fps after blending in the ISO 100/800 (or 100/1600 if you want to push it) and I can't help on Windows.
Quote from: dmilligan on April 27, 2017, 11:06:53 PM
That's exactly what HDR video is supposed to do.
I guess so, but I'm fairly sure it's not supposed to noticeably flicker - at least not as bad, as it does;
Quote from: DeafEyeJedi on April 28, 2017, 05:57:12 PM
If on Mac -- use @Danne's cr2hdr.app or MLP (depending on if shot in RAW or H264) to convert and render out ProRes w nice looking HDR effect.
It is also recommended to shoot in 50/60p when shooting HDR videos as the process will be halfed w fps after blending in the ISO 100/800 (or 100/1600 if you want to push it) and I can't help on Windows.
Well, that's unfortunate for me, because I'm a windows user. / Canon T3 (1100D) doesn't support 50/60p recording (highest I can get it is 35),
So I guess no HDR videos for me?
Hello,
I am trying to manually change video settings (ISO, Aperture, shutter) on the 1100D,
I came a cross a YouTube Video pointing to download magiclantern to do this.
I did it maybe a year ago, but now I seem not to be able to access it again.
Do I really need this program to manually change settings in video mode?
I also found the following but I cannot find on my camera the info button they are taking about:
Get into video mode from the rocker around the shutter button.
Press info a few times until you have a page of menu items.
Tap on the icon in the upper right corner. That will get you to the option for Manual Video.
Then you can change the settings by taping the setting you want to change and then adjusting via clicking left or right or rotating the click wheel.
Once you start a video by pressing the red record button you can change the settings without interrupting the recording.
Press the INFO button repeatedly until the settings are visible on the bottom of the screen.
Either tap the item or move to it using the click wheel right or left.
Then the easiest method of changing it is to rotate the wheel until you reach the value you want. Alternately you can tap the item such as ISO and then use the small arrows on screen left and right, and then press Set.
Thanks for any suggestions.
Nic
Hello sorry if this is a noob question but I'm in a kind of emergency ^^.
I built a script for my 1100D via PicoC (http://www.magiclantern.fm/forum/index.php?topic=4362.msg24457#msg24457) but I can't find the scripts menu, is that not available for 1100D builds? (I updated ML to nightly this morning).
Thanks
Ok sorry got my answer, I just found that picoc is deprecated and we must use LUA scripts now.
Hope this is the right place to ask.
I'm brand new to ML, and before flashing I want to know is it possible to shoot 1080 video on the T3?
Thanks
Nope
http://www.magiclantern.fm/forum/index.php?topic=3928.msg189097#msg189097 (http://www.magiclantern.fm/forum/index.php?topic=3928.msg189097#msg189097)
Hellooooo. Just wondering if anyone is using and maintaining this camera.
Many of the modules are no longer compiling, tests are failing, there are experimental builds waiting for reports from users and a few of us are trying to get new features running on these older cameras but nobody is downloading test builds for the 1100D.
Hi! I've just signed up to say that I use 1100D and can help with testing.
Welcome to the forum @nuvon -- jump over to the 12-bit (and 10-bit) RAW video development discussion (http://www.magiclantern.fm/forum/index.php?topic=5601.msg194442#msg194442) and let's breath some new life into this old camera.
Hi, guys. Thanks for your great job
I'm new to this forum, so I have 2 questions:
1. what's the last installable and usable nightly for our camera?
2. how can I help the development for our old, but still nice, 1100d?
1. the first one from the download page should be fine (more or less, there are a few things not working, such as Lua scripting)
2. watch other topics and see where the 1100D may need help (such as 10/12-bit raw recording, linked above, and - of particular interest for me right now - Lua updates (http://www.magiclantern.fm/forum/index.php?topic=14828.msg194706#msg194706))
This camera is a tricky one (lowest amount of RAM out of all ML supported cameras, unusual display aspect ratio, lower resolution screen), so things are very likely to go wrong on this model first. Yet, testing feedback on this camera is almost nonexistent, so that's were you can help.
If you can compile ML and attempt to fix some of these issues, that would be even better. To get started, my (biased) recommendation would be to look at the QEMU guide (https://bitbucket.org/hudson/magic-lantern/src/qemu/contrib/qemu/) - there is an installation video for Ubuntu (https://twitter.com/autoexec_bin/status/913530810686418944), for Mac (http://www.magiclantern.fm/forum/index.php?topic=16012.msg191686#msg191686) and a guide for Windows (http://www.magiclantern.fm/forum/index.php?topic=20214.0).
screenshot: https://ibb.co/d5xzJb
tested builds:
- magiclantern-Nightly.2017Mar30.1100D105.zip
- magiclantern-Nightly.2017Oct31.1100D105.zip
- magiclantern-lua_fix.2017Dec23.1100D105.zip
is there a fix for it?
There is an experimental raw video build, but other than a few snapshots from Danne (https://www.magiclantern.fm/forum/index.php?topic=5601.msg194925#msg194925), I have no idea how it works in practice => please report back. The silent picture module requires the LiveView raw backend enabled, so try it from the 10/12-bit raw video build.
If it works fine or if I can solve it easily based on user feedback, I'll consider integrating this feature into mainline.
Got a 1100D available. Tested "from the 10/12-bit raw video build" from experimental section. Not sure what to test so a few general results. (Lua not working):
- Silent dng files are recorded but with black borders. Only the first dng contains an image with 10/12bit. 14bit extracts all dng files from the MLV file.
- MLV files 10/12/14 bit with borders
Samples(20mb)
https://bitbucket.org/Dannephoto/magic-lantern/downloads/1100D_samples_MLV_DNG.zip
As too often I´m on a tight schedule but will do my best to help with feedback on this...
Can you try this on a MLV with more than 2 frames?
mlv_dump M29-1336.MLV --dng --no-stripes --no-fixcp
md5sum *.dng
No cegars with that command:
Macbooks-MacBook-Air:~ air$ /Users/air/Desktop/Switch.app/Contents/mlv_dump --dng --no-stripes --no-fixcp /Users/air/Desktop/magic/1100D/A_ORIGINALS/M29-1336.MLV
MLV Dumper
-----------------
Mode of operation:
- Input MLV file: '/Users/air/Desktop/magic/1100D/A_ORIGINALS/M29-1336.MLV'
- Decompressing before writing DNG
- Enforcing 14bpp for DNG output
- Using output path '/Users/air/Desktop/magic/1100D/A_ORIGINALS/M29-1336_' for DNGs
- Convert to DNG frames
- Output into '/Users/air/Desktop/magic/1100D/A_ORIGINALS/M29-1336_'
File /Users/air/Desktop/magic/1100D/A_ORIGINALS/M29-1336.MLV opened
File /Users/air/Desktop/magic/1100D/A_ORIGINALS/M29-1336.M00 not existing.
Processing...
Got a new RAWI, throwing away previous frame buffers etc.
[ERROR] Invalid block size at position 0x00228e00
Processed 2 video frames at 25.00 FPS (0.08 s)
Done
Macbooks-MacBook-Air:~ air$
Did the md5sum on the two files that came out:
4cbbaca5cc8c338a5ff978e5cc989203 M29-1336_000000.dng
bb60b5ea5fe3f75e08b4abecac7d7ef8 M29-1336_000001.dng
Note that md5sum isn´t installed so get it through brew if anybody wants to use it:
brew install md5sha1sum
Additional info:
Also want to point out that for every mlv_lite recording mode there are several beeps and display messages about "Hack error at 0" and "data corruption at slot 38"
mlv_play:
Trying to preview the MLV file in camera(mlv_play) gives the info "Invalid header size" and a stuck screen which resolves when pushing a button and gets me back to liveview.
I just had a glass of wine, so I might write nonsense, but it is my understanding that "more than 2 frames" means 3 or 4 or 5 frames, or any other number x where "x > 2" evaluates to True (at least in the English dialect I'm familiar with).
"Data corruption" does not sound good; may I see some EDMAC screenshots?
According to your question:
QuoteCan you try this on a MLV with more than 2 frames?
It´s about 60mb in size so I assume it´s more than two shitty frames in there:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/M29-1336.MLV
Enjoy your wine...
Hm, other than frame #2 (corrupted) and possibly #3 (broken metadata), all other frames are clean.
Can you run the stubs test (selftest.mo) from both the 10/12-bit build and the lua_fix build? Also EDMAC screenshots and other related stuff from selftest.mo and edmac.mo.
Later, work atm.
Quote from: a1ex on January 29, 2018, 11:03:50 AM
There is an experimental raw video build, but other than a few snapshots from Danne (https://www.magiclantern.fm/forum/index.php?topic=5601.msg194925#msg194925), I have no idea how it works in practice => please report back. The silent picture module requires the LiveView raw backend enabled, so try it from the 10/12-bit raw video build.
If it works fine or if I can solve it easily based on user feedback, I'll consider integrating this feature into mainline.
this works fine, but display goes off and not on again.
possible to combine silent pic with advanced bracketing and intervalometer?
Stubs API test starts and run but after a while falls into an error. Logs here:
https://drive.google.com/open?id=1HFFT-QkU7CBI4sp-riHxdRQIJQG4RuSL
or:
STUBTEST.LOG
https://drive.google.com/open?id=1FTZRqgt5DPXXkFHOHbhNG5plbiS0N6Rx
LOG000.LOG
https://drive.google.com/open?id=1Ne3e3fcGcfWbk5G7Kkp0KiUXwPNwLfbv
CRASH01.LOG
https://drive.google.com/open?id=1Xiq1-tsV3LVrcorednuBtwDpo4ZWP9St
CRASH00.LOG
https://drive.google.com/open?id=1aFlDB3xZbOCn3LV5qTgoW6ukizMIMwpV
Have to get back on those edmac tests
Well, sure could need some guidance around edmac.mo but just fooling around with it I came up with this:
https://drive.google.com/open?id=1s13Qyo7bXg3Dxh9V5NeLgxtfjHggg6ef
VRAM0.PPM
https://drive.google.com/open?id=1BtlR3ALKVdVm1nIHzD-698wrSrDZzOqM
EDMAC000.LOG
https://drive.google.com/open?id=1TXi_36f9VRHZMXnGpxf0GHX_KcTVW7Xz
Quote from: Danne on January 29, 2018, 04:28:18 PM
Stubs API test starts and run but after a while falls into an error.
Interesting, I just ran the Stubs API test on the EOSM2 thinking it might show what I need to work on and it failed on LoadCalendarFromRTC, same as your 1100D test. Ran it on the EOSM and it also failed at the same spot. All tests passed on the 700D.
The above log shows successful result on LoadCalendarFromRTC; the problem is at the next test ;)
Got this in QEMU:
m0 = MALLOC_FREE_MEMORY => 0x43148
[Pass] p = (void*)_malloc(50*1024) => 0xc1b40
[Pass] CACHEABLE(p) => 0xc1b40
m1 = MALLOC_FREE_MEMORY => 0x36938
_free(p)
m2 = MALLOC_FREE_MEMORY => 0x43148
[Pass] ABS((m0-m1) - 50*1024) => 0x10
[Pass] ABS(m0-m2) => 0x0
m0 = GetFreeMemForAllocateMemory() => 0x6f24c
ASSERT : Memory\Memory.c, Task = run_test, Line 188
1862: 7111.168 [MEM] NG AllocateMemory 262144
1863: 7111.168 [MEM] Total = 0x8b0000, Free = 0x6f1ec, MaxReg = 0x239d4
1864: 7111.936 [MEM] Num Alloc = 3296, Num Free = 293
The error is actually on the next line - it's unable to allocate 256K of memory...
The lua_fix and 10/12-bit experimental builds also have the latest changes for 1100D (https://bitbucket.org/hudson/magic-lantern/commits/branch/allocate-raw-lv-buffer); any luck with these?
The silent picture module should work too.
Tested 10/12-bit experimental
Silent DNG works and MLV has the correct size although giving malloc errors, check pics below. As I managed to stop the file before the camera buffer ran out it´s also possible to transcode the 10bit file with mlv_dump and the files looks really nice.
Stubs api test is working, ends with following message:
"test complete 11756 passed. 3 failed"
STUBTEST.LOG
https://drive.google.com/open?id=1AftiepRPtHyTs2iKOzcauhGLGH94uUUN
Some other log:
https://drive.google.com/open?id=1X88I13ruQ_jKapWnR1R0ijZI9fE5KFFe
Silent DNG:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/90630000.DNG
MLV:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/M30-1622.MLV
Screenshots when recording 10bit
(https://s9.postimg.cc/jhfbxhyzj/Ska_rmavbild_2018-01-30_kl._14.24.32.png)
(https://s9.postimg.cc/6q15qzwxb/Ska_rmavbild_2018-01-30_kl._14.26.40.png)
can someone please update the download links in the first post...
Tested lua fix build 30.01.2018 and works fine for me. THANKS.
Done.
Reminder: nobody ran the Lua tests (https://www.magiclantern.fm/forum/index.php?topic=14828.msg194706#msg194706) on this camera yet. They were linked earlier in this thread (http://www.magiclantern.fm/forum/index.php?topic=1009.msg195488#msg195488) ~ 1 month ago.
Updated 10/12-bit builds with memory management from crop_rec_4k and attempted some integration to raw_video_10bit_12bit. Will it work or will it break raw video on all other cameras?
Quick dirty test:
magiclantern-raw_video_10bit_12bit.2018Jan31.1100D105Tested two 10bit MLV recordings: Data corruption at slot 51(file is recorded only two files extracted as before)
Tested on 12bit recording: Data corruption at slot 61(file is recorded only two files extracted as before)
Tests following this:
https://www.magiclantern.fm/forum/index.php?topic=14828.msg194706#msg194706
magiclantern-lua_fix.2018Jan30.1100D105LUATEST.LOGhttps://drive.google.com/file/d/1SivdU_wQi4Et1Mc4r5ygAF0lNbDIRDY3/view?usp=sharing
benchmarks memory(in liveview window)
malloc error :((sad smiley from liveview window)
Should test my 100D with the latest changes in raw_video_10bit_12bit branch....
QuoteUpdated 10/12-bit builds with memory management from crop_rec_4k and attempted some integration to raw_video_10bit_12bit. Will it work or will it break raw video on all other cameras?
magiclantern-raw_video_10bit_12bit.2018Jan31.100D101Tested a 100D with the latest changes And ran test recordings on 10/12/14 bit for mv1080, movie crop mode 5x zoom, all worked.
Data corruption: regression or nondeterministic issue also present in previous build? (this will take some more recordings to figure out)
Can you test the Jan31 build on something else than 100D?
Lua test locked up at testing Canon GUI functions? That's odd - this test is just flipping GUI modes back and forth (MENU, PLAY, LiveView, photo mode). This test also works in QEMU...
QuoteData corruption: regression or nondeterministic issue also present in previous build? (this will take some more recordings to figure out)
Was not an issue with earlier build. Only "Hack error at 0" Could test a few more files to see if I can reproduce data corruption.
Ran a few files on a 600D with this build and all files were recorded nicely:
magiclantern-raw_video_10bit_12bit.2018Jan31.600D102Don´t have my 5D mark III available, maybe someone else could test on that one.
Update*
Data corruption issues appears also on januay 30th build when stopping manually or camera automatically stops filming. When checking the MLV files there is a corrupted frame in the later part of the file more or less always present an all files.
Tested 31th january build on a faster SD card and 10bit was continuous with max resolution1424x480.
Data corruption seems gone. Maybe it was a slow/bad card. Will do more takes with the faster card...Yep, data corruption seems vanished.
Two noob questions. Turning off the beep? Is there a manual mode setting for when recording movies? Cannot find it.
How about lossless... :P
Some more tests:
- regular mlv_lite shooting works fine(mv720, only mode available on this cam)
sample: https://bitbucket.org/Dannephoto/magic-lantern/downloads/M31-1208_samples.zip
- 5xzoom reaches 2160x748 but needs some shaving at the top part it seems:
2160x748(5xzoom)
sample: https://bitbucket.org/Dannephoto/magic-lantern/downloads/M31-1212_samples.zip
(https://s9.postimg.cc/69l01xuzz/Ska_rmavbild_2018-01-31_kl._10.21.07.png)
1600x748(5xzoom)
sample: https://bitbucket.org/Dannephoto/magic-lantern/downloads/M31-1209_samples.zip
(https://s9.postimg.cc/kss53cvun/Ska_rmavbild_2018-01-31_kl._10.21.31.png)
Fullres silent DNG:
Seems problematic.
Sample: https://bitbucket.org/Dannephoto/magic-lantern/downloads/90640003.DNG
(https://s9.postimg.cc/46aku30a7/Ska_rmavbild_2018-01-31_kl._10.37.31.png)
Quote from: starbase64 on January 29, 2018, 04:24:29 PM
this works fine, but display goes off and not on again.
same problem on 70D, display is off after take a photo
@Danne: actually I was thinking at other models with low memory (600D, 650D, 700D, EOSM) and I remembered you had something from this list. These updates were taken from crop_rec_4k, initially written from 5D3, so that test is unlikely to give any surprises.
Can you also take a screenshot of the console (Debug menu - Show console) right after starting the camera in movie mode and enabling raw video, and another one right after turning it off?
Lossless compression on DIGIC 4 is hard - my attempt on 60D (some months ago) was unsuccessful. I'll revisit it at some point, but not right now - my short-term goal is to integrate the current stuff into mainline (QEMU, Lua, 10/12-bit raw video, 100D, 70D, 1200D etc).
The silent DNG looks fine to me (I have something to address the overexposure, work in progress, stay tuned).
@starbase64: if you are talking about the full-res silent picture, it should behave the way you want in the lua_fix build.
Quote from: a1ex on January 31, 2018, 12:12:31 PM
@starbase64: if you are talking about the full-res silent picture, it should behave the way you want in the lua_fix build.
cool, THANKS
On the 1100D:
With RAW video enabled
(https://s9.postimg.cc/4adl1vhz3/Ska_rmavbild_2018-01-31_kl._12.28.10.png)
RAW video disabled
(https://s9.postimg.cc/i41xqxia7/Ska_rmavbild_2018-01-31_kl._12.28.17.png)
Looks fine. I've got another test for you to try.
Start from the allocate-raw-lv-buffer branch and apply this patch:
diff -r 23524a6ed2f9 src/config-defines.h
--- a/src/config-defines.h
+++ b/src/config-defines.h
@@ -47,3 +47,3 @@
/** warning: it will slow down boot by a few seconds */
- //~ #define CONFIG_MARK_UNUSED_MEMORY_AT_STARTUP
+ #define CONFIG_MARK_UNUSED_MEMORY_AT_STARTUP
diff -r 23524a6ed2f9 src/raw.c
--- a/src/raw.c
+++ b/src/raw.c
@@ -139,6 +139,6 @@
#ifdef CONFIG_1100D
-#define CONFIG_ALLOCATE_RAW_LV_BUFFER
+#undef CONFIG_ALLOCATE_RAW_LV_BUFFER
#define DEFAULT_RAW_BUFFER MEM(MEM(0x4C64)) /* how much do we have allocated? */
-#define DEFAULT_RAW_BUFFER_SIZE 0 /* is this really overwritten by other code? needs some investigation */
-#define RAW_LV_BUFFER_ALLOC_SIZE (3906*968)
+#define DEFAULT_RAW_BUFFER_SIZE 10*1024*1024 /* is this really overwritten by other code? needs some investigation */
+//#define RAW_LV_BUFFER_ALLOC_SIZE (3906*968)
#endif
diff -r 23524a6ed2f9 src/mem.c
--- a/src/mem.c
+++ b/src/mem.c
@@ -927,4 +927,4 @@
-#define MEMORY_MAP_ADDRESS_TO_INDEX(p) ((int)CACHEABLE(p)/1024 * 720 / 512/1024)
-#define MEMORY_MAP_INDEX_TO_ADDRESS(i) ALIGN32((i) * 512 * 1024 / 720 * 1024)
+#define MEMORY_MAP_ADDRESS_TO_INDEX(p) ((int)CACHEABLE(p)/1024 * 720 / 128/1024)
+#define MEMORY_MAP_INDEX_TO_ADDRESS(i) ALIGN32((i) * 128 * 1024 / 720 * 1024)
Then take two screenshots of the Free Memory dialog:
- in movie mode, without any modules loaded
- in movie mode, with mlv_lite enabled (raw video active).
nothing loaded
(https://s9.postimg.cc/3q3lwcksf/Ska_rmavbild_2018-01-31_kl._14.13.12.png)
nothing loaded
(https://s9.postimg.cc/im253ybmn/Ska_rmavbild_2018-01-31_kl._14.13.26.png)
mlv_lite RAW video loaded
(https://s9.postimg.cc/5hwkr9bv3/Ska_rmavbild_2018-01-31_kl._14.13.19.png)
mlv_lite RAW video loaded
(https://s9.postimg.cc/atbhbzddb/Ska_rmavbild_2018-01-31_kl._14.13.32.png)
Wait a minute, that means the raw buffer is not overwritten by anything else. Then, where is all this allocation thingie coming from? Maybe back then it didn't work for some other reason, and we thought it's some sort of memory corruption? How do the same two screenshots look in x5 zoom?
(BTW, the screenshots are easier to compare if you don't add variable-sized white borders; try "convert foo.ppm foo.png")
A couple of jpegs 5x zoom
Nothing loaded
(https://s9.postimg.cc/sh2h1tue7/VRAM1.jpg)
(https://s9.postimg.cc/40kb7d1db/VRAM2.jpg)
loaded
(https://s9.postimg.cc/b3s6mzein/VRAM3.jpg)
(https://s9.postimg.cc/uye8941fz/VRAM4.jpg)
That's clean, too - we may not even need this allocation stuff. Can you check the photo mode as well? This time, the two states would be:
- global draw off (camera started that way, not turned off afterwards)
- global draw on, with any raw-based overlay enabled (such as raw histogram, raw zebras or raw spotmeter)
Can you define DEFAULT_RAW_BUFFER_SIZE as 8MB (8*1024*1024 - from counting the pixels in the screenshots I get about 8.7), keep CONFIG_MARK_UNUSED_MEMORY_AT_STARTUP (so it would re-check this size, just in case) and try recording? This time, the assert should no longer get triggered.
If successful, can you try this configuration in all the video modes? (photo mode, video mode, x5 zoom, whatever else this camera has).
TODO: I'm not really sure I understand how this raw buffer allocation is done in Canon code, and whether the results are repeatable; will experiment on 60D and see what I get.
In photo mode, liveview open:
global draw off(https://s18.postimg.cc/m47b2g7ix/VRAM4.png)
(https://s18.postimg.cc/n6hhkzy21/VRAM5.png)
global draw on(https://s18.postimg.cc/hv2l0arex/VRAM6.png)
(https://s18.postimg.cc/x3sie2st5/VRAM7.png)
I added this:
QuoteCan you define DEFAULT_RAW_BUFFER_SIZE as 8MB (8*1024*1024 - from counting the pixels in the screenshots I get about 8.7), keep CONFIG_MARK_UNUSED_MEMORY_AT_STARTUP (so it would re-check this size, just in case) and try recording? This time, the assert should no longer get triggered.
To my patched version from here:
https://www.magiclantern.fm/forum/index.php?topic=1009.msg196592#msg196592
And files comes out clean and nice without errors. But I don´t get errors with today´s raw_video_10bit_12bit either even without the fix. I had a slow card before which I believe corrupted files. 5x zoom still comes out with a fishy top border like described here:
https://www.magiclantern.fm/forum/index.php?topic=1009.msg196582#msg196582
Tets only done i 14bit. I was thinking I could try the same changes in raw_video_10bit_12bit but it will not compile:
../../src/raw.c:146:2: warning: #warning FIXME: using dummy DEFAULT_RAW_BUFFER_SIZE [-Wcpp]
#warning FIXME: using dummy DEFAULT_RAW_BUFFER_SIZE
^
../../src/raw.c: In function 'raw_lv_realloc_buffer':
../../src/raw.c:544:39: error: 'DEFAULT_RAW_BUFFER' undeclared (first use in this function)
if (raw_lv_buffer != (void *) DEFAULT_RAW_BUFFER)
^
../../src/raw.c:544:39: note: each undeclared identifier is reported only once for each function it appears in
make: *** [raw.o] Error 1
danands-MacBook-Pro:1100D.105 danne$ Anybody else tired of rescale and convert PPM files one by one by the way? ffmpeg does the trick:
for i in *.PPM ; do
ffmpeg -i "$i" -pix_fmt rgb24 -vf scale=500:-1 $(basename "${i/.PPM}").tif
done
Quote from: Danne on January 31, 2018, 07:59:16 PM
And files comes out clean and nice without errors. But I don´t get errors with today´s raw_video_10bit_12bit either even without the fix.
Well, it's easier when Canon code does the memory allocation for us (that was the point of these last tests - to use their buffer, like we do on all other models). This camera has the lowest amount of RAM out of all other ML-enabled cameras, so it's best if we don't have to allocate large stuff just to get raw LiveView data. However, should we ever need to do that (maybe if anyone would like to implement full-res LiveView for timelapse), the raw backend is now ready for that (cc @ these folks (http://www.magiclantern.fm/forum/index.php?topic=19336)).
Quote from: Danne on January 31, 2018, 07:59:16 PM
Anybody else tired of rescale and convert PPM files one by one by the way? ffmpeg does the trick:
for i in *.PPM ; do
ffmpeg -i "$i" -pix_fmt rgb24 -vf scale=500:-1 $(basename "${i/.PPM}").tif
done
What about this?
for i in *.PPM; do
convert $i -resize "500x500>" ${i%.PPM}.png
done
(for pixel peeping, like I did to estimate the raw buffer size, I actually prefer the screenshot non-resized)
Hey Danne - nice work on the 1100D. It would be great to get some simple silent DNG files from the various settings and run the raw_diag module so we could check that the skip values are correct. Looks like the zoom mode needs some adjustment.
convert is nice too :).
@dfort
A little dinner break and I see if I get the energy back today or I´ll just continue in the morning...
Quote from: Danne on January 31, 2018, 08:51:18 AM
malloc error :((sad smiley from liveview window)
Solved. Took many hours to rework the memory backend (https://bitbucket.org/hudson/magic-lantern/branch/memory-backend) (found lots of other issues besides this one), but now it runs on all models in QEMU. Overall, the memory backend should be a lot more robust.
Torture test: old-style Lua (without umm_malloc) on 1100D (the camera with lowest amount of memory). It finally worked! 8)
PR open (https://bitbucket.org/hudson/magic-lantern/pull-requests/906/memory-backend-improvements).
Epic progress. No cams here but will test as soon as possible.
Also looking for a high-res photo of the camera display (large enough to see the individual pixels), showing ML menu with any recent build.
If it's hard to get the entire screen in focus, just focus on some problem areas (e.g. some icon or fine print that doesn't look well).
Quote from: a1ex on February 27, 2018, 06:20:45 AM
Also looking for a high-res photo of the camera display (large enough to see the individual pixels), showing ML menu with any recent build.
If it's hard to get the entire screen in focus, just focus on some problem areas (e.g. some icon or fine print that doesn't look well).
I've been using magiclantern-Nightly.2017Aug07.1100D105, but per a1ex's request, I loaded magiclantern-lua_fix.2018Feb24.1100D105 and took the two attached photos. (This version is effectively non-functional for me - it displays a large number of error messages at launch, most of the menus are just black pages with an icon at the top, and I can't navigate within the menus themselves, but that's not what the question was about (so I'll return to magiclantern-Nightly.2017Aug07.1100D105 for now)).
Hopefully these images are close to what you're looking for. I can try other things if it's helpful.
(Please note that I have a scratch-guard coating on my display, so there might be some artifacts from that - if so, such artifacts should be consistent between the two photos.)
(https://thumb.ibb.co/cvjzxc/Img_6146a.jpg) (https://ibb.co/cvjzxc)
(https://thumb.ibb.co/jqnmcc/Img_6148a.jpg) (https://ibb.co/jqnmcc)
Ha, the screen looks very similar to the one from VxWorks models (https://www.magiclantern.fm/forum/index.php?topic=1452.msg195564#msg195564).
Press MENU to get out of that screen (you have it in the regular builds too).
Can you try a few more different screens? In particular, raw histogram has some fine details (the vertical bars). A large console should also help. Also, a large zoom on fine print, please (even if it's just a small part of the screen in the picture).
Vertically, things are pretty clear - odd lines are missing (first line being 0). Horizontally, I'm not very sure what happens. Best guess: all columns end up used, half of them on odd physical lines, and the other half on even ones.
Quote from: a1ex on February 27, 2018, 03:37:29 PM
Can you try a few more different screens? In particular, raw histogram has some fine details (the vertical bars). A large console should also help. Also, a large zoom on fine print, please (even if it's just a small part of the screen in the picture).
As I said, this new version doesn't play well with my camera. I can't get the histogram to display - menu item is on, but grayed out. It works in the 2017Aug07 version, if that's helpful (not sure if you're looking for something new or just how the 1100D display looks in general).
Fine print from magiclantern-lua_fix.2018Feb24.1100D105 version:
(https://thumb.ibb.co/n2H2YH/Img_6162a.jpg) (https://ibb.co/n2H2YH)
Histogram from magiclantern-Nightly.2017Aug07.1100D105 version:
(https://thumb.ibb.co/gYxNHc/Img_6166a.jpg) (https://ibb.co/gYxNHc)
Yes, that helps. Can you (or anyone else who might have an extreme macro lens) zoom on the histogram even more? I'd like to find out how the subpixels are arranged and how the display buffer is interpreted by the hardware (just as a curiosity, not something of high priority).
BTW, you have some modules from the older version, that's the reason you've got the errors.
Whenever something is grayed out, it also has a message at the bottom of the screen. Can you read it?
The four photos I posted were taken with my iPhone SE. I dug out my old A590 and S30, both of which have macro features, but neither one got an image sharper or higher-resolution than the iPhone pic I already posted. Hopefully, someone with a better second camera/lens will chime in.
I need to leave for a while, will look at the 2018Feb24 version again another time - I'll try a completely clean install to see if it clears up any of the issues I'm seeing.
I would like to know if there will be firmware for the t3 1100d with firmware 1.0.6 because the one that currently exists is for firmware 1.0.5, thanks :)
Doing a minor firmware update like 1.0.5 -> 1.0.6 on the 1100D should be relatively easy.
https://www.magiclantern.fm/forum/index.php?topic=19417.0
It requires a firmware dump and some time. I can help but someone needs to get this started. You can use the portable ROM dumper that is on the bottom of the Nightly downloads page (https://builds.magiclantern.fm/). Don't post a direct link to the firmware dump! Just post when you have it and we'll take it from there.
Instructions on how to run the portable dumper:
https://www.magiclantern.fm/forum/index.php?topic=16534.0
Thanks @Danne - Another Canon firmware update ML port in progress:
(https://farm1.staticflickr.com/968/40974495164_7cdbd3b412.jpg) (https://flic.kr/p/25qLZTb)
Cool! Glad to be able to help.
It's Alive!
(https://farm1.staticflickr.com/830/27839502768_da580c865c.jpg) (https://flic.kr/p/Jq5Jg3)
(https://farm1.staticflickr.com/979/39900656140_cbed45d3f1.jpg) (https://flic.kr/p/23MThXf)
That was the easy part, several modules aren't compiling but that's happening on the unified 1100D.105 nightly builds too.
Getting some interesting message in QEMU:
1583: 7037.440 [MC] cam event guimode comp. 1
1623: 8292.096 [STARTUP] too heavy... free : 442KB
1624: 14325.504 [STARTUP] too heavy... free : 442KB
1625: 20293.376 [STARTUP] too heavy... free : 442KB
1626: 26326.784 [STARTUP] too heavy... free : 442KB
1627: 32294.656 [STARTUP] too heavy... free : 442KB
1628: 38328.064 [STARTUP] too heavy... free : 442KB
1629: 44295.936 [STARTUP] too heavy... free : 442KB
1630: 50329.344 [STARTUP] too heavy... free : 442KB
1631: 56297.216 [STARTUP] too heavy... free : 442KB
1632: 62330.624 [STARTUP] too heavy... free : 442KB
1633: 2762.496 [STARTUP] too heavy... free : 442KB
1634: 8795.904 [STARTUP] too heavy... free : 442KB
1635: 14763.776 [STARTUP] too heavy... free : 442KB
I'll post a test build on my downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/) but the selftest module isn't working so it will be just to see if it is working the same as the 1.0.5 nightly version. Seems like it would be better to test this camera on the raw_video_10bit_12bit branch because more modules are working on that branch.
One question, is anyone actually using this camera and is willing to run it through some tests?
This was my first DSLR, now it's my second backup camera. I use ML on it and am interested in trying out the latest version. The other two Canons I have are a 70D and 5DMkIII.
@DavidSamish - You can start by trying the 1100D.106 test build I posted on my downloads page and reporting your findings. If it works and seems about as stable as the nightly build I can prepare builds using the various branches so we can run some tests on real hardware.
Thanks for the update, @dfort !!!
will test too the 1.0.6 build
@aplinhares - thanks. There's a 1100D Canon Firmware for Testers.zip package on my downloads page with both the Canon 1.0.5 and 1.0.6 firmware updaters so you don't need to search for them to go back and forth. If the test build works about the same as the current nightly we can start testing some other branches that give the 1100D some more functionality.
@Dfort: I upgraded my firmware to Canon's 1.0.6 alright, but with a different card loaded with your 1.0.6 ML files; ML folder and autoexe.bin file, I can't seem to do the ML firmware update from the Canon-menu-firmware route. Do I need the ML-SETUP.FIR file from the other card? Nope- that didn't work. What am I doing wrong?
@DavidSamish - This is an early test build and doesn't have an ML-SETUP.FIR file for the 1.0.6 firmware yet. If you didn't uninstall ML before doing the Canon firmware update then your camera boot flag is still set so put the 1100D.106 ML files on a bootable card -- a card that has had ML installed should have the bootflag set. You can also set the bootflag on your card using either EOScard (http://pel.hu/eoscard/) for the PC or MacBoot (http://www.zenoshrdlu.com/macboot/macboot.html) for the Macintosh. If all else fails, go back to 1.0.5, install 1100D.105 and make sure it is working then update again to 1.0.6 making sure you don't uninstall ML or format the card in a way that erases the bootflag.
Once I get some feedback that the test build actually works on the camera I'll ask for a ML-SETUP.FIR for the 1100D.106.
One thing I'd like to be double-checked: the Q button code. Debug -> Show GUI events -> press Q and write down the event code.
On 1200D, this button code appears to be different than what we have assumed.
The 1100D was falling behind other cameras on the unified branch so I brought it up to date with this pull request (https://bitbucket.org/hudson/magic-lantern/pull-requests/925/1100d-unified-updates/diff). New test builds for the unified branch for both 1.0.5 and 1.0.6 posted on my downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/). Once these check out we can move on to the lua_fix tests.
Also, please check the previous post (https://www.magiclantern.fm/forum/index.php?topic=1009.msg200927#msg200927) about the Q button code.
@dfort: I got the 1.0.6 firmware and the ML 1100D106 to work together. I had to degrade to 1.0.5 and re-upgrade, as you mentioned. The MacBoot didn't work; I got "The Java class file "MacBoot.class" could not be launched."
I am getting an error message: 'Error loading "ML/MODULES/t3_106.sym" File does not exist." and on the bottom of the screen "missing symbol file: ML/MODULES/t3_1006.sym : File does not exist" and
"save configs...
save configs..."
So far so good...
That doesn't sound good. Are you sure one message says "t3_106.sym" and the other one says "t3_1006.sym" ???
I know it is a PITA but also check the 1.0.5 test build because I put in a pull request to get some modules working on that version.
I'm not seeing these problems in QEMU or maybe I just don't know what to look for.
So sorry, only t3_106 is listed - my bad typo :-[
Even that is weird because if you look at the file structure on the download:
(https://farm1.staticflickr.com/912/41860779941_2f5ac2b03c.jpg) (https://flic.kr/p/26M6rtc)
So how is this happening?
Quote from: DavidSamish on May 03, 2018, 04:06:14 AM
I am getting an error message: 'Error loading "ML/MODULES/t3_106.sym" File does not exist."
Are you deleting everything off the card before transferring all the files from the download or just copying over the autoexec.bin file?
That's weird. I started my T3 today, and there is no error message. Maybe it "needed" a couple of restarts. ML seems to be working.
Ok--so how is the camera handling? Is it working as expected?
Turn on the selftest module and run the Debug -> Self tests -> Stubs API test -- problems? Go back to 1.0.5 and try it again. What we're looking for is if the issues we find on 1.0.6 are new or inherited from 1.0.5.
Once we get through this part I'll make a lua_fix build for 1.0.6. In the meantime, you could run the lua_fix build for 1.0.5 that is on the experiments download page (https://builds.magiclantern.fm/experiments.html).
[EDIT] There have been some download activity on the test builds but no reports yet. I posted a 1.0.6 lua_fix build hoping that someone takes the initiative to do some testing and report back.
Quote from: a1ex on December 16, 2017, 01:36:42 AM
For every single camera model available on the Experiments page (lua_fix build), please run:
- api_test.lua (upload the log)
- selftest.mo -> stubs tests (upload the log)
- bench.mo -> memory benchmarks (upload the screenshot)
- overall sanity check (for example, if you decide to take this build out and use it for a couple of hours, please report back)
This is what the memory benchmark tests looks like in QEMU:
(https://farm1.staticflickr.com/864/40084153210_4b6338c4fe.jpg) (https://flic.kr/p/2456LeQ)
[EDIT] If anyone wants to try out 1100D.106 in QEMU, here's the new script:
1100D/debugmsg.gdb
# ./run_canon_fw.sh 1100D -d debugmsg
# ./run_canon_fw.sh 1100D -d debugmsg -s -S & arm-none-eabi-gdb -x 1100D/debugmsg.gdb
source -v debug-logging.gdb
# To get debugging symbols from Magic Lantern, uncomment one of these:
#symbol-file ../magic-lantern/platform/1100D.106/magiclantern
#symbol-file ../magic-lantern/platform/1100D.106/autoexec
#symbol-file ../magic-lantern/platform/1100D.106/stubs.o
macro define CURRENT_TASK 0x1a2c
macro define CURRENT_ISR (MEM(0x670) ? MEM(0x674) >> 2 : 0)
# GDB hook is very slow; -d debugmsg is much faster
# ./run_canon_fw.sh will use this address, don't delete it
# b *0xff06c91c
# DebugMsg_log
b *0xff06fafc
task_create_log
b *0xff1e8638
register_interrupt_log
b *0xff1d34d4
SetEDmac_log
continue
[EDIT 2] Found out that many of the lua tests work in QEMU so I tried running them and it did fine up to the middle of the exposure tests then showed some sort of a srm_malloc_suite error.
(https://farm1.staticflickr.com/828/28037073638_16600fb4df.jpg) (https://flic.kr/p/JHxkcm)
The same error is showing up on 1.0.5 and 1.0.6. However, running just the exposure test completed without any errors.
More information on Reply #305 of the How to run Magic Lantern into QEMU?!... (https://www.magiclantern.fm/forum/index.php?topic=2864.msg201034#msg201034) topic.
Some testing with the 1100D. Provided autoexe.bin and other info logs from three test builds:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/tests_1100D_new%20firmware.zip
Started with this build since it was already on my cam:
testbuild_105_01_stubtest(zipped folder)
Changeset: 23524a6ed2f9+ (allocate-raw-lv-buffer) tip
Seems more stable than with lua test builds(check autoexe.bin for build info)
Both firmware versions seems to behave the same in my tests. Cannot do any allround tests because Q button stopped working in both lua versions. Check zipped folder:
testbuild_105_02_stubtest_luatest
testbuild_106_03_stubtest_luatest
Thanks for testing. I suspected that 1.0.6 would be about the same as 1.0.5 and that 1.0.5 has some issues.
The selftest module test turned up something I haven't seen before:
[FAIL] bmp = bmp_load("ML/CROPMKS/CINESCO2.BMP", 1) => 0x0
That is the only failed test so we aren't in too bad a shape there but the lua tests stopped on the GUI function test on both 1.0.5 and 1.0.6. Let's see what other tests it can pass or fail. Check out this post on the 60D topic (https://www.magiclantern.fm/forum/index.php?topic=14739.msg200395#msg200395) for instruction on how to run individual lua tests.
As expected, the benchmark looks very different on the camera than in lua--see Reply #1505 (https://www.magiclantern.fm/forum/index.php?topic=1009.msg201029#msg201029) for the same test in QEMU.
(https://farm1.staticflickr.com/904/41262381675_2e55242577.jpg) (https://flic.kr/p/25SduvH)
Hey
I'm new here so apologies if I'm posting on the wrong thread but i have a question specific to canon 1100d.
On page 52 of this forum someone suggested that it might be possible to rewire your camera to be able to take a mic...
I Just bought rodé videomic go thinking it could connect to my canon 1100d (it does have something that looks a lot like a 3.5 input) but when cable wouldn't go in input i looked it up and found that that model doesnt take external mic... Bit of a bugger as i'm travelling and it was a mission to get the microphone in the first place...
Has anyone managed to hack their camera's hardware to allow it to take a mic?
Cheers
D
Hello, new to photography and camera firmware hacking. But, I've been rooting Android since 2012, and I tuned my 2004 Grand Prix's PCM.
I've found the nightly build for my Rebel T3 (1100D)
I understand the nightly builds should be flashed over a stable build, but I can't find any other builds for my rig?
Could someone point me in the right direction?
Thanks
Sent from my Moto Z (2) using Tapatalk
Quote from: FastKatt on June 25, 2018, 03:46:18 AM
I understand the nightly builds should be flashed over a stable build, but I can't find any other builds for my rig?
Not correct. Consider all instructions not found/linked on this site outdated and invalid.
Follow instruction found in -> Top of page -> Downloads -> Download Nightly Builds -> 1100D / Rebel T3 1.0.5 -> Installation
BTW: If you are new to photography consider learning how to use your cam without ML. Learning about exposure time, aperture and ISO is challenging enough (been there, done that). YMMV esp. if you are addicted to video recording.
Those are the instructions I followed, before I signed up on the forums. The only thing I did not do is copy my ROM files back to my computer.
I was hoping to have recording bars at the top of the screen, and like the idea of having a battery icon work a percentage (xx%)
I probably wouldn't get into very many of the features of this hack, but still wanted to have it there in case I found I was at a point where I would like to use something.
I am finding there is a lot to be learned, thanks for the advice!
Sent from my Moto Z (2) using Tapatalk
Quote from: FastKatt on June 25, 2018, 07:00:53 PM
Those are the instructions I followed, before I signed up on the forums.
Please link/quote the part of instructions talking about "stable build" having to be overwritten to work. We like to correct our errors.
Quote from: FastKatt on June 25, 2018, 07:00:53 PM
The only thing I did not do is copy my ROM files back to my computer.
There is a chance getting a bricked cam to work using these files.
Quote from: FastKatt on June 25, 2018, 07:00:53 PM
I was hoping to have recording bars at the top of the screen, and like the idea of having a battery icon work a percentage (xx%)
In movie mode toggle screens by pressing DISP button until ML screen appears.
Looking for a quick test:
- qemu branch
- compile from minimal/qemu-frsp with "make MODEL=1100D"
- you'll get a small autoexec.bin with no dependencies (no other files required), that's going to capture a full-res silent picture and preview it
- if it works, please upload a picture of the camera screen (just want to check where the preview appears on the screen)
- the picture will not be saved on the card (it should only display a preview).
Tried the qemu-frsp quick test on a 500D and it works. I had to run it a few times because the timing of the button presses seem to make a difference. Anyway, the request is for testing on the 1100D. One of the few people I know who has access to this camera and can compile ML is on vacation so I uploaded a test file to my downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/). Look for 1100D_qemu-frsp_test.zip
This is for the 1100D.105 and when you unzip it, the autoexec.bin file placed on a bootable card and run on a camera that has the bootflag set.
Note that this will capture a full-res silent picture. If you haven't used this feature before you'll probably be surprised by an overexposed image. That's because FRSP doesn't use the camera shutter and the capture speed is usually much slower than what you have set.
Here is what the test looks like on the 500D. Note that there is a black bar at the top of the image so it doesn't cover the entire screen.
(https://farm2.staticflickr.com/1806/28695169727_7dc5174751.jpg) (https://flic.kr/p/KHGfeD)
Interesting. So the Canon overlays were captured in the image? Have you tried this a few times and does it always appears the same?
Maybe you just have to press the buttons quicker. The test program only gives you 5 seconds to do so; after that, it attempts to capture the image regardless of whether you went to LiveView/PLAY or not.
Also make sure you are in M mode, and ISO must not be Auto. Otherwise you may get an error message.
OK - I deleted the earlier post. Now I believe I captured what you requested.
(https://thumb.ibb.co/d5UcjT/canont3pic.jpg) (https://ibb.co/d5UcjT)
That is a lamp shade in the upper left of the image. The rest is overexposed but I believe it gives you what you were hopinh for.
After numerous Err 70s that seem to be related to a quirky SD card, I got the following (using 1100D_qemu-frsp_test):
(https://thumb.ibb.co/hKLXJo/Img_6674.jpg) (https://ibb.co/hKLXJo)
(please excuse the crud-laden screen protector)
Hello there! T3 owner and ML user here. I am willing to test firmware that you throw at me.
My camera runs 1.0.5 right now. Is 1.0.6 ML just as stable as 1.0.5? If so, I may upgrade the "official" firmware.
Latestbuild isn't 1.05 still?
magiclantern-Nightly.2018Jul03.1100D105.zip
I worked on a port for the 1.0.6 Canon firmware (https://www.magiclantern.fm/forum/index.php?topic=1009.msg200539#msg200539). Don't have the camera so we're depending on user input. You can get a test build from my downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/).
If you download the current build from the official downloads page you'll see lots of modules aren't building so a while back I submitted a fix for the 1100D.105 unified branch. Don't have the camera so we're depending on user input. You can get a test build from my downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/). Please post your test results here or on the pull request (https://bitbucket.org/hudson/magic-lantern/pull-requests/925/1100d-unified-updates/diff).
Quote from: dfort on August 19, 2018, 06:04:53 AM
I worked on a port for the 1.0.6 Canon firmware (https://www.magiclantern.fm/forum/index.php?topic=1009.msg200539#msg200539). Don't have the camera so we're depending on user input. You can get a test build from my downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/).
Uh oh... I uninstalled ML from 1.0.5 camera by doing the firmware update and waiting one minute. Then I upgraded the camera to 1.0.6, downloaded your latest test Nightly, placed it on a card, and attempted to re-enable ML booting through the Firmware Update.
Of course, as I now see reading back one page, ML-SETUP.FIR is not updated to 1.0.6 support yet. So on my camera the firmware update screen hangs with "wrong firmware version, expected 105, pull the battery".
I tried using EOSCard to set BOOTDISK and EOS_DEVELOP but, of course, even if the *card* is marked bootable, the *camera* is not hacked to read it.
How are people getting 1.0.6 ML to boot without a 1.0.6 ML-SETUP.FIR? Can I get one made somehow?
Best using 2 cards. One for ML and an obsolete one for Canon firmware.
Format both cards.
Use "obsolete" to downgrade to Canon firmware 1.0.5.
Copy ML for 1.0.5 to "ML card" and install ML on cam. Remove card.
Take "obsolete" and upgrade cam to Canon firmware 1.0.6.
Take "ML card" and copy files for ML (for 1.0.6) to card. Overwrite all files.
Done.
Thanks! I actually solved it myself by following your steps above - but did it using just one card and EOSCard to disable bootable when going 1.0.5-ml -> 1.0.6. (Camera crashed when trying to use a Bootable card without a valid autoexec.bin on filesystem)
Next question for @a1ex: I can't find "Show GUI Events" on the Debug menu, otherwise I'd tell you the Q code for 1.0.6.
Right, I've disabled a bunch of features to squeeze RAM, including FEATURE_SHOW_GUI_EVENTS.
Here's a test build for 1.0.6 with this feature enabled: https://builds.magiclantern.fm/jenkins/job/1100D.106-test/
Cool. Good to know my firmware updates are good for something.
Been a while since I worked on it and never noticed the comment about the 600D. Suppose it also applies to the 1100D?
diff -r 9025834982de platform/1100D.106/features.h
--- a/platform/1100D.106/features.h Fri May 04 17:38:44 2018 -0700
+++ b/platform/1100D.106/features.h Mon Nov 26 13:56:02 2018 +0100
@@ -23,6 +23,5 @@
// disabled, because autoexec.bin gets to big and 600D does not boot
#undef FEATURE_SHOW_TASKS
#undef FEATURE_SHOW_CPU_USAGE
-#undef FEATURE_SHOW_GUI_EVENTS
#undef FEATURE_SHOW_EDMAC_INFO
#undef FEATURE_FLEXINFO
Quote from: dfort on November 27, 2018, 04:36:42 AM
Cool. Good to know my firmware updates are good for something.
Yeah, looking forward to the holiday season, to... catch up with ML developments :D
Quote from: dfort on November 27, 2018, 04:36:42 AM
Been a while since I worked on it and never noticed the comment about the 600D. Suppose it also applies to the 1100D?
From model_list.c in QEMU source:
{
.name = "600D",
.ram_size = 0x10000000, /* 256MB */
...
},
{
.name = "1100D",
.ram_size = 0x08000000, /* 128MB */
...
},
so the issue is much worse on 1100D.
However, out of all DIGIC 2 and newer models, the crown goes to 1000D (64 MB). Even the old 400D appears to have 128 MB.
Edit: apparently the sensor in 1100D might be faster than expected:
Quote from: a1ex on November 28, 2018, 09:12:22 PM
- 1100D might have 128 MPix/s (32 MHz x 4 channels, but default video readout apparently uses 2? I really need to double-check that)
That would be just as fast as 700D & co., if this hypothesis is valid. That is, faster than 600D & co.
Photo mode readout configuration: timer A = 1474, B = 2876, clock = 32 MHz => 7.55 fps at full resolution.
The camera is advertised for 3 frames per second, right? There are 4 pixels read out for each timer A increment, i.e. 4 channels read out at once. There is some overhead too, that's why timer A * 4 is greater than horizontal resolution.
Video readout configuration, from raw_res.txt:
720p25: A = 1000, B = 1280, readout size 1496 x 967 (this includes black borders)
720p30: A = 960, B = 1112, same readout size
Timer A can be pushed to 872 in both modes.
What's interesting: for each timer A increment, only 2 pixels appear to be read out. In other words, the sensor might throttled in LiveView. No other DIGIC <= 5 camera does that, to my knowledge, so I'd like to find out how it works. Will prepare some low-level tests.
Edit Jan 1: false alarm. The 1100D definitely uses 4 channels for LiveView readout. Daniel Rozsnyo took one of these apart and showed me the analog signal from one of these 4 channels in LiveView:
(https://a1ex.magiclantern.fm/bleeding-edge/1100D/1100D-lv-readout.jpg)
Reducing that overhead might be doable (likely one of the ADTG registers); doing so might enable higher frame rates, up to about some
theoretical 80 FPS at 1428x804 (i.e. full-width 16:9) !!!
Quote from: a1ex on January 01, 2019, 10:03:21 AM
1100D, on the other hand, is an interesting beast:
It runs at 32 MHz x 4 channels (i.e. pixel clock is the same 700D & co.), but for some reason, it has a huge overhead. In regular (24/25/30p) movie mode, C0F06084/88 is set to 0x200c3/0x3c903af, i.e. xmax = 1886 (likely rounded to 1888), out of which 390 pixels are cropped from the left side. ML still has to crop 68 pixels of left OB; that gives 1428 active horizontal pixels, 458 (!) for OB width and 2 pixels for rounding (guess); these require "only" 14.75 μs/line. The unexplained overhead would be 12.5 μs/line, or exactly 400 clock ticks. This one is worth fine-tuning, if you ask me.
Why?
- 720p24/30: 960 / 32 = 30 μs/line
- 720p25: 1000 / 32 = 31.25 μs/line
- FPS override: 872 / 32 = 27.25 μs/line
- theoretical value: (872 - 400) / 32 = 14.75 μs/line! (without altering OB areas)
For a 16:9 frame, which would be just 1428x804, it would require only 11.86 ms!
Assuming one can somehow drop 400 pixels from the left OB, that would free another 100 clock ticks, i.e. 11.63 μs/line, or 9.35 ms for a 16:9 LiveView frame.
Quote from: a1ex on November 26, 2018, 01:56:18 PM
Right, I've disabled a bunch of features to squeeze RAM, including FEATURE_SHOW_GUI_EVENTS.
Here's a test build for 1.0.6 with this feature enabled: https://builds.magiclantern.fm/jenkins/job/1100D.106-test/
What features where disable?
Good to know that there is still develop in this mod, thanks!
Alright fellas... Been wanting to get myself into this as I've finally borrowed one from work. Definitely feels like an interesting beast needless to say @a1ex!
Compiled from @Danne's branch (crop_rec_4k_mlv_snd_isogain_1x3_presets) and seems I got it to installed just fine (turned off cam and back on) then there goes this pattern of three long intermediate flashes with three additional long flashes 'n vice versa from the orange blinking LED just above the play button on this body.
LiveView does not appear anything. It's pitched black. Battery/Card pull gets you out of it. Any hints? Am I better off upgrading this to 1.0.6 from 1.0.5? :o
Surprising you got that far. The 1100D is a Digic 4 LV State camera and isn't supported in the crop_rec branches. Try the raw_video_10bit_12bit_LVState branch if you want bleeding edge on this camera.
hey there.
Latest night build is magiclantern-Nightly.2018Nov26.1100D106 ?
Why when try to update it, says that expects firmware 1.05?
What is it that you are looking for? If you click on that link a1ex gave you it points to a build that was done from my repository. Here's that link again:
https://builds.magiclantern.fm/jenkins/job/1100D.106-test/
What a1ex did was to delete the line that blocked SHOW_GUI_EVENTS.
Magic Lantern Nightly.2018Nov26.1100D106
Camera : 1100D
Firmware : 106
Changeset: 9025834982de+ (lua_fix_1100D.106) tip
Built on : 2018-11-26 12:56:02 by jenkins@nightly
diff -r 9025834982de platform/1100D.106/features.h
--- a/platform/1100D.106/features.h Fri May 04 17:38:44 2018 -0700
+++ b/platform/1100D.106/features.h Mon Nov 26 13:56:02 2018 +0100
@@ -23,6 +23,5 @@
// disabled, because autoexec.bin gets to big and 600D does not boot
#undef FEATURE_SHOW_TASKS
#undef FEATURE_SHOW_CPU_USAGE
-#undef FEATURE_SHOW_GUI_EVENTS
#undef FEATURE_SHOW_EDMAC_INFO
#undef FEATURE_FLEXINFO
Are you saying that this isn't working on 1.0.6? I guess I could update it with the latest lua_fix changes but unless you're testing the 1.0.6 port you should probably be using either the "stable" nightly build (https://builds.magiclantern.fm/1100D-105.html) or something from the experiments downloads page (https://builds.magiclantern.fm/experiments.html).
Hi,
So something strange has happened to my footage. For some reason some of the videos have been recorded without the sound, which I thought was going to be awkward to match up with my external sound recording but not the end of the world. Thing is though, when I load the footage into premiere with my two clips of seperately recorded external sound, and match everything up with the clap I make at the begining of each shot, the two sound files match up and the but the video quickly finds itself out of synch! Really don't understand what could have happened! I've tried fucking about with the audio and video and using other anchor points to match them up but they always end up out of synch again. Anyone got any ideas what's happened?
I was using my 1100D with whatever the latest version of ML was in february - april this year...
thanks
EDIT 3.35pm: I've just checked another bit of footage that was taken the same day with no change in the settings but this time the camera's own audio was recorded also but even that is out of synch with the video! I just don't understand how this is possible and if I can fix it.
hello, my problem is about 1100D Canon RAW feature, I installed the last experimental ML 10/12-bit RAW video version (2019 Mar 24). I expected something like that: https://www.youtube.com/watch?v=F_zLhgMvpOo
But everytime I record any video, it looks so bad like a super zoom. It doesn't matter if I choose different ratio or resolution the crop/zoom effect is still there. So did I install the wrong version or..?
Thank you for your time anyway.
Without details about settings, workflow any answer is right, wrong, irrelevant.
Quote from: Walter Schulz on November 24, 2019, 01:48:00 AM
Without details about settings, workflow any answer is right, wrong, irrelevant.
Hello, I'm using the 2:35:1 ratio, resolution: 1280x326, 14 bit. 25 fps, shutter speed 1/50, RAW.
I'm using the EFS 18-55mm III. When I select the 1280x326 resolution it also says "stretch by 1.67x to get the full 1280x544 resolution in post". When I convert the mlv files the video doesn't look squeezed as it should be. It's just a perfect look video in 1280x326, it's like a crop in 1280x326 more than a squeezed version of the 1280x544. That's why the video looks wrong when I stretch the height by 1.67x. I saw many tutorials online and their videos looked squeezed (vertically only) so they can apply the stretch by 1.67x in post, anyway my footage is just already perfect regarding the ratio but the resolution is totally wrong. I hope it makes sense, thank you for your time!
No workflow info for post. Try again.
Which modules in use?
Quote from: Walter Schulz on November 24, 2019, 01:53:07 PM
No workflow info for post. Try again.
I used
MLV app, default settings, no stretch applied, exported in Prores4444. Then I tried the
MLV Converter, default settings, exported in DNG. I use after effects but it doesn't matter because the problem is not in the comp settings, it's probably in some step before the post process in after effects. With these two Apps I get the same results: a perfect 1280x326 footage where there's no need to stretch the height. I don't undestand why. Thanks.
If I understand well, the 1100D operates in "720p" mode by default, but using a 3x3 pixel binning (with line skipping). All other models use 5x3 binning in this mode, so their videos need to be stretched, but this doesn't apply to 1100D. The generic code assumes 5x3 binning in 720p for all models, so it has to be added as an exception. It needs to be corrected here:
https://bitbucket.org/hudson/magic-lantern/src/d318f774b24ecc7d533ab79dd9418d097442fd81/src/raw.c#lines-905
PR welcome, but I may not be able to look into it until holidays.
Quote from: a1ex on November 24, 2019, 02:13:09 PM
If I understand well, the 1100D operates in "720p" mode by default, but using a 3x3 pixel binning (with line skipping). All other models use 5x3 binning in this mode, so their videos need to be stretched, but this doesn't apply to 1100D. The generic code assumes 5x3 binning in 720p for all models, so it has to be added as an exception. It needs to be corrected here:
https://bitbucket.org/hudson/magic-lantern/src/d318f774b24ecc7d533ab79dd9418d097442fd81/src/raw.c#lines-905
PR welcome, but I may not be able to look into it until holidays.
Yes the 1100D operates in 720p, but I didn't touch anything regarding binning or other settings, plus in many 1100D videos they didn't talk about pixel binning, they just wrote in description the same settings I wrote in the previous post. Thanks again!
And you did not touch the source code either, which was what I was talking about ;)
Quote from: a1ex on January 29, 2018, 11:03:50 AM
There is an experimental raw video build, but other than a few snapshots from Danne (https://www.magiclantern.fm/forum/index.php?topic=5601.msg194925#msg194925), I have no idea how it works in practice => please report back.
Apparently you were the first person trying to use raw video on 1100D :)
Why? If anyone else would have tried this before, they would have noticed this issue, as it's too obvious. Since they didn't... QED.
FYI, I don't have this camera, so I wasn't aware of the issue.
Quote from: a1ex on November 24, 2019, 02:28:05 PM
And you did not touch the source code either, which was what I was talking about ;)
Apparently you were the first person trying to use raw video on 1100D :)
Why? If anyone else would have tried this before, they would have noticed this issue, as it's too obvious. Since they didn't... QED.
FYI, I don't have this camera, so I wasn't aware of the issue.
Hello, thanks!
I just paste one of the links I found on YouTube:
Maybe they just crop the footage, I tried to avoid the problem in this way:
I want to get 2:66:1 ratio, 1280x481.
But I record in "16:9" with a 960x324. Then I make a new composition in after effects using the 1280x481 resolution and I just change the scale till the height fits the composition, obviously I cut the edges a bit, but since I'm using 2:66:1 instead of 2:35:1 it's not a big deal. Not sure if it's wrong but it works, and the ratio is correct.
Hey, I have a 1100D available to test whatever if whatever is needed. I'll try to see if RAW recording works later these holidays and update with results.
By the way, thanks for all the effort put in by the ML team, you guys are amazing ;)
Hello everyone,
I own a 1100D and have been using it as a beginner tool for the raw video workflow.
There are two main ways you can get it to record short clips or continuous raw video in the 16:9 -> 2.xx:1 aspect ratios.
The first one, my current way of using the camera, is to shoot in 4:3 and 1.2:1 aspect ratios then avoid stretching in post since you already have 2.22:1 and 2:1 videos. In this mode, you can use the ML live view overlay with all it's active features you selected from the menus ( histogram, waveform, focus peaking, zebras, etc ). This works only for composition. As soon as you press record, the overlay is gone untill the clip stops. I recommend using AF Live; this will allow you to back-button autofocus or zoom to focus, and not mess up the overlay when you exit zoom.
By not cropping and using this workaround, you can shoot:
3:2 - 2.49:1 actual a/r
4:3 - 2.22:1
1.2 - 2:1
1.175 - 1.95:1 ( new smartphone standard )
1:1 - 1.66:1 ( taller than 1.77:1 then corresponds to 16:9)
Here is what you can expect with a fast sd card ( Sandisk ExtremePro 95 Mb/s in my case )
25p
1.95:1 1408x720 10bit - 5 Sec 6 frames
1408x720 12bit - 3 Sec 4 frames
1408x720 14bit - 2 Sec
2:1 1408x704 10bit - 5 Sec 17 frames
1408x704 12bit - 3 Sec 6 frames
1408x704 14bit - 2 Sec 3 frames
2.22:1 1408x634 10bit - 8 Sec 7 frames
1408x634 12bit - 4 Sec 11 frames
1408x634 14bit - 3 Sec 2 frames
25p Continuous: 1248x562 10bit 2.22:1 ( I tested up to 12 min - 20.9 MB/s required )
24p
1.95:1 1408x720 10bit - 6 Sec 2 frames
1408x720 12bit - 3 Sec 13 frames
1408x720 14bit - 2 Sec 7 frames
2:1 1408x704 10bit - 6 Sec 8 frames
1408x704 12bit - 3 Sec 15 frames
1408x704 14bit - 2 Sec 8 frames
2.22:1 1408x634 10bit - 10 Sec 5 frames
1408x634 12bit - 5 Sec
1408x634 14bit - 3 Sec 9 frames
24p Continuous: 1280x576 10bit 2.22:1 ( untested - 21.0 MB/s required )
The second way to shoot the actual aspect ratio that you want, but the one that is not really reliable if you need to record clip after clip ( like a paid job ), goes something like this:
- set the autofocus to (-: AF ( not AF Live ) and the lens to AF - this is very important
- go into the settings and turn off 5x zoom from the zoom tweaks ( in my testing, 5x zoom results in artefacts on live view )
- select all your raw preferences ( bit depth, resolution, fps )
now, you should have a cropped live view image with that weird resolution ( lets say 1408x476 - the max 16:9 available ), but still retain overlays
- press display untill you get the ML overlay ( combo it with Av for the ML menu if it doesn't show up at first )
- while in live view and the ML overlay, press the zoom button once and the overlays should disappear, giving a clear full display ( you can only do your horizontal framing, since you miss out on the remaining vertical part of the frame covered by the black crop )
- press Av to go back to the ML menu, and you should see that it says 1408x792 or any full aspect ratio resolution that you have selected and you can start recording
This method is prone to fail after recording 1-2 clips, and you have to repeat the zoom-procedure to get back to full a/r recording, as the software switches back to the cropped resolution and overlays.
As a reference, you get about 7 seconds worth of video in 1280x720p 10bit 25p
Well, I hope I got everything right; I hope someone finds this useful and let me know if I can help with any other info regarding the 1100D. I ain't no expert, but I'll try to help.
Cheers
Hello all,
I recently decided to do some live streaming for a project. I have this old Rebel T3 that's been tucked away in a bag for years. I was wondering if there was any added benefit to using ML on it for my purposes? There seems to be a number of features it unlocks including RAW video capture but as I'll be indoors, with the camera using the HDMI output to a capture card, is there any value I would unlock using this firmware?
For starters: Unlimited streaming duration via HDMI if using lua_fix experimental build.
That alone is worth me giving it a shot.
I'll be playing with it later today. Thank you for the feedback!
QuoteQuote from: lane on September 03, 2020, 11:03:39 PM
That alone is worth me giving it a shot.
I'll be playing with it later today. Thank you for the feedback!
Lane, I was wondering if you had any luck? I'm in the same boat. Have a Rebel T3, hoping to use with EOS Webcam Utility but that 30 minute mirror timeout isn't going to let it happen. If ML's experimental build can make it possible, I'd love to find out!
And here we go again:
Top of page -> Downloads -> Downloads (dropdown menu) -> Experiments -> Latest Lua updates + fixes
After installing:
Prefs tab -> PowerSave in LiveView -> 30-minute timer Disabled
Hello. After installing magiclantern-Nightly.2018Jul03.1100D105 and searching through the user guide, forums, Google, and of course ML menu itself, I'm still at a loss whether it's possible to achieve the following (and if so, how) with 1100D:
1A. Record cropped video (1:1 sensor-video ratio, like the 640x480 crop mode in 550D, as opposed to recording with the whole sensor and then downsampling)
1B. (If the above is not possible) Record in 5x digital zoom Live View mode WITHOUT a computer connection. According to this article (https://www.astropix.com/html/i_astrop/eq_tests/canon_one_to_one_pixel_resolution.html), recording in 5x Live View mode is "close enough" for imaging planets (which is what I'm going for). I don't understand how "close to 1:1 sampling" is acceptable (I'd imagine it has to be exact) but I'd still like to try it. I know normally this is done with a computer connection, but it's not possible for me, so I wonder if with ML it's possible to record this way directly to the SD card.
2. Record RAW video
I apologize if it looks like I didn't RTFM or search, as it seems that all of this should be obvious, but I did look at the features comparison matrix (https://builds.magiclantern.fm/features.html) and the current raw recording modules (https://www.magiclantern.fm/forum/index.php?topic=22820.0) topic and it doesn't seem like any of these functions are available for this camera model (I certainly don't see any of the relevant modules in the ML menu). Should I download the Lua build? It's newer but seems to contain fixes, not extra features.
I'd appreciate any help, thank you in advance.
Regards,
Andrew
Edit: OK, I installed the Lua build, tried MLV_Lite and MLV_Rec. It seems that they do crop the video, but also squeeze it. Since crop_rec is unavailable for my camera, apparently it's impossible to achieve what I want, although hopefully someone can prove me wrong...
Back again (only 2 years late lol)
1100D with magiclantern-Nightly.2018Nov26.1100D106.zip from https://builds.magiclantern.fm/jenkins/job/1100D.106-test/2/
Output of LUATEST.LOG:
===============================================================================
ML/SCRIPTS/API_TEST.LUA - 2020-12-22 15:39:55
===============================================================================
Strict mode tests...
Strict mode tests passed.
Generic tests...
arg = table:
[0] = "API_TEST.LUA"
camera = table:
shutter = table:
raw = 0
apex = -7.
ms = 0
value = 0
aperture = table:
raw = 43
apex = 4.375
value = 4.5
min = table:
raw = 43
apex = 4.375
value = 4.5
max = table:
raw = 90
apex = 10.250001
value = 34.799999
iso = table:
raw = 0
apex = 0
value = 0
ec = table:
raw = 0
value = 0
flash = true
flash_ec = table:
raw = 0
value = 0
kelvin = 6500
mode = 2
metering_mode = 3
drive_mode = 0
model = "Canon EOS REBEL T3"
model_short = "1100D"
firmware = "1.0.6"
temperature = 156
gui = table:
menu = false
play = false
play_photo = false
play_movie = false
qr = false
idle = true
shoot = function: p
reboot = function: p
wait = function: p
bulb = function: p
burst = function: p
event = table:
pre_shoot = nil
post_shoot = nil
shoot_task = nil
seconds_clock = nil
keypress = nil
custom_picture_taking = nil
intervalometer = nil
config_save = nil
console = table:
hide = function: p
show = function: p
write = function: p
clear = function: p
lv = table:
enabled = false
paused = false
running = false
zoom = 1
overlays = false
pause = function: p
info = function: p
resume = function: p
wait = function: p
stop = function: p
start = function: p
lens = table:
name = "EF75-300mm f/4-5.6"
focal_length = 135
focus_distance = 0
hyperfocal = 213427
dof_near = -563463912
dof_far = 1000000
af = true
af_mode = 0
focus = function: p
autofocus = function: p
display = table:
idle = nil
height = 480
width = 720
rect = function: p
notify_box = function: p
on = function: p
draw = function: p
screenshot = function: p
line = function: p
load = function: p
print = function: p
off = function: p
clear = function: p
pixel = function: p
circle = function: p
key = table:
last = 10
press = function: p
wait = function: p
menu = table:
visible = false
block = function: p
open = function: p
get = function: p
new = function: p
select = function: p
close = function: p
set = function: p
movie = table:
recording = false
stop = function: p
start = function: p
dryos = table:
clock = 8
ms_clock = 8253
image_prefix = "IMG_"
dcim_dir = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = nil
path = "B:/"
path = "B:/DCIM/"
path = "B:/DCIM/100CANON/"
config_dir = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = nil
path = "B:/"
path = "ML/"
path = "ML/SETTINGS/"
ml_card = table:
cluster_size = 32768
drive_letter = "B"
file_number = 9857
folder_number = 100
free_space = 15438176
type = "SD"
_card_ptr = userdata
path = "B:/"
shooting_card = table:
cluster_size = 32768
drive_letter = "B"
file_number = 9857
folder_number = 100
free_space = 15438176
type = "SD"
_card_ptr = userdata
path = "B:/"
date = table:
year = 2020
sec = 57
wday = 6
hour = 15
month = 12
isdst = false
day = 22
yday = 1
min = 39
rename = function: p
directory = function: p
call = function: p
remove = function: p
interval = table:
time = 10
count = 0
running = false
stop = function: p
battery = table:
function not available on this camera
stack traceback:
[C]: in ?
[C]: in for iterator 'for iterator'
ML/SCRIPTS/LIB/logger.lua:125: in function 'logger.serialize'
ML/SCRIPTS/API_TEST.LUA:36: in function <ML/SCRIPTS/API_TEST.LUA:35>
[C]: in function 'globals.xpcall'
ML/SCRIPTS/API_TEST.LUA:35: in function 'globals.print_table'
ML/SCRIPTS/API_TEST.LUA:81: in function 'globals.generic_tests'
ML/SCRIPTS/API_TEST.LUA:1338: in function 'globals.api_tests'
ML/SCRIPTS/API_TEST.LUA:1364: in main chunktask = table:
create = function: p
yield = function: p
property = table:
Generic tests completed.
Module tests...
Testing file I/O...
Copy test: autoexec.bin -> tmp.bin
Copy test OK
Append test: tmp.txt
Append test OK
Rename test: apple.txt -> banana.txt
Rename test OK
Rename test: apple.txt -> ML/banana.txt
Rename test OK
File I/O tests completed.
Testing Canon GUI functions...
It's not showing here but there was a LUA error output to the screen.
(https://i.imgur.com/5cm6hIm.png)
Output from STUBTEST.LOG:
[Pass] is_play_mode() => 0x1
[INFO] Camera model: Canon EOS REBEL T3 1.0.6 (0x80000288 1100D)
[Pass] is_camera("DIGIC", "*") => 0x1
[Pass] is_camera(__camera_model_short, firmware_version) => 0x1
[Pass] src = fio_malloc(size) => 0x44600084
[Pass] dst = fio_malloc(size) => 0x44e04094
[Pass] memcmp(dst, src, 4097) => 0xffffff99
[Pass] edmac_memcpy(dst, src, 4097) => 0x44e04094
[Pass] memcmp(dst, src, 4097) => 0x0
[Pass] edmac_memcpy(dst, src, 4097) => 0x44e04094
[Pass] memcmp(dst, src, size) => 0xffffffcf
[Pass] edmac_memcpy(dst, src, size) => 0x44e04094
[Pass] memcmp(dst, src, size) => 0x0
[Pass] memcmp(dst, src, size) => 0xffffffdc
[Pass] edmac_memcpy_start(dst, src, size) => 0x44e04094
dt => 0x34fd
[Pass] copied => 0x400f6c
[Pass] copied => 0x400f6c
[Pass] copied => 0x400f6c
[Pass] memcmp(dst, src, copied) => 0x0
[Pass] memcmp(dst, src, copied + 16) => 0xc7
edmac_memcpy_finish()
free(src)
free(dst)
Cache test A (EDMAC on BMP buffer)...
[Pass] bmp = bmp_load("ML/CROPMKS/CINESCO2.BMP", 1) => 0xa7f3d8
[Pass] old => 0x0
[Pass] irq => 0xc0
[Pass] differences => 0x960
[Pass] old => 0x0
[Pass] irq => 0xc0
[Pass] differences => 0x0
Cache test B (FIO on 8K buffer)...
[Pass] tries[0] => 0xef
[Pass] tries[1] => 0x105
[Pass] tries[2] => 0xff
[Pass] tries[3] => 0xf5
[Pass] failr[0] => 0x87
[Pass] failw[0] => 0xc6
[Pass] failr[1] => 0x9d
[Pass] failw[1] => 0x0
[Pass] failr[2] => 0x0
[Pass] failw[2] => 0xd9
[Pass] failr[3] => 0x0
[Pass] failw[3] => 0x0
times[0] / tries[0] => 0x41
times[1] / tries[1] => 0x3c
times[2] / tries[2] => 0x32
times[3] / tries[3] => 0x3c
Cache tests finished.
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x1
[Pass] lv_focus_status => 0x3
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x1
[Pass] lv_focus_status => 0x3
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x1
[Pass] lv_focus_status => 0x3
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x1
[Pass] lv_focus_status => 0x3
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x1
[Pass] lv_focus_status => 0x3
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[FAIL] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[FAIL] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[FAIL] HALFSHUTTER_PRESSED => 0x0
[FAIL] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[FAIL] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x1
The camera crashed shortly after this and I needed to pull the battery. I captured a photo of the screen at this point.
(https://i.imgur.com/SqGFOGR.jpg)
Output from bench.mo:
(https://i.imgur.com/V7Zaq1f.png)
Output from SHOW_GUI_EVENTS + hitting Q once or twice
(https://i.imgur.com/gE8hNjq.png)
Please let me know if you'd like to see anything else!
Info about lens used would be helpful, I suppose.
Would be nice if you can also try the Lua build from https://builds.magiclantern.fm/experiments.html - same tests.
Long answer here (https://www.magiclantern.fm/forum/index.php?topic=14828.msg194706#msg194706).
Quote from: Walter Schulz on December 22, 2020, 09:21:24 PM
Info about lens used would be helpful, I suppose.
Canon 75-300mm (https://en.wikipedia.org/wiki/Canon_EF_75%E2%80%93300mm_lens) (no USM, no IS).
Quote from: a1ex on December 22, 2020, 09:32:26 PM
Would be nice if you can also try the Lua build from https://builds.magiclantern.fm/experiments.html - same tests.
Long answer here (https://www.magiclantern.fm/forum/index.php?topic=14828.msg194706#msg194706).
Ok, I'll give it a shot in a bit. (Also will put the 18-55 kit on, and point it at something it can actually focus on :P)
EDIT: oh wait I have a 1.0.6, not 1.0.5
I'm afraid both lenses won't be able to provide distance info thus crashing at this point couldn't be prevented. a1ex?
Focus distance is only printed, not used in any of the "decision" code.
1.0.5 available here: https://builds.magiclantern.fm/1100D-105.html
Quote from: a1ex on December 22, 2020, 10:17:52 PM
Focus distance is only printed, not used in any of the "decision" code.
1.0.5 available here: https://builds.magiclantern.fm/1100D-105.html
I mean my camera is already at (official) 1.0.6. I guess I could downgrade. Are there instructions or is it just like a regular FW flash?
Quote from: a1ex on December 22, 2020, 09:32:26 PM
Would be nice if you can also try the Lua build from https://builds.magiclantern.fm/experiments.html - same tests.
Long answer here (https://www.magiclantern.fm/forum/index.php?topic=14828.msg194706#msg194706).
Formatted card and removed ML, downgraded to 1.0.5, installed ML test from that experimental link. Attached 18-55mm kit lens.
Lua self-test results:
===============================================================================
ML/SCRIPTS/API_TEST.LUA - 2020-12-22 20:16:53
===============================================================================
Strict mode tests...
Strict mode tests passed.
Generic tests...
arg = table:
[0] = "API_TEST.LUA"
camera = table:
shutter = table:
raw = 0
apex = -7.
ms = 0
value = 0
aperture = table:
raw = 40
apex = 4.
value = 4.
min = table:
raw = 40
apex = 4.
value = 4.
max = table:
raw = 83
apex = 9.375
value = 25.7
iso = table:
raw = 0
apex = 0
value = 0
ec = table:
raw = 0
value = 0
flash = true
flash_ec = table:
raw = 0
value = 0
kelvin = 6500
mode = 2
metering_mode = 3
drive_mode = 0
model = "Canon EOS REBEL T3"
model_short = "1100D"
firmware = "1.0.5"
temperature = 156
gui = table:
menu = false
play = false
play_photo = false
play_movie = false
qr = false
idle = true
wait = function: 0x5f34280
burst = function: 0x5f35608
bulb = function: 0x5f35588
reboot = function: 0x5f35328
shoot = function: 0x5f35354
event = table:
pre_shoot = nil
post_shoot = nil
shoot_task = nil
seconds_clock = nil
keypress = nil
custom_picture_taking = nil
intervalometer = nil
config_save = nil
console = table:
show = function: 0x5f32c14
write = function: 0x5f32ca8
hide = function: 0x5f32c04
clear = function: 0x5f32bf4
lv = table:
enabled = false
paused = false
running = false
zoom = 1
overlays = false
wait = function: 0x5f361f8
resume = function: 0x5f35e28
info = function: 0x5f35b34
start = function: 0x5f35790
stop = function: 0x5f357a0
pause = function: 0x5f35e38
lens = table:
name = "EF-S18-55mm f/3.5-5.6 IS II"
focal_length = 24
focus_distance = 1130
hyperfocal = 7626
dof_near = 994
dof_far = 1310
af = true
af_mode = 0
focus = function: 0x5f36ea4
autofocus = function: 0x5f36cdc
display = table:
idle = nil
height = 480
width = 720
off = function: 0x5f37720
print = function: 0x5f38b50
draw = function: 0x5f378cc
load = function: 0x5f37a14
circle = function: 0x5f38088
pixel = function: 0x5f38984
line = function: 0x5f386bc
rect = function: 0x5f38358
on = function: 0x5f37730
screenshot = function: 0x5f3764c
notify_box = function: 0x5f377e4
clear = function: 0x5f3763c
key = table:
last = 10
press = function: 0x5f39328
wait = function: 0x5f39060
menu = table:
visible = false
block = function: 0x5f39890
open = function: 0x5f396a0
set = function: 0x5f3a914
new = function: 0x5f3b750
close = function: 0x5f39688
select = function: 0x5f3a840
get = function: 0x5f3aaf4
movie = table:
recording = false
start = function: 0x5f37338
stop = function: 0x5f372a4
dryos = table:
clock = 45
ms_clock = 45075
image_prefix = "IMG_"
config_dir = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = nil
path = "B:/"
path = "ML/"
path = "ML/SETTINGS/"
ml_card = table:
drive_letter = "B"
dcim_dir = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = nil
path = "B:/"
path = "B:/DCIM/"
path = "B:/DCIM/100CANON/"
file_number = 9857
folder_number = 100
free_space = 15336
image_path = function: 0x5f3cc50
type = "SD"
_card_ptr = userdata
path = "B:/"
shooting_card = table:
drive_letter = "B"
dcim_dir = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = nil
path = "B:/"
path = "B:/DCIM/"
path = "B:/DCIM/100CANON/"
file_number = 9857
folder_number = 100
free_space = 15336
image_path = function: 0x5f3cc50
type = "SD"
_card_ptr = userdata
path = "B:/"
cf_card = nil
sd_card = table:
drive_letter = "B"
dcim_dir = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = nil
path = "B:/"
path = "B:/DCIM/"
path = "B:/DCIM/100CANON/"
file_number = 9857
folder_number = 100
free_space = 15336
image_path = function: 0x5f3cc50
type = "SD"
_card_ptr = userdata
path = "B:/"
date = table:
month = 12
sec = 55
min = 16
yday = 1
isdst = false
wday = 6
year = 2020
day = 22
hour = 20
directory = function: 0x5f3c340
rename = function: 0x5f3c200
remove = function: 0x5f3c2d4
call = function: 0x5f3bffc
interval = table:
time = 10
count = 0
running = false
stop = function: 0x5f3d690
battery = table:
function not available on this camera
stack traceback:
[C]: in ?
[C]: in for iterator 'for iterator'
ML/SCRIPTS/LIB/logger.lua:125: in function 'logger.serialize'
ML/SCRIPTS/API_TEST.LUA:45: in function <ML/SCRIPTS/API_TEST.LUA:44>
[C]: in function 'xpcall'
ML/SCRIPTS/API_TEST.LUA:44: in function 'print_table'
ML/SCRIPTS/API_TEST.LUA:90: in function 'generic_tests'
ML/SCRIPTS/API_TEST.LUA:1568: in function <ML/SCRIPTS/API_TEST.LUA:1564>
[C]: in function 'xpcall'
ML/SCRIPTS/API_TEST.LUA:1564: in function 'api_tests'
ML/SCRIPTS/API_TEST.LUA:1603: in main chunktask = table:
yield = function: 0x5f3dcf8
create = function: 0x5f3de78
property = table:
Generic tests completed.
Module tests...
Testing file I/O...
Copy test: autoexec.bin -> tmp.bin
Copy test OK
Append test: tmp.txt
Append test OK
Rename test: apple.txt -> banana.txt
Rename test OK
Rename test: apple.txt -> ML/banana.txt
Rename test OK
SD card (B:/) present
- free space: 15336 MiB
- next image: B:/DCIM/100CANON/IMG_9858.JPG
- DCIM dir. : B:/DCIM/100CANON/
- B:/DCIM/
- B:/DCIM/100CANON/
- B:/DCIM/EOSMISC/
- B:/MISC/
- B:/ML/
- B:/ML/CROPMKS/
- B:/ML/CROPMKS/CINESCO2.BMP
- B:/ML/CROPMKS/_CINES~1.BMP
- B:/ML/CROPMKS/CRSSMTR2.BMP
- B:/ML/CROPMKS/_CRSSM~1.BMP
- B:/ML/CROPMKS/PASSPORT.BMP
- B:/ML/CROPMKS/_PASSP~1.BMP
- B:/ML/CROPMKS/PHIPHOTO.BMP
- B:/ML/CROPMKS/_PHIPH~1.BMP
- B:/ML/CROPMKS/PHIVIDEO.BMP
- B:/ML/CROPMKS/_PHIVI~1.BMP
- B:/ML/DATA/
- B:/ML/DATA/APSC8P.LUT
- B:/ML/DATA/_APSC8~1.LUT
- B:/ML/DATA/APSC8R.LUT
- B:/ML/DATA/_APSC8~2.LUT
- B:/ML/DATA/FF8P.LUT
- B:/ML/DATA/_FF8~1.LUT
- B:/ML/DATA/FF8R.LUT
- B:/ML/DATA/_FF8~~2.LUT
- B:/ML/DOC/
- B:/ML/FONTS/
- B:/ML/FONTS/ARGHLF22.RBF
- B:/ML/FONTS/_ARGHL~1.RBF
- B:/ML/FONTS/ARGNOR23.RBF
- B:/ML/FONTS/_ARGNO~1.RBF
- B:/ML/FONTS/ARGNOR28.RBF
- B:/ML/FONTS/_ARGNO~2.RBF
- B:/ML/FONTS/ARGNOR32.RBF
- B:/ML/FONTS/_ARGNO~3.RBF
- B:/ML/FONTS/TERM12.RBF
- B:/ML/FONTS/_TERM1~1.RBF
- B:/ML/FONTS/TERM20.RBF
- B:/ML/FONTS/_TERM2~1.RBF
- B:/ML/MODULES/
- B:/ML/MODULES/ADV_INT.MO
- B:/ML/MODULES/_ADV_I~1.MO
- B:/ML/MODULES/ARKANOID.MO
- B:/ML/MODULES/_ARKAN~1.MO
- B:/ML/MODULES/AUTOEXPO.MO
- B:/ML/MODULES/_AUTOE~1.MO
- B:/ML/MODULES/BENCH.MO
- B:/ML/MODULES/_BENC~1.MO
- B:/ML/MODULES/DEFLICK.MO
- B:/ML/MODULES/_DEFLI~1.MO
- B:/ML/MODULES/DUAL_ISO.MO
- B:/ML/MODULES/_DUAL_~1.MO
- B:/ML/MODULES/EDMAC.MO
- B:/ML/MODULES/_EDMA~1.MO
- B:/ML/MODULES/ETTR.MO
- B:/ML/MODULES/_ETT~1.MO
- B:/ML/MODULES/FILE_MAN.MO
- B:/ML/MODULES/_FILE_~1.MO
- B:/ML/MODULES/IMG_NAME.MO
- B:/ML/MODULES/_IMG_N~1.MO
- B:/ML/MODULES/LUA.MO
- B:/ML/MODULES/_LU~1.MO
- B:/ML/MODULES/MLV_LITE.MO
- B:/ML/MODULES/_MLV_L~1.MO
- B:/ML/MODULES/MLV_PLAY.MO
- B:/ML/MODULES/_MLV_P~1.MO
- B:/ML/MODULES/MLV_REC.MO
- B:/ML/MODULES/_MLV_R~1.MO
- B:/ML/MODULES/MLV_SND.MO
- B:/ML/MODULES/_MLV_S~1.MO
- B:/ML/MODULES/PIC_VIEW.MO
- B:/ML/MODULES/_PIC_V~1.MO
- B:/ML/MODULES/SELFTEST.MO
- B:/ML/MODULES/_SELFT~1.MO
- B:/ML/MODULES/SILENT.MO
- B:/ML/MODULES/_SILEN~1.MO
- B:/ML/MODULES/T3_105.SYM
- B:/ML/MODULES/_T3_10~1.SYM
- B:/ML/MODULES/LOADING.LCK
- B:/ML/SCRIPTS/
- B:/ML/SCRIPTS/LIB/
- B:/ML/SCRIPTS/LIB/CONFIG.LUA
- B:/ML/SCRIPTS/LIB/_CONFI~1.LUA
- B:/ML/SCRIPTS/LIB/KEYS.LUA
- B:/ML/SCRIPTS/LIB/_KEY~1.LUA
- B:/ML/SCRIPTS/LIB/LOGGER.LUA
- B:/ML/SCRIPTS/LIB/_LOGGE~1.LUA
- B:/ML/SCRIPTS/LIB/STRICT.LUA
- B:/ML/SCRIPTS/LIB/_STRIC~1.LUA
- B:/ML/SCRIPTS/API_TEST.LUA
- B:/ML/SCRIPTS/_API_T~1.LUA
- B:/ML/SCRIPTS/CALC.LUA
- B:/ML/SCRIPTS/_CAL~1.LUA
- B:/ML/SCRIPTS/COPY2M.LUA
- B:/ML/SCRIPTS/_COPY2~1.LUA
- B:/ML/SCRIPTS/EDITOR.LUA
- B:/ML/SCRIPTS/_EDITO~1.LUA
- B:/ML/SCRIPTS/HELLO.LUA
- B:/ML/SCRIPTS/_HELL~1.LUA
- B:/ML/SCRIPTS/_LI~1
- B:/ML/SCRIPTS/MENUTEST.LUA
- B:/ML/SCRIPTS/_MENUT~1.LUA
- B:/ML/SCRIPTS/PONG.LUA
- B:/ML/SCRIPTS/_PON~1.LUA
- B:/ML/SCRIPTS/RECDELAY.LUA
- B:/ML/SCRIPTS/_RECDE~1.LUA
- B:/ML/SCRIPTS/SCRNSHOT.LUA
- B:/ML/SCRIPTS/_SCRNS~1.LUA
- B:/ML/SCRIPTS/SOKOBAN.LUA
- B:/ML/SCRIPTS/_SOKOB~1.LUA
- B:/ML/SCRIPTS/UNLOAD.LUA
- B:/ML/SCRIPTS/_UNLOA~1.LUA
- B:/ML/LOGS/
- B:/ML/LOGS/ROM0.BIN
- B:/ML/LOGS/ROM1.BIN
- B:/ML/LOGS/LUATEST.LOG
- B:/ML/SETTINGS/
- B:/ML/SETTINGS/LUA.EN
- B:/ML/SETTINGS/MAGIC.CFG
- B:/ML/SETTINGS/MENUS.CFG
- B:/ML/_CROPM~1
- B:/ML/_DAT~1
- B:/ML/_DO~1
- B:/ML/DOCS
- B:/ML/_DOC~1
- B:/ML/_FONT~1
- B:/ML/_MODUL~1
- B:/ML/README
- B:/ML/_READM~1
- B:/ML/_SCRIP~1
- B:/TRASHE~1/
- B:/TEMPOR~1/
- B:/TEMPOR~1/FOLDERS.501/
- B:/TEMPOR~1/FOLDERS.501/TEMPOR~1/
- B:/TEMPOR~1/FOLDERS.501/_TEMPO~1
- B:/TEMPOR~1/_FOLDE~1.501
- B:/AUTOEXEC.BIN
- B:/~1.TRA
- B:/~1.TEM
- B:/APDIS~1
- B:/~1.APD
- B:/_AUTOE~1.BIN
- B:/ML-SETUP.FIR
- B:/_ML-SE~1.FIR
- B:/_M~1
File I/O tests completed.
Testing Canon GUI functions...
ML/SCRIPTS/API_TEST.LUA:289: assertion failed!
stack traceback:
[C]: in function 'assert'
ML/SCRIPTS/API_TEST.LUA:289: in function 'test_camera_gui'
ML/SCRIPTS/API_TEST.LUA:1572: in function <ML/SCRIPTS/API_TEST.LUA:1564>
[C]: in function 'xpcall'
ML/SCRIPTS/API_TEST.LUA:1564: in function 'api_tests'
ML/SCRIPTS/API_TEST.LUA:1603: in main chunkOnce again the test crashes, just after switching to Image Review mode and/or trying an autofocus test. Actually it goes to a black screen and doesn't return until I take some action (like take a photo).
(https://i.imgur.com/r45n9pI.png)
looking at the script I think the half-press is supposed to take it out of play mode (it does) but put it in another, maybe shooting mode (which is, maybe, not camera.gui.mode == 0 on this one). I added a printf and it remains that camera.gui.mode==1 after half-press.
Also, even after unpress_half_shutter (looking at the main Shoot params screen), camera.gui.mode is still 1. No idea how that value is getting set but it obviously is not being re-set back to 0 after leaving Play mode. If it ever WAS zero :)
More tests. This time I commented out line 289 (gui.mode == 0). Camera proceeds through the random GUI tests, menu tests, shooting test, and then dies in the half-shutter button test.
===============================================================================
ML/SCRIPTS/API_TEST.LUA - 2020-12-22 23:35:30
===============================================================================
Strict mode tests...
Strict mode tests passed.
Generic tests...
arg = table:
[0] = "API_TEST.LUA"
camera = table:
shutter = table:
raw = 0
apex = -7.
ms = 0
value = 0
aperture = table:
raw = 48
apex = 5.
value = 5.6
min = table:
raw = 40
apex = 4.
value = 4.
max = table:
raw = 83
apex = 9.375
value = 25.7
iso = table:
raw = 0
apex = 0
value = 0
ec = table:
raw = 0
value = 0
flash = true
flash_ec = table:
raw = 0
value = 0
kelvin = 5200
mode = 2
metering_mode = 3
drive_mode = 0
model = "Canon EOS REBEL T3"
model_short = "1100D"
firmware = "1.0.5"
temperature = 145
gui = table:
menu = false
play = false
play_photo = false
play_movie = false
qr = false
idle = true
wait = function: 0x5f34280
burst = function: 0x5f35608
bulb = function: 0x5f35588
reboot = function: 0x5f35328
shoot = function: 0x5f35354
event = table:
pre_shoot = nil
post_shoot = nil
shoot_task = nil
seconds_clock = nil
keypress = nil
custom_picture_taking = nil
intervalometer = nil
config_save = nil
console = table:
show = function: 0x5f32c14
write = function: 0x5f32ca8
hide = function: 0x5f32c04
clear = function: 0x5f32bf4
lv = table:
enabled = false
paused = false
running = false
zoom = 1
overlays = false
wait = function: 0x5f361f8
resume = function: 0x5f35e28
info = function: 0x5f35b34
start = function: 0x5f35790
stop = function: 0x5f357a0
pause = function: 0x5f35e38
lens = table:
name = "EF-S18-55mm f/3.5-5.6 IS II"
focal_length = 25
focus_distance = 580
hyperfocal = 5924
dof_near = 536
dof_far = 632
af = true
af_mode = 0
focus = function: 0x5f36ea4
autofocus = function: 0x5f36cdc
display = table:
idle = nil
height = 480
width = 720
off = function: 0x5f37720
print = function: 0x5f38b50
draw = function: 0x5f378cc
load = function: 0x5f37a14
circle = function: 0x5f38088
pixel = function: 0x5f38984
line = function: 0x5f386bc
rect = function: 0x5f38358
on = function: 0x5f37730
screenshot = function: 0x5f3764c
notify_box = function: 0x5f377e4
clear = function: 0x5f3763c
key = table:
last = 10
press = function: 0x5f39328
wait = function: 0x5f39060
menu = table:
visible = false
block = function: 0x5f39890
open = function: 0x5f396a0
set = function: 0x5f3a914
new = function: 0x5f3b750
close = function: 0x5f39688
select = function: 0x5f3a840
get = function: 0x5f3aaf4
movie = table:
recording = false
start = function: 0x5f37338
stop = function: 0x5f372a4
dryos = table:
clock = 5
ms_clock = 5617
image_prefix = "IMG_"
config_dir = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = nil
path = "B:/"
path = "ML/"
path = "ML/SETTINGS/"
ml_card = table:
drive_letter = "B"
dcim_dir = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = nil
path = "B:/"
path = "B:/DCIM/"
path = "B:/DCIM/100CANON/"
file_number = 9858
folder_number = 100
free_space = 15334
image_path = function: 0x5f3cc50
type = "SD"
_card_ptr = userdata
path = "B:/"
shooting_card = table:
drive_letter = "B"
dcim_dir = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = nil
path = "B:/"
path = "B:/DCIM/"
path = "B:/DCIM/100CANON/"
file_number = 9858
folder_number = 100
free_space = 15334
image_path = function: 0x5f3cc50
type = "SD"
_card_ptr = userdata
path = "B:/"
cf_card = nil
sd_card = table:
drive_letter = "B"
dcim_dir = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = nil
path = "B:/"
path = "B:/DCIM/"
path = "B:/DCIM/100CANON/"
file_number = 9858
folder_number = 100
free_space = 15334
image_path = function: 0x5f3cc50
type = "SD"
_card_ptr = userdata
path = "B:/"
date = table:
month = 12
sec = 31
min = 35
yday = 1
isdst = false
wday = 6
year = 2020
day = 22
hour = 23
directory = function: 0x5f3c340
rename = function: 0x5f3c200
remove = function: 0x5f3c2d4
call = function: 0x5f3bffc
interval = table:
time = 10
count = 0
running = false
stop = function: 0x5f3d690
battery = table:
function not available on this camera
stack traceback:
[C]: in ?
[C]: in for iterator 'for iterator'
ML/SCRIPTS/LIB/logger.lua:125: in function 'logger.serialize'
ML/SCRIPTS/API_TEST.LUA:45: in function <ML/SCRIPTS/API_TEST.LUA:44>
[C]: in function 'xpcall'
ML/SCRIPTS/API_TEST.LUA:44: in function 'print_table'
ML/SCRIPTS/API_TEST.LUA:90: in function 'generic_tests'
ML/SCRIPTS/API_TEST.LUA:1568: in function <ML/SCRIPTS/API_TEST.LUA:1564>
[C]: in function 'xpcall'
ML/SCRIPTS/API_TEST.LUA:1564: in function 'api_tests'
ML/SCRIPTS/API_TEST.LUA:1603: in main chunktask = table:
yield = function: 0x5f3dcf8
create = function: 0x5f3de78
property = table:
Generic tests completed.
Module tests...
Testing file I/O...
Copy test: autoexec.bin -> tmp.bin
Copy test OK
Append test: tmp.txt
Append test OK
Rename test: apple.txt -> banana.txt
Rename test OK
Rename test: apple.txt -> ML/banana.txt
Rename test OK
SD card (B:/) present
- free space: 15334 MiB
- next image: B:/DCIM/100CANON/IMG_9859.JPG
- DCIM dir. : B:/DCIM/100CANON/
- B:/DCIM/100CANON/IMG_9858.JPG
- B:/DCIM/
- B:/DCIM/100CANON/
- B:/DCIM/100CANON/IMG_9858.JPG
- B:/DCIM/EOSMISC/
- B:/DCIM/EOSMISC/M0100.CTG
- B:/MISC/
- B:/TRASHE~1/
- B:/ML/
- B:/ML/CROPMKS/
- B:/ML/CROPMKS/CINESCO2.BMP
- B:/ML/CROPMKS/CRSSMTR2.BMP
- B:/ML/CROPMKS/PASSPORT.BMP
- B:/ML/CROPMKS/PHIPHOTO.BMP
- B:/ML/CROPMKS/PHIVIDEO.BMP
- B:/ML/DATA/
- B:/ML/DATA/APSC8P.LUT
- B:/ML/DATA/APSC8R.LUT
- B:/ML/DATA/FF8P.LUT
- B:/ML/DATA/FF8R.LUT
- B:/ML/DOC/
- B:/ML/FONTS/
- B:/ML/FONTS/ARGHLF22.RBF
- B:/ML/FONTS/ARGNOR23.RBF
- B:/ML/FONTS/ARGNOR28.RBF
- B:/ML/FONTS/ARGNOR32.RBF
- B:/ML/FONTS/TERM12.RBF
- B:/ML/FONTS/TERM20.RBF
- B:/ML/MODULES/
- B:/ML/MODULES/ADV_INT.MO
- B:/ML/MODULES/ARKANOID.MO
- B:/ML/MODULES/AUTOEXPO.MO
- B:/ML/MODULES/BENCH.MO
- B:/ML/MODULES/DEFLICK.MO
- B:/ML/MODULES/DUAL_ISO.MO
- B:/ML/MODULES/EDMAC.MO
- B:/ML/MODULES/ETTR.MO
- B:/ML/MODULES/FILE_MAN.MO
- B:/ML/MODULES/IMG_NAME.MO
- B:/ML/MODULES/LUA.MO
- B:/ML/MODULES/MLV_LITE.MO
- B:/ML/MODULES/MLV_PLAY.MO
- B:/ML/MODULES/MLV_REC.MO
- B:/ML/MODULES/MLV_SND.MO
- B:/ML/MODULES/PIC_VIEW.MO
- B:/ML/MODULES/SELFTEST.MO
- B:/ML/MODULES/SILENT.MO
- B:/ML/MODULES/T3_105.SYM
- B:/ML/MODULES/LOADING.LCK
- B:/ML/SCRIPTS/
- B:/ML/SCRIPTS/LIB/
- B:/ML/SCRIPTS/LIB/CONFIG.LUA
- B:/ML/SCRIPTS/LIB/KEYS.LUA
- B:/ML/SCRIPTS/LIB/LOGGER.LUA
- B:/ML/SCRIPTS/LIB/STRICT.LUA
- B:/ML/SCRIPTS/API_TEST.LUA
- B:/ML/SCRIPTS/CALC.LUA
- B:/ML/SCRIPTS/COPY2M.LUA
- B:/ML/SCRIPTS/EDITOR.LUA
- B:/ML/SCRIPTS/HELLO.LUA
- B:/ML/SCRIPTS/MENUTEST.LUA
- B:/ML/SCRIPTS/PONG.LUA
- B:/ML/SCRIPTS/RECDELAY.LUA
- B:/ML/SCRIPTS/SCRNSHOT.LUA
- B:/ML/SCRIPTS/SOKOBAN.LUA
- B:/ML/SCRIPTS/UNLOAD.LUA
- B:/ML/LOGS/
- B:/ML/LOGS/ROM0.BIN
- B:/ML/LOGS/ROM1.BIN
- B:/ML/LOGS/LUATEST.LOG
- B:/ML/SETTINGS/
- B:/ML/SETTINGS/LUA.EN
- B:/ML/SETTINGS/MAGIC.CFG
- B:/ML/SETTINGS/MENUS.CFG
- B:/ML/DOCS
- B:/ML/README
- B:/FSEVEN~1/
- B:/FSEVEN~1/000000~1
- B:/FSEVEN~1/000000~2
- B:/TEMPOR~1/
- B:/TEMPOR~1/FOLDERS.501/
- B:/TEMPOR~1/FOLDERS.501/TEMPOR~1/
- B:/TEMPOR~1/FOLDERS.501/_TEMPO~1
- B:/TEMPOR~1/_FOLDE~1.501
- B:/AUTOEXEC.BIN
- B:/~1.TRA
- B:/~1.TEM
- B:/APDIS~1
- B:/~1.APD
File I/O tests completed.
Testing Canon GUI functions...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Start LiveView...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Enter MENU mode...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Resume LiveView...
Pause LiveView...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Resume LiveView...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Stop LiveView...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Start LiveView...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Resume LiveView...
Pause LiveView...
Enter PLAY mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Canon GUI tests completed.
Testing ML menu API...
Menu tests completed.
Testing picture taking functions...
Please switch to M mode.
Snap simulation test...
Single picture...
B:/DCIM/100CANON/IMG_9859.CR2 not found.
B:/DCIM/100CANON/IMG_9859.JPG: 2728334
Two burst pictures...
Ideally, the camera should be in some continuous shooting mode (not checked).
B:/DCIM/100CANON/ABC_9860.CR2 not found.
B:/DCIM/100CANON/ABC_9860.JPG: 2726155
B:/DCIM/100CANON/ABC_9861.CR2 not found.
B:/DCIM/100CANON/ABC_9861.JPG: 2725744
Bracketed pictures...
B:/DCIM/100CANON/IMG_9862.CR2 not found.
B:/DCIM/100CANON/IMG_9862.JPG: 1772649
B:/DCIM/100CANON/IMG_9863.CR2 not found.
B:/DCIM/100CANON/IMG_9863.JPG: 2713347
B:/DCIM/100CANON/IMG_9864.CR2 not found.
B:/DCIM/100CANON/IMG_9864.JPG: 3909756
Bulb picture...
Elapsed time: 11817
B:/DCIM/100CANON/IMG_9865.CR2 not found.
B:/DCIM/100CANON/IMG_9865.JPG: 382079
Picture taking tests completed.
Testing multitasking...
Only one task allowed to interrupt...
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Multitasking tests completed.
Testing half-shutter...
ML/SCRIPTS/API_TEST.LUA:657: assertion failed!
stack traceback:
[C]: in function 'assert'
ML/SCRIPTS/API_TEST.LUA:657: in function 'test_keys'
ML/SCRIPTS/API_TEST.LUA:1577: in function <ML/SCRIPTS/API_TEST.LUA:1564>
[C]: in function 'xpcall'
ML/SCRIPTS/API_TEST.LUA:1564: in function 'api_tests'
ML/SCRIPTS/API_TEST.LUA:1603: in main chunk
Line 657 is:
assert(camera.gui.idle == true)
so, like before, half-shutter from the menu apparently does *not* put the camera into mode 0 / "idle" mode? Or, it does, and ML is reading it wrong? I don't know enough about the code to really say :)
I am curious why the assertions during random menu / play / liveview mode pass OK but I think it's because they are not half-shutter related.
May as well move on to the next Lua api_test issue: movie recording throws assert error as well.
===============================================================================
ML/SCRIPTS/API_TEST.LUA - 2020-12-22 23:56:03
===============================================================================
Strict mode tests...
Strict mode tests passed.
Generic tests...
arg = table:
[0] = "API_TEST.LUA"
camera = table:
shutter = table:
raw = 75
apex = 2.375
ms = 193
value = 0.192776
aperture = table:
raw = 48
apex = 5.
value = 5.6
min = table:
raw = 40
apex = 4.
value = 4.
max = table:
raw = 83
apex = 9.375
value = 25.7
iso = table:
raw = 104
apex = 9.
value = 1600
ec = table:
raw = 0
value = 0
flash = true
flash_ec = table:
raw = 0
value = 0
kelvin = 5200
mode = 3
metering_mode = 3
drive_mode = 0
model = "Canon EOS REBEL T3"
model_short = "1100D"
firmware = "1.0.5"
temperature = 146
gui = table:
menu = false
play = false
play_photo = false
play_movie = false
qr = false
idle = true
wait = function: 0x5f34280
burst = function: 0x5f35608
bulb = function: 0x5f35588
reboot = function: 0x5f35328
shoot = function: 0x5f35354
event = table:
pre_shoot = nil
post_shoot = nil
shoot_task = nil
seconds_clock = nil
keypress = nil
custom_picture_taking = nil
intervalometer = nil
config_save = nil
console = table:
show = function: 0x5f32c14
write = function: 0x5f32ca8
hide = function: 0x5f32c04
clear = function: 0x5f32bf4
lv = table:
enabled = false
paused = false
running = false
zoom = 1
overlays = false
wait = function: 0x5f361f8
resume = function: 0x5f35e28
info = function: 0x5f35b34
start = function: 0x5f35790
stop = function: 0x5f357a0
pause = function: 0x5f35e38
lens = table:
name = "EF-S18-55mm f/3.5-5.6 IS II"
focal_length = 24
focus_distance = 1820
hyperfocal = 5461
dof_near = 1382
dof_far = 2682
af = true
af_mode = 0
focus = function: 0x5f36ea4
autofocus = function: 0x5f36cdc
display = table:
idle = nil
height = 480
width = 720
off = function: 0x5f37720
print = function: 0x5f38b50
draw = function: 0x5f378cc
load = function: 0x5f37a14
circle = function: 0x5f38088
pixel = function: 0x5f38984
line = function: 0x5f386bc
rect = function: 0x5f38358
on = function: 0x5f37730
screenshot = function: 0x5f3764c
notify_box = function: 0x5f377e4
clear = function: 0x5f3763c
key = table:
last = 10
press = function: 0x5f39328
wait = function: 0x5f39060
menu = table:
visible = false
block = function: 0x5f39890
open = function: 0x5f396a0
set = function: 0x5f3a914
new = function: 0x5f3b750
close = function: 0x5f39688
select = function: 0x5f3a840
get = function: 0x5f3aaf4
movie = table:
recording = false
start = function: 0x5f37338
stop = function: 0x5f372a4
dryos = table:
clock = 26
ms_clock = 26107
image_prefix = "IMG_"
config_dir = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = nil
path = "B:/"
path = "ML/"
path = "ML/SETTINGS/"
ml_card = table:
drive_letter = "B"
dcim_dir = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = nil
path = "B:/"
path = "B:/DCIM/"
path = "B:/DCIM/100CANON/"
file_number = 9865
folder_number = 100
free_space = 15337
image_path = function: 0x5f3cc50
type = "SD"
_card_ptr = userdata
path = "B:/"
shooting_card = table:
drive_letter = "B"
dcim_dir = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = nil
path = "B:/"
path = "B:/DCIM/"
path = "B:/DCIM/100CANON/"
file_number = 9865
folder_number = 100
free_space = 15337
image_path = function: 0x5f3cc50
type = "SD"
_card_ptr = userdata
path = "B:/"
cf_card = nil
sd_card = table:
drive_letter = "B"
dcim_dir = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = table:
exists = true
create = function: 0x5f3ca74
children = function: 0x5f3c8fc
files = function: 0x5f3c7e0
parent = nil
path = "B:/"
path = "B:/DCIM/"
path = "B:/DCIM/100CANON/"
file_number = 9865
folder_number = 100
free_space = 15337
image_path = function: 0x5f3cc50
type = "SD"
_card_ptr = userdata
path = "B:/"
date = table:
month = 12
sec = 5
min = 56
yday = 1
isdst = false
wday = 6
year = 2020
day = 22
hour = 23
directory = function: 0x5f3c340
rename = function: 0x5f3c200
remove = function: 0x5f3c2d4
call = function: 0x5f3bffc
interval = table:
time = 10
count = 0
running = false
stop = function: 0x5f3d690
battery = table:
function not available on this camera
stack traceback:
[C]: in ?
[C]: in for iterator 'for iterator'
ML/SCRIPTS/LIB/logger.lua:125: in function 'logger.serialize'
ML/SCRIPTS/API_TEST.LUA:45: in function <ML/SCRIPTS/API_TEST.LUA:44>
[C]: in function 'xpcall'
ML/SCRIPTS/API_TEST.LUA:44: in function 'print_table'
ML/SCRIPTS/API_TEST.LUA:90: in function 'generic_tests'
ML/SCRIPTS/API_TEST.LUA:1568: in function <ML/SCRIPTS/API_TEST.LUA:1564>
[C]: in function 'xpcall'
ML/SCRIPTS/API_TEST.LUA:1564: in function 'api_tests'
ML/SCRIPTS/API_TEST.LUA:1603: in main chunktask = table:
yield = function: 0x5f3dcf8
create = function: 0x5f3de78
property = table:
Generic tests completed.
Module tests...
Testing file I/O...
Copy test: autoexec.bin -> tmp.bin
Copy test OK
Append test: tmp.txt
Append test OK
Rename test: apple.txt -> banana.txt
Rename test OK
Rename test: apple.txt -> ML/banana.txt
Rename test OK
SD card (B:/) present
- free space: 15337 MiB
- next image: B:/DCIM/100CANON/IMG_9866.JPG
- DCIM dir. : B:/DCIM/100CANON/
- B:/DCIM/
- B:/DCIM/100CANON/
- B:/DCIM/EOSMISC/
- B:/MISC/
- B:/TRASHE~1/
- B:/ML/
- B:/ML/CROPMKS/
- B:/ML/CROPMKS/CINESCO2.BMP
- B:/ML/CROPMKS/CRSSMTR2.BMP
- B:/ML/CROPMKS/PASSPORT.BMP
- B:/ML/CROPMKS/PHIPHOTO.BMP
- B:/ML/CROPMKS/PHIVIDEO.BMP
- B:/ML/DATA/
- B:/ML/DATA/APSC8P.LUT
- B:/ML/DATA/APSC8R.LUT
- B:/ML/DATA/FF8P.LUT
- B:/ML/DATA/FF8R.LUT
- B:/ML/DOC/
- B:/ML/FONTS/
- B:/ML/FONTS/ARGHLF22.RBF
- B:/ML/FONTS/ARGNOR23.RBF
- B:/ML/FONTS/ARGNOR28.RBF
- B:/ML/FONTS/ARGNOR32.RBF
- B:/ML/FONTS/TERM12.RBF
- B:/ML/FONTS/TERM20.RBF
- B:/ML/MODULES/
- B:/ML/MODULES/ADV_INT.MO
- B:/ML/MODULES/ARKANOID.MO
- B:/ML/MODULES/AUTOEXPO.MO
- B:/ML/MODULES/BENCH.MO
- B:/ML/MODULES/DEFLICK.MO
- B:/ML/MODULES/DUAL_ISO.MO
- B:/ML/MODULES/EDMAC.MO
- B:/ML/MODULES/ETTR.MO
- B:/ML/MODULES/FILE_MAN.MO
- B:/ML/MODULES/IMG_NAME.MO
- B:/ML/MODULES/LUA.MO
- B:/ML/MODULES/MLV_LITE.MO
- B:/ML/MODULES/MLV_PLAY.MO
- B:/ML/MODULES/MLV_REC.MO
- B:/ML/MODULES/MLV_SND.MO
- B:/ML/MODULES/PIC_VIEW.MO
- B:/ML/MODULES/SELFTEST.MO
- B:/ML/MODULES/SILENT.MO
- B:/ML/MODULES/T3_105.SYM
- B:/ML/MODULES/LOADING.LCK
- B:/ML/SCRIPTS/
- B:/ML/SCRIPTS/LIB/
- B:/ML/SCRIPTS/LIB/CONFIG.LUA
- B:/ML/SCRIPTS/LIB/KEYS.LUA
- B:/ML/SCRIPTS/LIB/LOGGER.LUA
- B:/ML/SCRIPTS/LIB/STRICT.LUA
- B:/ML/SCRIPTS/API_TEST.LUA
- B:/ML/SCRIPTS/CALC.LUA
- B:/ML/SCRIPTS/COPY2M.LUA
- B:/ML/SCRIPTS/EDITOR.LUA
- B:/ML/SCRIPTS/HELLO.LUA
- B:/ML/SCRIPTS/MENUTEST.LUA
- B:/ML/SCRIPTS/PONG.LUA
- B:/ML/SCRIPTS/RECDELAY.LUA
- B:/ML/SCRIPTS/SCRNSHOT.LUA
- B:/ML/SCRIPTS/SOKOBAN.LUA
- B:/ML/SCRIPTS/UNLOAD.LUA
- B:/ML/LOGS/
- B:/ML/LOGS/ROM0.BIN
- B:/ML/LOGS/ROM1.BIN
- B:/ML/LOGS/LUATEST.LOG
- B:/ML/SETTINGS/
- B:/ML/SETTINGS/LUA.EN
- B:/ML/SETTINGS/MAGIC.CFG
- B:/ML/SETTINGS/MENUS.CFG
- B:/ML/DOCS
- B:/ML/README
- B:/FSEVEN~1/
- B:/FSEVEN~1/FSEVEN~1
- B:/FSEVEN~1/000000~1
- B:/FSEVEN~1/000000~2
- B:/FSEVEN~1/000000~3
- B:/FSEVEN~1/000000~4
- B:/TEMPOR~1/
- B:/TEMPOR~1/FOLDERS.501/
- B:/TEMPOR~1/FOLDERS.501/TEMPOR~1/
- B:/TEMPOR~1/FOLDERS.501/_TEMPO~1
- B:/TEMPOR~1/_FOLDE~1.501
- B:/AUTOEXEC.BIN
- B:/~1.TRA
- B:/~1.TEM
- B:/APDIS~1
- B:/~1.APD
File I/O tests completed.
Testing Canon GUI functions...
Enter MENU mode...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Start LiveView...
Pause LiveView...
Enter MENU mode...
Exit MENU mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Enter MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Resume LiveView...
Pause LiveView...
Resume LiveView...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Enter MENU mode...
Exit MENU mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Resume LiveView...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Stop LiveView...
Start LiveView...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Enter PLAY mode...
Enter MENU mode...
Exit MENU mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Resume LiveView...
Canon GUI tests completed.
Testing ML menu API...
Menu tests completed.
Testing picture taking functions...
Snap simulation test...
Single picture...
B:/DCIM/100CANON/IMG_9866.CR2 not found.
B:/DCIM/100CANON/IMG_9866.JPG: 2768933
Two burst pictures...
Ideally, the camera should be in some continuous shooting mode (not checked).
B:/DCIM/100CANON/ABC_9867.CR2 not found.
B:/DCIM/100CANON/ABC_9867.JPG: 2958982
B:/DCIM/100CANON/ABC_9868.CR2 not found.
B:/DCIM/100CANON/ABC_9868.JPG: 3069728
Bracketed pictures...
B:/DCIM/100CANON/IMG_9869.CR2 not found.
B:/DCIM/100CANON/IMG_9869.JPG: 1893654
B:/DCIM/100CANON/IMG_9870.CR2 not found.
B:/DCIM/100CANON/IMG_9870.JPG: 2939208
B:/DCIM/100CANON/IMG_9871.CR2 not found.
B:/DCIM/100CANON/IMG_9871.JPG: 3281851
Bulb picture...
Elapsed time: 11626
B:/DCIM/100CANON/IMG_9872.CR2 not found.
B:/DCIM/100CANON/IMG_9872.JPG: 702038
Picture taking tests completed.
Testing multitasking...
Only one task allowed to interrupt...
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Multitasking tests completed.
Testing half-shutter...
Half-shutter test OK.
Testing module 'lv'...
Starting LiveView...
Overlays: Canon
Overlays: Canon
Overlays: ML
Overlays: ML
Overlays:
- Zebras: LumaFast, over 99%
- Focus Peak: OFF
- Magic Zoom: OFF
- Cropmarks: OFF
- Ghost image: OFF
- Spotmeter: Percent, AFbox
- False color: OFF
- Histogram: RAW N/A, Log
- Waveform: Small
- Vectorscope: OFF
Turning everything off:
- Zebras: LumaFast, over 99% -> OFF
- Spotmeter: Percent, AFbox -> OFF
- Histogram: RAW N/A, Log -> OFF
- Waveform: Small -> OFF
Turning on one by one:
- Zebras: ON/OFF (LumaFast, over 99%)
- Focus Peak: ON/OFF (ON,0.5,local)
- Magic Zoom: ON/OFF ((+), Med, TL, 2:1)
- Cropmarks: ON/OFF (CINESCO2.BMP)
- Ghost image: ON/OFF (ON)
- Spotmeter: ON/OFF (Percent, AFbox)
- False color: ON/OFF (Marshall)
- Histogram: ON/OFF (RAW N/A, Log)
- Waveform: ON/OFF (Small)
- Vectorscope: ON/OFF (ON)
Turning everything on:
- Zebras: ON
- Focus Peak: ON
- Magic Zoom: ON
- Cropmarks: ON
- Ghost image: ON
- Spotmeter: ON
- False color: ON
- Histogram: ON
- Waveform: ON
- Vectorscope: ON
Restoring previous state:
- Zebras: LumaFast, over 99%
- Focus Peak: OFF
- Magic Zoom: OFF
- Cropmarks: OFF
- Ghost image: OFF
- Spotmeter: Percent, AFbox
- False color: OFF
- Histogram: RAW N/A, Log
- Waveform: Small
- Vectorscope: OFF
Overlays working :)
Overlays: disabled
Overlays: Canon
Overlays: Canon
Overlays: Canon
Overlays: disabled
Overlays: ML
Overlays: disabled
Overlays: Canon
Overlays: Canon
Overlays: Canon
Overlays: disabled
Overlays: ML
Overlays: disabled
Overlays: ML
Setting zoom to x1...
Setting zoom to x5...
Setting zoom to x10...
Setting zoom to x5...
Setting zoom to x1...
Setting zoom to x10...
Setting zoom to x1...
Pausing LiveView...
Resuming LiveView...
Stopping LiveView...
LiveView tests completed.
Testing lens focus functionality...
Autofocus outside LiveView...
Is there something to focus on?
29...Focus distance: 1820
Autofocus in LiveView...
Please trigger autofocus (half-shutter / AF-ON / * ).
59...58...Autofocus triggered.
Autofocus completed.
Focus distance: 1820
Focusing backward...
Focus distance: 655350
Focus motor position: 421
Focusing forward with step size 3, wait=true...
.........
Focus distance: 250
Focus motor position: -1468
Focusing backward with step size 3, wait=true...
..........
Focus distance: 655350
Focus motor position: 428
Focus range: 9 steps forward, 10 steps backward.
Motor steps: 1889 forward, 1896 backward, 7 lost.
Focusing forward with step size 3, wait=false...
...............................
Focus distance: 250
Focus motor position: -1460
Focusing backward with step size 3, wait=false...
..............................
Focus distance: 655350
Focus motor position: 434
Focus range: 31 steps forward, 30 steps backward.
Motor steps: 1888 forward, 1894 backward, 6 lost.
Focusing forward with step size 2, wait=true...
...........................................................
Focus distance: 250
Focus motor position: -1430
Focusing backward with step size 2, wait=true...
...........................................................
Focus distance: 655350
Focus motor position: 466
Focus range: 59 steps forward, 59 steps backward.
Motor steps: 1864 forward, 1896 backward, 32 lost.
Focusing forward with step size 2, wait=false...
...
Focus distance: 250
Focus motor position: -1394
Focusing backward with step size 2, wait=false...
...
Focus distance: 655350
Focus motor position: 498
Focus range: 135 steps forward, 139 steps backward.
Motor steps: 1860 forward, 1892 backward, 32 lost.
Focus test completed.
Testing exposure settings...
Camera : Canon EOS REBEL T3 (1100D) 1.0.5
Lens : EF-S18-55mm f/3.5-5.6 IS II
Shoot mode: 3
Shutter : Ç5 (raw 75, 0.192776s, 193ms, apex 2.375)
Aperture : Å5.6 (raw 48, f/5.6, apex 5.)
Av range : Å4.0..Å25 (raw 40..83, f/4...f/25.7, apex 4...9.375)
ISO : Ä1600 (raw 104, 1600, apex 9.)
EC : 0.0 (raw 0, 0 EV)
Flash EC : 0.0 (raw 0, 0 EV)
Setting shutter to random values...
Setting ISO to random values...
Setting aperture to random values...
Please switch to Av mode.
Setting EC to random values...
Setting Flash EC to random values...
Exposure tests completed.
Testing movie recording...
Please switch to Movie mode.
ML/SCRIPTS/API_TEST.LUA:1537: assertion failed!
stack traceback:
[C]: in function 'assert'
ML/SCRIPTS/API_TEST.LUA:1537: in function 'test_movie'
ML/SCRIPTS/API_TEST.LUA:1581: in function <ML/SCRIPTS/API_TEST.LUA:1564>
[C]: in function 'xpcall'
ML/SCRIPTS/API_TEST.LUA:1564: in function 'api_tests'
ML/SCRIPTS/API_TEST.LUA:1603: in main chunk
which in this case would be:
-- now it should work
-- hide the console for a nicer look
console.hide(); assert(not console.visible)
movie.start()
assert(movie.recording)
so movie recording apparently does not actually start when calling movie.start(). Which is true, there are no .mov files on my card.
EDIT: odd, just re-ran this part of the test, and it completed fine this time. No idea what the deal was before. Maybe needs a delay before or after movie.start.
EDIT2: one other thing to add is that the console flickers a lot in manual / Av / Tv / etc modes as it is continually being overwritten by the shot params UI, and then draws atop it, etc. I may as well take a vid if you want to see the whole thing :)
Once again Stub Test (selftest.mo) crashes and requires a battery pull.
[Pass] is_play_mode() => 0x1
[INFO] Camera model: Canon EOS REBEL T3 1.0.5 (0x80000288 1100D)
[Pass] is_camera("DIGIC", "*") => 0x1
[Pass] is_camera(__camera_model_short, firmware_version) => 0x1
[Pass] src = fio_malloc(size) => 0x45fb4154
[Pass] dst = fio_malloc(size) => 0x42e00084
[Pass] memcmp(dst, src, 4097) => 0xffffffa9
[Pass] edmac_memcpy(dst, src, 4097) => 0x42e00084
[Pass] memcmp(dst, src, 4097) => 0x0
[Pass] edmac_memcpy(dst, src, 4097) => 0x42e00084
[Pass] memcmp(dst, src, size) => 0xffffff6f
[Pass] edmac_memcpy(dst, src, size) => 0x42e00084
[Pass] memcmp(dst, src, size) => 0x0
[Pass] memcmp(dst, src, size) => 0x8d
[Pass] edmac_memcpy_start(dst, src, size) => 0x42e00084
dt => 0x37a8
[Pass] copied => 0x4013bc
[Pass] copied => 0x4013bc
[Pass] copied => 0x4013bc
[Pass] memcmp(dst, src, copied) => 0x0
[Pass] memcmp(dst, src, copied + 16) => 0xa
edmac_memcpy_finish()
free(src)
free(dst)
Cache test A (EDMAC on BMP buffer)...
[Pass] bmp = bmp_load("ML/CROPMKS/CINESCO2.BMP", 1) => 0x5fb4154
[Pass] old => 0x0
[Pass] irq => 0xc0
[Pass] differences => 0x98e
[Pass] old => 0x0
[Pass] irq => 0xc0
[Pass] differences => 0x0
Cache test B (FIO on 8K buffer)...
[Pass] tries[0] => 0x100
[Pass] tries[1] => 0xfe
[Pass] tries[2] => 0xff
[Pass] tries[3] => 0xeb
[Pass] failr[0] => 0x97
[Pass] failw[0] => 0xce
[Pass] failr[1] => 0x8f
[Pass] failw[1] => 0x0
[Pass] failr[2] => 0x0
[Pass] failw[2] => 0xc5
[Pass] failr[3] => 0x0
[Pass] failw[3] => 0x0
times[0] / tries[0] => 0x3b
times[1] / tries[1] => 0x44
times[2] / tries[2] => 0x3d
times[3] / tries[3] => 0x3f
Cache tests finished.
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[FAIL] wait_focus_status(1000, 3) => 0x0
[FAIL] lv_focus_status => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] lv_focus_status => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x2
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[FAIL] wait_focus_status(1000, 3) => 0x0
[FAIL] lv_focus_status => 0x2
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] lv_focus_status => 0x2
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x2
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[FAIL] wait_focus_status(1000, 3) => 0x0
[FAIL] lv_focus_status => 0x2
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] lv_focus_status => 0x2
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x2
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[FAIL] wait_focus_status(1000, 3) => 0x0
[FAIL] lv_focus_status => 0x2
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] lv_focus_status => 0x2
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x2
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[FAIL] wait_focus_status(1000, 3) => 0x0
[FAIL] lv_focus_status => 0x2
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] lv_focus_status => 0x2
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] wait_focus_status(1000, 3) => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x2
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x2
[Pass] HALFSHUTTER_PRESSED => 0x0
[FAIL] HALFSHUTTER_PRESSED => 0x0
[FAIL] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x2
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x2
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x2
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x1
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x1
[Pass] get_focus_confirmation() => 0x0
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] lv_focus_status => 0x2
I am looking at the code and the log is written after each successful test. These last lines are from the AF test, the next is the file-io test, which I guess is where it's dying.
On the root of the card is TEST.DAT, 131072 bytes (exactly 128K), and is full of mostly junk data - probably uninitialized. It appears to die without any helpful print before it can create the file full of "Will it blend?" messages. My wild unfounded guess is... I don't see the first TEST.DAT file getting deleted anywhere in selftest.c, before attempting to FIO_Create a new file with the exact same name. Is it possible that the camera will not let you overwrite files like this, causing the test to crash?
Now we are talking :)
Quote from: greg_kennedy on December 23, 2020, 04:51:21 AM
so, like before, half-shutter from the menu apparently does *not* put the camera into mode 0 / "idle" mode? Or, it does, and ML is reading it wrong?
Apparently yes - in consts.h, CURRENT_GUI_MODE might be 0x3960 (at least for pattern matching).
Will try reproducing it in QEMU.
Quote from: greg_kennedy on December 24, 2020, 01:57:47 AM
On the root of the card is TEST.DAT, 131072 bytes (exactly 128K), and is full of mostly junk data - probably uninitialized. It appears to die without any helpful print before it can create the file full of "Will it blend?" messages. My wild unfounded guess is... I don't see the first TEST.DAT file getting deleted anywhere in selftest.c, before attempting to FIO_Create a new file with the exact same name. Is it possible that the camera will not let you overwrite files like this, causing the test to crash?
Junk data is expected - it dumps a section of the ROM, same block written twice (2 x 65536 bytes). If the contents of that file match the description, the first few lines from stub_test_file_io() might have succeeded.
Overwriting should be OK - the wrapper code in fio-ml.c will call FIO_RemoveFile prior to FIO_CreateFile. Otherwise, at least on some models, FIO_CreateFile would happily create multiple files with the same name on the filesystem, and that confuses at least the FAT32 driver in Linux - didn't check other systems on this particular one :)
Next test is checking the resulting file size - no surprises expected.
The following test is attempting to read back the file from card; that's where I would expect things to go wrong if memory allocation fails. You might be able to see some error messages - not yet written to a log file - directly on the screen.
This issue should be reproducible in QEMU as well.
Edit Dec.28 2020: both issues hopefully fixed (tested in QEMU only); new build available on the Experiments page. Please report back.
Hi I'm new and currently trying to complete the test described on the LUA scripting thread with my old 1100D, I'm using the latest dec 28 2020 build.
https://www.magiclantern.fm/forum/index.php?topic=14828.msg194706#msg194706
I will post results when I find them.
Wel the camera is still running tests.. now lua test.. However it did crash
- selftest.mo -> stubs tests (upload the log)
https://imgur.com/a/UeVMVFY
The Lua script was flashing flashing flashing flashing and when I realized that the battery is going down and the test just goes on and on picket the camera and between the flashing screen noticed it wanted to switch to M mode (text was so so small and constantly flashing but managed to read it.) Maybe it shouldn't flash that "info" it could make the same beeping as asking for half shutter.
Ok the LUA test crashed also. I will upload logs.7z to somewhere... i quest.
https://ufile.io/w7jddbvp
- api_test.lua (upload the log)
- selftest.mo -> stubs tests (upload the log)
- bench.mo -> memory benchmarks (upload the screenshot)
Soo I'm not at all sure I did this correctly but I did complete all the test I think :) Also the errors could be due to low battery idk. Hope the logs help, I will try to run the tests again, not the benchmarks but the 2 other tests after the battery is full again.
For sanity... Welllll the menu sometimes becomes transparent, now its probably me as setting default settings made it not transparent.
ML is really cool :) Eats allot of battery but that's not an issue.. Well it is for me as I don't have a mod/power cort.
Thanks, you did the tests correctly.
ERR70 from the stubs test appears to come from here (first fail):
m0 = GetFreeMemForAllocateMemory() => 0x6361c
[FAIL] p = (void*)_AllocateMemory(128*1024) => 0x0
The memory backend reports 0x6361c = 407068 bytes available for AllocateMemory, but... attempting to allocate 128K (131072 bytes) fails for some reason. Best guess: memory fragmentation. Most of the subsequent failures are caused by the initial crash.
If you try to load only selftest.mo, and run the stubs test only with that module loaded, does it still crash?
Lua test worked for the most part, but crashed near the end (at "Setting aperture to random values"). Is this crash repeatable? If you run the same test a few times, does it crash in the same place?
Menu becoming transparent... is a feature, if you press LiveView while in ML menu (which might help when adjusting settings that affect the image).
When asking for M mode change, api_test.lua actually does attempt to beep, in the same way as when asking for half-shutter. If it didn't beep, there might be a problem with beeps as well. Beeps are not yet emulated in QEMU.
Re running the LUA test and it passed fine, (multiple runs, with all the mods initialized). This time it was on Manual photo mode from the start.
Could be that initially it was just running the switch to Manual call so many times, as it was cycling quite along time. Dunno. I could try to run the lua test again, with the movie record mode and see if it gets stuck again. (running now.) Will post results later
I will take video of the (switch to manual mode loop.) https://youtu.be/EYLJFQxn2Xo
So it definitively doesn't make a beep when asking for M mode.
https://youtu.be/0fDR3bcC1bQ Flickering.
Re sunning the selftest.mo (stubs test) and only that mod was loaded. still crashing. I re run it with RAW and switched to low quality jpeg output in the hopes it had something to do with it, same result.
https://ufile.io/25loyiop new logs.
The feature comparison matrix says mlv_lite isn't supported on 1100d. Is that still the case?