Messages

In LV it's not needed, because contrast detection is very accurate.

http://www.lensrentals.com/blog/2012/07/autofocus-reality-part-1-center-point-single-shot-accuracy

How to reproduce the audio remote shot issue? On my 5D2 it takes a single picture.

Is the .422 data (silent pics) considered the state of the feed for the h264 encoder?

Yes, this is the input for the H264 encoder. You can alter some data in those buffers and it will show up in the recorded video.

Not possible (look at MZ bars when idle). There's no absolute method for evaluating focus; the current one will do false triggers when there's little or no movement.

Why not trying before asking?!

Any decent audio editor has this.

For example: http://wiki.audacityteam.org/wiki/Nyquist_Effect_Plug-ins#Noise_Gate

5D3 has it, exactly as you describe it.

It's not easy to implement; if it can be done, there will be a lot of flicker when moving one image.

Already done in 2.3 with arrow keys

Fun stuff: the 5D3 has a headphone jack and it's possible to upload music on it and listen while taking pictures

On-topic: audio meters are working, but Canon has them too.

CARD_DRIVE is used in string concatenation at compile time

1%: you need to enable ENGIO messages.

Code Select Expand


[JPCORE] SetEncodeH264Parameter I 1920,1088,1
[JPCORE] SetEncodeH264Parameter P 1920,1088,2


This should be what happens when encoding one frame (5D2): http://pastebin.com/J21HuvLX

I don't think bahlik's issue is the same, because the description is different ("some flickering screen").

I didn't play much with it, but it has an auto setting. Not sure what it does, I didn't read the manual.

Good point about ML on the other type card that you normally use. However, this complicates things a bit, as ML was designed to work with a single card drive, and it would require major code changes (those CARD_DRIVE"path/to/file" constructs would no longer work if CARD_DRIVE is not a constant).

Yes, record the 5x zoom image via HDMI - it's 1:1 crop on all Canon cameras

Here you go: http://en.wikipedia.org/wiki/Quantization_%28signal_processing%29 and http://vcodex.blogspot.com/2009/04/h264-quantization-parameter.html

In all Canon DSLRs, the algorithm is VBR with a max bitrate limit. When this limit is low enough, the bitrate is almost constant in practice, so this combination of settings is labeled as CBR. When this limit is raised, some scenes will not have enough detail to increase the bitrate (in most cases because quantizers are at lowest level, so quality is as high as it can get).

There is hope for MJPEG 422 or clean HDMI out though

You will receive help as long as you do your homework. And you have received help and solved both of your issues, so what's the problem?

The question was serious, it was something already written in bold, as "Very important" or "Important notes", not something thrown "on a page amoungst all the other hundreds of pages". It's something that can't be fixed, so you need to know that when using ML. What should I do to make sure the users read this?

Put the battery door back.

Is FPS override on?

Then, can you explain why we have to say the same things over and over again?

Should they be written in blinking red?

Update error means you should format the card from the camera.

There is an install guide, you need to follow it

Turn off FPS override.

Also, why people don't read bold warnings? The shutdown problem is mentioned 3 times in the install guide, one time in the user guide (under Important Notes) and also here: http://www.magiclantern.fm/bestpractices

It's not the same as in digic 4, it was researched from scratch. I've exposed all the H.264 parameters to Marvin and that's all he could control.

Those are the parameters for ALL-I. Most of them give ERR70 if changed.

Code Select Expand


Transform8x8Flag = 2
Profile = 100
Level = 51
BitRate = 90000000
EntropyCodingMode = 0
IntraPicInitQP = 20
InterPicInitQP = 20
QpOffsetForB = 0
MinQpI = 10
MinQpP = 10
MinQpB = 10
MaxQpI = 51
MaxQpP = 51
MaxQpB = 51
MinBitrate = 0
MaxBitrate = 0
SarWidth = 0
SarHeight = 0
AspectRatioIdc = 1
VideoFmtAndVspFlag = 81
VideoFullRangeFlag = 1
TimingInfoPresentFlag = 0
RateControlEnable = 2
ScalingMatrices = 0
pScalingMatrixAddr[0] = 0
pScalingMatrixAddr[1] = 0
pScalingMatrixAddr[2] = 0
pScalingMatrixAddr[3] = 0
pScalingMatrixAddr[4] = 0
pScalingMatrixAddr[5] = 0


I can change max bitrate and quantizers, but that's all.

Right, so it's practically the same thing as if you would install ML in the camera (from a convenience's point of view).

Zebras and peaking are already working, even fast zebras worked from the first try