500d development - page 179 - DSLR Hack development - CHDK Forum supplierdeeply

500d development

  • 2487 Replies
  • 898804 Views
Re: 500d development
« Reply #1780 on: 10 / November / 2011, 01:34:32 »
Advertisements
I can't see the flicker, so I can't tell what it is. Conflict with Canon's bottom bar?

Just to test a hypothesis: try 1775 with this option in config file:
Code: [Select]
shutter.display.degrees = 1

It should display shutter value in degrees in movie mode.
Yes, its in degress, im guess u meant 1775 right? And on that one, the bottom text is very solid with no flickers and of coarse no crashes, on the one u just made, the text just does a really faint flicker even when not recording, its barely noticeble, but you can tell on this one it flickers real fast every so often and when it does flicker during recording thats when it crashes, 1775 is perfectly solid no flicker at all, just thought that might hint something to u that might help. no canon menus up at the time of coarse when it flickers, I thought it was metering, but you cant seem to make it do it, it just does it like a refesh rate flickers.

*

Offline a1ex

  • *****
  • 671
  • ML dev
Re: 500d development
« Reply #1781 on: 10 / November / 2011, 01:43:51 »
Good, now the full color bar should be there without flicker.

Re: 500d development
« Reply #1782 on: 10 / November / 2011, 01:47:50 »
Good, now the full color bar should be there without flicker.
that one is stable!!!!!!
just to note in case cause its a differ cam, is the black behind the bottom bar font suppose to connect all the way across or is it suppose to be in 4 sections? on my cam its in 4 sections if thats important or not?

Forget that last note: i was using my manual lens, with my auto its in many sections, so basically i guess i should ask, is each info suppuse to be seperated or on a contiunous black bar, lol, looks fine to me either way i am just making sure u see what i see so u know everything
« Last Edit: 10 / November / 2011, 01:54:59 by mk11174 »

*

Offline a1ex

  • *****
  • 671
  • ML dev
Re: 500d development
« Reply #1783 on: 10 / November / 2011, 01:52:54 »
Great!

This one has flicker, but it's just to test my boundary checks.


Re: 500d development
« Reply #1784 on: 10 / November / 2011, 01:58:06 »
Great!

This one has flicker, but it's just to test my boundary checks.
This one was solid black behind everythhing on bottom bar only and froze right away when i hit record

*

Offline a1ex

  • *****
  • 671
  • ML dev
Re: 500d development
« Reply #1785 on: 10 / November / 2011, 02:05:21 »
This should explain the menu freezing too. Boundary checks are OK now, ML menu is even a bit smaller than normal, so I doubt it writes outside image buffer limits.

Let's try Trammell's workaround (NOP instructions inside bmp_fill loop).


Re: 500d development
« Reply #1786 on: 10 / November / 2011, 02:17:44 »
This should explain the menu freezing too. Boundary checks are OK now, ML menu is even a bit smaller than normal, so I doubt it writes outside image buffer limits.

Let's try Trammell's workaround (NOP instructions inside bmp_fill loop).


DANG!!!! U THE MAN!!! Nice and stable!!!

*

Offline a1ex

  • *****
  • 671
  • ML dev
Re: 500d development
« Reply #1787 on: 10 / November / 2011, 02:24:34 »
Yay!

This one has everything enabled (changeset 5297a7d2a67c).

You can also try to enable AF frame clearing.


Re: 500d development
« Reply #1788 on: 10 / November / 2011, 02:37:55 »
Yay!

This one has everything enabled (changeset 5297a7d2a67c).

You can also try to enable AF frame clearing.
Yep!!! AF Frame ok too!!!! Awsome!!!

Re: 500d development
« Reply #1789 on: 10 / November / 2011, 04:28:36 »
Is anyone experiencing compile errors with latest changest.
I cant compile past tweaks.c, looking for nonexistent zebra.h

Adam

 

Related Topics