Messages

Sorry, I did not mention it. It was LV mode, not  photo mode. That's why I wrote it set 30"on the camera (small lcd at the top), while showing correct time on the screen (global draw). The correct time for the exposure should have been around 1/30 s. The av mode photo was correctly exposed.

I see some problems with Auto-ETTR for taking photos in unified 27 June and 28 June builds at least. In M mode starting ETTR sets time to 30", although the time shown on the screen is different. If I try to take a photo it really tries to expose it for 30 seconds... In AV mode it works OK.

Aligned + 64K clusters is giving me the best speeds.. expect a 1-2mb cut from formatting in camera to 32k clusters. At least on 64GB cards.

I reformatted the card:

diskpart
list disk
select disk [...] <- I chose the disk with 29GB, same order as in diskmgmt.msc
clean
create partition primary align=4096

Then format in explorer - fat32, 64kb, quick.

To check:
wmic partition get BlockSize, StartingOffset, Name, Index
StartingOffset divided by BlockSize should be a multiple of 4096 I think? (I got 8192)
Was the procedure alright?

The result with the same options as the previous test:
2186, 2027, 1506

Generally it was about 2000 frames. Much more than 1000 with a genuine format. BTW, reformatting the card in camera removes the alignment.

I forgot to mention - all tests were done with 27 june unified build.

[No format]

@akumiszcza thank you for your continued detailed bug reports - how did it work with a card format?

This is I who should thank you, and others, for wonderful new builds of ML!

As for formatting, it makes wonders!

Settings: quality jpeg L, small hacks on, global draw off, auto ettr always on, 1920x1080 @ 23.976 at x5

Everywhere below these are numbers of frames before a frame is skipped. Started right after turning on - no video recorded before. Second and third trial done immediately after frame skipped.

No format (card taken out of box and put into camera): 1060 frames, 1123, 1017
In camera format (keep ML): 1497, 1878, 1898!

1000-1100 vs almost 1900 is a hell of a difference. And the format takes seconds, so it's a "quick format", not erasing each byte on the card.

Speed during recording: 81.7 MB/s.


I didn't try formatting the card in card reader yet.

[Footer format mismatch]

I just got my KomputerBay 32GB 1000x today and tested it on the newest build - magiclantern-2013Jun27.50D.109.go.unified.b77a85f7ac68.zip

I did not format the card, just copied everything and updated firmware. Things I've noticed:

1. Benchmark test failed at first. It went through till 5/10 and then froze. Even after turning off the camera the test was still appearing.
2. Later benchmark showed:

3. 1584x1058 @ 23.952 at 1x - continuous, 1920x1080 @ 23.952  at 5x - about 600 frames (I did not change RAW to JPEG and probably some other options were not set properly though).
4. When I half-pressed shutter during 5x zoom (for IS to work) the screen turned pink again from gray (the option in movie menu to automatically half-press shutter does not work BTW).
5. While previewing the raw movie I got Footer format mismatch, but the preview worked.
6. When I chose lower resolution for 5x mode (1700-something 16:9) which was continuous on my card, the recording stopped after about 100 frames or so twice. Other tests with the same settings worked OK. Some random thing. The buffers went straight to almost full in a second or so.
7. A file was split in two even though it was very small one - RAW is 78.5MB, R00 is 103.7MB.

In the new build I see speeds required 10x as they should be - 270 MB/s instead of 27 for instance.

1. While silent pics are turned on, if you open live view and press af-on to get autofocus, the silent pics (burst in this case) is started. All dngs are blank of course, as the mirror is in wrong position.
2. Trying to shoot raw video while in double-zoomed mode (x10?) results in bad blocks, even first frame is bad (at least for mlmod-2013Jun21.50D.109.go.unified.9f26e15d9146.zip).

I got 4 crash dumps with mlmod-2013Jun21.50D.109.go.unified.9f26e15d9146.zip build. It was during filming in raw and pressing arrows on joystick to check if changing aperture works.

CRASH00.LOG
ASSERT: IsChunkSignature( hPos )
at PackMemory\PackMem.c:987, task RscMgr
lv:0 mode:3


Magic Lantern version : 2013Jun21.50D.109.go.unified.9f26e15d9146
Mercurial changeset   : 9f26e15d9146+ (unified) tip
Built on 2013-06-21 18:24:10 by [email protected].
Free Memory  : 284K + 3449K

CRASH01.LOG
ASSERT: IsSuiteSignature( hSuite )
at PackMemory\PackMem.c:986, task RscMgr
lv:0 mode:3


Magic Lantern version : 2013Jun21.50D.109.go.unified.9f26e15d9146
Mercurial changeset   : 9f26e15d9146+ (unified) tip
Built on 2013-06-21 18:24:10 by [email protected].
Free Memory  : 284K + 3454K

CRASH02.LOG
ASSERT: IsSuiteSignature( hSuite )
at PackMemory\PackMem.c:986, task RscMgr
lv:0 mode:3


Magic Lantern version : 2013Jun21.50D.109.go.unified.9f26e15d9146
Mercurial changeset   : 9f26e15d9146+ (unified) tip
Built on 2013-06-21 18:24:10 by [email protected].
Free Memory  : 284K + 3458K

CRASH03.LOG
ASSERT: IsSuiteSignature( hSuite )
at PackMemory\PackMem.c:986, task RscMgr
lv:0 mode:3


Magic Lantern version : 2013Jun21.50D.109.go.unified.9f26e15d9146
Mercurial changeset   : 9f26e15d9146+ (unified) tip
Built on 2013-06-21 18:24:10 by [email protected].
Free Memory  : 284K + 3463K

I've tested the latest builds here (fast-raw test build from yesterday) especially for auto-ettr, as my card is too slow to make serious raw video tests (although I like the fact that when I see the speed in green while choosing the resolution, it really does not lose frames).

1. In Liveview M mode it works quite well. It changes both ISO and time, the aperture is constant.
2. Sometimes when I do a photo after Auto-ETTR (in liveview M) it is greatly underexposed. If I reset configuration and set everything again, it goes back to normal. Weird.
3. In Liveview Av mode it seems to not change ISO, just +/- EV. I guess it's +/- 2 EV max then.
4. In photo mode the double half-shutter and set key options open liveview for a moment, then ML does Auto-ETTR, and photo mode comes back.
5. Sometimes this Auto-ETTR in photo mode takes a long time, and sometimes it's very quick.
6. Sometimes it's hard to trigger double haf-shutter, I need to click half shutter multiple times (it seems it doesn't work fine if the camera starts autofocusing in the meantime).
7. Autosnap and full-time Auto-ETTR seem to not work in photo mode. As I understand, autosnap should trigger another photo itself and the full-time mode should trigger Auto-ETTR after one takes an underexposed photo. Both things do not happen on my camera.

My first tests of 50D raw video:

Photos, I mean videos , taken with Canon 100-400 LIS lens. I had only a Sandisk 30MB/s card, so the resolution was about 1200x600 (I tested several of them). It's nice to be able to process 14-bit dng files.

I used @GregoryOfManhatten's 28 may build. The new 8 June build is especially interesting to me for Auto-ETTR and silent pics functions.

Several questions if I may:
1. How to turn off Live view mode in raw video? Pressing live view again stops it only, turning off camera deletes all settings.
2. Is it possible for ML to remember raw video settings?
3. Was anybody able to use Auto-ETTR of the new build in photo mode? It worked for me (more less) in Live view mode only.