Messages

wait, you tell me that the side view (top right) isnt photoshopped and the wheel removed?
where is the metallic belt hook?

this is improper behavior.

right, and this is known as a general ML issue.
there might be a fix for this somwhen, when we know how to deal with that.
(its about digic registers)

hahaha what a mean fake

@Lopo:

the canon firmware we linked is just a link to canon download site, its the original firmware from original download servers.

we cannot simply improve quality by using the second digic. both are used for different things.
this doesnt simply allow us to somehow improve picture quality.

frame rates, as already stated in some other thread, are not patchable yet, and even if we could patch,
i don't expect more fps than any other camera can do. maybe 5 or 10 fps more. not sure. thats just a guess.


WB, yes - thats feature request. maybe some hotkey to smoothly alter WB towards current scene.

I would like to know , when revisit the photos been made, and you press the Picture Style button, vectorscop can be expanded to cover the entire screen with histogram and waveform in both corners,

can you please put that in the "Feature Requests" forum?
its not 7D-related, this would be a ML base feature.

copy it on all the cards you use (autoexec.bin and ML folder)

a) what functions are and are not (partially/fully) implemented in the current release
b) a list of issues that have been identified and acknowledged to date. (Hopefully updated regularly)

a) there is a list of functions and the problems they cause at http://magiclantern.wikia.com/wiki/7D_support
b) this thread is for identifying and documenting problems. some get fixed instantly, others will follow. there is no separate bugtracker.

Thank you g3gg0 , for me is wok good, i'm juste start the test in my 7D, take some picture and put after in the forum HDR .

you're welcome. thanks for contributing

the camera can't check this battery...@@  all battery
The camera may be a problem
"Cannot communicate with battery use this battery?"

did i understand that correctly?
a) you tried more than just one battery?
b) camera tells you always (with every battery) that it could not comm. when you try to fw upgrade?
c) when you open "battery info" page it also tells you some error? (screenshot pls)
d) did you check your battery contact? (see photo below)

and please say yes/no for every single point to prevent confusion

[not]

sorry, that there are people who dont know how to behave well in forums.
if you follow this thread, you will see that we indeed accept feedback that is not offending.

short howto:
BAD: saying this is a "pre-matured", "watered down" release and we should "write code instead of posting"
reason: destructive criticism, condescending "you do what i say - i have the money" (srsly, wtf?)

GOOD: well, nearly any other way of telling that you expected feature XY to be implemented.

but:
thanks to all the others who replied here, telling us what we have to know for the next releases. keep that going!
even if we didn't answer directly to your posts, we read them all and think/talk about how to fix issues that were found.
(this is perhaps your post left no open questions to ask )

so lets continue this discussion.
thanks.

use Original battery

thanks for the video, its perfect and you are doing it right.
so i think, the (required) 2.0.3 canon firmware detects your battery as faulty or thinks its not original.
can you check what the battery info screen says?
or can you check contacts?

Provide a bit of context please, we are not magician yet .... 

nooooooooooo
not "a bit", but at least 200 characters

Nope, no dowload for me!   

This is the link I have used: http://bitbucket.org/hudson/magic-lantern/downloads/magiclantern-7D.203.Alpha1.zip

I will ask our administrators. It seems to be a local problem. Thanks again!

it looks like bitbucket.org is forbidden in your network or some nameserver issue. whatever.
temporary workaround:
http://upload.g3gg0.de/pub_files/555516d18b253314d5255e24b48e9eba/magiclantern-7D_203_Alpha1%5B1%5D.zip

edit:
hehe, alex was faster. but in case dropbox is forbidden too (as here in my network)

Hello, just for your information, the download link for the alpha seems to be broken!

thanks, but just checked the DL link, seems to work fine.
and according to DL counter (>3k) it never disappeared.
try to use the DL link without the S in HTTPS maybe its your proxy/browser?

[ISO noise:]

I've never posted on a forum lime this before...

First off, you guys rock. For someone who knows nothing about what you guys do, to me you seem like magicians. Filming on DSLRs is how I make a living, and I will definitely be donating.

My results:
-I have used a 3rd party photix battery successfully when fully charged
-I'm noticing that focus peaking does not work as well at high ISOs, I'm guessing it's picking up the noise as being in focus
-When in the ML menu, pressing the (-) button exits the menu, that's nice, but pressing the (+) button create a strange hybrid of the ML menu and the LV images where only the currently selected ML menu item is overlaying the screen
-When i turn on 16x9 crop so it blacks out the bottom of the screen where the waveform and histograms are, it every-so-often switches back and forth to blue and then black


