CHDKPTP - PC Remote Control Performance Analysis - page 36 - RAW Shooting and Processing - CHDK Forum
« previous next »
Pages: 1 ... 31 32 33 34 35 [36] 37 38 39 40 41 ... 47   Go Down

CHDKPTP - PC Remote Control Performance Analysis

  • 465 Replies
  • 135592 Views
*

Offline srsa_4c

  • ******
  • 4451
Re: CHDKPTP - PC Remote Control Performance Analysis
« Reply #350 on: 01 / October / 2012, 19:15:06 »
Advertisements
Quote from: SticK on 01 / October / 2012, 18:29:09
Discovery of the day.  I noticed the faults became less frequent when I observed the scrolling hints are the screen bottom.
Hmm, so there are scolling hints. I should see DIGIC 4 cameras more often  :).
Well, if you can disable those and it helps, I think that's good enough for a solution.
This is clearly a bug, but the condition to trigger it is rather special. I don't think that the S90 is the only model affected. If I wanted to fix this, I would disable CHDK screen refresh completely when the Canon menu is active. Too bad that we don't have a bug tracker...
Quote
The question now is whether or not your previous version will work better, same, or worse.  What do you think?
I think that you should disable those scrolling hints and stay with my previous version. If you can still trigger these crashes (with hints disabled), report it again.
Logged
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP - PC Remote Control Performance Analysis
« Reply #351 on: 01 / October / 2012, 19:45:32 »
Quote "I should see DIGIC 4 cameras more often"

Well ... hmmm ...... unless you really need that silly ::)-detection, and oh ... going to Digic V might get you :)-detection too, so why not? :haha.

BTW, Digic III on my SX110 also has the AF point zoom feature.  In my "digital photography opinion" as I almost always shoot photos in manual or priority modes, it is the only useful feature in these cameras.

Logged
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP - PC Remote Control Performance Analysis
« Reply #352 on: 02 / October / 2012, 00:07:53 »
With Hints & Tips OFF and back to srsa_test1, both S90s behave OK // I pushed the menus around quite a bit and no problems this evening.  So that looks pretty solid.

SUGGESTION: it might be a good idea to queue commands (scripts) // additionally have a queue depth level option that shows the "ERROR a script is already running" only when queue is full.

Also "WARNING a script is already running" may be less dire.

edit: @srsa_4c
Quote "This seems to clash with something related to the drawing of the Canon menu."
That was a good call.
« Last Edit: 02 / October / 2012, 08:24:55 by SticK »
Logged
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP - PC Remote Control Performance Analysis
« Reply #353 on: 02 / October / 2012, 08:42:03 »
QUESTION.  I am wondering what's available and possible for the CHDKPTP GUI.  It would be very useful if I can adapt it for my application.  While waiting for the lens to arrive, I would like to customize it ... for example... add buttons & link scripts, change window format, change size of the small liveview and its position, add a reticle, etc.  What do you have available, if at all?  Is there source available?  Is there a linker script available that I can do a "hello world" compile of the source?  If so, what tools would I need?  What would I need to read?  etc.  Can you help me with this?
Logged
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP - PC Remote Control Performance Analysis
« Reply #354 on: 02 / October / 2012, 11:48:14 »
An interesting liveview ISO problem to get handle on?

Code: [Select]
function myshoot(tv, av, sv, destdir)
sv = sv / 1.6461 -- ISO correction for S90
cli:execute('shoot -tv='..tv..' -av='..av..' -sv='..sv..'')
sys.sleep(2400)
local l,r=con:execwait('return get_meminfo().free_size')
print(" free", r)   
printf(" free: %s\n",r)   
dcimdl(destdir, true, false)
endDescription

 > Set ISO to 1600
 > Fig 1, liveview before shoot
 > !myshoot(0.4, 2.8, 1600, "C:\\CANON_S90\\")
     > JPG Ok, EXIF reads 1600, JPG brightness is same as seen in liveview Fig 1
 > Fig 2, liveview after shoot: Liveview goes dark ==>> gets internally set to ISO 100, but icon remains at 1600
 > If I shoot same again, JPG is exposed correctly, at 1600, but liveview still stays dark
 > When I press SET to do manual ISO reset, 1600 is correctly displayed // Ok, but liveview still dark
 > I have to jog the ISO value to restore the bright liveview, e.g. 1/3 stop (LEFT or RIGHT) liveview goes bright immediately, then back to 1600 and liveview is again as in Fig 1.

Strange and unexpected // good to fix if it's not finger trouble.  Thoughts?
Logged
*

Offline srsa_4c

  • ******
  • 4451
Re: CHDKPTP - PC Remote Control Performance Analysis
« Reply #355 on: 02 / October / 2012, 16:31:11 »
Quote from: SticK on 02 / October / 2012, 08:42:03
QUESTION.  I am wondering what's available and possible for the CHDKPTP GUI.  It would be very useful if I can adapt it for my application.  While waiting for the lens to arrive, I would like to customize it ... for example... add buttons & link scripts, change window format, change size of the small liveview and its position, add a reticle, etc.  What do you have available, if at all?  Is there source available?
Sure. Parts of chdkptp are written in C, higher level (cli, gui) is in Lua. They are in *.lua files beside the exe. See for example gui.lua. However, as I'm not a master of Lua, don't expect much help from me. The whole source is hosted in svn, here.
Quote
Is there a linker script available that I can do a "hello world" compile of the source?  If so, what tools would I need?  What would I need to read?  etc.  Can you help me with this?
The compilation requirements are detailed in README.TXT.
Quote from: SticK on 02 / October / 2012, 11:48:14
An interesting liveview ISO problem to get handle on?
Strange and unexpected // good to fix if it's not finger trouble.  Thoughts?
I'm again not the best person to answer this, but it's not too unusual that the overrides cause some side effects. You could extend the script to send some keypresses after shoot for example. Of course there may be a better way.
Logged
*

