The SX1 IS Porting Thread - page 21 - General Discussion and Assistance - CHDK Forum
supplierdeeply

The SX1 IS Porting Thread

  • 381 Replies
  • 108181 Views
*

Offline pev69

  • **
  • 55
Re: The SX1 IS Porting Thread
« Reply #200 on: 20 / April / 2009, 06:49:48 »
Advertisements
Hmm, I guess there should be an option in the menus whether you want the canon OSD elements visible either:
1) never when zebra enabled
2) only during the "non-blink" phase of blinking zebra
3) always

In general about the OSD (both canon and CHDK) I was thinking that the user should be able to determine the order in which the different overlay elements (canon, zebra, edge, grid, CHDK osd, CHDK histogram...) are drawn.

Also I am planning to change the GUI-drawing system, because at the moment it is a bit mixed up, and also things like the zebra are unnecessarily consuming more RAM (albeit sometimes only temporarily, but this can still lead to RAM fragmentation, which is not good and can potentially lead to trouble in the firmware) particularly if trying to "restore" the original OSD. My new system would draw all elements in the same frame-buffer, and when combined with the user-defined drawing order, should be consistent, more user- and firmware-friendly, and potentially faster and more efficient.

I know, this all sounds so pompous, but I'll see what I can do :)
« Last Edit: 20 / April / 2009, 07:17:49 by pev69 »

*

Offline reyalp

  • ******
  • 12159
Re: The SX1 IS Porting Thread
« Reply #201 on: 20 / April / 2009, 21:23:17 »
Also I am planning to change the GUI-drawing system, because at the moment it is a bit mixed up, and also things like the zebra are unnecessarily consuming more RAM (albeit sometimes only temporarily, but this can still lead to RAM fragmentation, which is not good and can potentially lead to trouble in the firmware) particularly if trying to "restore" the original OSD. My new system would draw all elements in the same frame-buffer, and when combined with the user-defined drawing order, should be consistent, more user- and firmware-friendly, and potentially faster and more efficient.

I know, this all sounds so pompous, but I'll see what I can do :)
Pompous or not, if you can do it, that would be GREAT. The gui system is a mess. FWIW, I found the variable that stores the current canon bitmap buffer for the SD990. This is listed in lib.c along with hints to finding it.

