Messages

Nanomad, and all the other devs.... Thanx

Now i will give my smaal contribution:

As requested:
https://www.dropbox.com/s/jfr1fpdv43fz2mc/Sandisk%2032GB%2045MB%3As.BMP
I have seen other cards perform a lot faster aldo this is in line what the card is supposed to do.

I did the stuptest: 1 fail.

Code Select Expand

[Pass] strlen("abc") => 0x3
[Pass] strlen("qwertyuiop") => 0xa
[Pass] strlen("") => 0x0
[Pass] strcpy(msg, "hi there") => 0x1ad108
[Pass] msg => 'hi there'
[Pass] snprintf(a, sizeof(a), "foo") => 0x3
[Pass] snprintf(b, sizeof(b), "foo") => 0x3
[Pass] strcmp(a, b) => 0x0
[Pass] snprintf(a, sizeof(a), "bar") => 0x3
[Pass] snprintf(b, sizeof(b), "baz") => 0x3
[Pass] strcmp(a, b) => 0xfffffff8
[Pass] snprintf(a, sizeof(a), "Display") => 0x7
[Pass] snprintf(b, sizeof(b), "Defishing") => 0x9
[Pass] strcmp(a, b) => 0x4
[Pass] snprintf(buf, 3, "%d", 1234) => 0x2
[Pass] buf => '12'
[Pass] memcpy(foo, bar, 6) => 0x1ad0c0
[Pass] foo => 'asdfghuiop'
[Pass] memset(bar, '*', 5) => 0x1ad0a0
[Pass] bar => '*****hjkl;'
       bzero32(bar + 5, 5)
[Pass] bar => '****'
       t0 = *(uint32_t*)0xC0242014 => 0x81282
       msleep(250)
       t1 = *(uint32_t*)0xC0242014 => 0xbe498
[Pass] ABS(mod(t1-t0, 1048576)/1000 - 250) => 0x0
       LoadCalendarFromRTC( &now )
       s0 = now.tm_sec => 0x4
       Date/time: 2013/04/30 15:09:04
       msleep(1500)
       LoadCalendarFromRTC( &now )
       s1 = now.tm_sec => 0x6
[Pass] mod(s1-s0, 60) => 0x2
[Pass] mod(s1-s0, 60) => 0x2
       m0 = MALLOC_FREE_MEMORY => 0x4f0a0
[Pass] p = malloc(50*1024) => 0xf0800
[Pass] CACHEABLE(p) => 0xf0800
       m1 = MALLOC_FREE_MEMORY => 0x42890
       free(p)
       m2 = MALLOC_FREE_MEMORY => 0x4f0a0
[Pass] ABS((m0-m1) - 50*1024) => 0x10
[Pass] ABS(m0-m2) => 0x0
       m0 = GetFreeMemForAllocateMemory() => 0x399108
[Pass] p = AllocateMemory(256*1024) => 0x7f5d58
[Pass] CACHEABLE(p) => 0x7f5d58
       m1 = GetFreeMemForAllocateMemory() => 0x3590fc
       FreeMemory(p)
       m2 = GetFreeMemForAllocateMemory() => 0x399108
[Pass] ABS((m0-m1) - 256*1024) => 0xc
[Pass] ABS(m0-m2) => 0x0
       m01 = MALLOC_FREE_MEMORY => 0x4f0a0
       m02 = GetFreeMemForAllocateMemory() => 0x399108
[Pass] p = alloc_dma_memory(256*1024) => 0x407f5d98
[Pass] UNCACHEABLE(p) => 0x407f5d98
[Pass] CACHEABLE(p) => 0x7f5d98
[Pass] UNCACHEABLE(CACHEABLE(p)) => 0x407f5d98
       free_dma_memory(p)
[Pass] p = (void*)shoot_malloc(24*1024*1024) => 0x4a000068
[Pass] UNCACHEABLE(p) => 0x4a000068
       shoot_free(p)
       m11 = MALLOC_FREE_MEMORY => 0x4f0a0
       m12 = GetFreeMemForAllocateMemory() => 0x399108
