500d development - page 124 - DSLR Hack development - CHDK Forum supplierdeeply

500d development

  • 2487 Replies
  • 914090 Views
Re: 500d development
« Reply #1230 on: 24 / May / 2011, 05:43:16 »
Advertisements
Thats soo cool! i wonder if we can find a way to get the pw....
« Last Edit: 24 / May / 2011, 05:47:14 by aznguy »

Re: 500d development
« Reply #1231 on: 24 / May / 2011, 06:21:22 »
anyone know how to simulate a constant press of the exsposure lock button, the little star button also known as the zoom out button, i notice that when you switch to one of the odd iso number like 160, 320, 640, well after you switch using magic lantern, it goes back to its estimated iso in a couple seconds, the only thing that holds it in place is if you press and hold that star button, once you release it, it goes back to estimated in a few seconds???

forget it, it seems it stays only in live view while using ML, if your out of live view it thats when it resets in a few seconds, but at least it stays set in live view just fine even though canons menu shows the estimated iso setting, would be nice to figure out how to get it to stay put in non live view mode though other then holding in the shutter half way, or the dof, or the ae lock button, all seem to keep it locked until you let it go while in non live view mode 8/
« Last Edit: 24 / May / 2011, 07:01:51 by mk11174 »

*

Offline a1ex

  • *****
  • 671
  • ML dev
Re: 500d development
« Reply #1232 on: 24 / May / 2011, 07:35:40 »
Basically, simulating button presses can be done by injecting fake events in GUI main loop.

See http://magiclantern.wikia.com/wiki/DevFAQ for how it's done on 550D, but keep in mind that 500D's loop is different.

Another method may be to send messages to gui_main_task's message queue.

*

Offline Jamez

  • **
  • 91
Re: 500d development
« Reply #1233 on: 24 / May / 2011, 09:26:23 »
Why would you want to limit features/functions?
I cant think when/why that would come in use.

PS Alex has fixed a bug with the intervalometer today, and ive ported it, and whilst im there
- Also added Focus delay
- Wider range of stack focus ranges
- Lens focus delay
- Bug fix on Rack focusing
- Moved the menu left a bit so we can see all of the options the last (i) wasnt being shown properly
- NB Code is not on bitbucket at present.


PPS I`ll match Coutts offer of free cookies for the property value we need to get all the VRAM related features working properly....
« Last Edit: 25 / May / 2011, 14:33:01 by Jamez »
Canon Kiss x3 Owner running...
Magic Lantern for 500D/T1i/Kiss X3
Canon EOS 500D/T1i - Magic Lantern Firmware Wiki


*

Offline Coutts

  • *****
  • 538
  • www.flickr.com/couttsphotog
    • Flickr
Re: 500d development
« Reply #1234 on: 24 / May / 2011, 11:22:02 »
Basically, simulating button presses can be done by injecting fake events in GUI main loop.

See http://magiclantern.wikia.com/wiki/DevFAQ for how it's done on 550D, but keep in mind that 500D's loop is different.

Another method may be to send messages to gui_main_task's message queue.
ctrlman_dispatch_event() can inject events, I've tried this a couple times.
we can't use fake_simple_button() though because of the differences in the 500d and 550d. The 500d is more like the 5d than the 550d for some reason.
Canon 5d
Canon 50mm f/1.8
Sigma 24mm f/1.8

Flickr

Re: 500d development
« Reply #1235 on: 25 / May / 2011, 11:25:33 »
I'm writing this bug here because I didn't want to paste links in Bitbucket without interaction.  You might be interested because of the newest bug fix in the Intervalometer mentioned above.  I have taken 10,000+ pictures so far in 2 days.  The problem is consistent across builds, at least when the interval is less than 20 seconds or so.  I have reset my camera and deleted the config.  Here is my description:  

3 pictures are triggered at about the desired interval.  Then it skips, or pauses, for 5 seconds or more.  Is this the bug you have fixed?  I would be happy to paste a link to the video or individual JPG's.

Am I eligible for the cookies if I suggest or implement a workaround?  An alternative to Properties.
« Last Edit: 25 / May / 2011, 11:31:45 by sbright33 »

Re: 500d development
« Reply #1236 on: 25 / May / 2011, 11:32:48 »
« Last Edit: 25 / May / 2011, 11:39:11 by bkkenny »

*

Offline a1ex

  • *****
  • 671
  • ML dev
Re: 500d development
« Reply #1237 on: 25 / May / 2011, 11:56:16 »
When display is off, the camera enters in some kind of sleep mode, where msleep calls may take much longer than normal. 550D ML tries to avoid this by simulating half-shutter presses every second when display is off.

To select NoWait mode, press the LV button (I think). On 550D it's [Q].


Re: 500d development
« Reply #1238 on: 25 / May / 2011, 11:57:34 »
On the 500D it doesn't seem possible to change out of the "Wait" mode. Thoughts anyone?

Use the LV button to switch to Wait/NoWait.

Re: 500d development
« Reply #1239 on: 25 / May / 2011, 12:06:39 »
I have spent 10 hours of my time making this video and trying to fix the problem.  It's much easier to see it than explain the defect.  It's subtle, but something that must be fixed before the Intervalometer can be used creatively on the 500d.  I'd be happy to help, but first I want to understand what has already been done to remedy the issue.

Thanks Alex I will try your suggestion!  Will get back to you shortly.
FYI my camera is not set to sleep, the screen is always on during this process.
« Last Edit: 25 / May / 2011, 12:11:15 by sbright33 »

 

Related Topics


SimplePortal 2.3.6 © 2008-2014, SimplePortal