CHDKPTP: ptpCamGUI 2.0 versus Canon's RemoteCapture DC - page 4 - RAW Shooting and Processing - CHDK Forum
« previous next »
Pages: 1 2 3 [4] 5 6 7   Go Down

CHDKPTP: ptpCamGUI 2.0 versus Canon's RemoteCapture DC

  • 68 Replies
  • 25384 Views
*

Offline reyalp

  • ******
  • 14110
Re: CHDKPTP: ptpCamGUI 2.0 versus Canon's RemoteCapture DC
« Reply #30 on: 21 / August / 2012, 01:10:44 »
Advertisements
Quote from: SticK on 21 / August / 2012, 00:56:06
This does not you should solve the problem that way however ... it's just for more insight.
I can see your screenshots, I get it, there's really no need to repeat it.

If I'm going to fix this, I need to understand the underlying cause of the problem. To do that, I need *data*. Since I don't have that camera, you are going to have to help provide it.

Assuming the last dump you provided is correct, the camera firmware thinks the viewport is 240 lines. Yet the dump shows the valid data is clearly only about 217 lines.

Here's some questions that might provide useful data:
Does the top of the chdkptp viewport match the top of the view you see in the actual camera display ? Or is the chdkptp display missing some of the top ?

Did you check edge overlay or zebra ?

If you change the camera to stitch assist mode, does the chdkptp viewport change size ?
Logged
Don't forget what the H stands for.
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP: ptpCamGUI 2.0 versus Canon's RemoteCapture DC
« Reply #31 on: 21 / August / 2012, 10:08:00 »
Quote "Does the top of the chdkptp viewport match the top of the view you see in the actual camera display ? Or is the chdkptp display missing some of the top ?"

Photo attached.

W.r.t. your other 2 questions, those are features I am not familiar with, so I'd have to learn them to chip in.  A couple of tips might help.

Could you please look at this in the meantime an tell me if it provides something useful.

Logged
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP: ptpCamGUI 2.0 versus Canon's RemoteCapture DC
« Reply #32 on: 21 / August / 2012, 10:43:00 »
EDGE LIVE Question.  I don't know what to look for so here's screen shot and data.  I did as you suggested earlier, that is the data hold is: check dump, shoot half, uncheck dump.

http://www.sendspace.com/file/fb5mv4
« Last Edit: 21 / August / 2012, 10:46:25 by SticK »
Logged
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP: ptpCamGUI 2.0 versus Canon's RemoteCapture DC
« Reply #33 on: 21 / August / 2012, 11:40:42 »
SHOOT HALF A/R ALTERATION

Something new that might be useful.  Here I simply press [shoot half] and when the shoot half condition is momentarily transferred to the client, there is a *vertical stretch* of the live view area towards the bottom of your viewport that fills your viewport in the *correct* but still oversized A/R, just for a brief moment.  Then the screen returns back to Figure 1.

I managed to catch the screen shot (Figure 2) (difficult) and dump.

http://www.sendspace.com/file/aqmi24

I tried zebra but don't know what to look for.

Logged
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP: ptpCamGUI 2.0 versus Canon's RemoteCapture DC
« Reply #34 on: 21 / August / 2012, 12:09:41 »
SX110 LCD TECHNICAL SPECIFICATION

The LCD has 230,000 R,G,B pixels.  Therefore ....

   [RGB] picture elements = 230,000 / 3
                                        =   76,666

   hence
    320 x 240 = 76,666.  @ 4:3 A/R

Thus for the SX110, RemoteCapture is correct, ie 320x240. 

Now, CHDKPTP live view is the correct height, ie 240, but, is not the correct width, *stretching* the live view *horizontally.* 

This is the best description I can give you of the problem.

Therein is the insight.
Logged
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP: ptpCamGUI 2.0 versus Canon's RemoteCapture DC
« Reply #35 on: 21 / August / 2012, 12:40:34 »
IN SUMMARY  ... in effect from the user's perspective, you are looking at 2 independent caveats.

This is the idea:

   1) GREEN ARROW:   decrease the width of the live view from what it is now to 320, and,

   2) YELLOW ARROW:  Decrease the viewport height to be the same as the live view, ie 240, in order to match the icon positions where they should be relative to the live view, as they are on the LCD.