[Pass] ABS(m01-m11) => 0x0
[Pass] ABS(m02-m12) => 0x0
       EngDrvOut(0xC0F14400, 0x1234)
[Pass] shamem_read(0xC0F14400) => 0x1234
       call("TurnOnDisplay")
[Pass] DISPLAY_IS_ON => 0x1
       call("TurnOffDisplay")
[Pass] DISPLAY_IS_ON => 0x0
       call("TurnOnDisplay")
[Pass] DISPLAY_IS_ON => 0x1
       SetGUIRequestMode(1); msleep(1000);
[Pass] CURRENT_DIALOG_MAYBE => 0x1
       SetGUIRequestMode(2); msleep(1000);
[Pass] CURRENT_DIALOG_MAYBE => 0x2
       SetGUIRequestMode(0); msleep(1000);
[Pass] CURRENT_DIALOG_MAYBE => 0x0
[Pass] display_idle() => 0x1
       GUI_Control(BGMT_PLAY, 0, 0, 0); msleep(500);
[Pass] PLAY_MODE => 0x1
[Pass] MENU_MODE => 0x0
       GUI_Control(BGMT_MENU, 0, 0, 0); msleep(500);
[Pass] MENU_MODE => 0x1
[Pass] PLAY_MODE => 0x0
[Pass] MEM(dialog->type) => 0x4c414944
       GUI_Control(BGMT_MENU, 0, 0, 0); msleep(500);
[Pass] MENU_MODE => 0x0
[Pass] PLAY_MODE => 0x0
       task_create("test", 0x1c, 0x1000, test_task, 0) => 0xc9220004
[Pass] test_task_created => 0x1
[Pass] get_task_name_from_id((unsigned int)get_current_task()) => 'run_test'
[Pass] mq = mq ? mq : (void*)msg_queue_create("test", 5) => 0xc96c00b2
[Pass] msg_queue_post(mq, 0x1234567) => 0x0
[Pass] msg_queue_receive(mq, (struct event **) &m, 500) => 0x0
[Pass] m => 0x1234567
[Pass] msg_queue_receive(mq, (struct event **) &m, 500) => 0x9
[Pass] sem = sem ? sem : create_named_semaphore("test", 1) => 0xc9f20294
[Pass] take_semaphore(sem, 500) => 0x0
[Pass] take_semaphore(sem, 500) => 0x9
[Pass] give_semaphore(sem) => 0x0
[Pass] take_semaphore(sem, 500) => 0x0
[Pass] give_semaphore(sem) => 0x0
[Pass] rlock = rlock ? rlock : CreateRecursiveLock(0) => 0xca8400c2
[Pass] AcquireRecursiveLock(rlock, 500) => 0x0
[Pass] AcquireRecursiveLock(rlock, 500) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0xf
[Pass] f = FIO_CreateFileEx(CARD_DRIVE"test.dat") => 0x4
[Pass] FIO_WriteFile(f, (void*)ROMBASEADDR, 0x10000) => 0x10000
[Pass] FIO_WriteFile(f, (void*)ROMBASEADDR, 0x10000) => 0x10000
       FIO_CloseFile(f)
[Pass] FIO_GetFileSize(CARD_DRIVE"test.dat", &size) => 0x0
[Pass] size => 0x20000
[Pass] p = alloc_dma_memory(0x20000) => 0x407f5d98
[Pass] f = FIO_Open(CARD_DRIVE"test.dat", O_RDONLY | O_SYNC) => 0x4
[Pass] FIO_ReadFile(f, p, 0x20000) => 0x20000
       FIO_CloseFile(f)
       free_dma_memory(p)
[Pass] count => 0x3a98
[Pass] FIO_RemoveFile(CARD_DRIVE"test.dat") => 0x0
       SW1(1,100)
[FAIL] HALFSHUTTER_PRESSED => 0x0
       SW1(0,100)
[Pass] HALFSHUTTER_PRESSED => 0x0


I will test most settings with the standard settings, if not if will make a note:

Overlay menu:
Zebras:
     Color space
                  RGB:OK
                  luma: OK
                  lumafast:OK
     Underexposure:OK
     Overexposure OK
     When recording:OK

