IXUS160/ELPH160 Porting attempt - page 27 - DryOS Development - CHDK Forum supplierdeeply

IXUS160/ELPH160 Porting attempt

  • 497 Replies
  • 185640 Views
Re: IXUS160/ELPH160 Porting attempt
« Reply #260 on: 02 / November / 2015, 17:51:37 »
Advertisements
Eyh guys, since two days now i've installed this CHDK on two ixus 160 cameras. I used a 4 GB and 16 Gb Sd cards.
I don't have lot of returns, to do any problem, certain time the OSd is not transparent but it return back to the normal few seconds later.
I tried to shoot in raw and dng, with and without timelapse scripting, but anything bugged.

I cross the fingers for the next.

I'll post a task on the forum about the USB video signal cable that i want to build for having FPV mode and duplicate image on a small tv.


Re: IXUS160/ELPH160 Porting attempt
« Reply #261 on: 02 / November / 2015, 18:41:50 »
certain time the OSd is not transparent but it return back to the normal few seconds later.
This is the same for all versions of CHDK on every camera.   The Canon firmware is not aware that CHDK is writing to the screen and so it sometimes overwrites the information that CHDK is trying to display.  This tends to be worse in shooting mode (vs playback / shot review) and is especially bad if you have a focus tracking window active.

While there might be a way for CHDK to tell the Canon firmware not to update the display,   so far nobody has found a reliable method to do so.

Quote
I tried to shoot in raw and dng, with and without timelapse scripting, but anything bugged.
Does this mean everything is working?
Ported :   A1200    SD940   G10    Powershot N    G16

Re: IXUS160/ELPH160 Porting attempt
« Reply #262 on: 03 / November / 2015, 03:59:17 »
Hi,

When I run this script on 1.4.0-4273:
Code: [Select]
print('start')
set_mf(1)
print('after mf 1')
sleep(1000)
print('before mf 0')
set_mf(0)
print('after mf 0')
My IXUS160 crash @ set_mf(0). It is no happening on another camera (A2500).
ROMLOG attached.

I found it trying to figure out if there are some interferences between set_md_filter() and set_focus()
after some bad focus @ infinity doing timelapses with a modified YASS4.LUA to always force the ND filter.

Re: IXUS160/ELPH160 Porting attempt
« Reply #263 on: 04 / November / 2015, 06:51:41 »
Hi, everybody!

I have two questions that are struggling me:

1) For my Canon Ixus 160, is there any chance to give a separate and constant name for each camera to be displayed when it connected to the PC? Something like C101, C102, C103 etc.

2) Is there any chance to add to each photo file name name of the camera where shoot took place?

So, standard photo file name is IMG_0019.JPG, how to give it a name like C101_IMG_0019.JPG, or C102_IMG_0019.JPG if the photo from another camera.

Thanks in advance!


IXUS160/ELPH160 Porting attempt
« Reply #264 on: 04 / November / 2015, 07:22:34 »
1) For my Canon Ixus 160, is there any chance to give a separate and constant name for each camera to be displayed when it connected to the PC? Something like C101, C102, C103 etc.
You mean something like this :  http://chdk.setepontos.com/index.php?topic=11631.0

Or are you thinking more about the issues of knowing which camera is which when you are using CHDKPTP?

Edit :typo
« Last Edit: 04 / November / 2015, 09:59:29 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline srsa_4c

  • ******
  • 4437
Re: IXUS160/ELPH160 Porting attempt
« Reply #265 on: 04 / November / 2015, 12:55:32 »
When I run this script on 1.4.0-4273:
(...)
My IXUS160 crash @ set_mf(0). It is no happening on another camera (A2500).
ROMLOG attached.
I've been able to reproduce this on my ixus150. What I found is: the above sequence doesn't cause a crash if you half press the shutter at least once before you issue set_mf(0).
Technical explanation: it appears some live view related callback routine(s) do not get set after using set_mf(1), which causes asserts in various places. These script commands use the SS.MFOn and SS.MFOff event procedures currently.

Suggestions:
- half press or shoot between set_mf(1) and set_mf(0)
- try set_aflock() instead

The script doesn't seem to make a lot of sense to me in its current form.



Back to this issue
I'm experiencing a random shutdown with the lens out when simply taking a picture with CHDK loaded.
Pierre has since reported that re-installing the same release to a clean card solved the problem. Guess it would be beneficial to add integrity check to the CHDK core and modules...
« Last Edit: 04 / November / 2015, 13:03:30 by srsa_4c »

Re: IXUS160/ELPH160 Porting attempt
« Reply #266 on: 04 / November / 2015, 16:13:45 »
@waterwingz : yes for my 2 ixus any problem, any bug, that's perfect !

Re: IXUS160/ELPH160 Porting attempt
« Reply #267 on: 09 / November / 2015, 21:09:22 »
Can I have the link for latest IXUS 160 CHDK firmware...please


*

Offline srsa_4c

  • ******
  • 4437
Re: IXUS160/ELPH160 Porting attempt
« Reply #268 on: 10 / November / 2015, 18:00:32 »
Can I have the link for latest IXUS 160 CHDK firmware...please
Sent you a link along with the usual warning.

*

Offline axman

  • ***
  • 145
Re: IXUS160/ELPH160 Porting attempt
« Reply #269 on: 12 / November / 2015, 17:58:06 »
May I have the link for latest IXUS 160 CHDK firmware, please? 
(2) brand new cameras in-hand. 
I don't care if they brick - I understand and accept the risk.
Thanks.

 

Related Topics