11476
Feature Requests / Re: Image Sequence 1080P Movie Mode
« on: June 28, 2012, 03:27:16 PM »
Use silent pic in burst mode 
News:
Etiquette, expectations, entitlement...
@autoexec_bin | #magiclantern | Discord | Reddit | Server issues
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
11477
General Help Q&A / [WONTFIX - DISABLED] Movie mode remap (problems)
« on: June 28, 2012, 03:14:24 PM »
I'm having some issues with movie mode remap (and ISO+LV). There were also a few bug reports on it (500D: black screen, 60D: not remembering settings).
Today I've got ERR70 on 60D by doing this:
1) started camera in M mode;
2) enabled LiveView;
3) pressed ISO+LV to go to movie mode;
4) pressed REC => instant ERR70.
I've tried with a minimal code base (the only extra code was switching to movie mode after 10 seconds). Still ERR70. After clearing Canon settings the problem disappeared, but it clearly shows that there's something fishy with this feature.
I'm seriously thinking to disable movie mode remap completely. Suggestions?
Today I've got ERR70 on 60D by doing this:
1) started camera in M mode;
2) enabled LiveView;
3) pressed ISO+LV to go to movie mode;
4) pressed REC => instant ERR70.
I've tried with a minimal code base (the only extra code was switching to movie mode after 10 seconds). Still ERR70. After clearing Canon settings the problem disappeared, but it clearly shows that there's something fishy with this feature.
I'm seriously thinking to disable movie mode remap completely. Suggestions?
11478
Feature Requests / Re: Possible to port HD video crop from T3i to all other Video Canon DSLRs?
« on: June 28, 2012, 07:16:43 AM »
No, and read the other titles before posting.
11479
General Chat / Re: ML 2.3 - general chat
« on: June 27, 2012, 08:19:54 PM »
That list can also be useful as a list of specifications - sort of. Although it's too big for normal users 
11480
General Chat / Re: ML 2.3 - general chat
« on: June 27, 2012, 07:50:56 PM »
That's right.
There is a nightly build server in the works, and I think after 2.3 it will be fully functional. Meanwhile you can compile yourself; the process became pretty easy lately, and I think this will encourage code contributions from other users.
About 2.3: the feature set is already frozen, and I'd like to have a period of release candidate (RC) testing, according to the plan posted here. That means:
1) ML should pass those tests on my cameras (550D, 60D, 5D2). It fails a few ones now.
2) Post the RC1, and collect tester feedback for one or two weeks.
3) From the feedbacks, I'll decide if we need an RC2 or if it's ready for release. Maybe a RC3 too.
I always did similar testing before full releases, but only with a few users asked privately. Now I'd like to do this on a larger scale, hoping that the end result will be rock solid. Existing contributors (no matter what kind of contribution) will be the ones who'll run the early tests.
I was also thinking to run some infinite stability test for at least 24 hours (need an external power source for that) and film a timelapse with that. The infinite test enables random things from menus, and I've ran it succesfully for a few hours.
Suggestions?
There is a nightly build server in the works, and I think after 2.3 it will be fully functional. Meanwhile you can compile yourself; the process became pretty easy lately, and I think this will encourage code contributions from other users.
About 2.3: the feature set is already frozen, and I'd like to have a period of release candidate (RC) testing, according to the plan posted here. That means:
1) ML should pass those tests on my cameras (550D, 60D, 5D2). It fails a few ones now.
2) Post the RC1, and collect tester feedback for one or two weeks.
3) From the feedbacks, I'll decide if we need an RC2 or if it's ready for release. Maybe a RC3 too.
I always did similar testing before full releases, but only with a few users asked privately. Now I'd like to do this on a larger scale, hoping that the end result will be rock solid. Existing contributors (no matter what kind of contribution) will be the ones who'll run the early tests.
I was also thinking to run some infinite stability test for at least 24 hours (need an external power source for that) and film a timelapse with that. The infinite test enables random things from menus, and I've ran it succesfully for a few hours.
Suggestions?
11481
Camera-specific Development / Re: Canon 1100D / T3
« on: June 27, 2012, 03:42:37 PM »
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.
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.
11482
General Help Q&A / Re: Few problems with ML...
« on: June 27, 2012, 02:58:31 PM »
Good catch... I think I'll move that function to the joystick center press only.
11483
General Help Q&A / Re: Few problems with ML...
« on: June 27, 2012, 02:42:45 PM »
1) Did you enable exposure override? The 50D doesn't have manual video controls with Canon firmware.
2) Check the half-shutter setting, if it's sticky it may block the SET button (50D issue, see the user guide).
2) Check the half-shutter setting, if it's sticky it may block the SET button (50D issue, see the user guide).
11484
Camera-specific Development / Re: Canon 1100D / T3
« on: June 27, 2012, 02:39:44 PM »
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.
The 60D gives random ERR70 if the second buffer has less than 1MB free. Probably I should also display the maximum contiguous block.
11485
Forum and Website / Re: RSS feed
« on: June 27, 2012, 07:25:43 AM »
For me it's OK, thanks. For other users who may want RSS... I don't know.
11486
General Development / Re: Development stupid questions
« on: June 27, 2012, 12:42:48 AM »
That 0 is cropmarks_flag: it tells ML to copy only bitmaps from that folder, not other files.
Language is C.
Language is C.
11487
Camera-specific Development / Re: Canon 1100D / T3
« on: June 26, 2012, 10:23:31 PM »
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
11488
Feature Requests / Re: High ISO Noise Reduction - different settings for different ISOs
« on: June 26, 2012, 03:44:37 PM »
Canon already does dark frame subtraction, BUT only combined with aggressive noise reduction.
Didn't check what happens with RAW.
Didn't check what happens with RAW.
11489
General Help Q&A / Re: Lua Script - Half Pressed Button
« on: June 26, 2012, 12:44:01 PM »
Half-shutter press is emulated with PROP_REMOTE_SW1 (0x80020015) : 1 = pressed, 0 not pressed.
11490
Camera-specific Development / Re: Canon 1100D / T3
« on: June 25, 2012, 04:25:56 PM »
Remove -mlong-calls from Makefile.inc .
11491
Camera-specific Development / Re: Canon 1100D / T3
« on: June 25, 2012, 03:30:18 PM »
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).
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).
11492
Camera-specific Development / Re: Canon 1100D / T3
« on: June 25, 2012, 02:50:33 PM »
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).
11493
Camera-specific Development / Re: Canon 1100D / T3
« on: June 25, 2012, 11:57:02 AM »
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?
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?
11494
Camera-specific Development / Re: Canon 1100D / T3
« on: June 25, 2012, 11:42:12 AM »
Those are state objects ( http://magiclantern.wikia.com/wiki/StateObjects , 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).
The state matrix (ff5969ac) is referenced from sub_FF0F73C8. So, with arm-console:
So, at 0x4C34, Canon firmware saves a pointer to EvfState object (see "struct state_object" in state-object.h).
Most of those things contain strings with their name (for our example, we have EvfState and Evf\\EvfState.c).
Code: [Select]
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:
Code: [Select]
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).
11495
Feature Requests / Re: High ISO Noise Reduction - different settings for different ISOs
« on: June 25, 2012, 11:06:13 AM »
Technically possible, but I don't see any point in doing this. I'd rather have dark frame subtraction without noise reduction, on RAW images.
11496
General Help Q&A / Re: Time lapse
« on: June 25, 2012, 10:41:53 AM »
I didn't really test this, but I think you can use auto ISO with FPS override mode (sort of a poor man's bulb ramping ).
).
11497
General Help Q&A / Re: Magic Lantern Newbie
« on: June 25, 2012, 10:40:03 AM »
Those things are good candidates for FAQ.
11498
Camera-specific Development / Re: Canon 1100D / T3
« on: June 25, 2012, 09:46:22 AM »
Here you go:
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.
Code: [Select]
#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.
11499
Feature Requests / Re: Additional 600D Digital Zoom setting?
« on: June 25, 2012, 08:50:27 AM »
No.
11500
Feature Requests / Re: Possibility of custom frame dimensions?
« on: June 25, 2012, 08:49:58 AM »
No.