Focuspeak:OK
                 Did not play with the sup settings.

Magic Zoom: Not 100% OK Image is flickering in 2:1 and 3:1 mode. In 1:1 mode fast flickering
      Trigger mode: OK (only + tested)
      Size: OK Only medium tested
      Position:
               Focus box OK
               Top-Left: OK
               Top-right: OK
               Bottom-right: OK
               Bottom-left:OK
Cropmarks:OK
      Bitmap : 5/5 OK
      Show in photo mode:OK
      Show in play mode: OK

Ghostimage:OK
      Autoupdate:OK

Spotmeter:OK
      Unit:
              Percent:OK
              0..255:OK
              rest: not tested
      Spot position:
              Focus box:OK
              Center:OK

False color:Not 100% ok?? A box as in spotmeter ( that is off) remains in the middel of the image and is not effected.
       Marshall:OK
       SmallHD:OK
       50-55:OK
       67-72:OK
       banding detection:OK
       Greenscreen: I do not have a green screen, seems to work but cant confirm

Histogram: OK
      Color space:
              Luma:OK
              RGB:OK
     scaling:
              Log:OK
              Linear:OK
    Clipwarning:OK

Waveform:OK
     small:OK
     medium:OK
     large:OK

Vector scope: OK
      UV scaling 2x:OK

More to come. I will test a complete menu en reference to my other posts.

Thats all for now...

Got home, did the low level format etc etc. and it works.

I will start testing in detail tomorrow. Thanks everyone !

Out in the feeld today, but will install the minute I get home! Tx

My 650d does work as advertised.  That leaves the card 

How big are raws? My 600D is shooting 6 raws in a row.

My rawes are up to 27mb

Do you shoot raw or raw + jpg?   Only raw works fine for me, raw + jpg will make it pause after 3-4 shots if I remember correctly.

Way easier if you use the pre-configured virtual machine

Haha, yes if you know what you are doeing! Out of curiosity I downloaded the virtual box image and got the latest code downloaded...  Thereafter it became to difficult for me...  But then again if I see a command line I het scared :-)

I found a download link for 650D alpha 1, is it an early stage alpha? 

If I am correct this is the source code from last month. If you have the skills you can compile your own version from this code. Unless you know what you are doeing I would not advise this

There is no precompiled public version available at the moment. A closed alpha is a viable to selecte testers, however this is still an early version. However progress is being made and when it's safe it will be released.

It does bring up the question: what assumptions about the experience/expertise level does ML want to make of its "audience"? So far? In the future?

Well lets asume you deep enough into photography to:
- spend 600+ euro on equipment.
- feel like the hardware could do a better job
- have the guts to download and install ML lantern on your expensive hardware.

Then i would also asume you would be willing to spend the time to figure things out on your own/documentation/forum.

I think the documentation we get with ML are already far superior to what we get from canon ( as there is no real in camera documentation).

Update:
- Added a better fw signature for the 650D
- Fixed MagicZoom vsync

Nanomad,  does the better firmware signature mean that boot problem that could brick a camera is fixed? And no more flickering magic zoom is very nice!

