Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Greg

Pages: [1] 2 3 ... 24
The last time I looked at the M50 rom dump was almost a year ago. There was a lot of functionality not visible in the menu but I don't remember.
If the R/RP has this feature, the M50 should also have it, but not visible in the menu.

You can check - "GUI_SetIsoSettingStep"

Modules Development / Re: Full-resolution silent pictures (
« on: January 16, 2021, 01:50:18 AM »
This can work on all cameras (as long as there is enough RAM on the cheaper ones), but requires some research.
If you average a large number of frames, you will limit the DR by a 14bit file.  ;)

Modules Development / Re: Full-resolution silent pictures (
« on: January 16, 2021, 01:01:24 AM »

Yes I know I can do that and use normal approaches to construct bracket sets for processing in post, eg

My suggestion is to do this in camera, ie before outputting the FRSP image.


My version doesn't have the delay between frames, create buffers before capturing.
Postprocess motion blur control is better. If you want to do it in camera and not wait a few minutes you have to use TWOADD (digic4) or EekoAddRawPath (digic5).
I've never had digic5 camera so I don't know how the Eeko works.

TWOADD low level frame subtraction -
If you have an idea how to reconfigure to get adding frames, this should work.

also be nice to be able to shoot 120p at 4k :)

We can get 8K@120FPS. It will work like 4K in M6II - M6II vs M50 4K ;D

M50 1.0.3

Is this based on the infamous "fishy" build?
I don't have the "fishy" build code. This is digic6-dumper branch and stubs, consts, button codes, several modifications (bmp_vram, disabled audio tasks etc).

You can load "fishy" autoexec.bin in IDA/ghidra, convert the file M50_101.sym to idc script to name the functions.

The M50 sensor is too slow to do this. You need 2x more data to read a dual pixel. So maybe at 10-15 FPS?
At the current stage of development, we should not think about such advanced features.

Yes, each camera has a different x sync calibration. You can change this value, but I don't know where (prop/eeprom).
Proposed name for the module ""  ;)

A few years ago I used arduino as a shutter button. Arduino sent a signal to the camera (shutter release connector) and then to the radio triggers.
This may be somewhat unstable. In some modes, the camera has a random delay.

Was reading chdk's wiki last days and then shocked seeing they could do some kind of 1/60000 flash sync speed.
It's possible for a CCD sensor.

this one I didn't understand.
A1ex knows how to change the aperture during FRSP exposure. If you know how to trigger a flash at the right time. You can try :
- Start FRSP @ F16
- set the aperture to F1.4
- trigger the flash
- set the aperture to F16

Wanna achieve soemthing like this for cheap

You can try "leaf shutter" by changing the aperture value when capturing FRSP.

I compiled this code in digic6-dumper branch. This is not ML, but 2 features with which the M50 is more useful.

These few lines of code modify properties, unlock features that the M50 doesn't have in the Canon menu.

M50 1.0.2 - manual silent shutter (M, Av, Tv, P) also works in continuous mode :

Code: [Select]
THUMB_FN(0xE053607E, GUI_SetSilentShutter)

#define SilentShutter_OFF           0x0
#define SilentShutter_ON            0x1

extern int GUI_SetSilentShutter(int);

30s - 1/4000s - OK
Bulb - ERR70

M50 1.0.2 - 7 frames exposure bracketing

Code: [Select]
THUMB_FN(0xE04E05BE, GUI_SetCFnBktSheetsData)

#define BktSheets3                  0x3
#define BktSheets5                  0x5
#define BktSheets7                  0x7

extern int GUI_SetCFnBktSheetsData(int);

So RP and M50 still have only automatic electronic shutter mode?
I thought these few lines of code were not a problem for them.

Camera-specific Development / Re: Canon 90D
« on: September 02, 2019, 11:06:40 PM »

Camera-specific Development / Re: Canon 90D
« on: August 28, 2019, 05:45:23 PM »
DR isn't better compared to the previous generation of sensors  ???

Right now I'd really like to unset the camera boot flag because when inserting a card that has ML for another camera on it the M50 just goes into a coma.

The EOS R too, just compared it.

EOS R (before/after)

Any tutorial how to remove that kind of banding? Or just dark frame substraction?Didn't the latest firmware for EOS R solve that?
I don't know if I should publish this script, maybe I should sell it to Canon?

Banding correction 200D (M50 also has this problem) before/after :


M50 - rolling shutter measurements -

It looks like we have 3 readout modes :
Code: [Select]
timer A = 534, timer B = 4061 @ E19EBAC8
timer A = 1064, timer B = 4061 @ E19EBB20
timer A = 772 timer B = 4061 @ E19EBB78

Code: [Select]
[SHTC] ShutterType(1) ReadOutMode(1) ReleaseType(1) // Manual mode, mechanical shutter
[SHTC] ShutterType(3) ReadOutMode(0) ReleaseType(1) // Silent mode, electronic shutter
[SHTC] ShutterType(1) ReadOutMode(0) ReleaseType(2) // Manual mode, mechanical shutter, AEB continuous

ShutterType(1 - mechanical, 2 - ???, 3 - electronic rolling shutter) // 2- electronic global reset?
ReadOutMode(0 - 12 bit, 1 - 14 bit, 2 - ???)
ReleaseType(1 - ???, 2 - ???)

The manual says that the data for continuous recordings are converted into 12 bits...
I didn't know about it.  :o

These histograms show dark frames (lens cap photography).
Look at the histogram and you'll see the missing bits. It looks like 12-bit converted to 14-bit.

Pages: [1] 2 3 ... 24