I am getting see loss of exposure control with the June 16 version. The live screen show a pink cast and it seems like exposure that was set before entering mode goes away. Not sure the dynamic range is still there. I do have camera set at Cinestyle mode, so that could be an issue.

June 19 NB still got problematic crop modes. 1x are ok.

Received the Komputerbay 1000x 64GB card yesterday. Got a "functionally" stable 1880x864 today using the June 16th build on the 5D2. The key for us was to turn off sync beep.

At that resolution and 23.976 fps we recorded 16GB before we got bored and stopped. :) ML benchmarks the card as more than fast enough to handle 1080p. In our test, the buffer was growing at a very slow rate, so the firmware won't do that rate forever on our camera. Hopefully, the new buffering strategy will deliver that last bit of performance.

FWIW, the Komputerbay card is available for just over $100.A great price for such a large, fast card!

Next week, I'll receive a Hoodman USB 3.0 reader. I'm hoping to eventually be able to transcode directly from the card to a RAID 1 or RAID 5 hard drive setup near real time. That would make a two or three CF card setup "wrangleable" with little to no downtime.

FWIW, 1880x864 @ 23.796 fps at two bytes per pixel is 78 Mbps (68.2 Mbps if it does bit packing with its 14-bit words.) That's over 13 minutes of shooting per card. That's not unlike shooting 3-perf film with 1,000 ft magazines.

(Sure, you don't have to backup your magazines to hard drives and film has way more resolution than ML RAW, but you don't have to buy ever more film stock or process your bits with chemicals either...)

You mean 78MB/s not Mb/s.

Trouble is though you still need to get up to around 2.3k/2.4k of bayer pixels to achieve HD resolution and that means around 70% more data than your recording at the moment. 1880x864 of raw bayer data falls well short of HD.

Yes. Big "B".

And you're absolutely right about the effective resolution of a Bayer signal being lower than the physical resolution. That said, I believe that the 5D2 delivers its h.264 signal from less than 1920x1080 photosites anyway. Shooting a similar number of pixels, preserving the full bit depth, avoiding the codec pre-filtering, and avoiding the DCT coding is all to the good. :)

Personally, I'm not a big resolution seeker. Don't get me wrong. I like the ability to shoot more clear detail, but I'm more into bit depth, dynamic range, nice grading, and good grain texture than the really fine stuff. There are a lot of great looking older films and photos our there that aren't particularly sharp. However, if I shot documentaries and nature footage, I'd be all over high resolution!

BTW, taking a close look at low ISO 5D2 RAW crop footage graded to ridiculous extremes, the grain looks amazingly good and filmic. As it falls apart at the limits, it does so gracefully. I think that's due to the high bit depth. Rather than the noise being on or off, blocky, and splotchy, it has a smoothness and grace about it that one doesn't usually associate with digital video. (This was with DNG processing in After Effects.)

Yes, I'd like more resolution, but getting this value out of my five year old camera is amazing. :)

You mean 78MB/s not Mb/s.

Trouble is though you still need to get up to around 2.3k/2.4k of bayer pixels to achieve HD resolution and that means around 70% more data than your recording at the moment. 1880x864 of raw bayer data falls well short of HD.

Does'nt matter if your competing image is coming out of same box (5d2). if you can grade and uprez to a much more pleasing image, you are ahead of the game.

Ok, for those with a 5D2 using NB after jun 16th and are having problems in crop mode, specifically pinkish cast image with low black levels.

a.d. has made a new fix which you can download here: https://bitbucket.org/a_d_/laboratory/wiki/Home

I tested this repeatedly in several resolutions in crop mode and pink cast is gone.

Take note that this fix will cause some "bad pixel" problems in SOME cameras in raw video mode. Like this one;

