ELPH300HS aka IXUS220HS - Porting Thread - page 82 - DryOS Development - CHDK Forum  

ELPH300HS aka IXUS220HS - Porting Thread

  • 899 Replies
  • 399366 Views
Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #810 on: 21 / May / 2013, 19:17:35 »
Advertisements
Thank you natraf!

I've attached two photos of play menu when different set is present. There should be info about how many shots is left, iso value should be seen, but it's better than last time -> zebra is seen :)


Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #811 on: 21 / May / 2013, 19:18:56 »
And two photos of play and rec menu.

The help text isn't seen in play menu. But other than thet everything looks OK.

What is recommended fps rate for live view?

*

Offline reyalp

  • ******
  • 14082
Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #812 on: 21 / May / 2013, 21:35:12 »
What is recommended fps rate for live view?
There is no specific recommended rate.

You should set the target rate to something lower than the maximum rate your USB and display system can sustain, otherwise the application may become unusable under linux. A lower frame rate will also put less load on the camera.
Don't forget what the H stands for.

*

bugmenot

Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #813 on: 31 / May / 2013, 13:04:32 »
Where I can find FASTEST working motion capture script and settings for ELPH300? Default is too slow react for capture lightning. I used IXUS85 and settings from MDFB-080914 and it was MUCH faster
« Last Edit: 31 / May / 2013, 13:06:11 by bugmenot »


Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #814 on: 31 / May / 2013, 13:58:35 »
Where I can find FASTEST working motion capture script and settings for ELPH300? Default is too slow react for capture lightning. I used IXUS85 and settings from MDFB-080914 and it was MUCH faster
MDFB-080914 is widely regarded as the fastest script available  (http://chdk.setepontos.com/index.php/topic,471.msg21328.html#msg21328 ).

As far as setting go,  you have to experiment.   Newer cams seem to be slower than older cam,  you can do some testing using information in this thread : http://chdk.setepontos.com/index.php?topic=9366.msg96633#msg96633
Ported :   A1200    SD940   G10    Powershot N    G16

Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #815 on: 01 / June / 2013, 06:43:18 »
I read about lua script engine faster than uBasic, in this case it does not help much, does it?
I think default MD script has messed up parameters or dont work properly with it settings,
I had try MDFB-080914 (VideoButtonModels) and had quick lack

Cameras was on different sectors so no right comparison, but anyway I dont see big improvements, despite CMOS and newer CPU in elph300

This cloud was rich of horisontal lightings.

with eelph300



ixus85 MDFB-080914



and in the end capture of ball lightning (exposure 1s)



Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #816 on: 01 / June / 2013, 07:44:55 »
I read about lua script engine faster than uBasic, in this case it does not help much, does it?
The default CHDK script yield settings for Lua allow it run faster than uBASIC.  However, this can be changed under script countrol : http://chdk.wikia.com/wiki/Script_commands#set_yield for uBASIC or Lua.

Regardless of that,  both uBASIC and Lua call the same MD script function, which is written in "C" and they will thus have the same motion detection capture performance.

Quote
I think default MD script has messed up parameters or dont work properly with it settings,
The default settings need to be tuned for each application and specific camera.  For example, not everyone wants to photograph lightening.

Quote
I had try MDFB-080914 (VideoButtonModels) and had quick lack
Some very nice shots!
Ported :   A1200    SD940   G10    Powershot N    G16

Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #817 on: 02 / June / 2013, 09:48:26 »
Quote
The default settings need to be tuned for each application and specific camera
I read this simple script and see it has no check of (Trigger Delay<measure_interval) , which may cause continues shooting if novice does not understand what means "Trigger Delay". Also why default script (that is first to use by novice) does not show review of all capabilities (that may be adjusted to tasks by choosing more special scripts later)?


Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #818 on: 02 / June / 2013, 10:15:21 »
I read this simple script and see it has no check of (Trigger Delay<measure_interval) , which may cause continues shooting if novice does not understand what means "Trigger Delay".
I don't believe that matters.  Trigger delay is just an intiial delay time that the script spends after md_detect_motion() is called.  As the the MD code scans the LCD display buffer looking for motion, this give the display a little time to "settle".   The measure_interval parameter determines how often the display buffer is scanned after the Trigger Delay has completed.   The length of one has no effect on the other.

Quote
Also why default script (that is first to use by novice) does not show review of all capabilities (that may be adjusted to tasks by choosing more special scripts later)?
Those eight scripts were designed to be as short as possible and still usable.  But at the last update, I added the two user  @parameters that actually matter when adjusting MD response as people seem to be having a hard time with it.  After that its up to the user to decide whether to modify those scripts or download better ones.
Ported :   A1200    SD940   G10    Powershot N    G16

Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #819 on: 02 / June / 2013, 17:51:40 »
I just started with CHDK on my Elph 300 HS. Really good so far. Being able to shoot Raw with this tiny camera is great.

Has anyone created a Lens Profile to use in Lightroom/Photoshop?  I searched the Adobe Lens Profile Downloader tool but none were available there.

Thanks.

 

Related Topics