Messages

Today I shipped my M to 1%, he will be taking over from here. I decided I just don't have the time right now to figure out some of the problems.

todo: merge 1%'s repo with main (and update to newest firmware version in the process)

Oh man, that is so backwards. I guess it will work in a pinch. If I have to save frames, might as well do AE

it's pretty easy to extract a frame, you just click the extract button when viewing a clip in library mode puts a jpeg right in the library next to the video clip

When I tried it only let me change a few settings not correct video like photos. Will have to try again. Correcting in LR is easier than in PS/AE

extract a frame from the clip, put the frame into develop module, change your settings like any other pic, then copy/paste the develop settings to the video clip. You can't load a video clip into the develop module but you can paste settings to them.

It's never been fast enough on my computer, the exporting takes literally HOURS for short clips.


I like that you can edit video the same way you'd edit photos (just copy/paste settings like curves, sharpening, white balance, etc) but that exporting just takes forever.

i've tried translating, and lost tens (countless) of hours to it. I refuse to try again

Can anyone tell me how to get a crop square that is just 2 lines ( to get maximum resolution from the crop) the one I am using just now you can see the whole square . I would like one that is just 2 lines preferably blacking out the edges of screen.
Is this possible with ML?

can you please draw an example in something like ms paint? i'm a bit confused

Yes please. Good thing I can use some stubs to verify image position so I don't get mis aligned like with 5d3.

I really really hope they fixed some other things and didn't just pull a 600D where they fixed nothing.

* also need to know how to dump ram segment since I'll probably need a new one.

I highly doubt the ram segment has changed but I'll verify that tonight. If anything the position of it just changed. The ram functions seem to all be the same, like some kind of "library package" for use on multiple platforms.

most likely the rom will be like:

before:
[=start===============end=]

now:
[=start=======[newcode]========end=]

just a slight shift (if anything new added)

That's it? Of all the bugs that is what you fix?

How do I go about porting/checking?

I can do it later today if you'd like, i like doing grunt work like checking stubs by hand

All you've gotta do is verify the stubs. Most likely stubs towards the start of the rom (cstart, etc) won't change but at some point canon added some code so everything after that point is shifted by a fixed amount. It's best to just check them all by hand though.

I used the 6D extensively this weekend using the autoexec.bin-Flush_tester release, seemed to be pretty stable - minus shoot malloc error with format dialog (could ignore, had another card with me).

Looking great 1% 

This looks promising:

- new pocket camera that shoots 1080p raw uncompressed 12-bit and costs <$1000
- new production camera updated with a new sensor and 4K recording ($4000)

http://gizmodo.com/5994043/blackmagic-pocket-cinema-camera-raw-video-in-the-palm-of-your-hand-for-1000

This changes the game for Canon and Nikon, they're playing catch-up now

Just loaded ML on my EOS M. It seems to have loaded ok and can see the overlay.
I tried the trash button to bring up the ML menu but no luck
I know this seems simple. how do I open the ML menu? can't find it anywhere

tap 2 fingers on the screen at the same time

1 finger tap is same as Q, to open submenus.

The M seems to suffer the vertical line thing too, here you can see it starts at about 0:04 and gets progressively worse through the timelapse. I shot this for about 9 hours.

With timer A/B control FPS override can be tuned to get rid of the lines. Unfortunately the side effect of timerB is dark noise.. The specs might be dust on the sensor? I'm not sure... Purple cast in the corners is part of the dark noise.

The noise pattern and noise pattern with curve to make it more visible.

http://imgur.com/a/ceynY#0

Exact FPS tends to be line free. Adjust shutter (in adv menu) up until you reach one you can actually use or until speckle/lines/etc disappears.

Maybe there is a way in post to remove both this and the lines. I tried AE and color exclusion.. maybe better to matte it somehow?

*TimerB over 2000 gets rid of the lines at extreme fps. YMMV

Reminds me of back when I had a powershot and used chdk, one effect of using >30second exposures made purple / pink distortions like that in the same manner (usually in one corner), they determined it's due to sensor heat.

what do the temps look like when this happens (higher than normal)?

Sure, the 5d2 had excellent video quality at that time, and both 21/20 mp chips don't like pixel binning like on the 5d3 so you have to expect some moire. Problem is: The world has revolved some times around the sun, and there are not-so-expensive cameras with ef lens mount that blow even the 5d3 out of the water (but lack Magic Lantern...): http://www.canonrumors.com/2012/09/canon-eos-5d-mark-iii-vs-blackmagic-design-cinema-camera/

good video, whoa.

I have compiled autoexec.bin for 5Dmark3 many times. Last time on 3/11/2013.
I used commands:
cd magic-lantern
hg pull
hg update
make -C /home/vXXXX/magic-lantern/platform/5D3.113
But I have got an error today:

$ make -C /home/vXXXX/magic-lantern/platform/5D3.113
make: Entering directory `/home/vXXXX/magic-lantern/platform/5D3.113'
[ CC       ]   boot-hack.o
/bin/sh: /home/vXXXX/gcc-arm-none-eabi-4_7-2012q4/bin/arm-none-eabi-gcc-4.7.3.exe: No such file or directory
../../Makefile.inc:672: recipe for target `boot-hack.o' failed
make: *** [boot-hack.o] Error 127
make: Leaving directory `/home/vXXXX/magic-lantern/platform/5D3.113'

There are only two dir in vXXXX :magic-lantern and arm-toolchain462
What is a problem?
Then... :
installed gcc-4.7.3,
made dir gcc-arm-none-eabi-4_7-2012q4 in vXXXX
copied all from installed gcc-4.7.3 dir to dir gcc-arm-none-eabi-4_7-2012q4

O.K.now

/bin/sh: /home/vXXXX/gcc-arm-none-eabi-4_7-2012q4/bin/arm-none-eabi-gcc-4.7.3.exe: No such file or directory

Please modify Makefile.userdefault to point to where your toolchain is located

First link loading infinitely, second link 404.

working for anyone else?


News article:
http://www.networkworld.com/community/node/82716

I'm busy with class at the moment (have to do school before ML), but I try to work on it when I get free time.

lately I'm trying to figure out a guimode number to use for the ML menu, to keep the canon EV bar from blinking on top of the ML menu.

I think the property exists but the low level activity from PropMgr doesn't happen, and the front-end code for the menu is obviously removed. I think canon is more careful to remove all code after we unlocked movie recording on the 50d. They probably have things ifdef'd out like we do with features.

PropMgr and its taskclass events / states are the missing link, since we don't understand much of the low level things. I have somewhat of an understanding of how the taskclass events trigger state changes but it's hard to study.

Maybe Java would be a language to think about - for cross platform compatibility? (but i don't like java very much )

http://nofilmschool.com/2013/01/canon-legal-team-modify-hack-firmware-1d-x-1d-c/

I was told by someone at Canon that they would "bring the might of its legal team" to anyone that attempts to modify at the software level, the features of an EOS-1 camera body.

so, it's not in the best interest of the developers to do this.

what phone? more details please

Great work so far!

I've thought about this, I think in the coming years as cameras begin to ship with built in WiFi like the 6d, then we can collect user data. But right now there isn't a good way to collect it, short of users uploading it themselves.

Collecting user data would allow us to organize the menus in a fashion that's most easily accessible to users: ie: features that are used most will come first on the menu.

Careful - I fried my first dslr (400D / Rebel XTi) by using an old flash with it. Research before putting it on the camera