RAW recording 5D2 recent NB produces 'bad pixels' (not with .H264 output) (http://www.magiclantern.fm/forum/index.php?topic=6426.0)

This does not show up when using h264 video.

My camera however don't have bad pixel issues with raw video so I use the fix provided by a.d.

With build dated Jun 27, ML developers have made significant progress allocating memory and increasing significantly the recording duration for RAW video.

On the 5D mkII new higher resolutions are now capable of recording continuously with a 1000x cf card. Performance have also improved on slower cards such as 600X.

Below are test results based on a 1000x lexar. FPS=23.976

At 1X

Resolution-------Number of frames

1872 x 1054-------1058
1872 x 1012-------4686
1872 x 936--------continuous
1872 x 850--------continuous
1856 x 1044-------2378
1856 x 928--------continuous
1728 x 972--------continuous
1472 x 1104-------continuous

Crop Mode 3X (5x magnify)

2144 x 1076-------371
2144 x 1072-------370
2144 x 974--------947
1920 x 1076-------1326
1856 x 1044-------continuous
1728 x 972---------continuous

..

I know they're probably wanting to get things to a certain point before they branch out to different models. But is there some insider talk on how this might work with some of the crop sensor range?
Just curious if they've tried it for even a moment.

Murray,

Most crop sensors that can run ML can do Raw video though limited. What particular models are you interested in, I'll try to retrieve some information from ML and transfer it here.

EDIT:

Among the crop sensor canons, the old 50D is performing well, I saw testers getting 1584x1058 and 1584x894 continuous and recording 2000х1080 in crop mode.

Cheers Ted

I've got a 60D myself. I can think of a few 7D owners who'd be curious too (it's also interesting to see if its weird architecture throws up any more problems for them in this area)

There is some progress with the 60D.

The 7D is in more dire straits due to the dual digic. Its running in alpha ML but sadly no raw video.

I myself have a 7D and as days goes by I'm thinking of letting it go or giving it to my son. :)

For 5D2 users looking at how the 30P recording has improved with jun 27 "small hacks" build.

Resolutions --No of frames@30P
1872 x 1054 --237
1872 x 1012 --312
1872 x 936 ---460
1872 x 850 ---770
1856 x 1044 --287
1856 x 928 ---489
1728 x 972 ---650
1728 x 864 ---3338
1472 x 1104 --701
1472 x 828 ---continuous
1600 x 900 ---continuous

Crop mode 3x
2144 x 1076 --132
2144 x 1072 --158
2144 x 974 ---213
1920 x 1076 --235
1856 x 1044 --294
1728 x 972 ---476
1600 x 900 ---continuous
1472 x 828 ---continuous


The highest res for continuous recording has indeed increased. Previous NB it was only at 1472x828 for 30P Now its at 1600x900.

Magic Lantern Improves 5D Mark III Dynamic Range to 14 Stops

5DMk3 : Video
7D : Stills only

Dual ISO - massive dynamic range improvement for 5D3 and 7D (http://www.magiclantern.fm/forum/index.php?topic=7139.0)

Just want to update 5D mkII users that for now DO NOT USE a128gig 1000x or 1050x UDMA7 CF card for Magic Lantern.

Tests I have been doing with techsupport from Komputerbay shows us that the 5DmkII

can accept the fast cards ONLY WHEN USING CANON FIRMWARE and for shooting stills and H264 .MOV files.

BUT the card CANNOT BE USE TO UPDATE FIRMWARE, even the firmware from Canon can't be "seen" by the 5D mkII

also MAGIC LANTERN FIRMWARE CANNOT BE "SEEN" BY THE 5dMKII, even if you use EOScard to make it bootable.

So far we are doing the tests using Komputerbay 128 gig 1000x and 1050x cf cards,

If you are using a 128 gig on the mkII + Magic Lantern please share if its 1000x or less, also if its UDMA7 or less.

Magic Lantern Improves 5D Mark III Dynamic Range to 14 Stops

5DMk3 : Video
7D : Stills only

Dual ISO - massive dynamic range improvement for 5D3 and 7D (http://www.magiclantern.fm/forum/index.php?topic=7139.0)

New update:

Dual ISO module has been ported to the 5DmkII. Photo mode.

Nice ! Thanks for the update
J

7D now recording RAW video continuously no longer in bursts. :)

Testing first versions of raw_rec module now.