New CHDK features - page 2 - CHDK Releases - CHDK Forum  
« previous next »
Pages: 1 [2] 3 4   Go Down

New CHDK features

  • 38 Replies
  • 7703 Views
*

Offline Caefix

  • *****
  • 945
  • Sorry, busy deleting test shots...
Re: New CHDK features
« Reply #10 on: 07 / December / 2021, 16:28:47 »
Advertisements
Ptp sometimes crashes  :-X, sometimes not  :D, probably expected  8), more tomorrow... :)
Logged
All lifetime is a loan from eternity.
*

Offline programmer0

  • *
  • 14
Re: New CHDK features
« Reply #11 on: 08 / December / 2021, 04:15:24 »
Fantastic. I tested it under Canon Powershot SX10IS with CHDKPTP program on a Lenovo G50-70 computer with Windows 10. Perhaps I will update the codes with the changes you propose, but I need to take a closer look at it. It is quite a complicated project.
« Last Edit: 08 / December / 2021, 04:18:53 by programmer0 »
Logged
*

Offline Caefix

  • *****
  • 945
  • Sorry, busy deleting test shots...
Re: New CHDK features
« Reply #12 on: 08 / December / 2021, 16:08:19 »
Mainly based on #5163 tapes digitally remastered ...  :D
A lot of spook is gone ...  :haha
Logged
All lifetime is a loan from eternity.
*

Offline programmer0

  • *
  • 14
Re: New CHDK features
« Reply #13 on: 09 / December / 2021, 01:08:46 »
This code works only for this format:
Code: [Select]
U Y1 V Y2 Y3 Y4

modules\histogram.c in do_waveform_process()

Code: [Select]
            Y = img_buf[v+1];
            U = ((v % (2 * step_v * step_x)) == 0)
                ? (signed char) img_buf[v+0] : (signed char) img_buf[v-3];
            V = ((v % (2 * step_v * step_x)) == 0)
                ? (signed char) img_buf[v+2] : (signed char) img_buf[v-1];

I also used stages for waveform as it is in the histogram which is reflected in this code.
Logged
*

Offline Caefix

  • *****
  • 945
  • Sorry, busy deleting test shots...
Re: New CHDK features
« Reply #14 on: 09 / December / 2021, 10:17:58 »
motion_detector.c tells ...  ???
Code: [Select]
// Pre Digic6:
//      ARRAY of UYVYYY values
//      6 bytes - 4 pixels
// Digic6:
//      ARRAY of UYVY values
//      4 bytes - 2 pixels

// Pre Digic6: U & V are signed char values (-128 - 127)
//      R = Y + 1.402 * V + 0.5
//      G = Y - 0.34414 * U - 0.71414 * V + 0.5
//      B = Y + 1.772 * V + 0.5
// Digi6: U & V are unsigned (0 - 255) subtract 128 to get signed value
//      R = Y + 1.402 * (V-128) + 0.5
//      G = Y - 0.34414 * (U-128) - 0.71414 * (V-128) + 0.5
//      B = Y + 1.772 * (V-128) + 0.5
Some // CHDK/LANG/ language file strings are colliding...  :( Need to reorder?
Code: [Select]
638 "Load Zones From File..."
639 "Select Zone File"
640 "Current Zone System"
641 "Show Zone Legend"
642 "Waveform parade mode"
643 "Color Temperature & Tint"
644 "Show percent overexposed"
645 "Show auto EV compensation"
646 "Zebra RGB as"
It seems quite compatible with the #5163 ../tools folder
(but broken chars, nearly unreadable) with older font_8x16_pack.c
or better: #5163´s gui_draw.c+h & fonts.h :)
Updates (&& 3rd language CHDK/LANG/german.lng) appended.
More spook gone ...  :haha
« Last Edit: 14 / December / 2021, 16:16:33 by Caefix »
Logged
All lifetime is a loan from eternity.
*

Offline Caefix

  • *****
  • 945
  • Sorry, busy deleting test shots...
Re: New CHDK features
« Reply #15 on: 12 / December / 2021, 10:57:59 »
Now the whole ../platform/.. Folder could be from #5163.  :D
Appended some of them & build (diskboot.bin+CHDK) as it runs on my Sx230.
Logged
All lifetime is a loan from eternity.
*

Offline programmer0

  • *
  • 14
Re: New CHDK features
« Reply #16 on: 12 / December / 2021, 11:49:56 »
In the project, I have modified only two language files: English and Polish. I added new strings for new functionalities at the end by increasing the numbers starting from 638 and modifying core / gui_lang.h in the same way. I found this to be the most sensible solution not to clash but beware of CHDK 1.4.1. It seems to me that in the longer term this fork should be rewritten along with refactoring the code based on the latest version 1.6. I will review these language files from this version. But I have to test it on my cameras first. I am thinking about additional functionalities, e.g. writing a module for detecting color harmony based on RGB or RYB. I also intend to write a module or extend the curve module with LUT3D functionality from .cube files by working directly on RAW data.
Logged
*

Offline Caefix

  • *****
  • 945
  • Sorry, busy deleting test shots...
Re: New CHDK features
« Reply #17 on: 14 / December / 2021, 16:33:31 »
Quote from: programmer0 on 12 / December / 2021, 11:49:56
... but beware of CHDK 1.4.1. It seems to me that in the longer term this fork should be rewritten along with refactoring the code based on the latest version 1.6.
Probably a 1/2 way stage is quite usefull ...
Gui_draw grew more between Your version & #5163 then since.
Now Lua & uBasic have get_min_av96 & get_max_av96.  :)
Zebra & histogram have the recent #ifndef THUMB_FW lines, seem easier to compare, work quite good, but the zones are gone & waves crashing.  :(
« Last Edit: 15 / December / 2021, 14:17:05 by Caefix »
Logged
All lifetime is a loan from eternity.
*

Offline programmer0

  • *
  • 14
Re: New CHDK features
« Reply #18 on: 15 / December / 2021, 04:35:09 »
I am unable to compile the official CHDK version 1.6.0 because I do not have the correct compiler. Version 1.4.1 has been compiled but there are problems with the latest version. The compiler used is not GCC 4.5.1 but 3.4.6. I can't update the fork to CHDK 1.6.0 yet. I do not know if I can handle it because I do not know where to download the appropriate GCC compiler with the ARM environment. Also, even version 1.4.1 cannot be compiled on Windows 10 but worked under Windows XP SP3.
Logged
*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: New CHDK features
« Reply #19 on: 15 / December / 2021, 04:49:06 »
Quote from: programmer0 on 15 / December / 2021, 04:35:09
I am unable to compile the official CHDK version 1.6.0 because I do not have the correct compiler. Version 1.4.1 has been compiled but there are problems with the latest version. The compiler used is not GCC 4.5.1 but 3.4.6. I can't update the fork to CHDK 1.6.0 yet. I do not know if I can handle it because I do not know where to download the appropriate GCC compiler with the ARM environment. Also, even version 1.4.1 cannot be compiled on Windows 10 but worked under Windows XP SP3.


All the GCC cross compilers can be downloaded from https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads


10-2020-q4-major and 9-2020-q2-update are known working versions for CHDK.


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)
Pages: 1 [2] 3 4   Go Up
« previous next »
 

Related Topics