chdkptp - alternative ptp client - page 18 - General Discussion and Assistance - CHDK Forum supplierdeeply

chdkptp - alternative ptp client

  • 1106 Replies
  • 448519 Views
*

Offline philmoz

  • *****
  • 3442
    • Photos
Re: alternative ptp client
« Reply #170 on: 30 / May / 2012, 08:45:29 »
Advertisements
Refresh for sx200is, together with EXMEM support and custom palette.

Should "print" call CHDK menu?
I have Canon print menu in playback and nothing in record modes.

Would it be possible to implement zoom slider?

If you have a proper firmware dump for the SX200 can you upload to a file share and post a link here.

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

*

Offline reyalp

  • ******
  • 13844
Re: alternative ptp client
« Reply #171 on: 30 / May / 2012, 13:00:44 »
It is interesting that the digital zoom works well up to x8.2, then remains fixed the lower part of the picture, which increases along with increasing zoom.
This is expected, the display width/height variables from the canon firmware aren't being used. see #if 0 section in platform/sub/lib.c

I'll try to fix these up later. You can look at D10 for an example. You probably don't need to implement the stitch stuff.
Refresh for sx200is, together with EXMEM support and custom palette.
Please make fixes that aren't specific to live view (exmem, palette etc) as patches to the trunk or release branch. When those are applied I can merge them into the live view. If live view stuff is mixed up with other stuff that goes into the trunk separately, it will make the final live view merge difficult.
Don't forget what the H stands for.

*

Offline blackhole

  • *****
  • 868
  • A590IS 101b
    • Planetary astrophotography
Re: alternative ptp client
« Reply #172 on: 30 / May / 2012, 13:22:16 »

This is expected, the display width/height variables from the canon firmware aren't being used. see #if 0 section in platform/sub/lib.c

I'll try to fix these up later. You can look at D10 for an example. You probably don't need to implement the stitch stuff.

Thanks, I'll do it today

*

Offline ADamb

  • **
  • 65
  • sx200is
Re: alternative ptp client
« Reply #173 on: 30 / May / 2012, 13:58:11 »
Quote
If you have a proper firmware dump for the SX200 can you upload to a file share and post a link here.
https://skydrive.live.com/redir?resid=67C21A0ED1F7A310!161&authkey=!ACChwRvupSTR7Uo

Quote
Please make fixes that aren't specific to live view (exmem, palette etc) as patches to the trunk or release branch. When those are applied I can merge them into the live view. If live view stuff is mixed up with other stuff that goes into the trunk separately, it will make the final live view merge difficult.
OK, I'll wait for my updates applied to trunk (they are in the cue), then repost patch.
SX200 IS-100C


*

Offline reyalp

  • ******
  • 13844
Re: alternative ptp client
« Reply #174 on: 31 / May / 2012, 00:29:50 »
In playback mode it work not quite correct. The first screenshot shows a 4:3 image. But it seems to display as 1:1. The second screenshot shows the same image with one step zoom in. In this case the camera switches to 16:9, but chdk ptp to 4:3.
Can you check if this depends on the last setting in record mode ?
For example, if you switch to record, change to 16:9 and then switch back to play, is it different ?
Don't forget what the H stands for.

*

Offline msl

  • *****
  • 1280
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
Re: alternative ptp client
« Reply #175 on: 31 / May / 2012, 07:02:05 »
Can you check if this depends on the last setting in record mode ? For example, if you switch to record, change to 16:9 and then switch back to play, is it different ?

Yes, there are different dependencies. I have tested with a 4:3 and a 16:9 image.

record mode = 4:3 -> playback mode: 4:3 image = (1:1 picture + black area on left side = 4:3 displaying) ; 16:9 image = 4:3 displaying
record mode = 16:9 -> playback mode: 4:3 image = 4:3 displaying; 16:9 image = 16:9 displaying

Also 3:2 and 1:1 aspect ratio have generated a wrong displaying in playback mode.

3:2 generates a 3:2 displaying. 1:1 generates a 1:1 displaying. The 4:3 picture has the same black area as on screenshot on left the side.

msl
CHDK-DE:  CHDK-DE links

*

Offline reyalp

  • ******
  • 13844
Re: alternative ptp client
« Reply #176 on: 02 / June / 2012, 20:14:11 »
Yes, there are different dependencies. I have tested with a 4:3 and a 16:9 image.
Great, thanks. I've checked in a test fix for sx220hs in the reyalp-ptp-live branch.
Don't forget what the H stands for.

*

Offline ADamb

  • **
  • 65
  • sx200is
Re: alternative ptp client
« Reply #177 on: 03 / June / 2012, 04:16:16 »
sx200is_100c, revisison 1897.
Stitch mode is wrong (should be offsetted), I'll do it later.
SX200 IS-100C


*

Offline msl

  • *****
  • 1280
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
Re: alternative ptp client
« Reply #178 on: 03 / June / 2012, 07:56:19 »
I've checked in a test fix for sx220hs in the reyalp-ptp-live branch.

Thanks. Now is all fine.  I think, we can do the same for the SX230. And it's time for moving to  the trunk.  :)

ADamb has right. The stitch mode needs a Y-offset for centered displaying. But this is more an advanced improvement.

msl
CHDK-DE:  CHDK-DE links

*

Offline reyalp

  • ******
  • 13844
Re: alternative ptp client
« Reply #179 on: 03 / June / 2012, 16:48:27 »
Thanks. Now is all fine.  I think, we can do the same for the SX230. And it's time for moving to  the trunk.  :)
Yes, getting there.
Quote
ADamb has right. The stitch mode needs a Y-offset for centered displaying. But this is more an advanced improvement.
Yes. I don't actually want to implement stitch support etc yet on all the cameras. I think a lot of this can be generic, rather than having the same mess of ifs in every camera. As long as the protocol supports the necessary parameters (which I think it does now), we can fix up the individual cameras over time. The main point of adding stitch support was to make sure we can support other weird offset cases.

For stitch, you can't see the previous image (if anyone knows how that's displayed, let me know), and if you wanted to do pans over PTP, you could make a super-stitch mode in the client that showed you the whole screen from the previous shot instead of a tiny window.
Don't forget what the H stands for.

 

Related Topics