SX60HS Porting - page 42 - DryOS Development - CHDK Forum

SX60HS Porting

  • 915 Replies
  • 287530 Views
Re: SX60HS Porting
« Reply #410 on: 25 / May / 2016, 13:31:09 »
Advertisements
Sorry, my inexperience with svn, I have added filewrite.c.  Hopefully this patch is up to standard :)
I do regularly update my svn copy to the latest version.

*

Offline reyalp

  • ******
  • 13502
Re: SX60HS Porting
« Reply #411 on: 25 / May / 2016, 16:35:49 »
Sorry, my inexperience with svn, I have added filewrite.c.  Hopefully this patch is up to standard :)
From a quick look, this one seems fine. Will try to add it tonight.
Quote
I do regularly update my svn copy to the latest version.
Oops, that part was my mistake, I was looking at the wrong file when I made the comment about versions :-[
Don't forget what the H stands for.

Re: SX60HS Porting
« Reply #412 on: 25 / May / 2016, 19:06:46 »
So what to do now? I made a skeleton movie_rec.c from capdis of task_MovieRecord and stuck in various LogCameraEvent to see what happens in the branch table...
It seems that it is always for start recording case 0, followed by one of cases 2,4,7 (all same address), followed by stop recording case 1, case 2,4,7.
Haven't nailed down bitrate at all, tried monitoring two different memory locations, but I'm not sure really what to look for, likely addresses in the code are near 0x13a60 and 0x13ae0:
Code: [Select]
0x00013a60 64superslomo or standard 30fps
0x00013a60: 0x2f000102 0x00010000 0x00000000  0x000f0000 <----this looks interesting
0x00013a70: 0x00060002 0x0820015a 0x0822015c 0x08260160
0x00013a80: 0x0824015e 0x0828045c 0x082a045e 0x082c0460
0x00013a90: 0x082e0462 0x08300464 0x0832010a 0x00000000

con 1> rmem -i32 0x13a60 16 standard 60fps
0x00013a60 64
0x00013a60: 0x2f000102 0x00010000 0x00000000 0x001e0000 <----this looks interesting
0x00013a70: 0x00010002 0x09cc0154 0x09ce0156 0x09d2015a
0x00013a80: 0x09d00158 0x09d403fa 0x09d603fc 0x09d803fe
0x00013a90: 0x09da0400 0x09dc0402 0x09de0108 0x002011d8

0x00013a60 64 iframe
0x00013a60: 0x2f000102 0x00010000 0x00000000 0x00030000<----this looks interesting
0x00013a70: 0x00010002 0x080c015a 0x080e015c 0x08120160
0x00013a80: 0x0810015e 0x08140448 0x0816044a 0x0818044c
0x00013a90: 0x081a044e 0x081c0450 0x081e010a 0x002011d8

Also looked at
Code: [Select]
Standard mode 30fps (before recording)
0x00013ae0 64
0x00013ae0: 0x00000000 0x00000000 0x00000000 0x00000000
0x00013af0: 0x00000000 0x00000000 0x00000000 0x00000000
0x00013b00: 0x00000000 0x00000000 0x00000000 0x00000000
0x00013b10: 0x00000000 0x00000000 0x00000000 0x00000000
con 1> rmem -i32 0x13ae0 16 (while recording)
0x00013ae0 64
0x00013ae0: 0x00000000 0x00000001 0x00000001 0x00000000
0x00013af0: 0x00000000 0x00000000 0x00000000 0x00000000
0x00013b00: 0x00000000 0x00000000 0x00000000 0x00000000
0x00013b10: 0x00000000 0x00000001 0x00000001 0x00000000
« Last Edit: 25 / May / 2016, 19:09:17 by 62ndidiot »

*

Offline srsa_4c

  • ******
  • 4430
Re: SX60HS Porting
« Reply #413 on: 25 / May / 2016, 20:02:31 »
So what to do now? I made a skeleton movie_rec.c from capdis of task_MovieRecord and stuck in various LogCameraEvent to see what happens in the branch table...
It seems that it is always for start recording case 0, followed by one of cases 2,4,7 (all same address), followed by stop recording case 1, case 2,4,7.
Haven't nailed down bitrate at all, tried monitoring two different memory locations, but I'm not sure really what to look for, likely addresses in the code are near 0x13a60 and 0x13ae0:
I have also done something similar, but stopped when I found out that most of the compression (and multiplexing?) related code is likely not running on the ARM core.
That makes the whole movie related code completely different on DIGIC 6, and needs original research.


*

Offline reyalp

  • ******
  • 13502
Re: SX60HS Porting
« Reply #414 on: 26 / May / 2016, 01:32:32 »
Don't forget what the H stands for.

*

Offline srsa_4c

  • ******
  • 4430
Re: SX60HS Porting
« Reply #415 on: 28 / May / 2016, 20:07:20 »
Has any of you experienced rare crashes when using a larger number of exposure overrides? Here's an example. An sx520 user is reporting about these, and I can't find an explanation. The code path causing trouble exists on all new CMOS models (including the sx60 and g7x).

Re: SX60HS Porting
« Reply #416 on: 29 / May / 2016, 02:31:03 »
I tried a couple of shots with the settings shown in the link.  Flash up. No crash. Fairly dark setting came out bright.  Is the crash associated with severe over exposure?

*

Offline srsa_4c

  • ******
  • 4430
Re: SX60HS Porting
« Reply #417 on: 29 / May / 2016, 10:20:49 »
I tried a couple of shots with the settings shown in the link.  Flash up. No crash. Fairly dark setting came out bright.  Is the crash associated with severe over exposure?
Thanks for trying. Unfortunately, only few details are known, and the reports come from a single person. Here's my related post.


Re: SX60HS Porting
« Reply #418 on: 07 / June / 2016, 20:55:31 »
I'm having trouble finding a lens profile for the SX 60 HS. I could build one using lensfun I suppose, but I can't find it using Adobe lens profile downloader. Anyone have a suggestion?

Re: SX60HS Porting
« Reply #419 on: 12 / June / 2016, 18:37:29 »
Hi to everyone,

I am from Croatia and I am new to this forum and I joined because I am the owner of Canon SX60 HS and I really like the camera. One of the reasons I bought it is because I wanted to use it to shoot timelapse videos.

I tried your pre Alpha release and I can tell you that intervalometer script works just fine. Disabling of dark frame substraction is also working and I am very happy with that. But, there is one strange thing which happens sometime. Sometime the camera is taking pictures rotated for 90 degrees clockwise. I found that if I first take only one picture without activating CHDK and after that if I start chdk then pictures are taken in proper orientation.

Firmware is 100b and I am using intervalometer script which is already inside the chdk. I am also shooting only jpeg, not raw.


Any suggestions are welcomed and if I can help somehow in process of porting CHDK to this awesome camera just let me know.

Regards,
gile2004


 

Related Topics