CHDKPTP - PC Remote Control Performance Analysis - page 4 - RAW Shooting and Processing - CHDK Forum

CHDKPTP - PC Remote Control Performance Analysis

  • 465 Replies
  • 50211 Views
*

Offline reyalp

  • ******
  • 11991
Re: CHDKPTP - PC Remote Control Performance Analysis
« Reply #30 on: 01 / September / 2012, 01:04:36 »
Advertisements
Can you give me a *full* build of TEST 2 ie TEST 2a, I will reformat and try it that way?
This doesn't make any sense. The "test 2" I posted is a complete build. All the other stuff in the "full" packages is just data files you could get from any CHDK build. All you need to do to get a "full" build is unzip the stock build onto the card, then unzip the test build on top of that, overwriting any files with the same name.

The only differences in that build are some functions related to the viewport and bitmap. Compiletime options may also be slightly different.

I'd guess that there is something up with that card, either something on the card that is confusing the canon software, or something wrong with the filesystem or card itself.

I'd start by re-formatting the card and re-installing.

edit:
Update on the palette situation. This camera (DryOS R39) appears different from both the older (e.g. D10, DryOS R31) and newer (e.g. G12, Dryos R45) cameras which have the palette found, so getting the correct palette doesn't look like it will just be a matter of finding equivalent code on some known camera. I found code that is pretty similar to D10, but according to your report it doesn't work.
« Last Edit: 01 / September / 2012, 01:10:19 by reyalp »
Don't forget what the H stands for.

*

Offline SticK

  • *****
  • 779
Re: CHDKPTP - PC Remote Control Performance Analysis
« Reply #31 on: 01 / September / 2012, 01:24:16 »
Quote "I'd start by re-formatting the card and re-installing."

That's what I just did // reformat // make bootable // stock build (works like SX110) // TEST-2 // now it looks normal.

I think I know where the problem could have happened .. when I tried to download multiple files from the FILES tab in CHDKPTP, I got a bunch of errors (earlier this evening) but, I cannot be sure.

Why would this happening?  The proliferation of directories?  Attached.

*

Offline SticK

  • *****
  • 779
Re: CHDKPTP - PC Remote Control Performance Analysis
« Reply #32 on: 01 / September / 2012, 01:30:57 »
HOLD YOUR HORSES!  ... I just connected to CHDKPTP and the palette *looks* OK.  Allow me to check it out further.

*

Offline SticK

  • *****
  • 779
Re: CHDKPTP - PC Remote Control Performance Analysis
« Reply #33 on: 01 / September / 2012, 01:56:38 »
PALETTE ... there is slight tonal difference in two of the rows ie a khaki row in camera LCD appears more brick-colored in CHDKPTP, but I think no one would ever notice overall.  To dig into that I expect would be diminishing returns vs time put in.

Subjectively the UI looks perfect so far // I think you got this one right on the money.

Now ?  I hope nothing I do using CHDKPTP happens to corrupt the directory structure.

What do you think of getting at the missing buttons on CHDKPTP?  For now, there is no <alt> button for example.  And the lens ring control?





*

Offline reyalp

  • ******
  • 11991
Re: CHDKPTP - PC Remote Control Performance Analysis
« Reply #34 on: 01 / September / 2012, 02:00:17 »
Why would this happening?  The proliferation of directories?  Attached.
I made several suggestions about things that might be related in this post: http://chdk.setepontos.com/index.php?topic=8613.msg90129#msg90129

Did these "strange directories" reappear in your fresh install ? If so, what sequence of events happened between the fresh install and the directories appearing (did you shoot pictures, how many, was CHDK raw or dng enabled ?)

If this happens again
Quote
when I tried to download multiple files from the FILES tab in CHDKPTP, I got a bunch of errors (earlier this evening)
It would be helpful to copy the specific errors.
Don't forget what the H stands for.

*

Offline SticK

  • *****
  • 779
Re: CHDKPTP - PC Remote Control Performance Analysis
« Reply #35 on: 01 / September / 2012, 02:16:42 »
Quote "Did these "strange directories" reappear in your fresh install ?"

So far I've only got one of the "strange directories" with all of few JPGs in it.  Could it be a Canon cryptic date code?  Tomorrow I start the imaging tests over again and will follow carefully.

Quote " (did you shoot pictures, how many, was CHDK raw or dng enabled ?)"

That could be a possibility, but I didn't notice there was a problem until much much later.

Quote "It would be helpful to copy the specific errors."

Something comes up I will get you copy so long as is doesn't distract from the technical I am focusing on now.

*

Offline philmoz

  • *****
  • 3116
    • Photos
Re: CHDKPTP - PC Remote Control Performance Analysis
« Reply #36 on: 01 / September / 2012, 02:28:02 »
Quote "I'd start by re-formatting the card and re-installing."

That's what I just did // reformat // make bootable // stock build (works like SX110) // TEST-2 // now it looks normal.

I think I know where the problem could have happened .. when I tried to download multiple files from the FILES tab in CHDKPTP, I got a bunch of errors (earlier this evening) but, I cannot be sure.