Offline waterwingz

  • ******
  • 12140
    • Waterwingz
Re: CHDKPTP - PC Remote Control Performance Analysis
« Reply #356 on: 02 / October / 2012, 16:37:15 »
Quote from: srsa_4c on 02 / October / 2012, 16:31:11
The compilation requirements are detailed in README.TXT.
I got it to compile on my raspberry pi so you can probably assume that its not a difficult job.
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP - PC Remote Control Performance Analysis
« Reply #357 on: 02 / October / 2012, 17:37:04 »
Quote "You could extend the script to send some keypresses after shoot for example."

I added ...
Code: [Select]
con:execwait('click("set")')
sys.sleep(1000)
con:execwait('click("set")')
sys.sleep(1000)
... and no effect.

In any case ... it's very simple to duplicate -- after having set up the Canon shooting parameters as you see them in Fig 1, boot the camera, put into M mode if not there, and say this in the command line:

  !myshoot(0.4, 2.8, 1600, "C:\\CANON_S90\\")

... or whatever directory you like, and the liveview will go dark (on the S90 for sure).  BTW you can use different values for ISO, the JPGs are OK and respect the ISO value you write, but the liveview always goes dark and has to be manually reset as I explained last time.  I don't think the Tv ad Av values matter for the fault, but for testing here I wrote them in the command as I set up the Canon values.

Here's dcimdl in case you don't have it.  myshoot() calls the new shoot (which you should have already, see also my code last post) and dcimdl.

Code: [Select]
function dcimdl(destdir,del,pretend)
    if pretend then
        pretend = '-pretend '
    else
        pretend = ''
    end
    local dcim,err=con:listdir('A/DCIM')
    if not dcim then
        printf('error listing directory %s\n',tostring(err))
    return
    end
    for i,dname in ipairs(dcim) do
        if dname ~= 'CANONMSC' then
            cli:print_status(cli:execute('mdl '..pretend..' -fmatch=%.[JDC][PNR][G2W]$ DCIM/'..dname..' '..destdir))
        end
    end
if del then
cli:print_status(cli:execute('rm '..pretend..' -skip_topdirs DCIM'))
end
end
edit:  it may be wise to wait for reyalp to look at this.
« Last Edit: 02 / October / 2012, 17:43:39 by SticK »
Logged
*

Offline srsa_4c

  • ******
  • 4451
Re: CHDKPTP - PC Remote Control Performance Analysis
« Reply #358 on: 02 / October / 2012, 17:58:44 »
Quote from: SticK on 02 / October / 2012, 17:37:04
edit:  it may be wise to wait for reyalp to look at this.
8)

In the meantime, try to set the required shooting parameters on camera with the Canon menu, and don't use the override params after the shoot command, if that's acceptable for you.

You can rotate the jogdial from a script by using
Code: [Select]
post_levent_to_ui("RotateJogDialLeft",1)
post_levent_to_ui("RotateJogDialRight",1)I found this in gui.lua.

You can look up reyalp's shoot command in cli.lua, search for "names={'shoot'},".
Logged
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP - PC Remote Control Performance Analysis
« Reply #359 on: 02 / October / 2012, 21:32:39 »
@srsa_4c

Quote "try to set the required shooting parameters on camera with the Canon menu"

Done, on the 100c.

Quote "and don't use the override params after the shoot command"

I issue =shoot() in the command line, and all's well ... liveview remains bright.  Next, if I do this now...
  !myshoot(0.4, 2.8, 1600, "C:\\CANON_S90\\")
it goes dark. 
  ... and ...
Now while the liveview is dark, but still shows ISO 1600 in the corner icon, and I say again ...
  =shoot()
sure enough ... the JPG's good, but liveview is dark, still. 

So it is related to the override.

Quote "You can look up reyalp's shoot command in cli.lua, search for "names={'shoot'},""

Have you tried my !myshoot(...) from here:
http://chdk.setepontos.com/index.php?topic=8613.msg91516#msg91516
and its subordinate here:
http://chdk.setepontos.com/index.php?topic=8613.msg91526#msg91526  (2nd code block)
Question mark?

Quote "You can rotate the jogdial from a script by using"

My guess it's the same as pressing the WHEEL L and WHEEL R buttons, and I have used those quite extensively.  They work OK for me.

edit: please try my code // if you can't get it to work, I can send you a package nicely gift-wrapped.
« Last Edit: 02 / October / 2012, 21:35:08 by SticK »
Logged
Pages: 1 ... 31 32 33 34 35 [36] 37 38 39 40 41 ... 47   Go Up
« previous next »
 

Related Topics


SimplePortal © 2008-2014, SimplePortal