Messages

I bet you won't see reproduceable differences. I you have time you may prove me wrong.

Delete ML directory, FIR file and Autoexec.bin.
Copy extracted nightly build contents to card.
Startup cam.

Confirmed,
I can trigger e.g. dim display by pressing info, however can't trigger it by lcd sensor.

Thanks! Bug report: https://bitbucket.org/hudson/magic-lantern/issue/2218/option-use-lcd-sensor-on-not-enforcing

Small bug in Powersave options?

Prefs tab -> Powersave in LiveView -> Use LCD Sensor ON
doesn't work for me. It should force selected powersave options if triggered but won't.
Someone out there able to confirm this bug?

You may want to press trashcan button.

I suppose you're using "Frames autodetect". Turn it off and select the number you want to use.

https://builds.magiclantern.fm/#/features
7D column:
- No mark on HEADPHONE_MONITORING but a mark on HEADPHONE_OUTPUT_VOLUME?
Robot error?

I told you the math before. Okay, here we go again:
1920 x 1080 x 60 x 14 / 8 = 217 728 000 Byte/s -> 207,7 MByte/s

- There is no such CF-card and never will be one.
- UDMA 7 is specified for 167 MByte/s
It simply won't work for continuous recording.

Benchmark test runs by DeafEyeJedi (and others): http://www.magiclantern.fm/forum/index.php?topic=12630.msg133459#msg133459

Sorry, but I was occupied with some other issues.
About temperature: That's a design flaw and 7D is not the only DSLR affected.

Still unable to reproduce your crashes. Will retry this week.

Please tell me which steps works for you to force crashes.

Where is the contradiction? One is bandwidth needed for a specific settting (resolution/frame rate). Another one is bandwidth provided by 5D3's SD-card interface.
One is the condition you need, another one is the condition you are able to use.

And topic is about CF-cards ...

You will have a hard time trying to connect SD-cards into CF-card slots ...
http://cpn.canon-europe.com/files/education/infobank/digital_image_file/cfsd-cards.jpg

And don't think about using a SD-to-CF adapter. They are out there but they don't provide fast data transfer rates.

I was about to read you the Riot Act, IT support version.
Rule 1 in data recovery: You don't write anything to the media you are trying to restore!
And it doesn't matter how small the file is. It's like dancing pogo in a mine field.

And formatting the very data storage you want to save is out of question. Period.

Now go on and try to update your other cardreaders firmware (if any).

Sorry, I won't try to fight legal stuff and economics with reason.

You're wrong about the main reason for this limitation. It's connected to the price tag because video cameras will be taxed in a different (more expensive) way. And  everything able to record up to 30 minutes is not a video camera by definition.
http://www.dpreview.com/articles/0794343949/wto-looking-at-moves-to-remove-30-minute-limit-from-digital-cameras

http://www.magiclantern.fm/forum/index.php?topic=13597.msg131347#msg131347

Is it really that hard to understand that 5d3's SD-card interface is limited to 21 MByte/s write speed?

RAW recording is easy to calculate. Just look at the numbers ML will give you at the bottom line:
Horizontal resolution x vertical resolution x frame rate x 14 / 8 = Byte/s
1920 x 1080 x 24 x 14 / 8 = 87 091 200 Byte/s = 83,1 MByte/s

Sorry, unable to give it a try last days. Time consuming tests for +40 GByte MLV recording and seamless recording +23:59:59.

Looks good. +40 GByte recording works with 7D and 650D.

Sorry, but 5D3's SD-card interface is limited to 21 MByte/s, too.
You need the fastest CF-cards available to record 1080p24 continuously.

In other news: Since late January ML is able to record +30 minutes without frames loss/drop at 29:59. You don't even need to set "Movie Restart ON". Just press the button and record as long as you like and battery/card's memory size*/temperature limit allows.

* = Today's build enables MLV recording to exceed 40 GByte.

H.264 is still hampered by hardcoded 29:59 limit and is therefore not able to pass this border without frame loss.

Sorry, 5D3.123 users: Not available for you, yet. Please be patient!
5D3.123 users: You need magiclantern-Nightly.2015Mar16.5D3123 or newer build.

Please do a little more research and look what the other brands have to offer. If you want to dive into video and you have no gear/investment to protect you might find there are real strong players out there.

If you want to understand crop mode you have to understand what Canon does in DSLR video. Here we name it "native" video modes. All cameras (excluded 5D3 and - not confirmed yet - 7D2) will use every third sensor line. All other lines are just skipped. And if you do your math you will find all DSLRs (but 5D3) will not be able to record true 1080p. We call this "native" video resolution = liveview resolution. To surpress aliasing Canon uses some image manipulation. Add some aliasing surpression, noise reduction, blow up to 1080p and add sharpening. And for most cams there is a crappy IPB ratio as well. If you ever wondered why Canon's native DSLR output does not stand that well against some modern cams ... And again: 5D3 is another game.
Now comes ML offering RAW video. It's more or less just grabbing data sent to the display. Therefore you have All-I (= no interpolated/predicted frames), no sharpening, to scaling issues and no sharpening trying to mess with your data. But those frames may have an aliasing problem because lines are skipped. You may add a customized antialiasing filter with some price tag to surpress this.
Now comes electronic zoom as introduced with 600D. Just zoom in when in video mode and you have 3x focal length, virtually. And if you put 3x and 1/3 (=ratio of unskipped to lines in total) together you get 1. As in "frame grabbing" without line skipping. Or in other words: By zooming in (electronic) you change from skipping lines to sensor readout for all lines involved. And aliasing is not that much a concern anymore.

But -as almost everything - it comes with a price. Because it is electronic zoom you can't use all the sensor area but a frame within. As in "crop". Your FOV will be reduced. And if you have aliasing you have to deal with it in post. Because there is no filter available for this mode to put in front of your lens.

And there is another culprit: RAW data means serious data streams. 720p@24fps will be around 38 MByte/s. 550D won't do that for long because it's SD interface is limited to about 21 MByte/s.
7D does better but continuous true 1080p24 is out of question now.

Audio can be recorded in cam with MLV (ML video = ML's video format). If you think you want to go there you may do so.

MLV postprocessing is not that streamlined as - for example - putting NEF into Lightroom. Some people might want to use stronger words here.


Please take your time and make your decision with care. It is not a bed of roses. Or get a 5D3 and some really fast cards.

Back to square one:

What are you trying to do?
You can shoot in 1728x1156 but only for a very limited time or with very low fps.
You can do continuous recording in lower resolutions but this will result in a cropped view. It will be a frame inside Liveview's 1728x1156 frame.
Look at the numbers ML will tell you (text at bottom) if you select horizontal resolution and aspect ratio for any given fps.

Of course there is: 1728x1156.

Yes, it states 1728x1156 is possible but it also states that cam's write speed is limited to about 21 MByte/s so you can't have it for continuous recording.
1728x1156@24 continuous would require an interface with about 80 MByte/s. Numbers don't match -> Go for lower resolutions for continuous recording or shorter durations with higher resolutions.

Sorry, but which question do you want to ask?

- Which is the highest resolution (if non-crop is used) available for continuous recording?
- Which is the highest resolution available if non-crop is used? Nope, not interested in continuous recording
- Which is the highest resolution for a squared frame in non-crop mode?

Let's define "non-crop" = without electronic 3x zoom

Which ML build are you running? I suppose an old one.
Backup your ML directory, delete it and Autoexec.bin from card. Copy extracted latest nightly build content to card. Apply all settings previously used and retry.