500d development - page 148 - DSLR Hack development - CHDK Forum  
« previous next »
Pages: 1 ... 143 144 145 146 147 [148] 149 150 151 152 153 ... 249   Go Down

500d development

  • 2487 Replies
  • 901321 Views
*

Offline Coutts

  • *****
  • 538
  • www.flickr.com/couttsphotog
    • Flickr
Re: 500d development
« Reply #1470 on: 02 / July / 2011, 22:19:28 »
Advertisements
another small build:

- fixed audio meter
- fixed live view lcd shortcut display
- fixed audio menu items (removed unused ones)
- fixed version string

https://bitbucket.org/coutts/magic-lantern-500d/changeset/80baaacedbeb
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 #1471 on: 02 / July / 2011, 22:52:55 »
- Implemented display of current kelvin wb in live view when sensor shortcuts display is active (while you have the sensor covered). helpful to know what your current white balance is without having to open the ML menu to check.
Logged
Canon 5d
Canon 50mm f/1.8
Sigma 24mm f/1.8

Flickr
*

Offline gravityrem

  • *
  • 40
Re: 500d development
« Reply #1472 on: 03 / July / 2011, 03:30:25 »
cool coutts !

So you're still in the game ? Your macbook is fixed ?
Logged
*

Offline PHrag

  • *
  • 33
    • Flickr
Re: 500d development
« Reply #1473 on: 03 / July / 2011, 04:35:59 »
these also contain all the unreleased fixes and tweaks right?
EDIT: sorry, tryied it, everything new is there  :)
« Last Edit: 03 / July / 2011, 04:59:06 by PHrag »
Logged
Canon 500D (T1i)
EF-S 18-55 (kit)
Flickr
*

Offline Coutts

  • *****
  • 538
  • www.flickr.com/couttsphotog
    • Flickr
Re: 500d development
« Reply #1474 on: 03 / July / 2011, 16:41:30 »
-Fixed focus peaking overlay offset in live view mode ONLY. No guarantees for movie recording yet (still very unstable for some reason).

https://bitbucket.org/coutts/magic-lantern-500d/changeset/f82ec9e69b7f

I have fixed it temporarily by using the LV buffer for focus peaking, as it seems to work on the LV buffer fine but is offset with the HD buffer. So, it works, but the drawback is the LV buffer is a lower resolution, which means a lower resolution/quality focus map. This will work for now, but is going to need work.

I think Indy has been looking into making vram buffers at will at any size, so when he figures that out, buffers won't be an issue anymore.
« Last Edit: 03 / July / 2011, 17:05:53 by Coutts »
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 #1475 on: 03 / July / 2011, 19:57:19 »
Crop marks semi-working, no guarantees while recording though. ML bottom bar in LV is showing too, eventually it will only show when canon bottom bar is hidden (need to find that pointer).

https://bitbucket.org/coutts/magic-lantern-500d/changeset/827a82673ae3
Logged
Canon 5d
Canon 50mm f/1.8
Sigma 24mm f/1.8

Flickr
*

Offline RoaldFre

  • *
  • 35
Re: 500d development
« Reply #1476 on: 04 / July / 2011, 05:28:09 »
Quote from: Coutts on 03 / July / 2011, 16:41:30
I think Indy has been looking into making vram buffers at will at any size, so when he figures that out, buffers won't be an issue anymore.

Do you mean "instructing the digic to give us a buffer of arbitrary resolution", or "making zebra work with the different buffer resolutions of the different camera models"?
Logged
*

Offline a1ex

  • *****
  • 671
  • ML dev
Re: 500d development
« Reply #1477 on: 04 / July / 2011, 07:50:11 »
Indy has been looking at getting the size of VRAM buffers via some functions; right now we can get the size of LV buffers (with vram_info), but only for built-in LCD (not HDMI).

http://groups.google.com/group/ml-devel/msg/0ad6be691f2f5992
Logged
*

Offline arm.indiana

  • ***
  • 105
Re: 500d development
« Reply #1478 on: 05 / July / 2011, 13:24:43 »
I'm sure we can learn how vram buffers pointer are updated by understanding this state object
ROM:FF0601B4 create_display_device_state_object      ; CODE XREF: InitializeDisplayDeviceController+90p
(550d 1.0.9)

See http://magiclantern.wikia.com/wiki/VRAM_ADDR_from_code

Indy


Quote from: a1ex on 04 / July / 2011, 07:50:11
Indy has been looking at getting the size of VRAM buffers via some functions; right now we can get the size of LV buffers (with vram_info), but only for built-in LCD (not HDMI).

http://groups.google.com/group/ml-devel/msg/0ad6be691f2f5992
« Last Edit: 05 / July / 2011, 13:39:20 by arm.indiana »
Logged
*

Offline a1ex

  • *****
  • 671
  • ML dev
Re: 500d development
« Reply #1479 on: 06 / July / 2011, 02:26:10 »
In existing ML code (which should be cleaned up), stateobj_disp[1] is the same as YUV422_LV_BUFFER_DMA_ADDR (i.e. a pointer to current LV buffer). LiveView image (LV) is triple-buffered.

If we can find a similar stateobj for HD buffer, it will solve magic zoom problems in 60D and 600D; not sure if the same issue is present on 500D.

On 550D, that stateobj might be around 0x4c5c (found with mem-spy). But I wasn't able to find it neither on 60D, nor on 600D.
Logged
Pages: 1 ... 143 144 145 146 147 [148] 149 150 151 152 153 ... 249   Go Up
« previous next »
 

Related Topics