5D2 RAW video Builds 14-Bit

[togg]

There are many other benchmark and reviews on this forum. I remember though yesterday when I was searching through, I found a guy who had a 32, 64, and 128 gb card. He did benchmarks for all three. The 32 and the 64 were the same. And the 128gb was significantly slower than the rest.

Here we go: http://www.magiclantern.fm/forum/index.php?topic=5510.25 Its post #49

Thanks a lot. And he was really lucky with his purchase!

[Redrocks]

My 64GB Komputerbay is almost continuous @1.85.

1872 x 1012

5917
6331
5089
reformat
261
6579
5418
5498


1856 x 1004

14000+

[coma]

Komputerbay 64GB 1856 x 1044

2035 frames which is nearly 2 mins

interesting fact: 1880 hack is giving me about 1-2MB/s less in writing speed…

[xNiNELiVES]

My 64GB Komputerbay is almost continuous @1.85.

1872 x 1012

5917
6331
5089
reformat
261
6579
5418
5498


1856 x 1004

14000+

What about 1880 @ 1.85?

[coma]

What about 1880 @ 1.85?

1880 is actually 1872 (camera limit)

[xNiNELiVES]

Komputerbay 64GB 1856 x 1044

2035 frames which is nearly 2 mins

interesting fact: 1880 hack is giving me about 1-2MB/s less in writing speed…

I think it's like that with any higher resolutions... Idk I may be wrong.

[xNiNELiVES]

1880 is actually 1872 (camera limit)

I was wondering that, but why do they offer 1880 over 1872? I feel like the ML team found that the sensor actually doesn't utilize all of the sensor's pixels. For example the sensor is actually 22 mp but it only uses 21 mp, same with other cameras such as the 5d3.

Again I'm just speculating. I have no idea.

[ted ramasola]

I was wondering that, but why do they offer 1880 over 1872? I feel like the ML team found that the sensor actually doesn't utilize all of the sensor's pixels. For example the sensor is actually 22 mp but it only uses 21 mp, same with other cameras such as the 5d3.

Again I'm just speculating. I have no idea.

1880 is not on the official repo and not "endorsed" by a1ex. It is only available in a.d. compile.
Thats the reason why it's an option in menu to switch on and off.

[xNiNELiVES]

1880 is not on the official repo and not "endorsed" by a1ex. It is only available in a.d. compile.
Thats the reason why it's an option in menu to switch on and off.

So what's the point of A.d. adding it in when it's actually 1872? Is that what the dngs come out to when they're extracted?

[ted ramasola]

So what's the point of A.d. adding it in when it's actually 1872? Is that what the dngs come out to when they're extracted?

Its not just 1880 is "actually 1872", a.d added it since its possible, and the dngs is still 1880, but if I understood a1ex correctly (he or a.d. could chime in and correct or add to this), 1872 is more "efficient" to process and determined that 1880 was not efficient to process thus some report to get lower performance than with 1872.  It was explained way back, probably in this thread or in another.

There are some features added by a.d. that sometimes make it to the repo, some don't, like the black borders. My understanding is a1ex found out it "sometimes" causes problems with other users. So whenever he thinks its not efficient in other cameras or models, he doesn't port it to the official repo.

The black borders and 1880 don't cause problems with my camera and card though so I personally use a.d.'s build.

[xNiNELiVES]

Its not just 1880 is "actually 1872", a.d added it since its possible, and the dngs is still 1880, but if I understood a1ex correctly (he or a.d. could chime in and correct or add to this), 1872 is more "efficient" to process and determined that 1880 was not efficient to process thus some report to get lower performance than with 1872.  It was explained way back, probably in this thread or in another.

There are some features added by a.d. that sometimes make it to the repo, some don't, like the black borders. My understanding is a1ex found out it "sometimes" causes problems with other users. So whenever he thinks its not efficient in other cameras or models, he doesn't port it to the official repo.

The black borders and 1880 don't cause problems with my camera and card though so I personally use a.d.'s build.

Oh ok. Well I like these individual features and I rather have 8 more pixels. I'll stick with ad too. Nothing against a1ex or anything.

[reddeercity]

