SX260 HS Porting Thread - page 48 - DryOS Development - CHDK Forum

SX260 HS Porting Thread

  • 642 Replies
  • 233462 Views
*

Offline reyalp

  • ******
  • 14128
Re: SX260 HS Porting Thread
« Reply #470 on: 01 / January / 2013, 16:59:20 »
Advertisements
DOF calculator changes the hyperfocal distance too. I'll have to make sure ND is out when I calculate hyperfocal distance. I'm not sure how exact the Av values are, but they would be a good start to figuring out an exposure correction for the shot, around 2 fstops, it looks like.
There should probably be 2 (or more) propcases for AV, one which shows the real aperture based on zoom and iris, and one that reflects the effective aperture with the ND filter.

I'll add CAM_HAS_ND_FILTER back to platform_camera.h for sx240 and sx260.

Quote
The ND filter option in the CHDK menu doesn't do anything. Is there another change that needs to be made?
If set_nd_filter works, I don't see how this would fail. It should be applied when the other overrides are applied. There is "CAM_HAS_NATIVE_ND_FILTER" not sure what that's about.
Don't forget what the H stands for.

*

Offline lapser

  • *****
  • 1093
Re: SX260 HS Porting Thread
« Reply #471 on: 01 / January / 2013, 17:09:49 »
There should probably be 2 (or more) propcases for AV, one which shows the real aperture based on zoom and iris, and one that reflects the effective aperture with the ND filter.
I'll add CAM_HAS_ND_FILTER back to platform_camera.h for sx240 and sx260.
Thanks. I'll do some more experimenting in the script and print the other Av values
Quote
If set_nd_filter works, I don't see how this would fail. It should be applied when the other overrides are applied. There is "CAM_HAS_NATIVE_ND_FILTER" not sure what that's about.
Oops, I had overrides disabled. My full name is Memory Lapser.

With overrides on, the screen darkens in half shoot. Everything works.

[EDIT]
I think CAM_HAS_NATIVE_ND_FILTER means you set it directly with the propcase
Code: [Select]
void shooting_set_nd_filter_state(short v, short is_now)
{
#if CAM_HAS_ND_FILTER
    if ((mode_get()&MODE_MASK) != MODE_PLAY)
    {
        if (is_now)
        {
            if (v==1)
                PutInNdFilter();
            else if (v==2)
                PutOutNdFilter();
#if defined(CAM_HAS_NATIVE_ND_FILTER) && defined(PROPCASE_ND_FILTER_STATE)
            int n = (v==1) ? 1 : 0;
            set_property_case(PROPCASE_ND_FILTER_STATE, &n, sizeof(n));
#endif
        }
        else
            photo_param_put_off.nd_filter=v;
    }
#endif
}
« Last Edit: 01 / January / 2013, 17:15:26 by lapser »
EOS-M3_120f / SX50_100b / SX260_101a / G1X_100g / D20_100b
https://www.youtube.com/user/DrLapser/videos

*

Offline reyalp

  • ******
  • 14128
Re: SX260 HS Porting Thread
« Reply #472 on: 01 / January / 2013, 17:56:08 »
I think CAM_HAS_NATIVE_ND_FILTER means you set it directly with the propcase
According to the camera.h comments, this is for cameras that have ND control in the canon menu. It sets the propcase in addition to calling the function, so I'd guess it's there to update the exif and/or UI state. I think this was something Phil added, so he may be able to shed more light on it.

edit:
CAM_HAS_ND_FILTER is now defined for sx260 and sx240 in both trunk and release branches, will appear in autobuilds 2446 and 2447 respectively.
« Last Edit: 01 / January / 2013, 18:01:47 by reyalp »
Don't forget what the H stands for.

*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: SX260 HS Porting Thread
« Reply #473 on: 02 / January / 2013, 02:14:43 »
I think CAM_HAS_NATIVE_ND_FILTER means you set it directly with the propcase
According to the camera.h comments, this is for cameras that have ND control in the canon menu. It sets the propcase in addition to calling the function, so I'd guess it's there to update the exif and/or UI state. I think this was something Phil added, so he may be able to shed more light on it.

http://trac.assembla.com/chdk/changeset/1884/trunk/core/shooting.c

Fixes a problem when CHDK enables the ND filter; but the camera did not know about it - caused the screen to flicker very badly.

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)

SX260HS .DNG
« Reply #474 on: 10 / January / 2013, 05:00:52 »
Hi,
I am planning to buy the SX260HS camera. The wiki page says that there are few problems to create .DNG in auto mode. Hence, I have a few questons for you

1) Can I create .DNG files in PAMS mode  (as I can now with the CHDK SX230HS. I don't care to shoot RAW in auto)

2) Is there any lens profile available for Lightroom. (I found one for the SX230HS in this forum)

3) Is the video working well?

4) Are there any major problem with the CHDK for this camera?

Thanks


*

Offline msl

  • *****
  • 1280
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
Re: SX260 HS Porting Thread
« Reply #475 on: 10 / January / 2013, 05:45:07 »
1. Yes, only the AUTO mode does not work correctly for RAW/DNG.
2. Yes, https://chdkde.box.com/s/eu46o3etddfh7omz1dql
3. Yes, also unlimited video length.
4. No

msl
CHDK-DE:  CHDK-DE links

Re: SX260 HS Porting Thread
« Reply #476 on: 10 / January / 2013, 06:37:57 »
Hi,

Thanks for the link and answers.

Do you know where I can dowload one or more .DNG files for this camera?
I would like to have a look at them.

I am asking all these question because I have already the CHDK for the Canon SX230HS, and I am very satisfied with. The only thing I don't lke of the SX230HS is the 16:9 screen, which is fine on the SX260HS. So I am eager to upgrade. However I really don't want to give up the excellent .DNG quality of the CHDK software.


Re: SX260 HS Porting Thread
« Reply #477 on: 13 / January / 2013, 04:14:59 »
i start to use this new "firmware" and i find this very useful. Thanks to those who develop this FW.
is it possible to get a stable version instead the "alpha" in the future?
tnx

Re: SX260 HS Porting Thread
« Reply #478 on: 19 / January / 2013, 17:13:25 »
In order to get to the stable versions, you must go through the various alpha and beta stages.  No one is making a living from this and cannot devote their time and energies exclusively to this.  Be grateful for what you get and give feedback, report bugs and ask how you can help, if you want to speed things up.

*

Offline reyalp

  • ******
  • 14128
Re: SX260 HS Porting Thread
« Reply #479 on: 19 / January / 2013, 17:48:58 »
In order to get to the stable versions, you must go through the various alpha and beta stages.  No one is making a living from this and cannot devote their time and energies exclusively to this.  Be grateful for what you get and give feedback, report bugs and ask how you can help, if you want to speed things up.
The alpha/beta status is pretty arbitrary. Since we (the core developers) don't have most of the cameras, we rely on the porters and users to let us know when the status should be changed. If there are no major outstanding issues on the this camera, we can change the status to beta or final.
Don't forget what the H stands for.

 

Related Topics


SimplePortal © 2008-2014, SimplePortal