A590IS porting...

dvip

The A590is also boots faster with a 4GB FAT16 card.
I think the partition on the 8GB card slows things down.

I know that recently, some work was done in the booting code for some cameras.
I wonder if the A590is was one of them, I hope, I like the A590is.

waterwingz

dvip
I know that recently, some work was done in the booting code for some cameras.
I wonder if the A590is was one of them, I hope, I like the A590is.

The recent boot code changes removed a little bit of unnecessary code in the initial stages of the boot load. Time wise we are talking microseconds of difference and it was certainly nothing that would cause FAT16 or FAT32 cards to boot differently.

Sorry.

nafraf

A590 101b, new version attached:
* port rewritten using code_gen tool
* filewritetask implemented
* boot.c rewritten: capt_seq_task and init_file_modules_task added to taskCreateHook(int *p)
* Modifications to platform_camera, suggested here
#define CAM_EV_IN_VIDEO 1
#undef CAM_CAN_SD_OVER_NOT_IN_MF

Please test if everything is working 😉

peabody

In 1.1, the A590is subject distance override at infinity is 52855, not 65535. Why is that?

dvip

nafraf
A590 101b, new version attached:
* port rewritten using code_gen tool
* filewritetask implemented
* boot.c rewritten: capt_seq_task and init_file_modules_task added to taskCreateHook(int *p)
* Modifications to platform_camera, suggested here
#define CAM_EV_IN_VIDEO 1
#undef CAM_CAN_SD_OVER_NOT_IN_MF

Please test if everything is working 😉

@nafraf,
I just tested the new port using the code_gen tool on my A590IS-101b and it works great.

You may also want to take a look at this bug.
If you set:
CHDK Settings->OSD Settings->Miscellaneous Values->Show Misc Values [Shoot]
it behaves as:
CHDK Settings->OSD Settings->Miscellaneous Values->Show Misc Values [Always]

blackhole

A590 101b, new version attached:
* port rewritten using code_gen tool
* filewritetask implemented
* boot.c rewritten: capt_seq_task and init_file_modules_task added to taskCreateHook(int *p)
* Modifications to platform_camera, suggested here
#define CAM_EV_IN_VIDEO 1
#undef CAM_CAN_SD_OVER_NOT_IN_MF

Please test if everything is working

Thanks for that.
I tried your version and filewritetask works great.
CAM_EV_IN_VIDEO I'm trying on before and never worked very well, if you're recording a dark scene just does not respond, you have to expose the sensor briefly to the bright light and then sometimes respond,maybe is this reason why was commented in the platform_camera. I never noticed that enabling this has some negative effects.
This is a much better solution, but I do not know if it works on all cameras, I've tried it with A530, A590 and A1100, and works well.

nafraf

blackhole
Thanks for that.
I tried your version and filewritetask works great.

thanks for report. Could you confirm if photo overrides are working? I modified the hook, so I'd like to be sure that it is still working.

CAM_EV_IN_VIDEO I'm trying on before and never worked very well, if you're recording a dark scene just does not respond, you have to expose the sensor briefly to the bright light and then sometimes respond,maybe is this reason why was commented in the platform_camera. I never noticed that enabling this has some negative effects.
This is a much better solution, but I do not know if it works on all cameras, I've tried it with A530, A590 and A1100, and works well.

OK, I'll remove CAM_EV_IN_VIDEO.

blackhole

@nafraf
I sent you a PM

nafraf

peabody
In 1.1, the A590is subject distance override at infinity is 52855, not 65535. Why is that?

Hi, I don't have access to a590, could you test this: https://chdk.setepontos.com/d/2509/106 ?

blackhole

@nafraf

Mode 32791 is an unnamed mode with fish icon, but different than when the camera is in the aquarium mode.

nafraf

blackhole
@nafraf

Mode 32791 is an unnamed mode with fish icon, but different than when the camera is in the aquarium mode.

It is the under water icon in D10. What if you try to take a photo using it?

blackhole

