Messages

95+20 is smaller than 120 if I'm not mistaken...

(that's the theoretical speed, according to benchmarks)

Doesn't the 650D already have manual audio controls in Canon menu?!

are you sure? that changeset only draws zebra less often...

edit: I recommend disabling everything from features.h, maybe some things from internals.h, until you isolate the problem. You can also prevent certain tasks from starting, in boot-hack.c.

You shouldn't disable asserts in cases like this. If you do that, you are only hiding the error instead of solving it (it's like treating the symptom and not the cause), and you don't even understand what's going on.

This practice is dangerous and sooner or later it may brick the camera. Seriously.

Good morning... bug reports with versions from one month ago are not accepted

Raw zebras are CPU intensive. Before you had YUV zebras with zero cpu. Just turn them off while recording.

I've fixed a similar FPS problem on 5D3 a few days ago.

@JulianH: you said FPS override is too complex. There is a beginner mode and an advanced mode, use the one corresponding to your skill level

You don't have to use the advanced mode

Also, can you check for cpu usage when FPS override is on? Exact FPS does a bit of searching through all these timer combinations, so there may be surprises.

Global draw is vague, there are a ton of overlays under it...

I can no longer reproduce the issue, all these resolutions are clean for me.

Is it worth the extra hassle (programming complexity + workflow) for a 20% improvement in write speed?

Can't really help with that, this is how ML looks in movie mode on all cameras. You can try a custom cropmark.

Of course.

"Would be nice to ..."

What's the problem? An error message doesn't start with "would be nice"

In photo mode, raw histogram is adjusted to match the CR2 one. When recording raw, this can have severe side effects on the video exposure (white level will be wrong).

Therefore, I'm restrincting raw recording to movie mode.

You must enable it. In photo mode, most the raw stuff (white levels, histogram) behaves differently, it's optimized for getting a histogram that matches the CR2 pictures. For raw video, this can cause severe exposure issues.

In photo mode, you are not even getting the exposure values from menu (not even in expo override mode), you are just getting something with equivalent brightness (ExpSim). And white level on the raw files recorded in photo mode will be wrong.

See here: http://www.magiclantern.fm/forum/index.php?topic=6215

I'll restrict raw video to movie mode to avoid this kind of mistakes. The raw backend does behave differently in photo liveview, because... I'm assumming you are taking pictures in photo mode, not videos.

That happens if you ask for some exposure parameters that are out of range (usually if you have FPS override on, which limits shutter speeds a lot).

And... you are in photo mode.

What exposure warning message?!

You have full manual exposure, right?

No, but you are welcome to implement it

It probably is, but we have no idea how to do it.

I did not say 90.000

No, it's not. H.264 happens on a dedicated chip, 14-12 conversion from the other thread is done on the ARM CPU.

In raw, 200 is identical to 160, 400 is identical to 320 and so on. Look on the histogram.

Also note that 10/12 bit is not going to work at FullHD resolutions, unless you overclock the CPU by a factor of 2 or 3.

Well, the AF-ON is technically impossible to implemement reliably (if you compile from the official repo you won't find that there), and joystick... it's for centering the focus box.

I prefer portable code, and for now, LiveView button is the only portable solution, because almost all other cameras are using it for normal H.264 recording (except 50D). The idea behind modules was that they should be portable, same binary working on all cameras.

Also, a.d. should point out the differences between his builds the and main repo.

1. what if you want to focus on the bigger image?

2. that's why I still recommend the LiveView button (all these top buttons send the same code)