Custom Colors : standardizing a semi-transparent grey - page 5 - General Discussion and Assistance - CHDK Forum
« previous next »
Pages: 1 2 3 4 [5] 6 7 8 9 10 11   Go Down

Custom Colors : standardizing a semi-transparent grey

  • 106 Replies
  • 37953 Views
*

Offline waterwingz

  • ******
  • 12140
    • Waterwingz
Re: Custom Colors : standardizing a semi-transparent grey
« Reply #40 on: 25 / October / 2014, 18:07:48 »
Advertisements
Quote from: philmoz on 25 / October / 2014, 17:11:23
Palettes 13, 15 & 16 still define different values for COLOR_GREY_DK, COLOR_GREY and COLOR_GREY_LT.
I should have been more explicit.  The grey colors used in those three palettes come from a continuous range of increasingly darker grey palette entries starting with white (@0x01) and running to almost black (@0x1D).   So I suspect it was just random luck which ones the poor person doing the port picked as light, normal and dark grey.  I think it's safe to just make them all the same for the cameras using those three palettes - the result will only change the absolute grey shades a little bit.

Quote
The easiest way to fix the console is to use the conf.osd_color value instead of conf.menu_color. This will display the console using the same colors as the other OSD text items (clock etc).
That works for me.  At one point one of my cams showed the console in playback as an ugly puke green color so pretty much anything was an improvement at that time.  That drove a lot of the script GUI work I did - getting enough info on a scrolling console blocked so much of the image that shooting was almost impossible.  A semi-transparent bacground would help a lot there!    I guess the only other choice would be to add an explicit entry to the Color Settings for Console Background.

One other "out there thought" - allow the user to specify the 32 bit value used for semi-transparent in the custom palette entry.
« Last Edit: 25 / October / 2014, 18:15:06 by waterwingz »
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: Custom Colors : standardizing a semi-transparent grey
« Reply #41 on: 25 / October / 2014, 18:41:23 »
Quote from: waterwingz on 25 / October / 2014, 18:07:48
Quote from: philmoz on 25 / October / 2014, 17:11:23
Palettes 13, 15 & 16 still define different values for COLOR_GREY_DK, COLOR_GREY and COLOR_GREY_LT.
I should have been more explicit.  The grey colors used in those three palettes come from a continuous range of increasingly darker grey palette entries starting with white (@0x01) and running to almost black (@0x1D).   So I suspect it was just random luck which ones the poor person doing the port picked as light, normal and dark grey.  I think it's safe to just make them all the same for the cameras using those three palettes - the result will only change the absolute grey shades a little bit.

Ok - if you're happy to use 13 for everything that would be easier (less cameras using 15 & 16).

Quote
One other "out there thought" - allow the user to specify the 32 bit value used for semi-transparent in the custom palette entry.

Since there's probably less than ten people on the planet who would ever use it, I'm thinking probably not :)

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)
*

Offline waterwingz

  • ******
  • 12140
    • Waterwingz
Re: Custom Colors : standardizing a semi-transparent grey
« Reply #42 on: 25 / October / 2014, 18:52:37 »
Quote from: philmoz on 25 / October / 2014, 18:41:23
Ok - if you're happy to use 13 for everything that would be easier (less cameras using 15 & 16).
Actually,  I was suggesting removing 15&16 altogether and moving all the affected cameras to 13.

Edit : or maybe that's what you meant?
« Last Edit: 25 / October / 2014, 20:32:00 by waterwingz »
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline waterwingz

  • ******
  • 12140
    • Waterwingz
Re: Custom Colors : standardizing a semi-transparent grey
« Reply #43 on: 25 / October / 2014, 21:43:49 »
Cameras with the custom palette implemented (blue = have trans_grey )

a1200             a1300             a1400              a2200             a2300       a2400
a2500             a3200             a3300              a3400             a4000       a810
d20               d30
g10               g12               g15                g1x
ixus100_sd780     ixus110_sd960     ixus115_elph100his ixus120_sd940
ixus125_elph110hs ixus132_elph115   ixus135_elph120    ixus140_elph130
ixus140_elph130   ixus240_elph320hs ixus255_elph330hs  ixus310_elph500hs
n                 n_facebook
s100              s110
sx160is           sx170is           sx200is            sx220hs           sx230hs     sx240hs   sx260hs
sx30              sx40hs            sx50hs             sx500is           sx510hs

