CHDK UI version 2.0 ?

philmoz

3450

Re: CHDK UI version 2.0 ?

« Reply #500 on: 12 / November / 2012, 17:52:09 »

Advertisements

Quote from: waterwingz on 12 / November / 2012, 09:48:06

Quote from: philmoz on 12 / November / 2012, 01:52:08
Latest version in my branch allows the Shutter Half Press or the Erase button to change the 'cursor' position when editing values. This works for all cameras.
Haven't been home yet to try this out. But one question comes to mind - these are the same buttons used to "select" user menu entries while user menu "edit" mode is enabled. Do they play nicely together ?

As srsa_4c and msl posted the buttons still work in the user menu as they did before.

The user menu edit really needs an overhaul - I need to look more closely at what tsvstar has done in his current branch.

One thing I forgot to mention is I made the leftmost 'cursor' position (max increment factor) dependant on the max size allowed for menu entries where a MIN/MAX is specified. So if an item has a max value of 800 then you can't increase the increment factor beyond 100. There's also code to handle negative values.

So if you see anything strange with it not allowing you to properly edit values it's probable I got the above code wrong.

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

waterwingz

12140

Re: CHDK UI version 2.0 ?

« Reply #501 on: 23 / November / 2012, 14:07:04 »

Not the biggest bug in the world so while I think of it I'll log it here.

If you disable the OSD, the icons & text still appear when you are in <ALT> mode. Not sure if that's always been the case or if its something new. But when running scripts and dumping to the console, it can be annoying and distracting.

Logged

Ported : A1200 SD940 G10 Powershot N G16

philmoz

3450

Re: CHDK UI version 2.0 ?

« Reply #502 on: 23 / November / 2012, 18:26:48 »

Quote from: waterwingz on 23 / November / 2012, 14:07:04

Not the biggest bug in the world so while I think of it I'll log it here.

If you disable the OSD, the icons & text still appear when you are in <ALT> mode. Not sure if that's always been the case or if its something new. But when running scripts and dumping to the console, it can be annoying and distracting.

Pretty sure it's always been that way.

Not easy to fix - the function that displays the OSD also displays the subject distance override info; which is editable in ALT mode on some cameras, so needs to be displayed.

Another area that needs some re-work

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

waterwingz

12140

Re: CHDK UI version 2.0 ?

« Reply #503 on: 23 / November / 2012, 18:30:07 »

Quote from: philmoz on 23 / November / 2012, 18:26:48

Pretty sure it's always been that way. Not easy to fix - the function that displays the OSD also displays the subject distance override info; which is editable in ALT mode on some cameras, so needs to be displayed.

Thought there might be some reason for it - thanks. I did the obvious thing and turned the various OSD things off individually. Not ideal - but I guess I could have cloned my CCHDK3.CFG file first though.

Quote

Another area that needs some re-work

Low priority. A discussion about tsvstar's user menu (even though I can't work it all) would probably have more value.

« Last Edit: 23 / November / 2012, 18:31:52 by waterwingz »

Logged

Ported : A1200 SD940 G10 Powershot N G16

waterwingz

12140

Re: CHDK UI version 2.0 ?

« Reply #504 on: 24 / November / 2012, 16:52:48 »

@philmoz :

Another one for the list of "things that go bump in the night".

I've been working with %range in my script header and using %range a 0 1 so that I get a boolean checkbox [ *] rather than [ 0 ] or [1 ]. Its quite nice.

However, on some occasions, when I pull up the script menu, the nice check boxes have reverted to [ 1 ] type inputs, and you can scroll them past the 0,1 range limits.

So far my only work-around solution is to turn the camera off and restart. Don't need to reload the script - just power cycle - and the [ * ] boxes are back. Going in & out of <ALT> does not clear it up.

I haven't looked at the source yet to see what's happening. Thought I'd mention it here in case its one of those initialize variable three minute fixes once you know its happening.

WW

Logged

Ported : A1200 SD940 G10 Powershot N G16

philmoz

3450

Re: CHDK UI version 2.0 ?

« Reply #505 on: 24 / November / 2012, 17:03:53 »

Quote from: waterwingz on 24 / November / 2012, 16:52:48

@philmoz :

Another one for the list of "things that go bump in the night".

I've been working with %range in my script header and using %range a 0 1 so that I get a boolean checkbox [ *] rather than [ 0 ] or [1 ]. Its quite nice.

However, on some occasions, when I pull up the script menu, the nice check boxes have reverted to [ 1 ] type inputs, and you can scroll them past the 0,1 range limits.