I'll try to look at the zebra stuff as soon as I can if none of the other devs get to it, but I'm going to be quite busy for the next few days :(
Don't forget what the H stands for.

*

Offline pev69

  • **
  • 55
Re: The SX1 IS Porting Thread
« Reply #202 on: 21 / April / 2009, 00:30:16 »
Also I am planning to change the GUI-drawing system, because at the moment it is a bit mixed up ...
I know, this all sounds so pompous, but I'll see what I can do :)

Pompous or not, if you can do it, that would be GREAT. The gui system is a mess. FWIW, I found the variable that stores the current canon bitmap buffer for the SD990. This is listed in lib.c along with hints to finding it.

Hey, good, and thanks. I'm further encouraged now :)

Quote
I'll try to look at the zebra stuff as soon as I can if none of the other devs get to it, but I'm going to be quite busy for the next few days :(

Great. Although it is a really small change, and does not change anything for other cameras (for which the CAM_HAS_VARIABLE_ASPECT is not defined), so you could just replace the files in the trunk right away ;).

EDIT: Well, the only significant change for other cameras is that the buffer is cleared once it has been succesfully malloc'ed.
« Last Edit: 21 / April / 2009, 00:33:39 by pev69 »

Re: The SX1 IS Porting Thread
« Reply #203 on: 24 / April / 2009, 02:17:54 »
Thanks to all cracks starting that port! Great work and fascinating to follow the conversations. Keep on please.

I've played around with it a bit and also tried to get the Motion Detection scripts running (several ones from the CHDK site). Without any success. My SX1 IS always fired within some intervall even without any motion to detect.

Also changed the several parameter settings, but without getting the desired behaviour.

Has anyone of you had success with that already?

e.g.
http://chdk.wikia.com/wiki/UBASIC/Scripts:Lightning_script_--_Fudgey
http://chdk.wikia.com/wiki/UBASIC/Scripts:_Multipurpose_Motion_Detection
http://chdk.wikia.com/wiki/UBASIC/Scripts:_Lightning_Photography

Regards from Zurich
Eric


Re: The SX1 IS Porting Thread
« Reply #204 on: 24 / April / 2009, 02:26:55 »
I'm not sure if this thread is the right place to diskuss this, but here are my experiences.
Ich tried this one:

http://chdk.setepontos.com/index.php/topic,471.msg17797.html#msg17797

And it worked for me. Tested not much, but the motion dectection worked.
You have to be careful, because most of the motion detect scripts are for digic II/III and not testet for the digicIV which the SX1 is having.

Re: The SX1 IS Porting Thread
« Reply #205 on: 24 / April / 2009, 02:33:09 »
Hi alexpreyer,

thanks alot for your fast reply. Sounds very promising  :) will move to a more appropriate place (http://chdk.setepontos.com/index.php/topic,471.135.html) for further discussion on motion detection issues.

Regards,
Eric
« Last Edit: 24 / April / 2009, 03:44:13 by elorup »

*

Offline pev69

  • **
  • 55
Re: The SX1 IS Porting Thread
« Reply #206 on: 24 / April / 2009, 05:13:34 »
It is still possible, that if the motion detection has problems in SX1, it is a porting issue, and therefore should be discussed here, at least if those of you who test it find no help in other MD threads in the forum. The variable aspect ratio may very well cause trouble there as well, and the viewport parameters may still be wrong. I have not tested these issues myself, but I will try to look into the MD code as well when I can. I have been rather busy with other things lately (last couple of days), so I have not been able to do much anything for CHDK.

Re: The SX1 IS Porting Thread
« Reply #207 on: 24 / April / 2009, 09:01:45 »
hi all!  I was very quiet the last few days, due to private technical issues...the last three days I was forced to finally "Migrate", "Clean", "Consolidate", "Update", etc, etc my private Client-Server environment @home, and so my virtual "Dev" Environment was offline.

I'm still here and still working (if times allows me) on the "PS.FI2" (1st Prio) ....and after that other issues (Continous AF notworking - 2nd Prio)....

@elorup:  As you may have read: the Shooting in Series with Autofocus "ON" will not work. Cam will crash. May be this is also the reason why your Motion Scripts do not work...? --> try to set the Cam in "AF only on first pic" Shooting and try the scripts again. Would be interesting to hear if this works out (for now)



*

Offline reyalp

  • ******
  • 12159
Re: The SX1 IS Porting Thread
« Reply #208 on: 24 / April / 2009, 16:45:11 »
Okay, here's the zebra modification for trunk 744. Unzip under the trunk744 dir and let it replace the files.
The changes in code are in core\gui_osd.c in functions gui_osd_zebra_init and gui_osd_draw_zebra. Plus definitions added for CAM_HAS_VARIABLE_ASPECT (include\camera.h) and PROPCASE_ASPECT_RATIO (include\propset2.h).

EDIT: There is a slight esthetic dismissal :) in the current logic when in 4:3 mode: canon's own OSD elements are not drawn on the black bars when zebra is visible; this is particularly noticable if you comment out the line
#define ZEBRA_CANONOSD_BORDER_RESTORE   1
near the beginning of the file core\gui_osd.c (this should cause all of canon's own elements to show with zebra, not just borders as the define does). It is due to the fact that I added a condition that nothing is drawn on the black bars when any zebra is drawn :). Will correct it later.

I've added this, with some minor changes. SVN #752

In the future, please post a patch rather than a zip of modified files. It makes it much easier to apply if there are changes between when you submit your change and when I commit it.
Don't forget what the H stands for.

*

Offline Sei

  • *
  • 19
Re: The SX1 IS Porting Thread
« Reply #209 on: 24 / April / 2009, 18:22:15 »
Motion detection with fudgey's script works on SX1 (version 080914 for cameras with video button from this thread). Although to run it correctly I had to mask right and bottom cells. Cells from those areas actuate shots without reason. I think intervalometer is in some part "guilty" of this. During tests I have manage to obtain 80-100ms of minimum delay.

 

Related Topics