A2500 porting thread - page 9 - DryOS Development - CHDK Forum supplierdeeply

A2500 porting thread

  • 157 Replies
  • 53224 Views
Re: A2500 porting thread
« Reply #80 on: 25 / December / 2013, 15:02:53 »
Advertisements
fixed it! how can I get more puglins for this camera? does any plugin work? im looking for a time lapse :C, thanks for everything brother, im not really into this type of things at the moment

Re: A2500 porting thread
« Reply #81 on: 25 / December / 2013, 15:07:23 »
fixed it!
Based on what srsa_4c said,  its not really fixed.  He disabled the part of the CHDK that lets it control exposure.  So what you have is CHDK without a lot of its basic functionality.

Quote
how can I get more puglins for this camera? does any plugin work? im looking for a time lapse :C,
If by "plugins" you mean scripts,  there are plenty listed here : http://chdk.wikia.com/wiki/User_Written_Scripts
« Last Edit: 25 / December / 2013, 15:09:12 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline srsa_4c

  • ******
  • 4450
Re: A2500 porting thread
« Reply #82 on: 25 / December / 2013, 15:22:50 »
fixed it!
Based on what srsa_4c said,  its not really fixed.  He disabled the part of the CHDK that lets it control exposure.  So what you have is CHDK without a lot of its basic functionality.
Fortunately not :) The only impact is that long (>64s) exposures won't be available.

I found a bug: the address of apex2us is wrong, I'll try to find the good one.

Re: A2500 porting thread
« Reply #83 on: 25 / December / 2013, 15:35:28 »
If you want I can test anything you want with my camera, how im going to save the scripts with notepad? is there any special encoding and format?


*

Offline nafraf

  • *****
  • 1308
Re: A2500 porting thread
« Reply #84 on: 25 / December / 2013, 15:49:50 »
I found a bug: the address of apex2us is wrong, I'll try to find the good one.
Maybe this 0xff9ef428?  I updated code in my personal svn.

Re: A2500 porting thread
« Reply #85 on: 25 / December / 2013, 15:52:40 »
how im going to save the scripts with notepad? is there any special encoding and format?
Plain text (UTF-8) is best.
Plain text ASCII is best.

Update :  corrected as per the link below from reyalp
« Last Edit: 25 / December / 2013, 16:02:36 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline srsa_4c

  • ******
  • 4450
Re: A2500 porting thread
« Reply #86 on: 25 / December / 2013, 15:58:43 »
I found a bug: the address of apex2us is wrong, I'll try to find the good one.
Maybe this 0xff9ef428?
Yes. Essentially, this function is what you replace with CHDK's apex2us replacement, the sigfinder's guess is correct. This seems to be the only change for now.

If you want I can test anything you want with my camera, how im going to save the scripts with notepad? is there any special encoding and format?
Use ASCII or ANSI format (naming can vary).

@nafraf: is there a list of things that haven't been tested yet (or are known to fail)?
It would be good to test the movie_status issue too, but I don't know how movie mode can be determined on this cam.

edit: utf-8 removed as recommended format :)
« Last Edit: 25 / December / 2013, 16:29:50 by srsa_4c »

*

Offline reyalp

  • ******
  • 13717
Re: A2500 porting thread
« Reply #87 on: 25 / December / 2013, 15:58:58 »
how im going to save the scripts with notepad? is there any special encoding and format?
Plain text (UTF-8) is best.
ASCII, not UTF-8. They should be the same if you only use ASCII chars, but some programs (including notepad in some cases AFAIK) put a BOM at the start of UTF-8 files, which will confuse the script interpreters.
Don't forget what the H stands for.


Re: A2500 porting thread
« Reply #88 on: 25 / December / 2013, 16:01:47 »
im looking for a time lapse
Incidentally,  there is a simple timelapse script already loaded with CHDK.  Its called interval.lua
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline nafraf

  • *****
  • 1308
Re: A2500 porting thread
« Reply #89 on: 25 / December / 2013, 16:15:59 »
@nafraf: is there a list of things that haven't been tested yet (or are known to fail)?
It would be good to test the movie_status issue too, but I don't know how movie mode can be determined on this cam.
Some features not fully tested:
- RAW capture.
- File counter.
- movie quality control
- camera_set_led()
- JPEG remote capture (rs -jpg)
- Liveview

 

Related Topics