Messages

Well, I never heard about 'RAID0 with lower RPM HDDs is more reliable'.
But, personally, if it's about 7,2K vs 5,9K RPM, I would pick the faster one. And I always assume that RAID0 arrays are unreliable. It could fall apart at any moment. Make sure you have proper backup somewhere safe.

NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO !!!

To add drama:
http://nooooooooooooooo.com/

Do you have any screenshots for us to compare?

No?

http://www.magiclantern.fm/forum/index.php?topic=950.0

Wow you guys are fast!!

ISO 12800: http://i.imgur.com/UwtiV.jpg

Denoised: http://i.imgur.com/gKEyi.jpg

super OOT: (yes, sorry...)
Looks like I recognize this place. Is it in Bandung, Indonesia?

I just got the EOS M. Unfortunately, there's no 3-10x digital zoom even though it was available in dpreview. I also don't see a menu setting for updating firmware, does this mean there's no hope for magic lantern?

Maybe you need to set the shooting mode to M to be able to update the firmware?

That's moire effect.

I also have the same problem. Hope to someone can explain how to fix this.

Thanks

Fix what?
Did you read the instructions?

Yes, boot hack will be there in time (i hope).  Started by setting up the compiler and trying to compile ML. Got the following error:

Code Select Expand


boot-hack.o: In function `my_init_task':
boot-hack.c:(.text+0x14): relocation truncated to fit: R_ARM_PC24 against symbol `get_current_task' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x4c): relocation truncated to fit: R_ARM_PC24 against symbol `init_task' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x100): relocation truncated to fit: R_ARM_PC24 against symbol `msleep' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x128): relocation truncated to fit: R_ARM_PC24 against symbol `msleep' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x138): relocation truncated to fit: R_ARM_PC24 against symbol `msleep' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x154): relocation truncated to fit: R_ARM_PC24 against symbol `msleep' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x16c): relocation truncated to fit: R_ARM_PC24 against symbol `msleep' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x1e8): relocation truncated to fit: R_ARM_PC24 against symbol `task_create' defined in *ABS* section in magiclantern
boot-hack.o: In function `my_assert_handler':
boot-hack.c:(.text+0x234): relocation truncated to fit: R_ARM_PC24 against symbol `get_current_task' defined in *ABS* section in magiclantern
boot-hack.o: In function `my_big_init_task':
boot-hack.c:(.text+0x2b8): relocation truncated to fit: R_ARM_PC24 against symbol `call' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x2e8): additional relocation overflows omitted from the output
collect2: ld returned 1 exit status
make[1]: *** [magiclantern] Error 1
make[1]: Leaving directory `/home/alexander/projects/magic-lantern/platform/60D.111'
make: *** [60D] Error 2


It seems you're using 64 bit compiler (CMIIW). You have to pass -mlong-calls parameter to compiler.

Try "hg pull" first before "hg update"

http://magiclantern.wikia.com/wiki/7D_support

"Support for the Canon EOS 7D has literally frozen, having a running version of Magic Lantern might never happen."

tried that, ive done it multiple times, still doesnt

From my experience, you have to update the firmware to 1.0.9 or reinstall the 1.0.9 firmware. It has to be updated at least once.

[-mlong-calls]

Sounds good to me. But I have no clue what that is. Can you explain?

In Makefile.inc, look for CFLAGS variable. Mine looks like this:

Code Select Expand

CFLAGS=\
        $(FLAGS) \
        -Os \
        -Wall \
        -W \
        -mstructure-size-boundary=32 \
        -Wno-unused-parameter \
        -Wno-implicit-function-declaration \
        -Wno-unused-function \
        -Wno-missing-field-initializers \
        -Wno-format \
        -std=gnu99 \
        -D__ARM__ \
        -I$(PLATFORM_INC) \
        -I$(SRC_DIR) \
        -mlong-calls \

Notice the -mlong-calls at the end of variable.

I just made a long post in General Development Discussion about my difficulty building ML using the ARM toolchain I built in my 64-bit Ubuntu 10.04 VM.

Use -mlong-calls on 64-bit systems. It will produce slightly larger binaries. From my experience, I have no problems compiling and running ML on 64-bit systems. I use Ubuntu 12.04 64-bit native, not VM.

[scaling it down]

The sensor on 5D mk ii is 5616x3744. When recording the camera crops the image to a 5616x3159 (16:9), scaling it down to a 1920x1080. As I understand the format of the final file will always be 1920x1080... but...

-deleted-

Btw it's 'line skipping', not 'downscaling'.

Nice site indeed!
But somehow I can't create a new post :-/