So far my only work-around solution is to turn the camera off and restart. Don't need to reload the script - just power cycle - and the [ * ] boxes are back. Going in & out of <ALT> does not clear it up.

I haven't looked at the source yet to see what's happening. Thought I'd mention it here in case its one of those initialize variable three minute fixes once you know its happening.

WW

Check to see if one of the saved param sets for the script is wrong (saved badly).

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

waterwingz

12140

Re: CHDK UI version 2.0 ?

« Reply #506 on: 24 / November / 2012, 21:50:33 »

Quote from: philmoz on 24 / November / 2012, 17:03:53

Check to see if one of the saved param sets for the script is wrong (saved badly).

There's only one and it the zero set. Looks okay when I open it up.

But here's what might have happened. I had downloaded a new version of the script over ptp (not sure how anyone writes scripts without ptp) and it might have had a new parameter or a different order ? The funny input checkbox problem happened twice today and I'm pretty sure I had change the script parameters both times, downloadwd, selected and ran (i.e. no power cycling). Probably safer to work with save params turned off I guess.

Logged

Ported : A1200 SD940 G10 Powershot N G16

waterwingz

12140

Re: CHDK UI version 2.0 ?

« Reply #507 on: 26 / November / 2012, 10:19:49 »

Quote from: RockyBot on 26 / November / 2012, 06:00:11

Changeset [2323]: Script code cleanup and bug fixes. - fixed bug where incorrect parameter ...
26 November 2012, 2:44 pm
Script code cleanup and bug fixes.
fixed bug where incorrect parameter set loaded at startup
fixed bug where parameters saved to wrong parameter set
fixed bugs where changed parameters not always saved to parameter set

This might explain some of the other weirdness I've seen in the last couple of days with a script I'm working on not behaving the way I would expect based on how the parameters are set.

Thanks philmoz.

Logged

Ported : A1200 SD940 G10 Powershot N G16

outslider

762

Re: CHDK UI version 2.0 ?

« Reply #508 on: 28 / November / 2012, 17:35:19 »

Hello, hello!

I had no time these days, so I just downloaded philmoz branch. I appreciate the work that has been done there, however for me the most significant advance in tsvstar-ui was usage of the jogdial to 'scroll' the selected parameter value.

I'm not sure, whether simmilar behavior is possible with philmoz branch, since it uses different logic, but I would very like to see it - it made life easier!

Logged

if (2*b || !2*b) {
cout<<question
}

Compile error: poor Yorick

andrewhazelden

93

Override Tv Type - Short Exp. Value

« Reply #509 on: 06 / March / 2013, 16:19:00 »

Quote from: philmoz on 03 / November / 2012, 05:09:08

Latest version (2245) in philmoz-uitest has two significant changes.
1. Added a new UI for the Tv (shutter speed) override for review.
...

Hi Waterwingz and Philmoz.

I was hoping you could clarify a CHDK question I have been researching.

I was asked a question about CHDK exposure control by an aerial photography user with a SX260HS camera. The user indicated the "classic" CHDK Value Factor based shutter speed override controls weren't visible in the unstable CHDK 1.2.0 builds. Supposedly there is a new option called "Short Exp. Value" that I know very little about.

I am interested in writing a blog/Wiki post explaining how the new system works and I was hoping you could clarify a few facts for accuracy. I searched online for any comments about the new CHDK camera controls and compared the english.lng file from the CHDK 1.10 and 1.2.0 builds.

In the SX260HS CHDK stable 1.1 firmware there are controls for:

244 " Value Factor"

I noticed the new the SX260HS CHDK unstable 1.2.0 build user has the options for:

240 " Ev Step Value"
241 " Long Exp. Value"
244 " Short Exp. Value"

From what I have gleaned online it looks like the "Short Exposure" mode is the best one for capturing images with a high shutter speed. The "Short Exposure" mode provides timing precision between a 0 to 9 second exposure duration.

According to the Canon SX260 HS user guide [url=http://bit.ly/CanonSX260_PDF]http://bit.ly/CanonSX260_PDF[/url] on page 36 the available TV mode "high speed" shutter values are: 1/200, 1/250, 1/320, 1/400, 1/500, 1/640, 1/800, 1/1000, 1/1250, 1/1600, 1/2000, 1/2500, 1/3200

If a model airplane wanted to capture a fast image with a 1/1250th of a second shutter speed the time in seconds would equal 0.0008 seconds.

I don't know the exact step values the CHDK user interface allows so I was wondering if you could let me know the step values for the short and long exposure "Override Tv type ->" field.

Thanks,
Andrew

Logged

Canon SD780IS