Jpg and dng are ok.
Exif says it is Easy shooting mode,WB is set to manual.

peabody

nafraf

peabody
In 1.1, the A590is subject distance override at infinity is 52855, not 65535. Why is that?

Hi, I don't have access to a590, could you test this: https://chdk.setepontos.com/d/2509/106 ?

Thanks, but I found that the min and max subject distance were specified in a change to camera.h a while back, so I'm going to assume that was done correctly. Since I had always seen 65535 in earlier versions, I just wanted to be sure it wasn't a bug of some kind.

dvip

@nafraf,
The A590IS has a tendency to overexpose video.
I think CAM_EV_IN_VIDEO is useful to correct for video overexposure and shouldn't be removed.
It is good to make videos of the moon, stars (with a telescope)... it helps to control overexposure well.

Perhaps the UI control should be modify to indicate that it is only to control video overexposure.

nafraf

dvip
@nafraf,
The A590IS has a tendency to overexpose video.
I think CAM_EV_IN_VIDEO is useful to correct for video overexposure and shouldn't be removed.
It is good to make videos of the moon, stars (with a telescope)... it helps to control overexposure well.

Perhaps the UI control should be modify to indicate that it is only to control video overexposure.

Hi, I have not used that feature. I removed it because blackhole reported that it was not working well in this post.
A modification to UI would affect all cameras, what is your suggestion?

dvip
You may also want to take a look at this bug.
If you set:
CHDK Settings->OSD Settings->Miscellaneous Values->Show Misc Values [Shoot]
it behaves as:
CHDK Settings->OSD Settings->Miscellaneous Values->Show Misc Values [Always]

I'll check this, it seems to be a bug.

dvip

@nafraf,
My suggestion is that since CAM_EV_IN_VIDEO is useful to control video overexposure and it doesn't crash nor affect the A590is, it is better to leave it there.

Nice to know that you are working on the OSD bug.

blackhole

The A590IS has a tendency to overexpose video.
I think CAM_EV_IN_VIDEO is useful to correct for video overexposure and shouldn't be removed.
It is good to make videos of the moon, stars (with a telescope)... it helps to control overexposure well.

A590 in video mode uses evaluative metering mode and you can not change it.
If you recording stars, 99.9 percent of the scene is black, because the stars as a point sources of light are overexposed. CAM_EV_IN_VIDEO does not respond at dark scenes, in bright scenes gives you just two EV steps what in overexposed scene usually not enough, if at all responds. Enabling "Fast EV Switch" in "Extra Photo Operations" menu gives you exactly what you need in this case.
Another disadvantage is that the CAM_EV_IN_VIDEO you can adjust only during recording.
Fast EV Switch can be adjusted before recording and during recording

dvip

>CAM_EV_IN_VIDEO does not respond at dark scenes

It is not for dark scenes, it is for too bright scenes.

It is useful for overexpose video scenes
in general. And it is fast and easy to access by just pressing
the +/- key during video recording.

reyalp

dvip
>CAM_EV_IN_VIDEO does not respond at dark scenes

It is not for dark scenes, it is for too bright scenes.

It is useful for overexpose video scenes
in general. And it is fast and easy to access by just pressing
the +/- key during video recording.

As developers, the question we are interested in is whether it works correctly on this camera? From the postings in this thread, that isn't clear to me.

dvip

@reyalp, I had more time to look into this now.

It works in the sense that it can decrease exposure while recording video, but it can't
increase exposure (something I never use it for).

The horizontal exposure level that appears on the screen when
you press the +/- button to activate this, never goes passed the middle to increase
exposure, in other words, it never goes into the positive steps that the exposure level displays on the screen.

It is fine with me if it is removed since "Enable Fast EV swit [.]"
can accomplish the same thing while recording video. But it won't
display any horizontal exposure level to indicate the steps of
exposure. However, you do see the screen getting darker/lighter when
you press the up/down buttons.

If it can save some memory or simplify code, it is fine to remove it.

« Previous Page Next Page »