G7 X porting thread [G7_X]

hiker_jon

Sorry,
I didn't think there had been changes. There were no posts to the thread. I should have checked elsewhere.

Jon

hiker_jon

Hi,
Are there any examples of how to use the new gui buffer that has full color with alpha? It occurs to me that (for Digic6) edgeoverlay could be replaced by a function that overlays a previous image (shifted) into the gui at (say)50%alpha with the current record output.

Another question: How do people typically track down recreview_hold? Are there special tools?

Jon

reyalp

hiker_jon
Hi,
Are there any examples of how to use the new gui buffer that has full color with alpha? It occurs to me that (for Digic6) edgeoverlay could be replaced by a function that overlays a previous image (shifted) into the gui at (say)50%alpha with the current record output.

On g7x, the GUI buffer is in exactly the same format as as the viewport. The alpha buffer is just a separate 8 bit opacity (0=transparent, 255 = fully opaque). So in principle, you could just dump the viewport to a file and load it later.

Both are defined in lib.c, and you can see examples of accessing them in gui_draw.c.

However, it would need to be updated every time the display updates, and you would want both the canon and CHDK ui to appear on top of it. Keeping a full copy of your overlay loaded would take up a lot of RAM too.

Having a full color UI opens up a lot of possibilities, but making it play nice with the existing code and not break the portability of CHDK is going to take some thought and effort.

Another question: How do people typically track down recreview_hold? Are there special tools?

My usual approach for most of these things is to look for references in known ports and find equivalent code.

hiker_jon

On this camera the CHDK gui does not appear in recreview mode. Perhaps there are more than one gui bitmaps?
The alt button works, but no menu shows. My build is 4701

reyalp

hiker_jon
On this camera the CHDK gui does not appear in recreview mode. Perhaps there are more than one gui bitmaps?

Note that recreview_hold is currently FAKEDEF'd on this port. From the logic in core/main.c, this will probably prevent CHDK from drawing when it thinks shooting is in progress.

62ndidiot

Note that recreview_hold is currently FAKEDEF'd on this port. From the logic in core/main.c, this will probably prevent CHDK from drawing when it thinks shooting is in progress.

I believe 0x91c0 will work to detect ReviewHold on g7x (100d)...There are actually several nearby addresses which are switched between zero and one's during ReviewHold mode.

reyalp

62ndidiot

Note that recreview_hold is currently FAKEDEF'd on this port. From the logic in core/main.c, this will probably prevent CHDK from drawing when it thinks shooting is in progress.

I believe 0x91c0 will work to detect ReviewHold on g7x (100d)...There are actually several nearby addresses which are switched between zero and one's during ReviewHold mode.

This does not seem correct to me, always 0.

I did find 0x91D4 ~~0x91c0~~ (near 0xfc33be5e, ref to "StartRecReviewTimer"), which is 1 post shoot review, regardless of whether the setting is hold or one of the time based settings.

The normal recreview_hold used in other ports is only 1 when the mode is set to hold. SX280 and the pre-digic 6 sig finder use a variable that's near ShootCon_NotifyStartReviewHold, but the code seems a bit different in g7x.

edit:
pasted the wrong address

62ndidiot

On sx60 100f it's 914c, which appears frequently in the disassembly. I agree the code at notifystartreviewhold doesn't seem to directly reference this or a related value, but it appears about 20 lines down for all sorts of cases.
I verified on my cam it is one during hold along with about five other candidates..915c 91a4 91a8 91f0

hiker_jon

Hi,
On my g7x 100d I think recreview_hold is 0x9194.
I found it by monitoring memory around that area and checking which long words went from zero to non-zero only in recreview mode.

reyalp

hiker_jon
Hi,
On my g7x 100d I think recreview_hold is 0x9194.
I found it by monitoring memory around that area and checking which long words went from zero to non-zero only in recreview mode.

Thanks. Like the one I posted earlier, this is 1 in any recreview, not just "hold". This may be more desirable behavior for some uses, but the normal CHDK implementation is only on "hold"

edit:
0x9194 is slightly different, it stays 1 if the button is held down, while 0x91D4 goes back to zero if you set a fixed review time and hold the button down.

62ndidiot

Interesting. What button are you referring to? I just set the recreview mode in the canon menu, to off, hold, timer seconds on the sx60. Its cancelled by a half press (shoot) and maybe other keys.

reyalp

62ndidiot
Interesting. What button are you referring to? I just set the recreview mode in the canon menu, to off, hold, timer seconds on the sx60. Its cancelled by a half press (shoot) and maybe other keys.

In general on powershots, if you set review to one of the time values and the camera isn't in continuous mode, review is kept on screen as long as full shoot is held.

reyalp

I didn't find a variable with the normal behavior between 0x9000 and 0x93b0, so I checked in recreview_hold as 0x9194. This means the "show OSD in review" will affect all review settings, not just hold.

reyalp

reyalp
Here's a test build for g7x firmware 100c.

This is completely untested, although it's very similar to 100d so there's a fair chance it will work. See the "G7 X notes" section of the included readme for known issues that apply to the G7X port in general.

6 downloads and no reports of whether it works or not? 🙁

62ndidiot

It'd sure be nice to get g7x, sx60hs into the main auto build trunk, just so the user base and feed back would increase.

reyalp

62ndidiot
It'd sure be nice to get g7x, sx60hs into the main auto build trunk, just so the user base and feed back would increase.

I would like to do this too. Some discussion here https://chdk.setepontos.com/d/11316/63

My feeling is still that the non-functional display accessing features like histogram and zebra should be disabled or fixed.

This wouldn't help with the 100c build though, because I wouldn't put a totally untested build in the autobuild. I probably should have set the expiration option.

62ndidiot

I have beta versions of histogram and zebra. I'll post them along with sx60hs builds for testing. They probably need similar adjustments that happened for MD and g7x viewport width versus buffer size.

Steenoe

My G7 X firminfo says:
Canon PowerShot G7 X
P-ID:329D PAL D
Firmware Ver GM1.00B (1.0.0.0)
Did anyone upload that particular firmware version? Otherwise, I would be more than happy to do so 😎

srsa_4c

Steenoe
My G7 X firminfo says:
Canon PowerShot G7 X
P-ID:329D PAL D
Firmware Ver GM1.00B (1.0.0.0)
Did anyone upload that particular firmware version?

I don't think so, I don't see it in my collection.

Steenoe

I don't think so, I don't see it in my collection.

I've posted the adress for download. Let me know if it work as intended.
https://chdk.setepontos.com/d/13057

It would be really cool to have CHDK up and running on the G7 X 😎

« Previous Page Next Page »