Menu

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.

Show posts Menu

Messages - Arcanemon

#1
Camera-specific Development / Re: Canon 1100D / T3
April 04, 2013, 08:24:59 PM
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.
#2
Camera-specific Development / Re: Canon 1100D / T3
April 04, 2013, 08:02:04 PM
Ok, I got some C skills programing but no too much.
In which archive are the constants?.
Thanks
#3
Camera-specific Development / Re: Canon 1100D / T3
April 04, 2013, 02:53:37 PM
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?

#4
Camera-specific Development / Re: Canon 1100D / T3
April 01, 2013, 06:19:41 PM
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.
#5
Camera-specific Development / Re: Canon 1100D / T3
April 01, 2013, 02:07:00 PM
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.


#6
Camera-specific Development / Re: Canon 1100D / T3
March 06, 2013, 11:25:57 AM
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
#7
Camera-specific Development / Re: Canon 1100D / T3
February 26, 2013, 11:53:32 AM
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
#8
Camera-specific Development / Re: Canon 1100D / T3
February 18, 2013, 09:14:01 PM
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
#9
Camera-specific Development / Re: Canon 1100D / T3
February 09, 2013, 06:29:17 PM
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
#10
Camera-specific Development / Re: Canon 1100D / T3
February 09, 2013, 01:20:00 PM
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.
#11
Camera-specific Development / Re: Canon 1100D / T3
February 09, 2013, 01:16:14 PM
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