500d development - page 71 - DSLR Hack development - CHDK Forum
« previous next »
Pages: 1 ... 66 67 68 69 70 [71] 72 73 74 75 76 ... 249   Go Down

500d development

  • 2487 Replies
  • 901244 Views
*

Offline Coutts

  • *****
  • 538
  • www.flickr.com/couttsphotog
    • Flickr
Re: 500d development
« Reply #700 on: 16 / April / 2011, 15:21:52 »
Advertisements
also I don't like the endless loops like shoot_task.. just seems like it's asking for trouble. I'm beginning to understand how the code can be "optimized". oh the joys of learning :) finally, i'm starting to make sense of things.
Logged
Canon 5d
Canon 50mm f/1.8
Sigma 24mm f/1.8

Flickr
*

Offline Coutts

  • *****
  • 538
  • www.flickr.com/couttsphotog
    • Flickr
Re: 500d development
« Reply #701 on: 16 / April / 2011, 19:03:07 »
prop_spy is now working. had to take code from the 5d repository because it looks like it doesn't work in the 550d (Alex, you should fix this).

updated bitbucket repository, everybody re-clone their working directory for the change.
Logged
Canon 5d
Canon 50mm f/1.8
Sigma 24mm f/1.8

Flickr
*

Offline rebelT1i

  • *
  • 31
Re: 500d development
« Reply #702 on: 16 / April / 2011, 19:30:40 »
Quote from: Coutts on 16 / April / 2011, 19:03:07
everybody re-clone their working directory for the change.

I don't know how to do this, Is it a big enough change for someone to explain how to do this for the other people here like me? Or am I the only one here that doesn't know how to do this?
Logged
*

Offline Coutts

  • *****
  • 538
  • www.flickr.com/couttsphotog
    • Flickr
Re: 500d development
« Reply #703 on: 16 / April / 2011, 19:55:02 »
actually don't re-clone. i think prop_spy works on the 550d but for some reason it's not working on the 500d. i'm trying to get alex's prop_spy to work still.

edit:
it works - but it's being spammed by the alo/htp/mlu stuff. comment out the mlu/htp/alo stuff in shoot_task in shoot.c and it should be cleaner. i don't think it's showing all of the properties though. i want to mess with it now but i'm heading out for the night, I need a drink.

i'll look at it more tomorrow, if anyone finds anything post it up!!
« Last Edit: 16 / April / 2011, 21:10:10 by Coutts »
Logged
Canon 5d
Canon 50mm f/1.8
Sigma 24mm f/1.8

Flickr
*

Offline a1ex

  • *****
  • 671
  • ML dev
Re: 500d development
« Reply #704 on: 17 / April / 2011, 02:21:52 »
Coutts: prop_spy is disabled with an "#if 0" in debug.c. Change it to "#if 1".
Logged
*

Offline RoaldFre

  • *
  • 35
Re: 500d development
« Reply #705 on: 17 / April / 2011, 06:53:13 »
Quote from: Coutts on 16 / April / 2011, 15:13:59
cfn[1] values:
ALO standard (default value) - 0
ALO low - 1000000
ALO high - 2000000
ALO off - 3000000

If I understand you correctly, the binary values are:

Code: [Select]
ALO standard 00000000
ALO low      01000000
ALO high     10000000
ALO off      11000000
You can change these as well using some bit twiddling by doing:

Code: [Select]
void set_alo(int mode)
{
        /*
         * mode:
         * 0 = standard
         * 1 = low
         * 2 = high
         * 3 = off
         */

        cfn[1] = (cfn[1] & (~0xC0)) | ((mode << 6) & 0xC0);
        //or, if you are sure that mode will only hold valid values (0 to 3):
        //cfn[1] = (cfn[1] & (~0xC0)) | (mode << 6));
        prop_request_change(PROP_CFN, cfn, xxxx);
}
I don't know what the third argument of prop_request_change should be out of the top op my head, though.
Logged
*

Offline RoaldFre

  • *
  • 35
Re: 500d development
« Reply #706 on: 17 / April / 2011, 06:56:19 »
Quote from: Coutts on 16 / April / 2011, 19:03:07
updated bitbucket repository, everybody re-clone their working directory for the change.

Note: you don't need to issue a clone command. You can just pull the specific changes by doing:

Code: [Select]
hg pull
Logged
*

Offline Coutts

  • *****
  • 538
  • www.flickr.com/couttsphotog
    • Flickr
Re: 500d development
« Reply #707 on: 17 / April / 2011, 10:37:45 »
^ hmm, i wonder if that would work. i'm trying to find the property location for ALO. I couldn't find it anywhere in the 500d dump.. i wonder if it even has one?
Logged
Canon 5d
Canon 50mm f/1.8
Sigma 24mm f/1.8

Flickr
*

Offline Coutts

  • *****
  • 538
  • www.flickr.com/couttsphotog
    • Flickr
Re: 500d development
« Reply #708 on: 17 / April / 2011, 10:42:29 »
Quote from: a1ex on 17 / April / 2011, 02:21:52
Coutts: prop_spy is disabled with an "#if 0" in debug.c. Change it to "#if 1".
whenever i'd enable it the camera wouldn't boot for some reason. i realize there is code here to filter out frequent prop changes, but i could only get the prop_spy code from the 5d to work. i don't think it's showing everything though.. i'm not seeing anything showing up for focus confirmation or shutter half press.
Logged
Canon 5d
Canon 50mm f/1.8
Sigma 24mm f/1.8

Flickr
*

Offline utnuc

  • **
  • 55
Re: 500d development
« Reply #709 on: 18 / April / 2011, 09:23:43 »
OK, I have fixed the cropmarks.  The code from the 550D pretty much worked, with some minor tweaking.  The new code allows you to add up to 9 cropmarks to your folder, and ML will find them and cycle through in the menu.  Known issues with the code:

CMs seem to not draw where the audio monitor resides
When you switch between CM files there seem to be some remnants of the old CM image

I don't know how to update the code repository, so I have attached the update zebra.c file (can someone help here?). 

Ben
Logged
Pages: 1 ... 66 67 68 69 70 [71] 72 73 74 75 76 ... 249   Go Up
« previous next »
 

Related Topics