Messages

Using magic lantern for 6d since oktober 2013.
The worst I saw happen is that it "freezes", popping out the battery was enough to start over again.

Not sure myself therefore I marked this blue. But I understood it like solved at least there were comments about edmac being same as 5dmk3 and resolution seems to be found, too.

600d isn't capable of AFMA tuning. that's available for 50D, 7D, 6D and 5Dmk2/3...

Yes, just came beware of it. It's the same as he posted in rawdiag here:
http://www.magiclantern.fm/forum/index.php?topic=10111.msg120656#msg120656

Thanx @Levas for posting this.
Link works here.

[thought]

It will kick me out of the ML menu and back to live view after a few seconds, no matter how many times I re-open ML menu! Am I missing something?

Yeah I can confirm this. But I thought this is normal behaviour as I was using ML for the first time on my cam. About 2-4 seconds and afterwards you get kicked out the menu if you don't navigate through it

My post may be not really helpful to make a decision. I can't really say much about 6D at all as I am a new 6d and also Canon user. But I am really impressed with the performance of the 6D. I got a smile on my face once I have seen first OoC pictures of it. This one has a real awesome lowlight performance. Center focus point really is awesome at lowlight. Compared to what I am used to use (Nikon D90 / D500 / D7100) the 6D is a monster. Pictures taken at night look like they have been taken at dusk / dawn. Would you be able to borrow the 6D for a day or a weekend? This way you could decide on your own if it's worth. I would really be happy if someone like you would join the 6d contributors. I guess this would help a lot. Ofc to invest in lenses with the xtra money earned by selling your mk3 is best as the loss in invested value for lenses is low once sold again.

6D can record about 13 seconds of RAW in default settings. You have to lower the resolution significantly for contunuous raw recording. Hopes were high for the new implemented SRM memory but 6D unfortuantely didn't see any improvement regarding recording times here. Yuu will have to keep your eyes open for a cam like 5d mkII / III or 7D owning cf card and having more write speed or something like a 60d with high amount of srm memory....

[EOS-6D113]

EOS-6D113 Nightly.2014Jul16
Confirmed: Using 24fps set in Canon Menu gives about 2MB/s better result with my sdhc card.
Following is the best I could get with my Panasonic Gold Card (Panasonic rates card on the sticker as Read: 90MB/S and Write 45MB/s.)

Thanx for feedback @Levas and also thank you Audionut for the feedback regarding compilation. 

Here is mine as promised to test @Levas. See also first post as Audionut already compiled it for you. Use his build first

Build removed //Audionut.

I can compile 3d6a945 in about 12 hours for you as I have no access to my build environment atm. Ofc if no one else agrees to do so in the meantime. It's just some minutes to do and upload it. I also am interested in the results

[GCC 4.8.4]

Did some testing regarding autexec binary sizes with different FLAGS and a fresh VM with GCC 4.8.4. Posted values are for building 6D.113. All changes I made were done to Makefile.setup and this is how it looks by default on bitbucket:
^{....
ifeq ($(TARGET_COMPILER), arm-gcc)
   CFLAGS += -Os -mthumb-interwork -march=armv5te \
            -D__ARM__
endif
....}
Compiling that outputs autoexec.bin: 464016 bytes

Next try:
^{....
ifeq ($(TARGET_COMPILER), arm-gcc)
   CFLAGS += -Os -mthumb-interwork -march=armv5te -mfloat-abi=softfp \
            -D__ARM__
endif
....}
autoexec.bin: 463440 bytes

Next try:
^{....
ifeq ($(TARGET_COMPILER), arm-gcc)
   CFLAGS += -O2 -mthumb-interwork -march=armv5te \
            -D__ARM__
endif
....}
autoexec.bin: 500400 bytes

Next try:
^{....
ifeq ($(TARGET_COMPILER), arm-gcc)
   CFLAGS += -O3 -mthumb-interwork -march=armv5te \
            -D__ARM__
endif
....}
autoexec.bin: 597936 bytes

Next try:
^{....
ifeq ($(TARGET_COMPILER), arm-gcc)
   CFLAGS += -O3 -mthumb-interwork -march=armv5te -mtune=arm946e-s \
            -D__ARM__
endif
....}
autoexec.bin: 597360 bytes

I expect to hold my cam in hands once I am back @home. Could increased binary sizes brick my brand new cam? Ofc I wouldn't use them for now cause I have no clue what to benchmark and first would need to get a feeling for default nightlies but red colored flags and a combo of them might be an option to use for compiling (mfloat-abi=softfp / mtune=arm946e-s / O2 / O3 ) and test later. At least my VM is setup to built ML and therefore I tried to set some flags and compare the output - just need to get comfortable with hg and bitbucket as I solely used git to fetch code from github while compiling android roms...

I like the idea of havin a new and unique FAQ. You did one. But as stated on that I miss a disclaimer and a golden rule. And I must admit (being a new user to ML forum) I feel like being lost. Too much stuff to read, lots of topics (some meanwhile outdated and so on). Maybe do a cut and archive + delete really old ones....

2 suggestions:

1) a better search (many people obviously do not know how to use the one on here, in addition to the fact it doesn't let one search multiple times in a row)

2) a arrow that takes one to the bottom of the page and an arrow that takes one to the top (as forums posts can get long, and scrolling isn't fast enough)

to 1) forum web admin should integrate "google custom search", too. Not to repalce existing search but as an addition. This is easy task to do. I did it on my phpbb forum onmy own. +1 because lots of ppl are more familar with google search

[golden rule]

Also something like this needs to be stated as a golden rule:

Don't ask for ETAs

Why? Well the developers are always at work creating updates and when you ask for an ETA, you're really taking time away from their busy schedule just to answer your questions. This is how it's done for other firmware and ROMs (e.g. custom Android ROMs). Why not be polite and follow these rules for Magic Lantern, too? Dev teams get annoyed when people ask for an ETA.

How about something like this to be added on 1st page as introduction:

Code Select Expand


/*
* Be aware that your warranty may be void if installing Magic Lantern to your camera.
*
* By installing Magic Lantern you agree that no one can be held responsible for bricked devices, dead SD cards or
* you fired from a job because some bug appeared and you weren't able to do the job. Please
* do some research if you have any concerns about features included in this firmware
* before installing it! YOU are choosing to install it and take the responsability for what you do.
*/

Great. I updated my sheet accordingly.

Yup, have seen that. Will have an eye for that. maybe you can help me a little bit. After reading through http://www.magiclantern.fm/forum/index.php?topic=11080.0 I think I need an overview of what's working, what's not and what needs to be backported and so on. Looks like lots of people of older camera models are missing features and so on. But I for myself need to focus first on 6D. So I put up a public spreadsheet where 6D owners can contribute. Once I hold the camera in my hands I can do my own tests and contribute to ML code where I am capable of doing so. Yes, i know the issues page on bitbucket for 6D. But that's only one side of the issues reported. when looking to TL issue tracker that's not the way I want to start cause ppl seem to be reporting here and there and I have no clue if ML issues are up2date.

here's the link:
https://docs.google.com/spreadsheets/d/1esD8gjphQh3_Y1wnJoUXikMXgY0fNvxIy909_Cf9EM8

sorry I needed to set it this way up. I want to have an overview as reading though all topics and comments I feel like being lost and I bet once holding camera in my hands I won't find all missing feature / bug myself cause my priorities are stills shooting and I come from Nikon. Never hold a canon before in my hands so where to know what's bugged or missing...

Congrats with you purchase!
You won't regret

Thank you very much. I hope so! I believe you guys won't regret, too 

Yup, just did it and happy over here. Ordered a brand new 6D 24-105 kit  Got tired of searching the whole internet for a suitable price but now got german stock (no grey import). Hopefully all goes fine and next week i am in for the game...

I think we need CreateMemorySuite and DeleteMemorySuite before creating a pull request.

reateMemorySuite and DeleteMemorySuite already exist:
https://bitbucket.org/hudson/magic-lantern/src/c62e719cc9d54c6e801e5e1d97f880cfa9ad8d8f/platform/6D.113/stubs.S?at=unified


Just those missing that I discovered and posted here....

@pittivale thx for posting results
@Levas at least we can now be rest assured that my posted stubs are all ok and future srm related findings will work, too. If in any case new stubs need to be added in future then you can drop me a msg and I will post 'em for you. Now i think it's time to commit the stubs to the repository so that they are merged into nightlies. If anyone can do this I would be grateful...

@all: as I am new to all this ML stuff and coming from android: I was able to use zram as kind of swapping to boost android roms and compress stuff into RAM. Could something like that be done for ML or am I pingpong'ing my brain too much about that? Such techniques would increase cpu load but offer around twice the amount of data to be compressed into RAM and as RAM (in our case here SRM, right?) is speedy enough this could definitiley increase continuous recording times. Could be worth a try but I don't know if zram modules could be adopted to ML OS...

As far as I can tell we should also be able to use SRM for photo mode, too? Let's say increase burst rate and therefore fps?

[On 5D3, you get 163 + 3x39 in normal mode, and 127 + 4x39 in factory mode. No difference.]

Some quick tests on 5D3 123, first outside LiveView, second in LV:


On 5D3, you get 163 + 3x39 in normal mode, and 127 + 4x39 in factory mode. No difference.

@Levas look at page1. a1ex posted values for 5dmk3 and also later some comment for 5dmk3 (bolded above). Looks like 6D is simpy the same. No difference!
Seems like 7D / 600D and maybe others will be winners regarding usefulness of using SRM for mlv recording...

Reformatted the card in camera (canon menu, with ML being restored) and checked the free memory.

Same totals.

Video mode
Shoot total 151MB and SRM total 3x34MB.

Photo mode 255MB and SRM total 4x34MB.

Also memory hack and extra mem hack in the raw-video menu didn't make any difference 

And shoot multiple clips with it, all the same recording length, same length as in older versions...
1792 x 750, 25P = 13/14 seconds of video (which is what too expect with 151MB+3x34MB)
Expect to have about 18 seconds of video(1792x750,25P) if you have 255MB shoot total and 3x34MB SRM available.

Thx for providing feedback.

[If you dont reformat you wont see it because it is already created.]

Also reformat card from camera for both test and see if mlv_rec allocates the 154MB before first recording. If you dont reformat you wont see it because it is already created.

@Levas please confirm...