Display (bitmap overlay)

pigeonhill

Phil

That did it 😀

BTW, I'll soon be posting a short video of my script running in the new CHDK version.

As I said elsewhere: the M3 is CHDK's flagship camera, or at least one of them 😉

Cheers

Garry

pigeonhill

@philmoz

I did a test video quicker than I thought:

https://photography.grayheron.net/2021/05/exciting-things-happening-in-chdk.html

Once again, thanks for all your hardwork, as well as others that have added their knowledge to the latest developments.

Cheers

Garry
UPDATE 1
Phil noticed a 'strangeness'. My script detects toggling beween ALT and non-ALT. In non-ALT the histogram is switch off via a set_config_value() call. I've checked to see if CHDK registers this OK and it does. What I see is in ALT mode, ie set_config_value(0), the histogram does not always disappear. If I go in and out of ALT a few times, it will disappear.

Ant

@philmoz
Addresses for EOS M3:

101a:
NHSTUB(VTMLock                             ,0xfc37eea1)
NHSTUB(VTMUnlock                           ,0xfc37f071)
DEF(debug_logging_ptr                      ,0x000286A0)
DEF(debug_logging_flag                     ,0x0002869😎
DEF(mzrm_sendmsg_ret_adr                   ,0xfc2fd873)

121a:
NHSTUB(VTMLock                             ,0xfc37f241)
NHSTUB(VTMUnlock                           ,0xfc37f411)
DEF(debug_logging_ptr                      ,0x000286c0)
DEF(debug_logging_flag                     ,0x000286b😎
DEF(mzrm_sendmsg_ret_adr                   ,0xfc2fd8bb)

philmoz

pigeonhill
What I see is in ALT mode, ie set_config_value(0), the histogram does not always disappear. If I go in and out of ALT a few times, it will disappear.

Does the histogram continue to update or is it a static image of the last values before it was switched off?

philmoz

Ant
Addresses for EOS M3:

Thanks, I've added these to the test branch.

I assume the 'msg' parameter is in R11 for the debug logging patch and that the flag bit to enable logging is 0x200.

Ant

philmozI assume the 'msg' parameter is in R11 for the debug logging patch and that the flag bit to enable logging is 0x200.

Yes. The flag bit is the same even for D6 DSLRs.

pigeonhill

@philmoz

Does the histogram continue to update or is it a static image of the last values before it was switched off?

Just tested and, I'm embarrassed to say, I can't replicate the behaviour I saw yesterday. For now, as I switch between ALT and non ALT modes, with my script swtiching on and off the histogram, the histogram is removed OK.

What is a bigger issue, on the M3, is that the CHDK histogram is not reliable, as reported in https://chdk.setepontos.com/d/14342/12;topicseen#new

Thus, for me, the CHDK histogram is not usable on the M3: I'll 'just' be using the Canon histogram.

pigeonhill

@philmoz

Partially ignore my last post, as I can replicate the problem: I had forgotten I coded a 'fix', ie clear the display when I switch between ALT modes 😉

I can confirm the histogram freezes, ie it continues to show a static image.

philmoz

pigeonhill
I can confirm the histogram freezes, ie it continues to show a static image.

@pigeonhill

Please check if the attached version fixes this.

m3-120f-1.6.0-5899-full.zip

758.04KB

pigeonhill

Phil

Looks to have fixed it.

See flashing of the histogram now and then, ie when clearing.

Do I assume this is just an artefact of your solution, ie loop until cleared?

However, as I said, until the CHDK histogram is ‘healed’, I won’t be using it on the M3.

Cheers

Garry

Ant

I modified the viewport dimensions for EOS M3.(in attachment)
I checked it in chdk-ptp with help of fase frame.
But values for EVF are theoretical.(I don't have it)

M3.lib.c.patch

5.08KB

philmoz

Ant
I modified the viewport dimensions for EOS M3.(in attachment)
I checked it in chdk-ptp with help of fase frame.
But values for EVF are theoretical.(I don't have it)

Thanks Ant.

@pigeonhill

Can you please check the edge overlay and zebra display in the EVF with the attached version.

m3-120f-1.6.0-5902-full.zip

757.93KB

pigeonhill

@reyalp

Haven't used zebra before, so had to work out how to use it, ie read the manual 😉

Also, zebras don't work in ALT mode: intentional I guess?

All blinkies, blink every secondish, ie including solid. You can clearly see the blinkies being built, top to bottom, ie over about a sec, creating the additional blinking.

BTW I see there is no option to have blinkies on all the time, ie not needing to press the half shutter. IMHO this would work better when you are adjusting exposure and using blinkies.

EVF blinkies are displaced downwards. BTW I have the Canon EVF-DC2. The offset is about 3/4 of the Canon text showing exposure.

In EVF mode, as the blinkies (slowly) refresh, residue (sparse) pixels are left behind in random patterns.

Cheers

Garry
UPDATE 1
Tried pano edge overlays, with exposure warning on and off. Same result. big blocks of red, taking up about 1/3 of the screen height, with clear (slow) top to bottom scanning visible,

philmoz

@pigeonhill

Test version for G7X 1.00d.

g7x-100d-1.6.0-5915-full.zip

753.73KB

pigeonhill

@philmoz

Quick test, eg with Canon histrogram and CHDK menu and OSD etc, looks good.

As I tweak my G7X bracketing script (different to M3 version, eg lens model and focus move) I will feedback any 'strangeness'.

Cheers

Garry

pigeonhill

@philmoz

When you get a chance, could you also throw a 101d G5X build my way, or point me where to where I can download the build: sorry can't build myself.

Or are you only building to order at the moment?

Cheers

Garry

Caefix

pigeonhill
@philmoz
sorry can't build myself.

😁 All You need is ...
https://chdk.setepontos.com/d/12752/53
... and a mouse ... 😖

pigeonhill

@Caefix

Thanks for the link.

I guess it’s more visceral that I don’t do C and build.

One day I’m sure I will make the transition.

Until then I ‘just’ stick with Lua 😀

Cheers

Garry

philmoz

@pigeonhill

G5X version.

g5x-101d-1.6.0-5918-full.zip

832.8KB

philmoz

Below is a summary of the changes needed in case anyone wants to try the Ximr layer drawing on another camera/firmware version.
As noted in the comments I find the Ghidra de-compiler view is the easiest way to check the values that may need updating.

Use existing port as a base for comparison
If camera has an EVF use G5X or M3 otherwise use G7X or G7X2

platform/CAMERA/makefile.inc
Add CAM_DRAW_RBGA = 1

platform/CAMERA/platform_camera.h
Delete CAM_SUPPORT_BITMAP_RES_CHANGE if present
Add CAM_HAS_DISPLAY_REFRESH_FLAG
Update CAM_BITMAP_WIDTH, CAM_BITMAP_HEIGHT, CAM_SCREEN_WIDTH and CAM_SCREEN_HEIGHT

platform/CAMERA/sub/FIRMWARE/stubs_entry2.S
Copy the definitions for debug_logging_ptr, debug_logging_flag and mzrm_sendmsg_ret_adr from the comparison port
Use the instructions in the comments to find the values for these

platform/CAMERA/lib.c
Copy the Ximr code from the comparison port - should be everything from the Ximr layer typedef to the end of the file
May also need to copy the definitions for displaytype, hdmi_out and evf_out (if camera has an EVF)
~~Check and update the value for FW_YUV_LAYER_BUF using the instructions in the comments~~
Delete the update_screen_dimensions function if present. Check if other functions are dependant on this code (e.g. viewport size functions using values set in this function). If so copy relevant logic to update_ui.
Check the implementation of vid_bitmap_refresh. Will probably need to refresh both buffers by calling transfer_src_overlay twice. If you see old CHDK frames randomly flashing on screen, such as CHDK menu after leaving ALT mode then try the double call to transfer_src_overlay.

platform/CAMERA/sub/FIRMWARE/boot.c
Copy the block of code containing debug_logging_my and patch_mzrm_sendmsg from the comparison port
Add the call to patch_mzrm_sendmsg to the boot function
Make sure the call is after any RAM initialisation otherwise the patch may get overwritten
Check the firmware disassembly and update the following in debug_logging_my
Source for the mzrm_sendmsg ‘msg’ parameter. Most ports store this in R11; but it may also be on the stack (e.g. G7X2)
Message types to detect calls to XimrExe and XimrExeGain

Edit: added note about vid_bitmap_refresh implementation in lib.c
Edit2: removed things that are now found by finish_thumb2

« Previous Page Next Page »