Checking modemap table on various cameras: 0 to go || 18 checked || 0 completed - page 3 - General Discussion and Assistance - CHDK Forum  

Checking modemap table on various cameras: 0 to go || 18 checked || 0 completed

  • 41 Replies
  • 6936 Views
*

Offline koshy

  • *****
  • 1037
Re: Checking modemap table on various cameras: 17 to go || 2 completed
« Reply #20 on: 13 / August / 2014, 19:20:55 »
Advertisements
The icon is for "Night Portrait Mode." As to whether this camera officially supports "Night Portrait Mode".. no idea, you would need to download the manual from the Canon website and check. I had a quick look, but I couldn't find any reference to it...
Thanks. That's exactly what it does. "Night Portrait Mode: Night portrait mode is for taking a very specific type of picture: at night, with a flash and using a tripod. Night mode attempts to bring out the background lights that often are lost when using flash photography at night. It's important to note that if you don't use a tripod with night mode, your photos are likely to end up blurry." It's available on A1100 by mode number entry and it works. It sets the flash to on and exposure to 1'' in that mode.
... though it does refer to a Night Snapshot mode.. with a slightly different icon.
That is on the mode dial and can be selected normally. The portrait one is not to be found on the cam itself.
.. and as for the camera crashing... you would need to check the camera logs to see why...
O.k. I'm attaching it for study.
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...)

*

Offline koshy

  • *****
  • 1037
Re: Checking modemap table on various cameras: 17 to go || 2 completed
« Reply #21 on: 13 / August / 2014, 19:27:39 »
OK, A2100: (In all of this I am using the  CHDK/scripts/test/setmode.lua)

// Mode 16390 in firmware => Long Shutter (icon attached)
Pressing Funct button on camera in 16390 => crash

// Current modemap entry not found in firmware - MODE_LONG_SHUTTER        32774
setting mode 32774 actually gives us 1'' exposure, too ?! But displays the Auto Icon.
Pressing Funct button on camera in 32774 => crash

I'm attaching exif dumps of two photos taken in 16390 and 32774.

// Mode 2598 in firmware => video mode (accessed normaly via mode dial on cam)

// Current modemap entry not found in firmware - MODE_VIDEO_COMPACT        2602

trying to set 2602 on cam works, also gets us to video mode

I recorded 5 sec in either 2598 and 2602 and I can't tell the difference.
What is MODE_VIDEO_COMPACT supposed to do?
Pressing Funct button on camera in 2602 => crash

// Current modemap entry not found in firmware - MODE_VIDEO_STD            2600
trying to set 2600 => crash
« Last Edit: 13 / August / 2014, 19:33:30 by koshy »
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...)

*

Offline koshy

  • *****
  • 1037
Re: Checking modemap table on various cameras: 17 to go || 2 completed
« Reply #22 on: 13 / August / 2014, 19:35:51 »
Pressing Funct button on camera in 16390 => crash
Pressing Funct button on camera in 32774 => crash
ROMLOGs enclosed.
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...)

*

Offline koshy

  • *****
  • 1037
Re: Checking modemap table on various cameras: 15 to go || 4 completed
« Reply #23 on: 13 / August / 2014, 20:15:31 »
A420:

// Mode  3614 in firmware but not in current modemap
// Mode  3615 in firmware but not in current modemap
// Mode  3616 in firmware but not in current modemap
// Mode  3618 in firmware but not in current modemap
Setting all of these crashes the camera. ROMLOGS are attached.

// Current modemap entry not found in firmware - MODE_VIDEO_STD            3613
This one is correct. It is what one gets for the prop when using the camera mode dial.
It also works via CHDK/scripts/test/setmode.lua

Is the FW dump the above is derived from correct?
I posted a fresh dump of A420 FW 100B here:
http://chdk.setepontos.com/index.php?topic=11818
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...)


*

Offline koshy

  • *****
  • 1037
A430:

// Mode  3614 in firmware but not in current modemap
// Mode  3615 in firmware but not in current modemap
// Mode  3616 in firmware but not in current modemap
// Mode  3618 in firmware but not in current modemap
Setting all of these crashes the camera. ROMLOGS are attached.

// Current modemap entry not found in firmware - MODE_VIDEO_COLOR_SWAP     2592
// Current modemap entry not found in firmware - MODE_VIDEO_COLOR_ACCENT   2591
// Current modemap entry not found in firmware - MODE_VIDEO_COMPACT        2595
// Current modemap entry not found in firmware - MODE_VIDEO_SPEED          2594
Setting all of these crashes the camera. ROMLOGS are attached.

// Current modemap entry not found in firmware - MODE_VIDEO_STD            3613
This one is correct. It is what one gets for the prop when using the camera mode dial.
It also works via CHDK/scripts/test/setmode.lua

Is the FW dump the above is derived from correct?
I posted a fresh dump of A430 FW 100B here:
http://chdk.setepontos.com/index.php?topic=11818
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...)

While I naturally applaud all this effort,  it's my understanding that the modemap table has only limited use.   AFAIK, you can use it from script to get the current camera shooting mode and set the mode.  Which can be useful for forcing P or M mode but I'm not sure anyone has ever really needed to use any of the other modes from a script ?

Or is there another reason for needing a 100% correct mode table ?
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline koshy

  • *****
  • 1037
Is there another reason for needing a 100% correct mode table ?
Frankly I don't know. It was nafraf's idea to do this work.
All I can say about it is that I have the cameras, he asked if we could do this and I said yes I'll do it.
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...)

*

Offline koshy

  • *****
  • 1037
A450 and A460:

// Mode 33290 in firmware but not in current modemap

Gets us to Stitch Assist mode on either camera.
This works but I didn't find the mode on the camera menu.
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...)


*

Offline nafraf

  • *****
  • 1308
Wrong modes causes camera crashes if selected using chdkptp GUI. But now, I'm seeing that some of that unmapped modes are crashing, and there are some modes which will remain unknown. 
:-[


*

Offline koshy

  • *****
  • 1037
Wrong modes causes camera crashes if selected using chdkptp GUI. But now, I'm seeing that some of that unmapped modes are crashing, and there are some modes which will remain unknown. 
:-[
We'll get it as far as we'll get it.
For some cams we'll get all of the modes right due to this. If there are some modes that crash to begin with and aren't on FW at all they should probably be removed. The not officially supported modes seem to cause trouble sometimes...
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...)

 

Related Topics