the sx20 porting thread

Microfunguy

Please give a link to the script that you are using.

vincecove

now i use motion detect video button and now is OK tank's for your great work bye bye

vincecove

i have used the script in chdk scripts page
the link is this
http://chdk.wikia.com/wiki/Category:Scripts

vincecove

but for the video button version i don't remember where i have downloaded this sorry, if you want give me your e-mail so i send you a zip file with this scripts bye

afrikaa

hi,
I tried shooting on the remote SX20 1.02c 1.02d with CHDK firmware does not work!
The CHDK 1.02d works quite well with a few restarts.
Can anyone solve the problem of remote shooting?

Microfunguy

vincecove
but for the video button version i don't remember where i have downloaded this

That is OK, I have those scripts.

vincecove

ciao afrikaa ma tu sei italiano?
😀

rseery

Nevermind.

fe50

rseery
Try as I may, I cannot download the 1.20D beta from the link on that page. Megaupload prompts me for the captcha and I enter it, wait the 25 secs, and then it just reprompts the captcha. No error messages from mega. Can someone reup this to Mega and provide a new link? The one from the SX20 Links page appears to be defective...

No, the link is ok, download too; maybe a problem with your browser / popup,- or adware blocker...

--> additional dl location for file sx20-102d-0.9.9-919-full_beta.zip is here: drop.io dl link.

Marek89

For 102B nothing ?

fe50

Marek89
For 102B nothing ?

As you can see from SX20 - Porting process & links on the wikia page, CHDK for the SX20 102.B is available from the CHDKDE Autobuild Server...

Marek89

I download for 102B and in menu is not CHDK or update firmware.

cacharrin

You need to make the card Bootable, and "Lock it" by moving the "Lock" button in the SD card.

ultimA

This weekend I did some work on CHDK again and completely rewrote the edge overlay. Together with f_m_b's patch you should not experience crashes with zebra or edge overlay anymore. Here is a complete build for 1.02d: http://www.megaupload.com/?d=2RPMWXLR (already has f_m_b's patch + new edge overlay)

For more information about the much better edge detection, see its topic with all the gory details: https://chdk.setepontos.com/d/5583

reyalp

From another thread, but it belongs here:

ultimA
I wanted to bring manual loading support to the SX20. I know it is stated a thousand times that CHDK does not support this for this camera, but it was never said why. I thought it was because no one has bothered finding the key/iv for it.

No, it's because no one got it to work (same for SX1). The keys have been known for a long time. If someone knew the answer to your questions, it would be done. There is no specific SUBCPU code in CHDK. My guess would be some hardware initialization that happens differently in the two loading processes, but there are probably other possibilities.

f_m_b

f_m_b
By the way "zebra blink mode" doesn't work with this changes.

With -Restore original screen "off"- "zebra blink mode" doesn't work on my sx20 (1.02b). But i don't have problems with that. If i want blinking zebra i set this option to "on".

ultimACan you be more specific in what way "zebra blink mode doesn't work" in your patch? For me it seems fine.

Settings:
Zebra mode "Blink 1/2/3"
Restore original screen "off"
Restore OSD "off"
Draw over zebra "Histo/OSD"

ultimA
... However, first we must confirm whether the patch zebra_2 really has shortcomings other than the flickering or not. You said it has, but I didn't notice it. If it is working just as good for others as it has for me, my changes for zebra become unnecessary. So please describe what settings did you use when it stopped working and in what way it didn't work.

Zebra works realy stable and fine on my sx20. I allthough use "Extra Photo Operations->Enable Ev switch" and zebra reacts fine while changing Ev with jogwheel.
I know only the following problems:
- Flickering
- No blinking with the settings above
- Changing Ev greater +/- 8 doesn't actualize zebra.
I think this is ok and this are little problems for the benefit of no crashes.

ultimA
And about the flickering in the osd, I don't think anyone will be able to solve that unless some double buffering is implemented. In your patch for example, first the zebra is painte onto the screen (overwriting every osd element), and then the osd is painted. So there is a short time frame when only the zebra is visible without the osd, this is where the flickering comes from. You won't be able solve that by tinkering with lib.c.

You are right. The internal asynchronous refresh of the firmware makes the changes in lib.c obsolete-> so we can revert lib.c.
I nice trick to stop flickering while "half-shutter" is pressed: Release the shutter button for a (realy) short time and press "half-shutter" again. On my sx20 it works fine.

ultimA

Ok, so the zebra is there but it doesn't blink, I confirm it. Yes it is much better than crashing the camera. So we have following options:
- We leave it as it is, it's good enough
- Prohibit displaying the histo (or OSD) the same time as zebra
- Implement double buffering either in zebra or globally.

The 2. option is listed just for completeness and I think we can forget about it. The first option is viable if we just want to get the port ready as soon as possible. But the best option ultimately would be 3 if you ask me, globally. To avoid memory problems we would have to use compression for the backbuffer too. That means i) limiting all drawing done in CHDK to eg. 16 colors ii) needing to speed up the bitvector, probably with inline ASM.

The limit of 16 colors is acceptable, since we are already using a palette to draw we cannot display full color images anyway. And 16 are more colors than any part of CHDK is using at the same time actively at the moment.

The speedup is a bit more tricky, since I have already tried it but failed because I lack expertise, so someone's help would be greatly appreciated (you can find my experiment commented out in bitvector.c, in ptach for edge overlay). We are talking about just a few lines of ASM, not hundreds. But I'm not sure if it would be enough, so this experiment might fail in the end so that we might be forced to take option 1. But I think it's worth a try.

ultimA

On a separate note: I suspect vid_get_viewport_height() and vid_get_bitmap_screen_height() should be defined to 270 instead of 240. Any reason why it's 240?

If I define it to 270 I can draw more towards to the bottom of the screen, no overflow and I can still see what I draw. So shouldn't it be 270? Or am I misinterpreting something? My error.

(As a side note: I fixed the ON/OFF button working normally. I'm telling so that nobody needs to work on that anymore.)

f_m_b

Half Bug: f_m_b Aug 13-> Half Shutter pressed, changing "light correction" with jog-wheel. Display doesn't actualize every time the "light correction".

The display don't actualize if the Ev value is too big +/-6. But you can't see this value on scren when osd is active, because "Enable Fast Ev switch?" is set in "Extra Photo Operations" and not as osd-parameter.

I mix some osd/"external Photo options" and show Ev-Value if zebra and osd are active and "Enable Fast Ev switch?" is set.
Whith this changes we don't fix the problem, but we can avoid a oversetting of Ev.

What do you think about it?
Better ideas?

Patch to show Ev-Value with zebra

ultimA

Again, I am missing something. Sorry I feel so stupid. But I just tried and I don't seem to be having a problem with this. I have
- Fast Ev Enabled
- Show Ev enabled in OSD settings (Misc.)
- Zebra enabled (both Solid or Blink)

I can see the Ev printed at the right side of the screen when the zebra is not displayed. When the Zebra is displayed, then everything should be missing.

As a technical note, you should put all the drawing before draw_set_draw_proc(NULL), like this

+                if (conf.fast_ev)
+                {
+                  gui_osd_draw_ev();
+                }
                 draw_set_draw_proc(NULL);

It doesn't matter for the SX20 (since we are in both cases drawing to the framebuffer directly), but this order does matter for other cameras. Also as a side note, since the drawing code is different in the sx20 for the zebra (no buffering), I'd advise you to be extra cautious not to disturb other cameras while making changes to the zebra, since the results that we see on the screen could be slightly differnet from other cameras.

« Previous Page Next Page »