I have getting a few corrupted frame in the Crop Mode. 
I'm on the July 11th Built, With the new raw2dng for PC
Frame size 2048x930 23.976p , recorded for 5700 frame  on Lexar 1000x 64GB card
Used Canon 70-200 @ 200 with 2x extender = 400 mm
in crop mode should = 1200 mm
no problems recording continuous

001467 by davidmiazga1, on Flickr



001637 by davidmiazga1, on Flickr



Edit: Fix Photo Links

Image 200 frame apart

[ted ramasola]

your attached images are not showing.

[xNiNELiVES]

I second this.

[dariSSight]

Why can't the Mark II get the new Dual ISO Dynamic Range, what different with the 7D that allows it?

[Redrocks]

Quote from: a1ex on June 27, 2013, 09:02:48 AM
@guentergunter: I have explained the reasons for mod16 resolutions, and I'll stick with that.

If a.d. wants to provide 1880, that's his own choice and I do not support it in any way. I know what trouble I had on 5D3 with random lockups because of DMA misalignment, so I'll stick with a portable solution that works everywhere.

As for the other options, some of them are good and will be added to vanilla builds (e.g. black bars, but in a clean way that does not fight with other overlays), others are just ugly hacks (e.g. dropping frames instead of optimizing playback code, or some status displays moved over ML overlays, therefore flickering like crazy if you enable both.

--------------

1880 doesn't seem worth taking a chance on at this point. Not that I don't appreciate a.d's efforts, I just prefer to work with the most reliable code. I did direct comparisons between a.d. & A1ex's builds:

http://www.magiclantern.fm/forum/index.php?topic=6662.msg53551#msg53551

[Redrocks]

Why can't the Mark II get the new Dual ISO Dynamic Range, what different with the 7D that allows it?

http://cdn.bitbucket.org/hudson/magic-lantern/downloads/dual_iso.pdf

3.1 What about other cameras?
Unfortunately, most other Canon cameras follow a different pattern for the CMOS #0 register,
without any obviously duplicate fields. As we know from Canon specs, most cameras have
a 4-channel sensor readout, except for 5D Mark III and 7D which have a 8-channel readout.
Therefore, it’s likely that our ISO trick may work on the 7D.

[xNiNELiVES]

As for the Dual ISO video on the 5D2: I obviously have no idea that it will ever happen but, 1% found that it should work on the 6D... If it works on the 6D there's quite a larger chance that it should work on our 5D2. Then again though, its an older canon camera, things change...

[ThibaudS]

Here's a stupid question ,
can someone tell me how to film in crop mode on the 5d2?
thanks!

[ted ramasola]

As for the RAW video on the 5D2: I obviously have no idea that it will ever happen but, 1% found that it should work on the 6D... If it works on the 6D there's quite a larger chance that it should work on our 5D2. Then again though, its an older canon camera, things change...

You mean the DUAL ISO RAW Video right?

[ted ramasola]

Here's a stupid question ,
can someone tell me how to film in crop mode on the 5d2?
thanks!

To record in 3X crop mode;

Press magnify button, (the one with the magnifying glass symbol) on your camera body.

5x magnify only NOT 10x.

While in 5x magnify, choose the resolution you want in ML menu. (you can choose higher resolution while 5X magnify is engaged)

Use AUTO preview or ML grayscale in ML menu.

Start recording by pressing SET button.

 

[xNiNELiVES]

You mean the DUAL ISO RAW Video right?

Yeah. That's what I meant.

[ThibaudS]

To record in 3X crop mode;

Press magnify button, (the one with the magnifying glass symbol) on your camera body.

5x magnify only NOT 10x.

While in 5x magnify, choose the resolution you want in ML menu. (you can choose higher resolution while 5X magnify is engaged)

Use AUTO preview or ML grayscale in ML menu.

Start recording by pressing SET button.

 

Thanks Ted !

[Doyle4]

Thanks Ted !

Also, in ML menu make sure that centre framing mode is set to x5 mode

[andyshon]

I guess this is pretty obvious, but turning off the buffer display does get me a little extra write speed. With a.d.s 5bad65ff8cb8 build, buffer display off, write speed peaks at 74MB/s and at 1856x1044 25fps I get between 700 and 800 frames. With buffer display on, or using the standard nightly 2013-07-20, write peaks at 73MB/s and at the same resolution I get 600 to 700 frames
Komputerbay 1000x 64GB in a very old and tired 5D2.