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

500d development

  • 2487 Replies
  • 901282 Views
*

Offline a1ex

  • *****
  • 671
  • ML dev
Re: 500d development
« Reply #1830 on: 19 / November / 2011, 14:29:42 »
Advertisements
So 1828 is crashing or not?

Re: 500d development
« Reply #1831 on: 19 / November / 2011, 14:32:49 »
So 1828 is crashing or not?
1828 seems to be just crashing at ML so far
ooops scratch that sorry, 1828 was fine in ml menu, i was playing around with 1826 again, but yes 1828 ok in ml
« Last Edit: 19 / November / 2011, 14:39:14 by mk11174 »

*

Offline a1ex

  • *****
  • 671
  • ML dev
Re: 500d development
« Reply #1832 on: 19 / November / 2011, 14:38:12 »
I don't understand, how to crash at ML?!

Re: 500d development
« Reply #1833 on: 19 / November / 2011, 14:43:02 »
I don't understand, how to crash at ML?!
When it does crash, it happens when you record, then press play to open ML menu, then it fine for a few seconds then it changes the highlighted menu, which we found was the record button option, the it freezes and crashes, everytime too, but 1828 stayed recording when opening ML menu during a record, its stable if your not recording, no issues in ML menu at all.

1828 seems to be crashing when the ml bottom bar is on, the more I try it the more its crashing, before I was just testing the ml menu, now, just trying to record it seems to be crashing, Ill try to do a recording of me playing with the cam to get it to crash.

Ok, I am uploading a video now, ill post link when its uploaded 8]

Lets see if the link posts ok from this board, never posted a link before on here: http://youtu.be/mpdzfZlHPs8
« Last Edit: 19 / November / 2011, 15:13:28 by mk11174 »


*

Offline a1ex

  • *****
  • 671
  • ML dev
Re: 500d development
« Reply #1834 on: 19 / November / 2011, 15:18:14 »
This one has bmp_fill and Q button disabled.

The Q button is the same as the record button here, right?

Re: 500d development
« Reply #1835 on: 19 / November / 2011, 15:44:17 »
This one has bmp_fill and Q button disabled.

The Q button is the same as the record button here, right?
yes Q is same as record.

Update!!! Wow, you seemed to have fixed both the crash while bottom bar is on again and now can use ML menu while recording, when I press record button now in menu it dont change the Q option it just stops the recording, but went back and forth and no crashes!!!!

Update 2: Only issue in this version is the ML menus overlay over eachother as you scroll through left to right, text is left over from each menu and make a mess of the screen till you exit ml menu then screen is clear and when you go back into ml menu all is normal till you scroll left to right again through the menus, and that happens wether your recording or not.
« Last Edit: 19 / November / 2011, 15:56:04 by mk11174 »

*

Offline a1ex

  • *****
  • 671
  • ML dev
Re: 500d development
« Reply #1836 on: 19 / November / 2011, 16:15:35 »
Quote
Only issue in this version is the ML menus overlay over eachother
Of course, that was the feature which was disabled :)

Let's try to enable it (that's bmp_fill), but disable the cache.

Re: 500d development
« Reply #1837 on: 19 / November / 2011, 16:51:46 »
Quote
Only issue in this version is the ML menus overlay over eachother
Of course, that was the feature which was disabled :)

Let's try to enable it (that's bmp_fill), but disable the cache.
Ok 1836 crashes like before while ML bottom bar is on and crashes in ML menu now but no change in the selection option before crashing, just crashes.


*

Offline a1ex

  • *****
  • 671
  • ML dev
Re: 500d development
« Reply #1838 on: 20 / November / 2011, 02:35:08 »
At least we have narrowed down the problem to bmp_fill function (in bmp.c). Now, somebody who has the camera and can compile the code can play with this function (maybe slow it down or adjust the caching bits?) until it works well.

Re: 500d development
« Reply #1839 on: 20 / November / 2011, 09:24:30 »
At least we have narrowed down the problem to bmp_fill function (in bmp.c). Now, somebody who has the camera and can compile the code can play with this function (maybe slow it down or adjust the caching bits?) until it works well.
Ok A1ex, and thanks for doing as much as u did to narrow it down. And does that mean for 500d its best to keep the our rec button disabled in ML to avoid err70 also? Or do u think its totally because of the bmp function?

 

Related Topics