Time for another "call to arms" from the CHDK user community I think.
« Last Edit: 25 / October / 2014, 21:55:39 by philmoz »
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: Custom Colors : standardizing a semi-transparent grey
« Reply #44 on: 25 / October / 2014, 22:28:14 »
I've added the transparent grey changes in revision 3693.

I also added a menu option to reset all adjustable colors back to default values, so it's easier to test the changes without deleting the whole OSD config file.

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)
*

Offline waterwingz

  • ******
  • 12140
    • Waterwingz
Re: Custom Colors : standardizing a semi-transparent grey
« Reply #45 on: 25 / October / 2014, 22:31:09 »
Quote from: philmoz on 25 / October / 2014, 22:28:14
I also added a menu option to reset all adjustable colors back to default values, so it's easier to test the changes without deleting the whole OSD config file.
Nice - that one cost me a few hours during experimenting.
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline msl

  • *****
  • 1280
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
Re: Custom Colors : standardizing a semi-transparent grey
« Reply #46 on: 26 / October / 2014, 05:27:17 »
Quote from: waterwingz on 25 / October / 2014, 21:43:49
Cameras with the custom palette implemented (blue = have trans_grey )
And what is with red ... :haha

I have added the SX220/230 for using the transparent grey. For the SX200 was defined a light transparent grey. There was also value for dark transparent grey, commented out. I have replaced these values ​​and enabled in platform_camera.h. Maybe someone with a Sx200 can test this.

msl
Logged
CHDK-DE:  CHDK-DE links
*

Offline srsa_4c

  • ******
  • 4451
Re: Custom Colors : standardizing a semi-transparent grey
« Reply #47 on: 26 / October / 2014, 09:09:10 »
The palette rework may have bad impact on some ports, an example is ixus870_sd880 (CHDK 1.3 vs 1.2):



Not all ports' palette is carefully chosen. As it turns out, none of the existing palettes is really suitable for this camera. Should I introduce a new one...? (Note that custom palette is not possible on this camera as it has "legacy" graphics despite being a DIGIC 4 model.)
Logged
*

Offline nafraf

  • *****
  • 1308
Re: Custom Colors : standardizing a semi-transparent grey
« Reply #48 on: 26 / October / 2014, 11:24:51 »
New GDKT column added to Camera Features Table informs if COLOR_GREY_DK_TRANS is defined in platform_camera.h
Logged
*

Offline waterwingz

  • ******
  • 12140
    • Waterwingz
Re: Custom Colors : standardizing a semi-transparent grey
« Reply #49 on: 26 / October / 2014, 12:25:26 »
Quote from: msl on 26 / October / 2014, 05:27:17
And what is with red ... :haha
Tested but not included in the patch file?

Quote from: srsa_4c on 26 / October / 2014, 09:09:10
The palette rework may have bad impact on some ports, an example is ixus870_sd880 (CHDK 1.3 vs 1.2):
The ixus870 does not have a pallete defined in its platform_camera.h file.  So I guess whatever form the "default" palette takes is different with 1.3.0.  I'll take a look.

Quote
Not all ports' palette is carefully chosen.
Not surprising.  It's typically something a person new to porting CHDK has to pick early in the learning process - and when they don't know what the colors "should be".

Quote
As it turns out, none of the existing palettes is really suitable for this camera. Should I introduce a new one...?
Probably the best option.

Quote
(Note that custom palette is not possible on this camera as it has "legacy" graphics despite being a DIGIC 4 model.)
I understand it won't work with the current custom palette code but I wonder if there is another way?

Quote from: nafraf on 26 / October / 2014, 11:24:51
New GDKT column added to Camera Features Table informs if COLOR_GREY_DK_TRANS is defined in platform_camera.h
Thanks - I was going to PM you about that today.   Saves me trying to keep up the table I created and posted earlier.

And a belated thanks to philmoz for getting this done much faster than I would have (when it eventually got to the top of my roundtuit list).
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
Pages: 1 2 3 4 [5] 6 7 8 9 10 11   Go Up
« previous next »
 

Related Topics


SimplePortal © 2008-2014, SimplePortal