500d development - page 132 - DSLR Hack development - CHDK Forum supplierdeeply
« previous next »
Pages: 1 ... 127 128 129 130 131 [132] 133 134 135 136 137 ... 249   Go Down

500d development

  • 2487 Replies
  • 901319 Views
*

Offline mk11174

  • ****
  • 417
Re: 500d development
« Reply #1310 on: 28 / May / 2011, 16:36:19 »
Advertisements
Can anyone tell me what image size I need to program into the 422 script with an error of this
Exception: unknown image size: 1193216
I know how to get the image size, just dont know what the dimentions would be, like 720*424*2 = 610560 just dont know what like the width or height should be to solve the equation?

NM, it was 944x632, der, lol
« Last Edit: 28 / May / 2011, 17:26:36 by mk11174 »
Logged
*

Offline mk11174

  • ****
  • 417
Re: 500d development
« Reply #1311 on: 28 / May / 2011, 17:21:37 »
just have to say, that slit scan feature is pretty neat, this is the first time i have seen it work, pretty cool fx you can make with it 8], i thought it was going to be a black and white image cause it was in liveview but turned out to be color when converted.
Logged
*

Offline Coutts

  • *****
  • 538
  • www.flickr.com/couttsphotog
    • Flickr
Re: 500d development
« Reply #1312 on: 28 / May / 2011, 18:03:42 »
Quote from: mk11174 on 28 / May / 2011, 16:36:19
Can anyone tell me what image size I need to program into the 422 script with an error of this
Exception: unknown image size: 1193216
I know how to get the image size, just dont know what the dimentions would be, like 720*424*2 = 610560 just dont know what like the width or height should be to solve the equation?

NM, it was 944x632, der, lol

http://magiclantern.wikia.com/wiki/500d_VRAM_Info

refer to the wiki page there, for the resolutions of the vram buffers.
Logged
Canon 5d
Canon 50mm f/1.8
Sigma 24mm f/1.8

Flickr
*

Offline mk11174

  • ****
  • 417
Re: 500d development
« Reply #1313 on: 28 / May / 2011, 18:06:23 »
Quote from: Coutts on 28 / May / 2011, 18:03:42


http://magiclantern.wikia.com/wiki/500d_VRAM_Info

refer to the wiki page there, for the resolutions of the vram buffers.

thanks, but i got it figured out, it works good, other then the split of coarse, i like playing with slitscan 8]
Logged
*

Offline pat_loonytoon

  • ***
  • 144
Re: 500d development
« Reply #1314 on: 28 / May / 2011, 19:33:11 »
How did you get the .422 files to convert? 422-jpg-v2 seems to have some issues with the files, as you well know.
Logged
*

Offline mk11174

  • ****
  • 417
Re: 500d development
« Reply #1315 on: 28 / May / 2011, 19:37:16 »
Quote from: pat_loonytoon on 28 / May / 2011, 19:33:11
How did you get the .422 files to convert? 422-jpg-v2 seems to have some issues with the files, as you well know.
using python and using the python script from the repository, but of coarse after editing in the image sizes so it recognizes the new image sizes coutts has programed.
Logged
*

Offline a1ex

  • *****
  • 671
  • ML dev
Re: 500d development
« Reply #1316 on: 28 / May / 2011, 19:46:56 »
Did you get some nice examples of slit-scan pictures? I wasn't able to get anything usable yet :)
Logged
*

Offline mk11174

  • ****
  • 417
Re: 500d development
« Reply #1317 on: 28 / May / 2011, 20:01:46 »
Quote from: a1ex on 28 / May / 2011, 19:46:56
Did you get some nice examples of slit-scan pictures? I wasn't able to get anything usable yet :)
just some fooling around ones, i tried having my daughter twist her head and body during a scan, looks freaky, i will mess around on the tripod later and see if i can get creative 8]





Its warped alot more on the left side cause I pulled cam away to let her see after the scan past her body 8] i will do more stuff on a tripod in the day for better quality, this is inside no light but pc monitor 8/
« Last Edit: 28 / May / 2011, 20:15:01 by mk11174 »
Logged
*

Offline Coutts

  • *****
  • 538
  • www.flickr.com/couttsphotog
    • Flickr
Re: 500d development
« Reply #1318 on: 28 / May / 2011, 22:39:50 »
re-wrote the constants file to be a little more organized like AJ's code :)
just a little snippet from it:
Code: [Select]
//////////////////////////////////////////////////////////////////////////////////
//                                                                                                                                                              //
//      Various things are declared here that are used throughout Magic Lantern.        //
//                                                                                                                                                              //
//      Organized (finally) by Coutts. Feel free to help find some of the missing       //
//      stuff, we could use an extra hand :)                                                                            //
//                                                                                                                                                              //
//////////////////////////////////////////////////////////////////////////////////


