Messages

I thought that just causes a lockup and battery drain due to an incomplete shutdown. Pulling the battery fixes it

true, but afaik one person reported that after draining the battery his flash was erased.
could be bad luck, could be a systematic bug in canon firmware.
so its better to avoid that situation

Mov file, so when you open any of the filmed mov file inside any video editing program, the very first frame of the video you see informations displayed instead of what you are filming and rest of mov be stuff that you have filmed.

Basically generate one frame of info that would only overlap the first frame of the video and be recorded into the mov. As I saw image effects is possible so maybe its possible to generate elements that can be recorded into the video.

ah i see. you want to have in the first frame some information about the file itself.
like current exposure time, time/date, lens name/type and such?

I am meaning the first frame inside the video file itself so no extra files.

where do you want to have that image saved?

hi.

we could use the LED output.
see the astrophotography thread here in forum, i built some example circuit you could use for that.
the parts are ~5€ when you order them at e.g. conrad.

but
a) you need some electronics skills and
b) we would have to implement it by hooking HEAD1 interrupt
c) if it works exactly as you need it, is still unsure

btw - is your flash fast enough? are you sure it is not varying in brightness?

hmm 1%, you uploaded a MVI_2369.MOV, remember?
it has one I every 4 frames, QP is about 10

did you follow all steps (exactly) as described in http://wiki.magiclantern.fm/install ?

if not, please do so. every step is important, even if it doesnt look like that.

ouch, that hurts.
thanks for that post, it will help us next time if a similar problem occurs

@oldskoolnj:
please understand that many problems can be solved if the people would read that page with that big fat warnings.
and as alex said, the referred page not a grave of hundreds of posts, but a collection of well-prepared known-issues.
you are encouraged to read that multiple times along with a warning you might brick your camera if you don't.

answering the same questions again and again is quite boring. especially if you do this as hobby.

this is a community - to criticise is absolutely okay if you have a better solution you can come up with.
feel free (!) to contribute by answering the questions and giving 1st level support in the forums to provide a better service.

really cool
is it possible to keep the drive letters #define-able so users would be able to compile custom veriants if they need that.

maybe he means that tips here: http://vimeo.com/26869155

Following my email, the regional Canon support center (France for my country) has called me to explain that what I am seeing "is normal because of the H.264 compression technique used, which uses keyframes when the picture changes significantly and hence a few identical frames are following the keyframe, etc..." (or something very similar)

i just DLed your video and had a closer look at it.

cannot confirm this. that freeze not starting from an I-frame.

last "good frame" is no 178, this is a P-frame. the next frame 179 is also a P-frame is "stuck" and has the same content as 178.
no 180 is an I-frame and 181, 182 and 183 a re P-frames again.

so we have 5 stuck frames based on P178:

P179 I180 P181 P182 P183

good P-frames have here about 90k memory usage, the "stuck" P-frames have about 7-11k and show a lot zero coefficients.
the next good frame (P184) contains mainly "intra" macroblocks (80%) that basically contains image contents.
this means, it is nearly an I-frame (but not tagged so).
the stuck frames starting from 296 are twice as large, but rest is the same.

conclusion:
so it seems, the MPEG encoder itselfs does everything right in terms of encoding. I-frames every 12 frames, P-frames are encoded correctly.
they seem to forget to update the MPEG source data? as they use 3 buffers AFAIR, a simple firmware bug that forgets to update one buffer might *not* be the reason.
maybe thats really in MPEG unit - do they have a 6-frame buffer for motion detection?

no, would not say that ML is mainly for video. the second sentence is absolutely right.
>  video is the domain in which ML proves to be the most useful or improving, in comparison with Canon's firmware

ML is for photo and video, but in video mode, things that ML can do have a lot more impact.
original canon fw has too few configuration possibilities in video mode and the few things ML "adds", bring a huge feature and usability boost.

in photo mode, canon fw is configurable quite good, so ML adds many things that make life easier.
e.g. instant(or quick) zoom to focus point in picture review - the thing i would miss the most.
or low fps mode in liveview when trying to focus infinity (stars) - suddenly the darkest night shows clouds in LV.

and *not* to install ML right before a shooting is a good idea. a very good idea..
in case you cant get it running the first time (e.c. card reader writes crap to card) and your camera wont
boot ML, but just lock up because disk is already boot-flagged, you get in stress really quick

ML alone wont do anything better - you have to know all the features and get used to them.
so just take one sunday afternoon and check what these features do.

here the output of some movie i recorded and analyzed

http://upload.g3gg0.de/pub_files/c4e2826707bdc0c9a88831de35451f28/H264_Parsing.log

and here screenshots of that tool
http://upload.g3gg0.de/pub_files/f82f98bdf0e202cdfd9340f6b557f7ab/shot1.png
http://upload.g3gg0.de/pub_files/0385b3de70e7d74f6055bf25cbb854a8/shot2.png
http://upload.g3gg0.de/pub_files/a55fd128fc03da9103e3b4cf931ea2ab/shot3.png
http://upload.g3gg0.de/pub_files/5c33631de2a773d9378a1462f3307585/shot4.png
http://upload.g3gg0.de/pub_files/cbdd60d7b681909bd41585f481ffdd99/shot5.png

i asked the company thomson if we can get a trial of their tool "AVC analyzer"

http://www.thomson-networks.com/products/monitoring-switching/media-file-analyzer

they sent me a dongle with 100 days evaluation for free
that tool is *really* able to look into every single frame and lets you check all coefficients down to the raw stream.
upload the files you want to compare and i will look at them  (or give you access to my PC or a VM via RDP so you can work with it)

want to access?

there are possibilities.

you can infect the cache to set a jump to your own code at any ROM position. this is working on e.g. 600D.

so you can add a breakpoint anywhere (by placing a "B @myBreakpointFunc") and do some usleep there
until some debugger task that communicates via ptp tells your "breakpoint" to continue and return where it came from.

but what would it help? breakpointing and waiting for user action will for sure raise an ERR70.
this might be useful for debugging ML code - there you dont need cache infection since it runs from RAM anyway.

if someone does the PTP <-> GDB part, i will do the "setBreakpoint" etc functions that require ARM patching etc.

tried all this?
http://www.magiclantern.fm/forum/index.php?topic=2221.0
http://www.magiclantern.fm/forum/index.php?topic=2296.0

thanks.
so basically the same.

my 500D turned into a 600D, but your 5dII will turn into a nikon coolpix. not a good deal if you ask me.

don't click it!

one idea.

are you sure your battery pack didnt cause e.g. a short circuit to the connectors in battery slot?
there are some pads that are responsible for shutter press etc.
so if your half-shutter pin there is short-circuited, the camera is disabling LV for example.
does your camera focus if you half-press your shutter?

maybe there was some electrostatic discharge that caused some electric defect. etc etc.

but that are all just wild guesses.

maybe its smth like that?

http://www.amazon.com/Opteka-Battery-Vertical-Shutter-Batteries/dp/B001HK4LWA

-- removed by author, original post changed --

really amazing.

how many meters above zero did you shoot that?
what lens and f-stops did you use for that?

i think here in germanyat 400m where i am the air is too misty for such a good shot

> If I could only get ML to 7D :/

we are still trying.

[What about ERR20 when taking pictures?]

here: http://wiki.magiclantern.fm/faq

What about ERR20 when taking pictures?

This problem is not related to (or caused by) Magic Lantern.
You will get this error when your shutter mechanism no longer works properly. Contact your Canon service center.
Consider entering your shutter count in the Camera Shutter Life Database.