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

IXUS160/ELPH160 Porting attempt

  • 497 Replies
  • 174443 Views
*

Offline adong

  • **
  • 66
Re: IXUS160/ELPH160 Porting attempt
« Reply #100 on: 15 / June / 2015, 03:44:52 »
Advertisements
4th possibility: deal with it.  :D

I may fiddle with it some more, but for now I'm fixing zebra + edge overlay.

*

Offline srsa_4c

  • ******
  • 4426
Re: IXUS160/ELPH160 Porting attempt
« Reply #101 on: 15 / June / 2015, 19:01:19 »
I may fiddle with it some more, but for now I'm fixing zebra + edge overlay.
Okay, no hurry.
I'd like to correct my earlier statement: sub_FF99C0E4 seems to assemble the new JPEG file name and schedule the file for writing. I'm fairly certain that the file counter is updated inside. ... somewhere ...
You may try to move the raw hook behind that call (right before loc_FFAD7E84), or, if that's too late, perhaps somewhere inside sub_FF99C0E4.

*

Offline adong

  • **
  • 66
Re: IXUS160/ELPH160 Porting attempt
« Reply #102 on: 16 / June / 2015, 03:22:59 »
Okay thanks, I'll try that once I get back home.

Re: IXUS160/ELPH160 Porting attempt
« Reply #103 on: 16 / June / 2015, 15:55:54 »
Ixus 160 works good with CHDK, but there is one thing that I forget: 20MP camera requires about 4 seconds for write RAW to memory card.

I'm using Transcend 300x card(TS8GSDU1) that should support ~25MB/s write speed, but Benchmark reports 10958 Kb/s only for Write(RAW). Is there any sense to find 600x card, or Ixus hardware limits write speed to 10MB/s ? Are there any other ways how to make RAW shoot faster ? Probably, disable to create jpeg ? I found only one good way yet - to use remoteshoot for transfer RAW directly to computer.


*

Offline adong

  • **
  • 66
Re: IXUS160/ELPH160 Porting attempt
« Reply #104 on: 16 / June / 2015, 16:07:34 »
Moving the raw hook right before loc_FFAD7E84 works.

Re: IXUS160/ELPH160 Porting attempt
« Reply #105 on: 16 / June / 2015, 16:31:57 »
Moving the raw hook right before loc_FFAD7E84 works.
Yah!

Ixus 160 works good with CHDK, but there is one thing that I forget: 20MP camera requires about 4 seconds for write RAW to memory card.
That sounds consistent with what I have experienced - roughly 2 seconds per 10Mb RAW image size (or 4 seconds for 20MB)

Quote
Are there any other ways how to make RAW shoot faster ?
The shooting is not the problem - it's the writing to the SD card that is "slow".

Quote
Probably, disable to create jpeg ?
We don't know how to do that.

Quote
I found only one good way yet - to use remoteshoot for transfer RAW directly to computer.
That does not save the 20MB of data to the SD card so of course it's faster.
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline reyalp

  • ******
  • 13454
Re: IXUS160/ELPH160 Porting attempt
« Reply #106 on: 16 / June / 2015, 16:51:13 »
Quote
Probably, disable to create jpeg ?
We don't know how to do that.

Quote
I found only one good way yet - to use remoteshoot for transfer RAW directly to computer.
That does not save the 20MB of data to the SD card so of course it's faster.
I wouldn't particularly expect the camera USB interface to be faster than the SD.

Remote shoot does indeed disable jpeg, and this could conceivably made an option outside of remoteshoot. However, this only skips saving the file, not all the processing. Since camera jpegs are typically only a few MB, this is unlikely to be a big win, and would remove the ability to preview. You could always switch to 640x480 jpegs to get negligrable write time.
Don't forget what the H stands for.

Re: IXUS160/ELPH160 Porting attempt
« Reply #107 on: 16 / June / 2015, 21:13:31 »
I wouldn't particularly expect the camera USB interface to be faster than the SD.
Yet that's what alex73 reported.

Quote
Remote shoot does indeed disable jpeg, and this could conceivably made an option outside of remoteshoot. However, this only skips saving the file, not all the processing. Since camera jpegs are typically only a few MB, this is unlikely to be a big win, and would remove the ability to preview. You could always switch to 640x480 jpegs to get negligrable write time.
I suppose it would then be easy to add a  Save JPG [ * ] menu item to the RAW menu?
Ported :   A1200    SD940   G10    Powershot N    G16


*

Offline reyalp

  • ******
  • 13454
Re: IXUS160/ELPH160 Porting attempt
« Reply #108 on: 16 / June / 2015, 23:57:40 »
I suppose it would then be easy to add a  Save JPG [ * ] menu item to the RAW menu?
It shouldn't be super hard, but I'd want to see some measurable benefit first. The write time for a minimum size and/or quality jpeg should be minimal, and using that you get a review image and avoid other various weirdness with the filewrite hook.

If we could stop the camera from doing the jpeg processing at all, that might provide more gain, but it would involve new platform specific code and reverse engineering.
Don't forget what the H stands for.

Re: IXUS160/ELPH160 Porting attempt
« Reply #109 on: 17 / June / 2015, 01:43:19 »
Hi reyalp.

If we could stop the camera from doing the jpeg processing at all, that might provide more gain, but it would involve new platform specific code and reverse engineering.

I agree that there is no sense to disable jpeg processing for shooting because transfer time is enough small for 640x480. And looks like remote shooting will be good solution for me. 640x480(or 2048x1536) is good for preview. Remote shooting is faster because USB speed is 20MB/s instead 10MB/s for card writing.

But just for understand process better: usually(without RAW saving) Ixus 160 able to shoot 0.8 photos per second(by Canon specification). But "shoot" process is very fast - 1/60 of seconds. What is happen for 1 second after that ? As far as I understand, it's conversion to JPEG. In this case, if we use JPEG+RAW, time for full process is just a sum from JPEG process and RAW saving. If JPEG+RAW requires 4 seconds for save, will this time be 3 seconds in case to disable JPEG ?

 

Related Topics