IXUS160/ELPH160 Porting attempt - page 43 - DryOS Development - CHDK Forum  

IXUS160/ELPH160 Porting attempt

  • 497 Replies
  • 192492 Views
*

Offline c_joerg

  • *****
  • 1231
Re: IXUS160/ELPH160 Porting attempt
« Reply #420 on: 22 / March / 2016, 05:38:24 »
Advertisements
The number in the manual just tells you the effective f-stop at the minimum and maximum zoom positions. Changing the zoom position changes the lens opening size and thus the reported f-stop.

Yes of courcse…
I got the 3.2 in wide angle and the 6.9 in tele.
But what does the 9.0 in wide and 20.0 in tele mean?
M100 100a, M3 121a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd

Re: IXUS160/ELPH160 Porting attempt
« Reply #421 on: 22 / March / 2016, 11:17:10 »
The number in the manual just tells you the effective f-stop at the minimum and maximum zoom positions. Changing the zoom position changes the lens opening size and thus the reported f-stop.
Yes of courcse… I got the 3.2 in wide angle and the 6.9 in tele. But what does the 9.0 in wide and 20.0 in tele mean?
I don't know.  It seems like it's too big a jump to be just from an ND filter.  Those are typically the equivalent of three f-stops.   

Looking at the DPReview article for the camera, it does not appear to have an adjustable aperture.

Sometimes the camera vendors play games with quoting some lens specifications in terms of "35mm equivalent" values. Might be something to do with that?
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline c_joerg

  • *****
  • 1231
Re: IXUS160/ELPH160 Porting attempt
« Reply #422 on: 22 / March / 2016, 12:31:54 »
I don't know.  It seems like it's too big a jump to be just from an ND filter.  Those are typically the equivalent of three f-stops.   

Looking at the DPReview article for the camera, it does not appear to have an adjustable aperture.

Sometimes the camera vendors play games with quoting some lens specifications in terms of "35mm equivalent" values. Might be something to do with that?

Yes, that’s the ND Filter. I checked it with isoinc and the ND has 3 steps. But when I set the ND with CHDK, this didn’t affect the EXIF data.
And from 3.2 to 9 and from 6.9 to 20 are nearly 3 steps.
When I point the camera near the sun, then I see that the aperture on the screen changes from 3.2 to 9. And this is seen in the EXIF as well.
I hoped I had a iris as well to get longer exposure for time-lapse but I’m happy with the cam and you can’t have everything….
« Last Edit: 22 / March / 2016, 13:04:30 by c_joerg »
M100 100a, M3 121a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd

*

Offline c_joerg

  • *****
  • 1231
Re: IXUS160/ELPH160 Porting attempt
« Reply #423 on: 23 / March / 2016, 03:31:46 »
I’m not sure if the right place to post here. But feel free to move it.

This might be interesting for other user:
I did some investigation with my IXUS160 and it looks like, that the noise reduction starts already on an exposure time around 1/7s. Typically on my other cams is > 1s.

I run a timelapse script (rawopint). The exposure time goes from approx. 0.02s to 2s. The sleep in the plot shows you how long the script slept between shots.  If the noise reduction is ‘on’, sleep makes already a jump on an exposure time from 1/7s (upper plot). The lower plot shows a run with noise reduction ‘off’. 
M100 100a, M3 121a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd


Re: IXUS160/ELPH160 Porting attempt
« Reply #424 on: 26 / March / 2016, 08:40:19 »
I would like to try slowing down the movie frame rate.
Using _EngDrvRead(0xC0F06014) to read the shadow RAM crashes the camera.
Does anyone know the correct value to use with _EngDrvRead() ?


thanks
Zweistein

Re: IXUS160/ELPH160 Porting attempt
« Reply #425 on: 26 / March / 2016, 11:58:06 »
I would like to try slowing down the movie frame rate.
Using _EngDrvRead(0xC0F06014) to read the shadow RAM crashes the camera.
Does anyone know the correct value to use with _EngDrvRead() ?
You might check with the people over at the SDM Yahoo Groups site  (or at stereoforum.org).  IIRC they use that call for their 3D video sync code.  Unfortunately,  the current SDM source code is not available so it's a bit hard for  us to help you with that here.

Ported :   A1200    SD940   G10    Powershot N    G16

Re: IXUS160/ELPH160 Porting attempt
« Reply #426 on: 26 / March / 2016, 12:32:45 »
OK, I have just tried installing SDM for the S95 and in the Welcome pages it says the source code is available via email on request.
 
The IXUS160 does not seem to be supported.


greetings
Zweistein

Re: IXUS160/ELPH160 Porting attempt
« Reply #427 on: 26 / March / 2016, 12:47:41 »
OK, I have just tried installing SDM for the S95 and in the Welcome pages it says the source code is available via email on request.
That's good to know.  Did you try making that request?  It would be interesting to see how  _EngDrvRead(0xC0F06014) is being used. 

The original discussion about this can be found here :  testing sync among more cameras

Quote
The IXUS160 does not seem to be supported.
Typically the SDM project can only support a camera once they "import" the essential code from the CHDK project.  The IXUS160 port is fairly new so perhaps they have not found time (or user interest) to support it yet?
Ported :   A1200    SD940   G10    Powershot N    G16


*

Offline srsa_4c

  • ******
  • 4450
Re: IXUS160/ELPH160 Porting attempt
« Reply #428 on: 26 / March / 2016, 13:08:45 »
Using _EngDrvRead(0xC0F06014) to read the shadow RAM crashes the camera.
Can't imagine how that would happen. The address delivered by the sigfinder is correct.

OK, I have just tried installing SDM for the S95 and in the Welcome pages it says the source code is available via email on request.
That's good to know.  Did you try making that request?
I'd be fairly surprised if "they" actually shared their source with anyone.

Re: IXUS160/ELPH160 Porting attempt
« Reply #429 on: 26 / March / 2016, 13:27:54 »
Quote
Did you try making that request?

No, as the IXUS160 is not supported,  but the original information by 'funnel'  is here :-
 
https://chdk.setepontos.com/index.php?topic=7938.0
 
He explains how the DIGIC address 0xC0F06014 is used and that it comes from information provided by MagicLantern.
 
I guess that address is not correct for IXUS160  ........  for some reason.


greetings
Zweistein

 

Related Topics