For me as a tester, i would welcome a more structured way for testing an feedback. A thumps up/down method, with the ability to provide additional info and ore links would be very nice. I now find myself struggling in providing good feedback ( and that includes what does work, what doesn't work, and what i have not tested) in a readable setup.

Additional if a new build is available it would be nice to have an overview of what has changed. This would enable me to focus on stuff that was changed, and not the whole thing.  This would also enable the developers to asks the testers to focus on a particular item.

This is the first time I am participating in a project as this, but the method used now with Nanomad works really well for me.

I would welcome a testers build!

A weekly update would be nice, and even if there are no changes, at least we would now that the bugs present are not jet fixed and we can focus on finding new bugs.

If you would have read the tread, you would know...  Its done when its done. No time frame, no deadline, no ms project planning.

If I could compile a version for you ( and I can't) I would not give it to you. Any bugs you run in to you will report back here. And as it would be a costum build the developers would have a hard time figuring out what may have coused the bug.

Wait for the build from nanomad, it will not have every option activated, but it will be testable. So fare the code is very stable ( far more stable then some comersial final software I have to work with) and that takes time.

Aldo I have a pre alpha running, I to look forward to a alpha version. And when it is there I will test and report back.

I would like to share some of the pre alpha testing. Shooting video at 2.5 fps will lead to a system crash ( already reported to nanomad, and a fix is in development as far as i know) Additionally, vertical lines apear in the video. Aldo this may not be specific for this release.

That seems correct. It's done when its done. I am testing a closed alpha, and as far as I know there are still a few bugs that need to be fixed before a public realease.

I have no coding skills so a can only speed up the process by testing. But even only testing consumes a lot of free time.

I think that it's a wise disision not to rush the alpha, and to realease a more or less stable code when the time ripe.

Lol,
However if you would have read the whole post you would know that we are planning to hack the space time continuum. After completion we will implement all future canon and mll features yesterday. So in fact it is already here. And that includes the antigravity function from the eos xx980d extreme from 2042.

in order to get back on the subject:

I have been using the closed alpha, and the good news is that it works as it should. Nu hang, or other noteworthy spoilers. Oldo i do not test and use everything thats seems to be working.

I would donate time to Nanomad, however that seems to be impossible, until someone is able to hack/reverse engineer the time space continuum. I do see some activity on the 650D here https://bitbucket.org/hudson/magic-lantern/commits/all/ so that keeps me entertained, as for the majority I have no clue what is going on. I mean...  dietlib atoi ....  or ... allow x++/x-- on floats...  its like reading an other language ..   o wait.. it is!.

Well spring time is here, maybe a new alpha egg will be in the ML nest in the near future.

My bad!!!  Thanx

2 clips at 1920, 24fps, 1/47, default bit rate. I started the timer several seconds in; last frame of first clip was at 12:11.58, the first frame of the second clip was at 12:13.00. So, 1.42 seconds on DIGIC 4.

I beleve ( oldo I am only awake for 10 min ) that I spotted a calculation error
13:00 - 11:58. = 01:02 seconds. And not 01:42. Or was it a typo?

Anyone heard from ProfessorX?  I know he was loving the pre-alfa.

Not on this forum, no. Would be nice to know if he had time to test.

Be patience , takes time! 

The software was sent to a few trusted testers. And runs in safe mode ( does not boot by itself ). As far is I know no big issues were found. Nanomad already announced that he will compile a public alpha.

That's the time to jump in if you want to make a contribution.

I might be wrong but I think nanomad is the sole developer working on the 650d. So if he finds time, that is greatly appreciated. If not, so be it...

I have no coding skills so I can't make a contributions in that part of the development. If you do have the skills, please help out we're you can.

Otherwise, wait for it, and be thankfull if and when it arrives.

Sorry for not reporting as promised.... kids... work.... well you know....

I will keep it short, most stuff works, some does not as breaker reported. Overall very stable, and responsive.

And as breaker i do like this mode:





Looking forward to the alpha, so more people can get testing.

nanomad, thats great news! I promised to test some more today, but I had no time for it. But tomorrow seems to me a good day for testing

Today is a good day for testing! today is your tomorrow, as you wrote your post yesterday  . I hope to do some testing during lunch today....  Will keep you posted. 

Nanomad, I have been using the build without specific testing, but just shooting, and so far its been nice and stable, nothing to report.

Aren't the audio settings menu not working at all? 

The 650D had audio settings in the canon firmware..  so no need in ML

Movie MENU:
- FPS override: Not working. The movie is auto-stopping after few seconds. Sometimes with crashreport.

Breaker, welkom to the party!

Confirmed, FPS override. Not working.

Some clips last for up to 10 sec, and then the camera crashed. The clip that is saved is a few MB, and consist out of only one frame

FPS set to 2.5

Code Select Expand

ASSERT: 0
at Graphics.c:3580, task CtrlSrv
lv:0 mode:3


Magic Lantern version : v2.3.NEXT.2013Mar02.650D101
Mercurial changeset   : 3eecdcedfce1+ (unified) tip
Built on 2013-03-02 19:43:49 by alex@thinkpad.
Free Memory  : 381K + 3612K