Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - breaker

#26
I don't know of any lately builds untill RAW waked up the 50D. It's still bleeding edge but i think it's been tested quite a lot lately; https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads

If you try the one with most downloads (09june13) - i suppose that's the most tested build lately. But it's mainly made and tested for RAW-Video.

EDIT: Now I see that 50D is a part of the Nightly build without RAW-Video. So you can ignore my incompetence :-X
#27
I would love to try it, but I have used my 30 days of trial some month ago. Since the plugin is used for a completely different task no i was hoping for a retry ;)
#28
This was a really nice comparison! The details with RAW is amazing! You can even see steam/smoke and fog naturally. :)
#29
Raw Video / Re: RAW on 650D / 700D?
June 15, 2013, 11:46:32 AM
It have been tryed, and I have tried it myself. But the main bug is that the contrast-focuspoints is showing up on the pictures. You'll find discussions and examples in the main 650D Alpha thread: http://www.magiclantern.fm/forum/index.php?topic=6320.0
#30
Will you continue to develope for the exsisting firmware, or will you look into 1.0.4 anytime soon? Is there any chance that the new firmware will make the software running more smoothly and make more CPU and momory free for ML?
And is there any chance that they have increased the SD bus speed to recognice unrecogniced SD's? ;) ;D
#31
Tragic Lantern / Re: Raw video on 50d and 40d
June 14, 2013, 06:17:34 PM
I got the benchmark working in moviemode. Just had to change the Movie Record (H264) setting to 640x480.
(Toshiba 1066X 64GB)

Moviemode, Global Draw OFF:

#32
Tragic Lantern / Re: Raw video on 50d and 40d
June 14, 2013, 06:09:50 PM
But remember to choose save to RAW in canon menu if not already done. And since Record start have been changed to Set button you will have to choose how to activate Auto-ETTR (double click shutter or Always on).
Personally I found ETTR unreliably on this build, but it seems to be a bit better on Andy600's build of today. Mostly unreliably on not Auto-ETTR when doubleclicking the shutter - sometimes I have to doubleclick many times before it activates.
#33
Tragic Lantern / Re: Raw video on 50d and 40d
June 14, 2013, 05:47:03 PM
My Toshiba 1066X 64GB arrived today, and I have been doing some tests  :)
I used Andy600's build of June 14th.

Benchmark in Moviemode, Global Draw OFF. Crashed during the test so here is a photo of the screen after the freeze:



Playbackmode, Global Draw ON:



When testing the card on ATTO Disk Benchmark (default settings) the highest writespeed i get is approx 125 MB/s.
#34
Tragic Lantern / Re: Raw video on 50d and 40d
June 12, 2013, 10:24:05 PM
Quote from: GregoryOfManhattan on June 12, 2013, 08:44:51 PM
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/12june13-50D-8823d8ad10ef.zip

I have a lot of problems with the Auto ETTR in this build. Since Recording has been moved to Set button I have choosen Shutter Doubleclick, but it's not always working. The result is also most of the time wrong. On the build from 08june13 it was great - also with Shutter Doubleclick selected!

Just for info; I'm waiting for a  Toshiba 64 GB 1066X which hopefully will arrive this weekend. I will post my benchmark then. Now i'm just playing with a Kingston 266X...
#35
Tragic Lantern / Re: Raw video on 50d and 40d
June 11, 2013, 08:17:53 PM
@ Ifani, can you playback the files on camera from Raw video Q-menu or in the file browser?
#36
Tragic Lantern / Re: Raw video on 50d and 40d
June 11, 2013, 05:52:49 PM
Have you tried to open one of the pictures in Photoshop? Or tried to open picture two or later of the sequence?
#37
I bought two cheap power adaptors ::). The last one claimed to be 100% Canon compatible, but non of those had the chip that is needed to be recogniced as an "original" battery so the camera wouldn't let me upgrade firmware (install ML).
I ended up with this nice-priced LanParte external battery which also can be charged when in use.
http://cheesycam.com/lanparte-external-battery-power-for-canon-dslr-test/

When ML autoload on 7d is released you can of course use your adaptor, but when setting the camera bootflag a battery with chip is needed.

#38
Share Your Videos / Re: first time lapse
May 17, 2013, 10:07:24 PM
Nice view, and flicker free! :)

