EOS M3 porting - page 47 - DryOS Development - CHDK Forum  
« previous next »
Pages: 1 ... 42 43 44 45 46 [47] 48 49 50 51 52 ... 62   Go Down

EOS M3 porting

  • 613 Replies
  • 206376 Views
*

Offline Ant

  • ****
  • 431
Re: EOS M3 porting
« Reply #460 on: 21 / March / 2018, 10:46:49 »
Advertisements
I can only say that motion detection feature was implemented on M3 port in 2016.
Not sure it will react on bees. You need to check this by yourself...
Logged
*

Offline reyalp

  • ******
  • 12149
Re: EOS M3 porting
« Reply #461 on: 21 / March / 2018, 12:57:44 »
Quote from: PhotonDecay on 20 / March / 2018, 20:22:56
Will this work?  Is there a recommended motion detection script for the M3?
The current version of MDFB works on other digic 6, so should probably work on M3 as well https://chdk.setepontos.com/index.php?topic=10864.0
Logged
Don't forget what the H stands for.
*

Offline Ant

  • ****
  • 431
Re: EOS M3 porting
« Reply #462 on: 22 / April / 2018, 15:59:23 »
Here you can find test build with Movie mode support for fw101a

IMHO the bitrate meter sometimes displays strange values...

« Last Edit: 22 / April / 2018, 16:03:08 by Ant »
Logged
*

Offline srsa_4c

  • ******
  • 4023
Re: EOS M3 porting
« Reply #463 on: 24 / April / 2018, 14:28:20 »
Quote from: Ant on 22 / April / 2018, 15:59:23
IMHO the bitrate meter sometimes displays strange values...
How strange?
The latest patch (which will probably break shortly) does not contain this fix - multiple recordings in a row will display nonsense 'remaining time'.
The other issue I'm aware of is that recorded file size info (and current bitrate) only updates when a chunk of movie data is passed to APENDSTRM (a chunk is 3 MB or something close).
Can you add 120f too? (No rush)
Logged
*

Offline Ant

  • ****
  • 431
Re: EOS M3 porting
« Reply #464 on: 24 / April / 2018, 15:52:16 »
Quote from: srsa_4c on 24 / April / 2018, 14:28:20
How strange?
On static scenes it displays 1900 - 3200 KB/s, but sometimes I see 9300 KB/s. (FullHD 25fps).
When I turn on 3x CBR video mode it displays 3100-6300KB/s and somtemes it increases up to 13000-30000KB/s.
Quote
Can you add 120f too? (No rush)
a few days later...
Logged
*

Offline srsa_4c

  • ******
  • 4023
Re: EOS M3 porting
« Reply #465 on: 24 / April / 2018, 16:32:53 »
Quote from: Ant on 24 / April / 2018, 15:52:16
sometimes I see 9300 KB/s. (FullHD 25fps).
(...)
it increases up to 13000-30000KB/s.
Just tried on M10, I don't see such anomalies. There could be a bug somewhere...

The current bitrate calculation could use some improvements as jumping values like
Quote
3100-6300KB/s
are not really correct or helpful (I get similar results).
Logged
*

Offline Ant

  • ****
  • 431
Re: EOS M3 porting
« Reply #466 on: 25 / April / 2018, 12:50:17 »
Quote from: srsa_4c on 24 / April / 2018, 14:28:20
Can you add 120f too? (No rush)

blind port for fw.120f
Need to be tested on real camera...
Logged
*

Offline srsa_4c

  • ******
  • 4023
Re: EOS M3 porting
« Reply #467 on: 26 / April / 2018, 14:28:01 »
Thx for 120f.
Quote from: Ant on 24 / April / 2018, 15:52:16
When I turn on 3x CBR video mode it displays 3100-6300KB/s
Turns out, the current method of calculating current bitrate does not work very well. The chunks do not come in a steady rate, which is why the calculated bitrate is jumping up/down. I'll try moving the calculation elsewhere, and/or apply some averaging. I'll update the proposed patch when done. This will not affect camera specific code.
Logged
*

Offline srsa_4c

  • ******
  • 4023
Re: EOS M3 porting
« Reply #468 on: 29 / April / 2018, 12:45:27 »
Quote from: srsa_4c on 26 / April / 2018, 14:28:01
Turns out, the current method of calculating current bitrate does not work very well. The chunks do not come in a steady rate, which is why the calculated bitrate is jumping up/down.
I could not come up with a satisfactory solution, so I removed the D6 specific bitrate calculation. Patch updated.
Logged
*

Offline Ant

  • ****
  • 431
Re: EOS M3 porting
« Reply #469 on: 29 / April / 2018, 13:33:57 »
Quote from: srsa_4c on 12 / February / 2018, 13:57:32
- The audio/video codec & muxer core's memory. Its firmware is above 0xe00000 (sx280, m10), its work RAM seems to be above 0xf00000 (only checked on sx280). This is another Xtensa variant (many things suggest so), configured as big endian. I have not been able to decode its instructions, except for one (retw.n: 0xd1, 0x0f).

I found that some names of exceptions(for example at 0x00E0A1D8) are similar to:
https://github.com/espressif/esp-idf/blob/master/components/esp32/include/xtensa/corebits.h

There are strings containing "bitrate" at aria 0x00E00000. Maybe bitrate information can be taken from there?
« Last Edit: 29 / April / 2018, 13:37:56 by Ant »
Logged
Pages: 1 ... 42 43 44 45 46 [47] 48 49 50 51 52 ... 62   Go Up
« previous next »
 

Related Topics