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

500d development

  • 2487 Replies
  • 901259 Views
*

Offline a1ex

  • *****
  • 671
  • ML dev
Re: 500d development
« Reply #990 on: 09 / May / 2011, 14:46:01 »
Advertisements
Quote
The write protection detection metal pin has been broken, and as a result the camera refuses to write to any SD cards - regardless of whether they are write protected or not.
CHDK does that (i.e. bypassing write protection), but I don't know the exact mechanism. Probably it's just a flag or a property to set. A starting point would be to compare two debug logs, one with SD card locked, and other without.

Quote
For the video ISOs (and probably images too!), multiples of 160 seem to work best.

These ISOs have a bit of negative digital gain (-1/3EV or so), and so they have a bit less noise, at the cost of a bit less dynamic range (i.e. highlights will clip earlier). I believe you can get the same effect with a curves adjustment, but I didn't try.

Re: 500d development
« Reply #991 on: 09 / May / 2011, 15:52:27 »
yes about the 160 iso, but the best we have now is by 100's unfortunatly for video, but at least its not to far off from 160, it is very interesting however how 320 and 640 are cleaner then 100 being that there higher numbers but yet 300 and 600 are worse, intersting why this is like this for video, i will do some tests with my lightning at 160 and 320 on stills to see if this is the same on stills, in my line of work of photography i grew up learning the higher the iso the more the grain, very cool info about this video though, thanks for sharing 8]

*

Offline reyalp

  • ******
  • 14082
Re: 500d development
« Reply #992 on: 09 / May / 2011, 16:35:51 »
CHDK does that (i.e. bypassing write protection), but I don't know the exact mechanism. Probably it's just a flag or a property to set. A starting point would be to compare two debug logs, one with SD card locked, and other without.
In P&S, there's a variable called GpioStatus (known as physw_status in CHDK) that has bits for the various switches and buttons. This is populated in the canon firmware in the PhySw task (kbd_task). The SD card lock is just one of those switches, and we mask it out in our replacement kbd_task.
Don't forget what the H stands for.

*

Offline Coutts

  • *****
  • 538
  • www.flickr.com/couttsphotog
    • Flickr
Re: 500d development
« Reply #993 on: 09 / May / 2011, 18:22:02 »
in 500d dump:

0xff206648
aLvae_setmoviemanualcontrol

this looks interesting...
Canon 5d
Canon 50mm f/1.8
Sigma 24mm f/1.8

Flickr


Re: 500d development
« Reply #994 on: 09 / May / 2011, 18:25:55 »
Coutts, thats what youre looking for! (hopefully)
btw latest build is really clean!

Re: 500d development
« Reply #995 on: 09 / May / 2011, 18:31:20 »
Freaking out with the 500d development.
Go on, and go well.
Just congratulate all the team working here.
GREAT WORK GUYS!!!
 

Re: 500d development
« Reply #996 on: 09 / May / 2011, 18:33:08 »
this looks interesting...
It sure does! :P
Canon EOS Rebel T1i
Canon 18-55 kit lens
Zenitar M2S 2/50mm

Flickr

*

Offline Coutts

  • *****
  • 538
  • www.flickr.com/couttsphotog
    • Flickr
Re: 500d development
« Reply #997 on: 09 / May / 2011, 18:43:06 »
decompiled 0xFF203C04:



arg0 = mem address that says if movie manual controls are on/off, 16884 in decimal is 0x41F4. I'm going to try right now and see what this address holds. if it's a 0 then this could be a start of figuring it out, it might just be a matter of "flipping a switch" in the camera and we'll have control like the 550d.


edit

yup, looks right. now to figure out how to change it's value (have to figure out how it's called in the firmware)). :)

« Last Edit: 09 / May / 2011, 18:47:44 by Coutts »
Canon 5d
Canon 50mm f/1.8
Sigma 24mm f/1.8

Flickr


Re: 500d development
« Reply #998 on: 09 / May / 2011, 19:10:29 »
WOW!!! Now that sound exciting, GREAT JOB!!!! Coutts

*

Offline zanak

  • *
  • 11
Re: 500d development
« Reply #999 on: 09 / May / 2011, 19:40:12 »
yes nice work !!!!!

 

Related Topics