Why would this happening?  The proliferation of directories?  Attached.

DISKBOOT.BIN does not belong in the DCIM directory so delete that.

The S90 uses date based folder naming for image directories which is where the 111___08, 112___08, directories are coming from. Older cameras used the 111CANON, 112CANON naming format which will also be used by CHDK in some cases. The 08 is the month number so you have the camera set to roll over to new directories each month, you can also set it to use daily directory rollover.

Either disable CHDK RAW saving altogether (the S90 has built in Canon RAW) or enable the CHDK option to save the RAW/DNG file in the same directory as the JPEG.

If you have already enabled the CHDK option to save the RAW/DNG files with the JPEG's then the port is broken and is not correctly implementing the date based folder naming - in this case disable CHDK RAW until someone gets around to fixing it.

I think what is happening is you don't have the CHDK option enabled to save the RAW/DNG with the JPEG. When you take a shot CHDK takes the latest folder number, e.g. 111, and created the 111CANON directory. On the next shot the firmware sees that both 111___08 and 111CANON exist, gets confused so increments the folder number to 112 and creates 112___08. Then CHDK creates 112CANON and the cycle continues.

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)

*

Offline SticK

  • *****
  • 779
Re: CHDKPTP - PC Remote Control Performance Analysis
« Reply #37 on: 01 / September / 2012, 02:46:55 »
TECHNICAL COMPARISON S90 vs SX110  -- Dark performance.

Before I close my day as it is 2:30 am, here is a sample of some the great results coming from the S90 optoelectronics.

Both these images were taken at Tv=64s ISO 1600 (the S90 can go to 3200 - not shown).  Dark subtract was disabled so you can see the relative noise performance and the "amplifier glow" artifact in the upper left.

The evidence shows amplifier glow as being sufficiently low (in both cameras) that it can be mitigated with dark subtract without great impact on dynamic range.  In the S90, the artifact is nonetheless confined tightly to the corner anyway.

In a previous test I determined that the S90 has an approximately 3 f-stop better absolute signal performance compared to the SX110.  However, absolute noise has to be taken into consideration, and seen here actually "improves" that performance further by a conservative 2 f-stops (difference in the noise brightness between the two images).  So it is safe to say that signal-to-noise ratio (SNR) performance of the S90 versus the S50 in the instrument at present is: the 7 f-stops from the previous absolute signal calculation *added with* this 2 f-stops, resulting in at least a 9 f-stop improvement.

This is dramatic.


*

Offline SticK

  • *****
  • 779
Re: CHDKPTP - PC Remote Control Performance Analysis
« Reply #38 on: 01 / September / 2012, 02:57:56 »
@philmoz

Quote "DISKBOOT.BIN does not belong in the DCIM directory so delete that"

Yes, that was the result of the directory corruption I expect // I reformatted and reinstalled the STOCK build followed by an overwrite with TEST-2.  I will start using CHDKPTP (and RAWs) at full power tomorrow // we'll see what happens.

Quote "... The 08 is the month number so you have the camera set to roll over to new directories each month, you can also set it to use daily directory rollover."

I did make sure that I had it set to the monthly rollover and was wondering why I got so many in one day.

Quote "I think what is happening is you don't have the CHDK option enabled to save the RAW/DNG with the JPEG. "

I am vigilant with those settings and with the SX110 never had a confused state in the directory structure.  In this case, the same files were in fact repeating from directory to directory.  Now that I know it can happen I'll keep an eye and trap culprit before I lose sight of what I did to make it occur.

Thank you for this clear explanation. 

 

*

Offline SticK

  • *****
  • 779
Re: CHDKPTP - PC Remote Control Performance Analysis
« Reply #39 on: 01 / September / 2012, 10:34:39 »
Hint for the SD CORRUPTION PROBLEM ?

My (present) corruption test is simple:  When I power ON (power SW) the camera untethered +or+ if I go COLD to PLAY (PLAY SW), I should see the last JPG.

Fresh installation from fresh format STOCK CHDK + TEST-2. RAW=OFF for all tests and has never been enabled. 

"Tethered" here means connected with CHDKPTP and running.

Here's what I did ...

a) Camera untethered, shoot from camera, corruption test: all's fine.

b) Tether, shoot from CHDKPTP, verify FILES tab, looks OK (only one Canon directory corresponding to this month // all JPG files there, no spurious filenames/directories).

c) Untether, corruption test: all's fine.

d) Untethered, run Create badpixel.bin (for DNG 1.1)

e) ??==>> Creation OK (4861 bad for 10 Mpx which is very acceptable)

f) ??==>> Corruption test: Does not pass // dark camera LCD (there is no "No Image" message, just dark).

g) Tether and verify FILES tab: directory structure *looks* OK as before (see attachment), ie nothing strange like duplicate filenames, and badpixel.bin is where it should be ...but ... "absence of evidence is not evidence of absence."

h) I am halting all further tests

I have a *feeling* the SD already corrupted because the unusual power-ON behavior.  Waiting for your feedback to proceed.
« Last Edit: 01 / September / 2012, 11:43:43 by SticK »

 

Related Topics