But it seems to be a bit out of focus, so I'll do a quick focus guide in case you don't know the trick with infinity focus (I didn't first time i shot stars... ;D)

- Set focus to manual and turn the fucus wheel to the infinity-mark "8" (not completely to the end position).
You can also do "half shutter-fucus" in auto with pointing at a contrast point in the view (might be the horizon, cloud or maybe the sun), and then set the focus back to manual. You will now see the right infinity point at the focusindicator.
#39
Quoteif that would be the generic 7D user opinion ...

Nope, it's not for the majority of 7D users. I have followed the developement of ML since you released ML for 7D. And even if we don't have all the amazing new features on our 7D's, I know it's all done for the best for every ML user - also for 7D users if it's possible.

Congratulation for the great job you, a1ex and the rest of the team have done with bringing 14 bit RAW to Canon DSLR! I celebrate with you - and I know you'll be back when the mission is completed :)
#40
Thank you nanomad for this update! I have loaded the new version, and is ready to play with it :) First impression is good!

And about people complaining about an vague installation instruction, i think it on purpose; Remember this is still an PreAlpha, and I don't recommend it for you if you haven't read at least this thread. I think you will find some hints someplace (think I have seen so...) But I am lucky - my camera was Bootflag-enabled at the first PreAlpha, so I don't have to look for it 8)
#41
Thanks for the update nanomad! Hope the rest of your work with 650d goes smooth :). Have a nice weekend!
#42
General Help Q&A / Re: Canon T4i and Mountain Lion
April 13, 2013, 12:51:51 PM
Don't be sorry - We can all use future releases of ML, and that's what matters :)

Thanks for all your hard work on ML for 650D!
#43
General Help Q&A / Re: Canon T4i and Mountain Lion
April 12, 2013, 05:00:12 PM
If i can do anything to help, just let me know.
#44
General Help Q&A / Re: Canon T4i and Mountain Lion
April 12, 2013, 04:52:28 PM
CRC like http://en.wikipedia.org/wiki/Cyclic_redundancy_check ? Will that make coming releases of ML unusable for us with 1.0.1 untill Canon releases an official FW upgrade?
#45
General Help Q&A / Re: Canon T4i and Mountain Lion
April 12, 2013, 04:38:31 PM
Quote from: nanomad on April 11, 2013, 10:05:01 PM
You can use the windows update .zip...just place the fir on the root of the sd card and run the firmware upgrade from the camera
Your t4i should already have 1.02

1.0.2 :o? I have 1.0.1 and my camera is still alive after all my preAlpha testing ::)
#46
Run luplo, RUN :D! - sorry, you can just sit back :P

Great to hear the progress nanomad! I tested todays nightly since i saw some activity around the FSP override in "hudson" yesterday, but still had crash after end of recording. But i assume from what you wrote that i will also need a newer .fir before it's fixed.
#47
Quote from: baga on March 08, 2013, 04:09:03 PM
Yes it's both.

I didn't realized that - I always forget that the screen is touch... ;) But testing it now, and for me the touch just works as Q. So you have to navigate with key's to the right box, and then you can press the screen to get into the submenu. I don't know if touch will work on that menu - some of the boxes are a bit too small to hit. Then it need to have some sort of magnifitcaion or white frame on touch and activation on release.

There is an own thread for the menu rationalization. Maybe it's mentioned there: http://www.magiclantern.fm/forum/index.php?topic=4386.0
#48
And here is today's testing.

! The MENU's I have tested is tested completely  - So when nothing is mentioned I think it's working !

Prefs MENU:
- Image review settings: The silent .422 pictures doesn't show up (not on PC ither). With Compare Images the primary picture sometimes changes.
- Quick Zoom: "Full zoom on AF pt." allways zooms on the middle of screen - not on AF points.
- FlexInfo Settings: Buggy as hell :o

Debug MENU:
- Burn-in tests: "Stubs API test" 83 passed, 3 failed:

[Pass] strlen("abc") => 0x3
[Pass] strlen("qwertyuiop") => 0xa
[Pass] strlen("") => 0x0
[Pass] strcpy(msg, "hi there") => 0x1acd00
[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) => 0x1acca0
[FAIL] foo => ''
[Pass] memset(bar, '*', 5) => 0x1acc80
[FAIL] bar => '*****ghjkl'
       bzero32(bar + 5, 5)