Again, from the user's perspective, the result would be CHDKPTP viewport that is 320x240, fully filled with live view, and all icons positioned as the appear in the camera LCD attached.

BEST of LUCK!  Please do get back to me if you need more tests or info.
Logged
*

Offline reyalp

  • ******
  • 14110
Re: CHDKPTP: ptpCamGUI 2.0 versus Canon's RemoteCapture DC
« Reply #36 on: 21 / August / 2012, 16:39:49 »
Thanks for the dumps and screenshots, I'll take a closer look at them when I have a bit more time.

Quote from: SticK on 21 / August / 2012, 10:43:00
EDGE LIVE Question.  I don't know what to look for so here's screen shot and data.  I did as you suggested earlier, that is the data hold is: check dump, shoot half, uncheck dump.
What I want to know is does the edge overlay displayed on the camera screen when match the features in the scene. Doing this in the chdkptp viewport will not be helpful, since we already know the viewport and ui framebuffers don't line up inside chdkptp.

To use edge overlay:
In the edge overlay menu, check "enable edge overlay"
In shooting mode, when you half press the shutter, the camera will outline the edges detected in the scene.  This  will be easier to interpret if the scene has relatively few well defined edges.
You can also set edge overlay to show "always", then you don't need to half press, but things may be a bit laggy.

I don't see any edge overlay in the screenshots.

To check the zebra, just enable zebra in the menu, aim at a high contrast scene (a light bulb is good) and see if the over/under exposed areas line up with what's in the scene. Also look out for "garbage", i.e. stuff that appears in the zebra display but does not correspond to any particular feature in the viewport.

Finally, I asked about "stitch assist", but looking at http://www.usa.canon.com/cusa/support/consumer/digital_cameras/other_powershot/powershot_sx110_is_black#Specifications there doesn't seem to be a stitch mode on this camera.

As an alternative, can you try zooming to the maximum digital zoom, and tell me if the chdkptp viewport changes size ? This may confirm whether the canon firmware viewport size functions are working. It may also change size if you switch to video modes, especially low resolution ones.
Quote
SX110 LCD TECHNICAL SPECIFICATION

The LCD has 230,000 R,G,B pixels.  Therefore ....
The actual framebuffer is definitely 720 Y values wide, and is UYVYYY format, not RGB. I'll take that over something derived from Canon marketing specs any day. Whatever the physical resolution of the LCD, the Canon firmwares actually use a wide range of different framebuffer layouts.

Note that the missing bottom edge is something specific to the sx110 or the sx110 CHDK port. The existing logic works fine on many other models.
Quote
I managed to catch the screen shot (Figure 2) (difficult) and dump.
Note if you want to record a dump of some specific action, you can check the 'record dump' box instead of using the "quick dump". This will record continuously until you uncheck it. Beware, this is essentially raw video so it will get very large very quickly. Unlike the quick dump, it the UI and Viefinder checkboxes will control which framebuffers are recorded.

Logged
Don't forget what the H stands for.
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP: ptpCamGUI 2.0 versus Canon's RemoteCapture DC
« Reply #37 on: 21 / August / 2012, 17:23:16 »
You're welcome.  Some answers you pose here could be found in the dumps and screenshots from earlier in the day I posted.  Please go over them first.

Just a quick update on Zebra and related ... In the meantime I had read your docs on Zebra mode, and it does work manually on camera when I hold down the shutter release 1/2 way.   But, because [shoot half] in CHDKPTP is momentary, I don't get a camera condition long enough to do a transfer to PTP.  Thus I was about to ask you about that ????  Is there a way to keep [shoot half] pressed?

As far as capturing data, "Dump to file" is what I did in the previous post where I tested EDGE, so I do know how it works.  Hence for the EDGE question you just posed, please refer to my earlier post named "EDGE LIVE," since you had indeed asked that question earlier.  You have the pic and the data.  I could not detect any changes in the CHDKPTP visual, but maybe you can.  Can you please look at it? ... with your description, perhaps the scene was not good for what you're looking to test.  Let me know.

LCD.  It's not marketing.  It does contain 230,000 pixels, exactly 230,400 individual R, G and B pixels (for Canon maybe yes, but they are not lying).  In what I referred to as *[RGB] picture elements* earlier, the bottom line for pixels for the rest of us, there are 1/3 of those, or, 76,800.  So if you multiply 4:3 A/R 320x240, you indeed get 76,800.  And ... you have to put some trust in RemoteCapture, because it reports exactly 320x240.  The two agree // nope, not marketing.  You can safely go with the spec.

