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

500d development

  • 2487 Replies
  • 812803 Views
*

Offline Coutts

  • *****
  • 538
  • www.flickr.com/couttsphotog
    • Flickr
Re: 500d development
« Reply #2080 on: 12 / December / 2011, 09:06:33 »
Advertisements
IIRC, the flash button and AV button send identical events in movie mode and there's no way to distinguish them (i think i found this out a few months ago), i never figured out a way to adapt the flash button shortcuts on the 500d.

@mk11174 find the dimensions of the HD / LV buffers in zoom mode. run:
dump_big_seg(4, "4.bin");
dump_big_seg(4, "4_1.bin");

to get 2 copies of the 0x4 range of memory on the card. then use img.py to locate buffers and determine their dimensions:
http://magiclantern.wikia.com/wiki/VRAM/550D#Step-by-step_example
Canon 5d
Canon 50mm f/1.8
Sigma 24mm f/1.8

Flickr

Re: 500d development
« Reply #2081 on: 12 / December / 2011, 10:35:20 »
IIRC, the flash button and AV button send identical events in movie mode and there's no way to distinguish them (i think i found this out a few months ago), i never figured out a way to adapt the flash button shortcuts on the 500d.

@mk11174 find the dimensions of the HD / LV buffers in zoom mode. run:
dump_big_seg(4, "4.bin");
dump_big_seg(4, "4_1.bin");

to get 2 copies of the 0x4 range of memory on the card. then use img.py to locate buffers and determine their dimensions:
http://magiclantern.wikia.com/wiki/VRAM/550D#Step-by-step_example
Ok, I guessing I will come up with same result you have right, or maybe some differ cause maybe cam differ? All your resolutions worked on your vram page just fine, I finally figured out where to program them into the code, lol, only thing I couldnt figure out is how to have both 944x632 for zoom mode and 928x616 be used at same time cause for 944x632 if set for any of the 3 res to get a silent picture while in zoom mode, you get a scrambled image out of zoom and of coarse magic zoom is then scrambled, so i gave up and just set 944x632 for 640x480 mode since i dont use that mode anyway, so if i want a silent picture in zoom mode i just switch to that resolution cause it dont matter if magic zoom is scrambled cause i am not going to be using it there anyway. Only thing is, I thought getting a zoom picture to finally be unscrambled on my cam would solve the hi res problem of been scrambled, it didnt, my hi res versions are scrambled still. I added 944x632 to the convertor for the single versions to convert and also set it up so i get the preview on cam, but am i suppose to change something somewhere to make the hi res unscrambled, it converts and all to a jpg, just all scrambled still with thick black borders in betwen each section???

Re: 500d development
« Reply #2082 on: 12 / December / 2011, 10:40:24 »
And to bad theres prob no way to figure out res and pitch setting for alexs idea of zooming while recording, that was a neat idea, works fine in 640x480 with audio off buffer dont seem to fill up, i set to zoom x5 in the xx_test, I went to 640x480 press record then went to xx_test to engage zoom it zoomed it looked fine, but playback is scrambled once zoomed, I tried all ur vram settings on all modes in the code but none seem to have any effect on it, but cool idea of his if there was a address and pitch that was findable to use for it.

Re: 500d development
« Reply #2083 on: 12 / December / 2011, 15:50:51 »
Thanks again to everyone working on this, I wanted to share a short clip I took using the focus peaking to keep the subject in focus, I got confused for a second but I am really happy with it so far! keep it up

Galapagos tortoise Close up.


*

Offline Gary

  • *
  • 43
Re: 500d development
« Reply #2084 on: 12 / December / 2011, 15:54:33 »
@mk - Did you do these?
> 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.

If so I will fix the script.  Send me the autoexec.bin.

Re: 500d development
« Reply #2085 on: 12 / December / 2011, 19:13:53 »
IIRC, the flash button and AV button send identical events in movie mode and there's no way to distinguish them (i think i found this out a few months ago), i never figured out a way to adapt the flash button shortcuts on the 500d.

@mk11174 find the dimensions of the HD / LV buffers in zoom mode. run:
dump_big_seg(4, "4.bin");
dump_big_seg(4, "4_1.bin");

