EOS M3 porting - page 14 - DryOS Development - CHDK Forum

EOS M3 porting

  • 696 Replies
  • 300911 Views
*

Offline reyalp

  • ******
  • 13443
Re: EOS M3 porting
« Reply #130 on: 26 / August / 2016, 17:00:27 »
Advertisements
Is DNG RAW shooting correctly implemented in your G7X port?
It seem to work in normal shooting modes like Auto, M, Tv, P. Some of the special scene modes don't.

edit:
Doesn't work == required hook points and/or buffer addresses vary, I haven't spent the time to implement. Also some like HDR probably don't make sense with raw.
« Last Edit: 26 / August / 2016, 17:05:34 by reyalp »
Don't forget what the H stands for.

*

Offline Ant

  • ****
  • 491
Re: EOS M3 porting
« Reply #131 on: 26 / August / 2016, 17:42:24 »
May be you will fix CR2 file extensions in ptpCHDK?
Also I am still waiting for Digic 6 frame buffers support.
More than ten months gone since it was implemented there:
https://chdk.setepontos.com/index.php?topic=6231.msg125049#msg125049
Please.
« Last Edit: 26 / August / 2016, 17:46:03 by Ant »

Re: EOS M3 porting
« Reply #132 on: 26 / August / 2016, 22:07:02 »
I'm also waiting, but still using live view in chdkptp. Noticed something strange the other day.  I have roughly adapted zebra and histogram (.c). Zebra displays a semitransparent green overlay on my lcd.  In chdkptp it is totally opaque. @Ant I'm happy to share the code....its in need of more work, and needs someone who is familiar with how it is "supposed" to work.

Edit: see attached
« Last Edit: 27 / August / 2016, 17:26:47 by 62ndidiot »

*

Offline reyalp

  • ******
  • 13443
Re: EOS M3 porting
« Reply #133 on: 26 / August / 2016, 22:37:45 »
May be you will fix CR2 file extensions in ptpCHDK?
By "support" I mean actually updating the the protocol to handle both jpeg and crw, not just changing the extension. Unfortunately, CHDK is not really aware of canon raw (whether the camera supports and whether it is enabled etc), so it is once again less simple than it might appear on the surface.
Quote
Also I am still waiting for Digic 6 frame buffers support.
More than ten months gone since it was implemented there:
https://chdk.setepontos.com/index.php?topic=6231.msg125049#msg125049
Please.
I am slowly working on this and the motion detection patch, e.g. r4675. If you want to speed things up, you are welcome to submit patches. Otherwise, it will happen when it happens...
In chdkptp it is totally opaque.
That's because the quick hack from the chdkptp thread doesn't transfer the alpha (opacity) buffer.
Don't forget what the H stands for.


Re: EOS M3 porting
« Reply #134 on: 26 / August / 2016, 23:32:22 »
FWIW ant's motion detector dot c works fine on Sx60hs.
I'm not very familiar with edge overlay. Is it best to have a very fine resolution (I.e. Thin lines that sometimes become dashes or thicker more definite lines; this is a function of the step size)

Re: EOS M3 porting
« Reply #135 on: 02 / September / 2016, 07:45:19 »
Hello all.
I had read this thread, but have questions.
If i will use CHDK(downloaded from this post https://chdk.setepontos.com/index.php?topic=12542.msg129050#msg129050), can i use wired remote control for my eos m3? Which firmware version i will use for it (i think 1.0.1.a, but can't find link for download it, just 1.0.1)

*

Offline Ant

  • ****
  • 491
Re: EOS M3 porting
« Reply #136 on: 02 / September / 2016, 09:50:47 »
can i use wired remote control for my eos m3?
Yes, but I'm not sure about full functionality...
If you need liveview thru USB you can use special build of ptpCHDK

Here you can find fresh CHDK for Canon EOS M3 firmware 1.0.1 (1.01A is an internal name)
« Last Edit: 02 / September / 2016, 09:59:49 by Ant »

*

Offline Ant

  • ****
  • 491
Re: EOS M3 porting
« Reply #137 on: 11 / September / 2016, 13:00:23 »
Exploring RAM dumps I found that RAW buffer width  is 6112 pixels.
But canon's CR2 files have 6096 sensor width.
Which value is correct?
Maybe G7X has this difference too...
« Last Edit: 11 / September / 2016, 13:01:55 by Ant »


Re: EOS M3 porting
« Reply #138 on: 11 / September / 2016, 13:53:04 »
I had a similar problem with the sx60hs which caused corruption. Need to use the true sensor dimensions in platform camera.h

You can find these in exif information.

*

Offline Ant

  • ****
  • 491
Re: EOS M3 porting
« Reply #139 on: 11 / September / 2016, 14:29:54 »
You can find these in exif information.

I'm using ExifTool v.10.21
JPG files do not contain sensor dimensions.
CR2 files contain sensor width that does not match with buffer width

 

Related Topics