[Pass] bar => '****'
       t0 = *(uint32_t*)0xC0242014 => 0x84d0b
       msleep(250)
       t1 = *(uint32_t*)0xC0242014 => 0xc355a
[Pass] ABS(mod(t1-t0, 1048576)/1000 - 250) => 0x6
       LoadCalendarFromRTC( &now )
       s0 = now.tm_sec => 0x2c
       Date/time: 2013/03/06 19:10:44
       msleep(1500)
       LoadCalendarFromRTC( &now )
       s1 = now.tm_sec => 0x2d
[Pass] mod(s1-s0, 60) => 0x1
[Pass] mod(s1-s0, 60) => 0x1
       m0 = MALLOC_FREE_MEMORY => 0x5f6c0
[Pass] p = malloc(50*1024) => 0xe0120
[Pass] CACHEABLE(p) => 0xe0120
       m1 = MALLOC_FREE_MEMORY => 0x52eb0
       free(p)
       m2 = MALLOC_FREE_MEMORY => 0x5f6c0
[Pass] ABS((m0-m1) - 50*1024) => 0x10
[Pass] ABS(m0-m2) => 0x0
       m0 = GetFreeMemForAllocateMemory() => 0x37ca54
[Pass] p = AllocateMemory(256*1024) => 0xa7a498
[Pass] CACHEABLE(p) => 0xa7a498
       m1 = GetFreeMemForAllocateMemory() => 0x33ca48
       FreeMemory(p)
       m2 = GetFreeMemForAllocateMemory() => 0x37ca54
[Pass] ABS((m0-m1) - 256*1024) => 0xc
[Pass] ABS(m0-m2) => 0x0
       m01 = MALLOC_FREE_MEMORY => 0x5f6c0
       m02 = GetFreeMemForAllocateMemory() => 0x37ca54
[Pass] p = alloc_dma_memory(256*1024) => 0x40a7a4d8
[Pass] UNCACHEABLE(p) => 0x40a7a4d8
[Pass] CACHEABLE(p) => 0xa7a4d8
[Pass] UNCACHEABLE(CACHEABLE(p)) => 0x40a7a4d8
       free_dma_memory(p)
[Pass] p = (void*)shoot_malloc(24*1024*1024) => 0x4a000068
[Pass] UNCACHEABLE(p) => 0x4a000068
       shoot_free(p)
       m11 = MALLOC_FREE_MEMORY => 0x5f6c0
       m12 = GetFreeMemForAllocateMemory() => 0x37ca54
[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) => 0x50d00004
[Pass] test_task_created => 0x1
[Pass] get_task_name_from_id(get_current_task()) => 'run_test'
[Pass] mq = mq ? mq : (void*)msg_queue_create("test", 5) => 0x511e00ae
[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) => 0x51b60114
[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) => 0x52580082
[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) => 0x407f9cc4
[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


Help MENU:
- No documentation. Not when hitting info button on the rest of the munu's ither. Suppose it's because it's nightly..?

When the screen is turned (self shot mode?) it's still mirrored.

I really like the Junkie mode - it gives a quick overview!

And thats all for now! Now my testing will be normal use ;)
nanomad if you need anything more to be tested, you know where to send it 8)
#49
Share Your Videos / Re: My first timelapse!
March 06, 2013, 08:08:15 PM
I don't know why, but my aperture is moving a bit in changing light in AV mode... In my test i have Av at F9,1 (Sigma 30mm) and when moving from a dark area to a lamp I can hear clearly "aperture sound" :o

If you read Documentation - Userguide, you will find a lot of good reading under Intervalometer. It's mentioned; "unscrew lens" which is unscrew until the lens looses electrical contact with the camera - by that way it will keep the Aperture unchanged.

#50
Quote from: blade on March 06, 2013, 08:48:50 AM
Today is a good day for testing! today is your tomorrow, as you wrote your post yesterday  :P. I hope to do some testing during lunch today....  Will keep you posted. 

That's right! And now I have too keep my promises ;) I have learned a lot from the systematic testing so far, and I find possibilities I would not have found without it!