Bug report: || fixed for: A1400, A2500

koshy

1053

« on: 05 / July / 2014, 19:55:37 »

Advertisements

I found that when writing DNG files two out of 32 cameras I looked at in terms of meta data today do not write the UniqueCameraModel meta data field correctly. The other 30 do it just fine. The ones that didn't in my tests are the A1400 and A2500. If it matters my FW versions are: 100b and 100a. I used 1.3 3462.

The A1400 writes an empty string where it should write "Canon PowerShot A1400"

| 24) UniqueCameraModel =
| - Tag 0xc614 (1 bytes, string[1])

The A2500 writes capital letter P where it should write "Canon PowerShot A2500"

| 24) UniqueCameraModel = P
| - Tag 0xc614 (1 bytes, string[1])

« Last Edit: 22 / July / 2014, 10:22:12 by koshy »

Logged

Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)

philmoz

3179

Re: Bug report? A1400, A2500

« Reply #1 on: 05 / July / 2014, 20:07:53 »

Quote from: koshy on 05 / July / 2014, 19:55:37

I found that when writing DNG files two out of 32 cameras I looked at in terms of meta data today do not write the UniqueCameraModel meta data field correctly. The other 30 do it just fine. The ones that didn't in my tests are the A1400 and A2500. If it matters my FW versions are: 100b and 100a. I used 1.3 3462.

The A1400 writes an empty string where it should write "Canon PowerShot A1400"

| 24) UniqueCameraModel =
| - Tag 0xc614 (1 bytes, string[1])

The A2500 writes capital letter P where it should write "Canon PowerShot A2500"

| 24) UniqueCameraModel = P
| - Tag 0xc614 (1 bytes, string[1])

The value for PARAM_CAMERA_NAME for these cameras may be wrong (they both use 4 at the moment).

Go into the 'Debug Parameters' menu (under 'Miscellaneous Stuff').
Set 'Debug data display' to Params.
Set 'PropCase/ParamsData Page' to 0

Exit ALT mode and the camera will display the first 10 param values, look for one with the camera name and note the param number on the left side. If the name is not there then change to page 1, then 2 etc (it should be on the first page).

Post the correct value here please.

Phil.

Logged

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)
g5x (1.00c, 1.01a, 1.01b)

koshy

1053

Re: Bug report? A1400, A2500

« Reply #2 on: 06 / July / 2014, 09:38:18 »

Quote from: philmoz on 05 / July / 2014, 20:07:53

Post the correct value here please.

Phil, I'd love to but I don't have the two cameras on my hands anymore and cannot easily get back at them. I completed the work I needed to do with them and only found this meta data shortcoming in my analysis phase of the aquired data.

Anyway, that means that we are looking for someone else who has an A1400 or A2500 and who would kindly follow the above instructions and post the requested result value here.

Logged

Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)

nafraf

1308

Re: Bug report? A1400, A2500

« Reply #3 on: 06 / July / 2014, 12:00:26 »

For A1400, fixed in trunk Changeset 3493

Logged

koshy

1053

Re: Bug report? A1400, A2500

« Reply #4 on: 12 / July / 2014, 14:39:54 »

Thank you nafraf.
Does anyone have an A2500?

Logged

Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)

nafraf

1308

Re: Bug report? A1400, A2500

« Reply #5 on: 12 / July / 2014, 16:59:03 »

philmoz fixed it for A2500. Changeset 3496. Now PARAM_CAMERA_NAME is detected in firmware.

Logged