I cannot comment on how the above relates to the size and format of the framebuffer.  You're the expert in that department.  I can only demonstrate what is happening "on the outside."  One thing is certain there are two inconsistencies:
    a) in horizontal size of your [liveview + viewport], and,
    b) the vertical size of your viewport. 
*Please* take a close look at the figure [9] here, where I simulate the desired result.

I will reread you reply a few times and see if I can fine tune the tests to your liking, and try the new ones.

Logged
*

Offline reyalp

  • ******
  • 14110
Re: CHDKPTP: ptpCamGUI 2.0 versus Canon's RemoteCapture DC
« Reply #38 on: 21 / August / 2012, 17:43:13 »
Quote from: SticK on 21 / August / 2012, 17:23:16
You're welcome.  Some answers you pose here could be found in the dumps and screenshots from earlier in the day I posted.
No, your screenshots do not answer the questions I posted. I asked you about edge overlay on the  camera, none of your screenshots show the edge overlay. In case it wasn't clear, the edge overlay is something that draws on the screen. You can read about it in the manual. If nothing displays in a scene that has edges, then you aren't using it correctly or something is broken.
Quote
Just a quick update on Zebra and related ... In the meantime I had read your docs on Zebra mode, and it does work manually on camera when I hold down the shutter release 1/2 way.
Specifically, *does the zebra image line up with the under / over exposed areas of the screen * ?
Quote
  But, because [shoot half] in CHDKPTP is momentary, I don't get a camera condition long enough to do a transfer to PTP.  Thus I was about to ask you about that ????  Is there a way to keep [shoot half] pressed?
Yes. There is.
lua press("shoot_half"); sleep(1000)
in the console will hold the halfshoot button for a second. But again for the zebra and edge tests, I'm not interested in what shows up in the chdkptp display, I'm looking for what appears on the physical screen.
Quote
As far as capturing data, "Dump to file" is what I did in the previous post where I tested EDGE, so I do know how it works.  Hence for the EDGE question you just posed, please refer to my earlier post named "EDGE LIVE," since you had indeed asked that question earlier.  You have the pic and the data.
Your picture does not display any edge overlay. So no, I don't have the data.
Quote
LCD.  It's not marketing.  It does contain 230,000 pixels, exactly 230,400 individual R, G and B pixels (for Canon maybe yes, but they are not lying).  In what I referred to as *[RGB] picture elements* earlier, the bottom line for pixels for the rest of us, there are 1/3 of those, or, 76,800.  So if you multiply 4:3 A/R 320x240, you indeed get 76,800.  And ... you have to put some trust in RemoteCapture, because it reports exactly 320x240.  The two agree // nope, not marketing.  You can safely go with the spec.
Well, since you know more about these cameras than I do, I guess I should just leave it to the expert and let you fix it  ::)

What is physically on the screen is irrelevant, we only have the framebuffer to work with.
Logged
Don't forget what the H stands for.
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP: ptpCamGUI 2.0 versus Canon's RemoteCapture DC
« Reply #39 on: 21 / August / 2012, 19:02:24 »
==>> I understand for EDGE and ZEBRA, you only want to know what's happening on the camera LCD.  If that's the case please use the words "camera LCD" to disambiguate from other "screens" in your descriptions of what you want tested when appropriate // it avoids confusion and unnecessary work.

==>> Because of your expertise in canon cameras that admittedly I don't have as you implied, I used a vernier to measure the horizontal pixel count on the camera LCD.  By eyeball on the SX110, I measure **approx** 6 RGB triplets per mm.  The width is 60 mm, hence there are **approx** 360 RGB triplets horizontally.  That I suppose is likely more in line with your framebuffer 720.  If that's true, then RemoteCapture is mapping the true SX110 360x270 area to 320x240, and CHDKPTP should have a viewport of 360x270.  That of course would be better.  Sounds reasonable?

I have an interesting answer on the ZOOM question // coming shortly.

Logged
Pages: 1 2 3 [4] 5 6 7   Go Up
« previous next »
 

Related Topics
SimplePortal 2.3.6 © 2008-2014, SimplePortal