SX60HS Porting - page 45 - DryOS Development - CHDK Forum

SX60HS Porting

  • 915 Replies
  • 287156 Views
*

Offline srsa_4c

  • ******
  • 4430
Re: SX60HS Porting
« Reply #440 on: 25 / June / 2016, 09:46:15 »
Advertisements
Quote
my camera cycles through displaytype cases (0,1,...7) in lib.c
This ocurred for the old value of displaytype 0x95e4....I am wondering if this variable is indexing one of eight buffers?
FWIW, you could try to find out if there's any correlation between the fw variable and the frame buffers.
This utility allows sampling up to 6 words in the camera's memory, with up to 500 samples/second speed. The first word to sample would be the fw variable, the rest would be the first word of 5 consecutive buffers - just make sure the viewport data is changing constantly while sampling.

Re: SX60HS Porting
« Reply #441 on: 29 / June / 2016, 13:04:06 »
Quote
FWIW, you could try to find out if there's any correlation between the fw variable and the frame buffers.
This utility allows sampling up to 6 words in the camera's memory, with up to 500 samples/second speed. The first word to sample would be the fw variable, the rest would be the first word of 5 consecutive buffers - just make sure the viewport data is changing constantly while sampling.
I ran the suggested utility....not sure it makes sense but there is variation at least partly correlated with the indexing variable: (full sheet attached)
   Maybe just random....
Code: [Select]
# tick(ms) delta(ms) value0 value1 value2 value3 value4 value5
INFO [0x95e4] [0x43334300] [0x433ca300] [0x43460300] [0x434f6300] [0x4358c300]
0 237530 20 0x00000003 0x1581157f 0x03ff0200 0x4a914b76 0x1c801f81 0x327d3281
1 237550 20 0x00000004 0x1581157f 0x03ff0200 0x4f8f4f75 0x1c801f81 0x327d3281
2 237570 20 0x00000005 0x1581157f 0x03ff0200 0x4f8f4f75 0x1d801b80 0x327d3281
3 237590 20 0x00000006 0x1581157f 0x03ff0200 0x4f8f4f75 0x1d801b80 0x327d3281
4 237610 20 0x00000007 0x1581157f 0x03ff0200 0x4f8f4f75 0x1d801b80 0x327e3382
5 237630 20 0x00000000 0x1581157f 0x03ff0200 0x4f8f4f75 0x1d801b80 0x327e3382
6 237650 20 0x00000001 0x1581157e 0x03ff0200 0x4f8f4f75 0x1d801b80 0x327e3382
7 237670 20 0x00000002 0x1581157e 0x03ff0200 0x4e904e75 0x1d801b80 0x327e3382
8 237690 20 0x00000003 0x1581157e 0x03ff0200 0x4e904e75 0x1d801b80 0x327e3382
9 237710 20 0x00000004 0x1581157e 0x03ff0200 0x4e904e75 0x1c801b80 0x327e3382
It would be useful if the utility did not output spaces after the commas... ::)

Edit1: interesting that the index variable seems to cycle to the next value every 20 ms, never? missing...almost like it is synchronized with the monitor....
« Last Edit: 29 / June / 2016, 14:55:08 by 62ndidiot »

*

Offline srsa_4c

  • ******
  • 4430
Re: SX60HS Porting
« Reply #442 on: 01 / July / 2016, 19:31:54 »
I ran the suggested utility....not sure it makes sense but there is variation at least partly correlated with the indexing variable: (full sheet attached)
   Maybe just random....
I'd say your index variable is not related to those framebuffers.
Quote
It would be useful if the utility did not output spaces after the commas...
Wish fulfilled. Also added 2 new sampling rates (200/s and 300/s), hopefully one of them will work for you too.
10 per sec works in smp mode. It's a mystery why dmp mode works at 1 per second.
DMP mode uses a cycle time of 94 milliseconds (chosen arbitrarily, so it's not a multiple of 10). The display refresh is asynchronous, which makes DMP appear as choppy.

*

Offline Ant

  • ****
  • 492
Re: SX60HS Porting
« Reply #443 on: 04 / July / 2016, 16:40:04 »
Is Edge Overlay module works properly here?
On my EOS M3 it's not ok.
I suspect that this is because new viewport pixel formats are stil not impemented in main CHDK branch


Re: SX60HS Porting
« Reply #444 on: 04 / July / 2016, 20:21:41 »
Yes, we need to implement code to process the new pixel format for Digic6.  I think this is necessary for Motion detect and Zebra as well.
Looks to me like edgeoverlay could be implemented with a small hack to edgeoverlay.c/ function average_filter_row. Maybe keyed on THUMB_FW or some other variable in platform_camera.h.
« Last Edit: 04 / July / 2016, 22:05:41 by 62ndidiot »

Re: SX60HS Porting
« Reply #445 on: 04 / July / 2016, 22:53:16 »
That being said, while the likes of reyalp, srsa and others have probably thought a lot more abou what is  the best approach than I have, it does look like it's not too difficult to customize each module to deal with the new viewport pixel format.
Edit:
Looked further...it's difficult..it looks like you need to support core/gui_draw.c digic6 functions which aren't there yet for edgeoverlay..motiondetect might be easier.
« Last Edit: 05 / July / 2016, 14:38:13 by 62ndidiot »

*

Offline srsa_4c

  • ******
  • 4430
Re: SX60HS Porting
« Reply #446 on: 05 / July / 2016, 20:43:10 »
One of the difficulties is that parts of the CHDK code still expect a one byte/pixel overlay. Some routines (maybe zebra, edge overlay) save and restore parts of the overlay during their activity - that is currently impossible on D6 (the overlay data not only has a different pixel format, it also has opacity information in a separate buffer). And of course, the drawing routines need to be optimized for greater speed. All this would have to be solved before "fixing" zebra and edge overlay.

Re: SX60HS Porting
« Reply #447 on: 06 / July / 2016, 22:48:24 »
I am a noob. And just bought a SX60. Have been using CHDK on SX50 and loved it.

Can I safely assume there is no current way to use CHDK on SX60 ? Or if there is can someone be helpful where the instructions are ?

Would greatly appreciate the help.


*

Offline reyalp

  • ******
  • 13502
Re: SX60HS Porting
« Reply #448 on: 06 / July / 2016, 23:43:54 »
I am a noob. And just bought a SX60. Have been using CHDK on SX50 and loved it.

Can I safely assume there is no current way to use CHDK on SX60 ? Or if there is can someone be helpful where the instructions are ?
There are test builds posted earlier in the thread. I'd suggest going back through the posts until you find the most recent one.

Note that quite a few features are not implemented yet, most stuff that relies on the display data like histogram, zebra, motion detection etc.
Don't forget what the H stands for.

Re: SX60HS Porting
« Reply #449 on: 06 / July / 2016, 23:58:21 »
Thank you. Will go through.

 

Related Topics