All images include the (on-sensor) phase detect pixels.
Unfortunately, the old LiveImageTool.Pause and LiveImageTool.Resume event procedures no longer work (they are empty), so the Canon menu needs to be active when running Capture.WholeParallel...
I did not check other cameras yet.
Maybe it's bad pixels.
There is also difference in RAW_TYPE register.
How to thrace what happend when camera enter to the Canon menu?
Did you find a reference to that somewhere in fw?
RAW_TYPE_REGISTER FC1BC312 RAW_TYPE_REGISTER_0 FC1CCCD8 RAW_TYPE_REGISTER_1 FC23CFC8 RAW_TYPE_REGISTER_2 FC23D922 RAW_TYPE_REGISTER_3 FC3E068E RAW_TYPE_REGISTER_4 FC3E06BC RAW_TYPE_REGISTER_5 FC3E06E2 RAW_TYPE_REGISTER_6 FC543DC6
I'm sure they are the phase detect pixels (they have visible pattern and don't cover the sensor's outer areas*). Additionally, there are also bad pixels.
So manual checking of 300+ references to 0xC0F37000 gives these addresses
Maybe there is more easy way to find function calls with certain arguments?
Finaly I found the way to remove bad pixels.EnableHeadDirectCapturePath function need to be called before EvfCaptureSystem.
The phase detect pixels remain, though.
On M3 there is no phase detect pixels with or whithout EnableHeadDirectCapturePath.
Interesting. I wonder if it's due to different fw code (different raw type used) or the third generation of "Hybrid CMOS AF" has separate readout for those phase detect pixels.
After calling SetSafFPGABypassMode I've got an image with some sort of focus pixels.
Started by pelle2004 General Discussion and Assistance
Started by brumela General Discussion and Assistance
Started by spamsickle « 1 2 » Feature Requests
Started by 24hrexposure Feature Requests
Started by waterwingz General Chat