500d development - page 208 - DSLR Hack development - CHDK Forum  

500d development

  • 2487 Replies
  • 812800 Views
Re: 500d development
« Reply #2070 on: 10 / December / 2011, 18:13:27 »
Advertisements
So, is there any certain reason why the Left key is the only button that gives a normal reading in spy event? why all others are 3f 0x1000020 arg 9 unless u press and hold flash button then arg 9 changes to arg 0 and address changes to 0x20? Just curious if its just how it has to be or is it not normal even though everything is working?

*

Offline a1ex

  • *****
  • 671
  • ML dev
Re: 500d development
« Reply #2071 on: 11 / December / 2011, 01:04:45 »
Look at handle_buttons_being_held (debug.c) and try returning 1 for BGMT_FLASH_MOVIE. It may solve the mistery.

Re: 500d development
« Reply #2072 on: 11 / December / 2011, 02:46:29 »
Look at handle_buttons_being_held (debug.c) and try returning 1 for BGMT_FLASH_MOVIE. It may solve the mistery.
no, 8/ doesnt seem to change the effect, i dont even know y it bothers me, lol, sensor shortcut is perfectly fine for doing the iso and kel, but ever since i started reading the spy_events, it got me curious y it is acting like that, just seems so weird that left key is the only key that displays normal results, any other button is acting like flash button is being pressed and it always says 3f unless the left key is pressed then it stays on 3a till any other key is pressed on cam then goes back to 3f, seems so strange

*

Offline a1ex

  • *****
  • 671
  • ML dev
Re: 500d development
« Reply #2073 on: 11 / December / 2011, 02:59:59 »
Try editing handle_buttons in gui.c:
- Comment out lines 38-45 (i.e. starting from handle_common_events_by_feature )
- Try catching flash button events in a clean environment (maybe just call handle_buttons_being_held and print the status of flash button)




Re: 500d development
« Reply #2074 on: 11 / December / 2011, 03:24:30 »
Try editing handle_buttons in gui.c:
- Comment out lines 38-45 (i.e. starting from handle_common_events_by_feature )
- Try catching flash button events in a clean environment (maybe just call handle_buttons_being_held and print the status of flash button)



well I got the commit out part fine, lol dont know what code to type on the catching flash button event part 8/ sorry, im just a newb lol

*

Offline Gary

  • *
  • 43
Re: 500d development
« Reply #2075 on: 11 / December / 2011, 11:13:48 »
I thought I answered your question about 926 x n.  I don't see Coutts post on this topic.  What is the next step?

*

Offline a1ex

  • *****
  • 671
  • ML dev
Re: 500d development
« Reply #2076 on: 11 / December / 2011, 12:15:49 »
Next step is to make silent_pic_take_sweep generic (i.e. compatible with all camera generations, not just 550D/60D/600D).

Basically you need to replace SENSOR_RES_X and SENSOR_RES_Y with 5 x size of one frame (i.e. size of hd_buffer), and 1024x680 with the size of one frame. Then adjust things in the converter until you get proper alignment.

Re: 500d development
« Reply #2077 on: 11 / December / 2011, 12:38:37 »
Try editing handle_buttons in gui.c:
- Comment out lines 38-45 (i.e. starting from handle_common_events_by_feature )
- Try catching flash button events in a clean environment (maybe just call handle_buttons_being_held and print the status of flash button)



Never mind, I will just leave well enough alone, if it aint broke dont try to fix it lol.
« Last Edit: 11 / December / 2011, 16:58:42 by mk11174 »


*

Offline Gary

  • *
  • 43
Re: 500d development
« Reply #2078 on: 11 / December / 2011, 21:26:38 »
Alex, you do the first 2, and I'll do the 3rd!

Re: 500d development
« Reply #2079 on: 11 / December / 2011, 23:56:34 »
so it seems 944 x 632 is the setting in vram.c to change to for video_mode_resolution == 1 ? to make it silent picture take a picture in 5x mode, but then magic zoom gets scrambled, so how can it be set so it stays in 928x616 mode untill u try to take a 5x mode picture????

 

Related Topics