Display (bitmap overlay)

srsa_4c

reyalp
@Ant asked
IIRC @srsa_4c also had some unresolved concerns, but I didn't immediately see them scrolling back in the thread.

A couple of those:
Possibly abusing something unknown (in addition to the layer scaling hack):
https://chdk.setepontos.com/d/12788/322
Loss of complete overlay when an unsupported video output device is in use (lo-res HDMI, analog video, optional EVF):
https://chdk.setepontos.com/d/12788/323
And surprise cases like this:
https://chdk.setepontos.com/d/12788/329

I still have the sx280 and m10 and will try to continue where I left off.

philmoz

waterwingz
I still have a couple of working G16's. That's one down , three to go.

@waterwingz - which firmware version(s) do you have?

philmoz

62ndidiot
Happy to test sx60hs

@62ndidiot - which firmware version(s) do you have?

waterwingz

philmoz
@waterwingz - which firmware version(s) do you have?

Just 1.01C

Sent from my Pixel 4a using Tapatalk

62ndidiot

I have sx60hs firmware 100f

philmoz

@waterwingz & @62ndidiot

Test versions for G16 1.01c and SX60 1.00f

I have not looked at this for a while so I may have missed something.

g16-101c-1.6.0-6027-full.zip

750.93KB

sx60hs-100f-1.6.0-6027-full.zip

755.87KB

62ndidiot

I tested sx60hs-100f-1.6.0-6027-full.zip . It seems to work very nicely. No more blinking when in shoot (Alt) mode. The menu is steady even with the electronic level displayed. 😁 Zebra, histogram, motion detect work. I was able to crash the camera in CHDK settings: Grid : a few messages flashed and then it shutdown, the SD card needed a file scan/repair after that. However, when I restored to version 1.5.1 choosing the GRID option also does not work, but it doesn't crash the camera. I suspect it is just something that was never right for this camera, as anything with grids is sensitive to the LCD resolution.

philmoz

62ndidiot
I was able to crash the camera in CHDK settings: Grid : a few messages flashed and then it shutdown.

Can you dump a ROMLOG please.

62ndidiot

romlog for sx60hs 100f crash associated with chdk setttings: grid attached

ROMLOG.LOG

620b

62ndidiot

I cannot reproduce the crash when setting grid. Now it shows nothing at all in 1.6.0-6027.
If I load a grid 3x8 from a file it shows a 3x3 grid. Not equal squares. A square in the middle, rectangles around it which are longer in the dimension orthogonal to the shared edge of the square. The histogram briefly blinks over the grid.
So I'm thinking the romlog I attached above might reflect a memory card error after the first crash. So I will use this for awhile and if any crashes occur I'll post a romlog for them. Sorry for confusion.

waterwingz

philmoz
@waterwingz & @62ndidiot
Test versions for G16 1.01c and SX60 1.00f
I have not looked at this for a while so I may have missed something.

Downloaded and installed this version on my G16. Tested in shooting mode with auto focus tracking window enabled and active. Menus and OSD icons all stable with no "flashing". Very nice!

I'm not sure what needs to be tested but I enabled grids and histogram and that worked stably. Took some photos, used CHDK overrides, ran the motion detection script - everything worked perfectly.

I then tried zebra and edge overlay with less success. Using a card setup for 1.6.0-6026 I could see the overexposed regions in zebra mode and edge overlay outlines. Overwriting the older 6026 version on the card with the new 6027 zip file makes the zebra and edge overlay stop working. I went back and forth unzipping to the same card (i.e. same CHDK config each time) but no zebra or edge overlay with the new version. There was no observable response on the LCD to enabling these features.

EDIT : I forgot to say "thank you" to @philmoz for doing this.

philmoz

waterwingz
I then tried zebra and edge overlay with less success. Using a card setup for 1.6.0-6026 I could see the overexposed regions in zebra mode and edge overlay outlines. Overwriting the older 6026 version on the card with the new 6027 zip file makes the zebra and edge overlay stop working. I went back and forth unzipping to the same card (i.e. same CHDK config each time) but no zebra or edge overlay with the new version. There was no observable response on the LCD to enabling these features.

When you get a chance can you try this version please.
This will display 4 numbers at the top left of the display - please post the 4 values from REC mode.

Edit: attachment removed - see later post for newer build.

waterwingz

philmoz
When you get a chance can you try this version please.
This will display 4 numbers at the top left of the display - please post the 4 values from REC mode.

rec mode : 640 -3 480 0
play mode : 360 -3 240 0
video mode 640 -3 360 0

philmoz

waterwingz

philmoz
When you get a chance can you try this version please.
This will display 4 numbers at the top left of the display - please post the 4 values from REC mode.

rec mode : 640 -3 480 0
play mode : 360 -3 240 0
video mode 640 -3 360 0

Thanks - it looks like the ximr_context structure is different to all the other versions so far.
Here is a test build with what I think the new structure is.

g16-101c-1.6.0-6028-full.zip

753.19KB

waterwingz

philmoz
Thanks - it looks like the ximr_context structure is different to all the other versions so far.
Here is a test build with what I think the new structure is.

Edge overlay and zebra now work as expected. I wasn't able to think of any other features to test that might be tied to display buffers. Do you have any things I should also try beyond the ones I listed above?

Also, don't forget to disable four debug numbers before you release this 😉

philmoz

waterwingz
Do you have any things I should also try beyond the ones I listed above?

It would be good to check HDMI output from the camera if possible.

waterwingz

philmoz
It would be good to check HDMI output from the camera if possible.

So after an interesting battle with connectors and cables, I found a combination that allowed me to connect my G16 to an HDMI capable monitor. Every things works fine when I don't load CHDK.

The first things I discovered is that the existing G16 port screws up the HDMI output. I didn't test HDMI when I did the port so perhaps that's not surprising. It looks like a buffer size issue - see the attached image.

Then I tried @philmoz 's new version and that crashed the camera when attached via an HDMI cable. When I say crashed, starting the camera in playback mode seems to begin normally based in the LED pattern. But no output appears on the HDMI port or the camera's LCD and after a couple seconds the camera simply powers off. No battery pull required to restart it - just press the playback or On/Off button again. ROMLOG attached in case it helps.

ROMLOG.LOG

3.93KB

philmoz

waterwingz
Then I tried @philmoz 's new version and that crashed the camera when attached via an HDMI cable.

Thanks for testing - I was afraid there would be problems with HDMI 🙁

I will need to create a version using the old display code that dumps the ximr_context structure data to a file.
Might take a little while.

waterwingz

philmoz
I will need to create a version using the old display code that dumps the ximr_context structure data to a file.

Any thoughts on why CHDK screws up the HDMI output on the current trunk release? I don't recall anything in the porting process specific to HDMI output.

Might take a little while.

Well, I finished the port over four years ago and nobody yet has complained about the HDMI not working ....

philmoz

waterwingz
Any thoughts on why CHDK screws up the HDMI output on the current trunk release? I don't recall anything in the porting process specific to HDMI output.

It probably needs the CAM_SUPPORT_BITMAP_RES_CHANGE flag and the implementation of update_screen_dimensions() in lib.c.

« Previous Page Next Page »