//////////////////////////////////////////////////////////////////////////
//      VRAM Information                                                                                                        //
//      Everything is confirmed and correct as far as vram goes - Coutts.       //
//                                                                                                                                              //
//      For more information regarding VRAM, please visit this WIKI page:       //
//      [url=http://magiclantern.wikia.com/wiki/500d_VRAM_Info ]Error[/url]                                      //
//////////////////////////////////////////////////////////////////////////
// ONLY used by slit-scan pics in shoot.c
#define YUV422_LV_BUFFER 0x43738800
#define YUV422_LV_PITCH 1440
#define YUV422_LV_HEIGHT 424

// Everything else (zebras, focus peaking, etc etc) use this DMA pointer
#define YUV422_LV_BUFFER_DMA_ADDR (*(uint32_t*)0x26a8)
#define YUV422_HD_BUFFER_DMA_ADDR (*(uint32_t*)0x48a0)
//--------------------------------end-----------------------------------//


//////////////////////////////////////////////////////////////////////////
//      Bitrate.c related things                                                                                        //
//      see mvrGetBufferUsage, which is not really safe to call => err70        //
//      macros copied from arm-console                                                                          //
//////////////////////////////////////////////////////////////////////////
#define MVR_752_STRUCT (*(void**)0x1e90)
#define MEM(x) (*(int*)(x))
#define div_maybe(a,b) ((a)/(b))
#define MVR_BUFFER_USAGE_FRAME ABS(div_maybe(-100*MEM(316 + MVR_752_STRUCT) - 100*MEM(324 + MVR_752_STRUCT) - 100*MEM(496 + MVR_752_STRUCT) - 100*MEM(504 + MVR_752_STRUCT) + 100*MEM(320 + MVR_752_STRUCT) + 100*MEM(328 + MVR_752_STRUCT), -MEM(316 + MVR_752_STRUCT) - MEM(324 + MVR_752_STRUCT) + MEM(320 + MVR_752_STRUCT) + MEM(328 + MVR_752_STRUCT)))
#define MVR_BUFFER_USAGE_SOUND div_maybe(-100*MEM(452 + MVR_752_STRUCT) + 100*MEM(440 + MVR_752_STRUCT), 0xa)
#define MVR_BUFFER_USAGE MAX(MVR_BUFFER_USAGE_FRAME, MVR_BUFFER_USAGE_SOUND)
//---------------------------------end----------------------------------//


//////////////////////////////////////////////////////////
//      Event codes and button press event related things       //
//      Everything is fixed for the 500d at this point          //
//      found using EVT spy with the debug console                      //
//////////////////////////////////////////////////////////
// CURRENT_DIALOG_MAYBE related things
// 3aa0 seems to reflect the same values but doesn't reset to 0 sometimes? this seems to be the right one.
#define CURRENT_DIALOG_MAYBE (*(int*)0x3a9c)
#define DLG_WB 6
#define DLG_FOCUS_MODE 0xA
#define DLG_DRIVE_MODE 9
#define DLG_PICTURE_STYLE 5
#define DLG_PLAY 1
#define DLG_MENU 2
#define DLG_Q_UNAVI 0x1E
#define DLG_FLASH_AE 0x21
#define DLG_PICQ 26
#define DLG_MOVIE_ENSURE_A_LENS_IS_ATTACHED 0x1b
#define DLG_MOVIE_PRESS_LV_TO_RESUME 0x1B

// button codes as received by gui_main_task
#define BGMT_PRESS_LEFT 0x39
#define BGMT_UNPRESS_LEFT 0x3a
#define BGMT_PRESS_UP 0x3b
#define BGMT_UNPRESS_UP 0x3c
#define BGMT_PRESS_RIGHT 0x37
#define BGMT_UNPRESS_RIGHT 0x38
#define BGMT_PRESS_DOWN 0x3d
#define BGMT_UNPRESS_DOWN 0x3e
#define BGMT_PRESS_SET 0x4
#define BGMT_UNPRESS_SET 0x5
#define BGMT_TRASH 0xA
#define BGMT_MENU 6
#define BGMT_DISP 7
#define BGMT_Q 8
#define BGMT_Q_ALT 0xF
#define BGMT_PLAY 9
#define BGMT_PRESS_HALFSHUTTER 0x23
#define BGMT_UNPRESS_HALFSHUTTER 0x24
#define BGMT_PRESS_FULLSHUTTER 0x25
#define BGMT_UNPRESS_FULLSHUTTER 0x26
#define BGMT_PRESS_ZOOMIN_MAYBE 0xB
#define BGMT_UNPRESS_ZOOMIN_MAYBE 0xC
//-----------------------end--------------------------//


edit:
some of the forward slashes got messed up after committing I guess, meh. you get the idea, it's more organized now :)
« Last Edit: 28 / May / 2011, 22:43:17 by Coutts »
Logged
Canon 5d
Canon 50mm f/1.8
Sigma 24mm f/1.8

Flickr
*

Offline pat_loonytoon

  • ***
  • 144
Re: 500d development
« Reply #1319 on: 28 / May / 2011, 23:29:24 »
wow python really hates me...oh well :/
422-jpg refuses to compile based on no Imaging module however PIL refuses to find python. Guess I'll wait until someone can compile it :(
Logged
Pages: 1 ... 127 128 129 130 131 [132] 133 134 135 136 137 ... 249   Go Up
« previous next »
 

Related Topics