to get 2 copies of the 0x4 range of memory on the card. then use img.py to locate buffers and determine their dimensions:
http://magiclantern.wikia.com/wiki/VRAM/550D#Step-by-step_example
hey Coutts, thanks, I actually got it going, it took some time trying to gwet it going cause i could not get Ubuntu to install pylab, so i tried on windows, but that was saying could not compare the to arrays so back to Ubuntu and it worked with python 2.6 installed, i got the plot part, this might be dumb question but is the plot suppose to turn into image as u adjust?

Update: scratch that, i just noticed the images being created in my home folder, i was looking on my desktop, lol sorry.
« Last Edit: 12 / December / 2011, 19:34:29 by mk11174 »

Re: 500d development
« Reply #2086 on: 12 / December / 2011, 19:42:07 »
@mk - Did you do these?
> 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.

If so I will fix the script.  Send me the autoexec.bin.
i tried but wasnt sure if i was doing it on the right one or the right way, wasnt sure if i was suppose to replace the 1024x680 or the whole line: and there was other 1024x680 a few lines down didnt know if those were suppose to be replaced as well.

As far as the Sensor_Res change, is it the one in shoot.c or const.h?  if its the one in shoot.c Do I erase the code (SENSOR_RES_X - NC * 1024) / 2; and put the number in its place or just change the 1024 in it to the 5x number?
« Last Edit: 13 / December / 2011, 10:11:56 by mk11174 »

Re: 500d development
« Reply #2087 on: 12 / December / 2011, 22:49:43 »
ok, i did all the steps, on 1 picture, now, do i look for more then 1 picture in the bin, or just the one at the 10000000 position, and also, do i have to re dump the bin files in every mode, so like do a dumb during zoom, and another no record then record, etc and recheck the bin for there info again like i just did. Its pretty cool how it all works though isnt it, putting in the right settings till u have a full image, kinda fun 8]


Re: 500d development
« Reply #2088 on: 13 / December / 2011, 09:45:49 »
Hey Alex, first off, nice clean update!!! And now I see you fixed the way the buffers work so now in 5x mode it uses 944x632 and in normal it uses 928x616 which now fixes the silent picture 5x zoom problem of scrambled images on my cam, maybe ur next update you can add else if (size == 944*632*2)  { w = 944;  h = 632; } to zebra.c for the 500D users to get the 422 quick preview going when taking a silent picture in zoom mode, I already set mine up, but I am sure other users will like to have it set that way now that its working right. No luck with Hi-Res though still all scrambled separated boxes.

Update never mind on the Hi res, I got it to work, 5x5 creates 4760x3200 image on my cam, I just edited the Const.h
#define SENSOR_RES_X 4720
#define SENSOR_RES_Y 3160

Then is Shoot.c I changed all the 1024x680 from lines 1064 to 1080 and set the to 944x632

Then in 422-jpg.py script I changed all the 1024x680 to 944x632  then in line 66 I changed  NC to 952 and NL to 640.

All converted fine except some overlapping in a few places, but no scrambled areas at all finally 8]

Not sure if I had to go through all this, but it worked when nothing else would.

Also take note to add   
else if (size == 944*632*2)  { w = 944;  h = 632; } // 500d x5 x10 
in the area of line 4464 that will give you previews of zoom silent pictures, and also make sure you add     
elif len(data) == 944*632*2:        #x5 zoom
        w, h = 944, 632
to your 422-jpg.py script in the 500D section, and double check you have
elif len(data) == 1576*632*2:      #3.3MP from HD buffer in 1080p mode (same size recording and idle)
        w, h = 1576, 632
in there as well just to have all the resolutions ready for conversion.

Hope this helps any newbies like me out there.
« Last Edit: 13 / December / 2011, 11:00:01 by mk11174 »

*

Offline Gary

  • *
  • 43
Re: 500d development
« Reply #2089 on: 13 / December / 2011, 12:42:42 »
Please post your autoexec.bin for testing.  Also the 422 python script.  Maybe I can fix the overlapping.  At what point will Alex include this in the official build?  Before or after we fix the overlapping?

 

Related Topics