g3gg0---would it be within your magical powers to enable FULL 1080p HD clean out on this or any camera (if not 7d then what about the 5DMK3?) TO be useful to most of us, it would need to be without sacrificing resolution. If its not possible, what about an improved codec for recording? Maybe mimic the All-I flavor of h.264 available on some of the newer cameras? Any of these would make Magic Lantern not just useful, but a necessity for anyone serious about filming at a professional level. A lot of broadcast acquisition standards mandate a MINIMUM of 50mbps acquisition codec. If you can push the cameras above that limit, it would be a big deal.

It would be worth charging $50 just for that feature. People would buy. Not saying that's how you guys roll, but you could....considering the feature would be most useful to professionals making money from these cameras and maybe some of the most serious basement filmmakers.

thanks for your feedback.
ISO noise: yes, this might be. will check it. tried to change focus peaking to mode (via Q)? maybe it helps in that situation
ML menu: maybe thats the menu feature where you can change the option using scroll wheel. if so, thats intended. i will check that when im at home.
Blue blinking: Known, alex called this "a feature" its okay, dont let you confuse by that.
All-I: could be possible. will be checked as soon MovRecState is being investigated.
other codecs: no. codec is a hardware implementation
FULL HDMI:
answered before and this applies to any camera:

please understand that the resolution still is limited to 1620x1080 and thats not easy to defeat.

YES ! i think this is what I expect from the HDMI.... NO red button.... THANK YOU ! was it hard to code ?
or you just had to bypass the REC red dot paint code-lines ?

i permanently disable overlay painting engine using canons developer commands.
this has some downsides, but together with alex we found a much cleaner solution by making the palette just transparent.
its not tested fully yet, but should have far fewer side effects.

what kind of thing is limiting the resolution ? (somthing is DOWNSCALING the video  to the HDMI port ? DISABLE IT !  )

i've already answered that even before you asked

please understand that the resolution still is limited to 1620x1080 and thats not easy to defeat.

and if it were that easy, believe me - i would have "disabled" that feature.
(btw its not just about disabling a feature, but to reconfigure all the undocumented DIGiC hardware registers)

what is the meaning "canon menus crash" ? can it be fix by or recover by a simple operation ? , then its worth the crashing...
no need to rec to cards ....

fixed by restarting the camera after removing battery

BTW ! mabey a stupied question : if i dont press record , and there is no recording , after 2-3 min in LIVE VIEW the camera shout off.. right ?
so i cant really record from the hdmi port without recoring to a cf card.....
mabey you can DISABLE IT ? i mean.. no auto-power-off... it will keep output video untill i turn off the camera ?....

i will have a look into that issue. maybe i find some way to do that.
but for now i think its ok to record on CF - what are the advantages you would see with that feature?

@video guys

http://www.youtube.com/watch?v=rnoHwlK3m2c

is this what you expect from clean HDMI?
please understand that the resolution still is limited to 1620x1080 and thats not easy to defeat.
also the method i use to disable paintings is somewhat problematic and will not work stable.
(canon menus might crash afterwards)

I would like to ask about "Focus Peak" feature.
When I turn it on, the "zoom window" still blinking / flashing. Is that normal?

i dont get what you mean.
in LV you have zoom permanently enabled and then enable focus peaking?
please describe exactly what you pressed and what is configured.

thanks

Same problem here, dont have a cardreader, any help!

are you sure, you are prepared for a firmware hack named Magic Lantern for >1k€ devices
if you don't even have a card reader and ask for help *here*?!
sorry, but thats a bit weird...

btw, this version was downloaded more that 2k times now

As an unwritten rule, ML uses 4 spaces soft-tab indenting (except for Makefiles), so no real tab characters. Remove any trailing white-spaces if you find any

basically true, but i would not mix that with code changes in one commit, as it will make merging harder.

nice changes!

btw i recommend *not* to alter that spaces in blank lines.
some text editors treat it this, others the other way.

so we would change it forth and back all the time
and this makes the patches unreadable.

you cann 'rollback' the last commit you made to your local repository.
if that doesnt work anymore, just commit the reverted file afterwards.

I really desired to shoot some seconds of the scene, will be possible in future?  should be great!

the display also says "press start" or "rec", so just do it
(at least on 600D and 7D)

#define TG_FREQ_BASE 24000000 will fix it

true. updated it in the timer table but not in source.
thanks for pointing out.

when ML menu is opening, it is first opening some canon menu (usually you get "my menu") before ML menu will appear.
this is because of the canon menu will disable all other paint events - and ML menu doesnt have to care about being overwritten
by all the canon stuff like metering bar and battery.

so this is intended behavior.

is it constant only using magic lantern?

ML should not change anything in bitrates yet.
you can easily confirm that by not loading ML and checking the result.