5D2 RAW video Builds 14-Bit

Started by a.d., May 20, 2013, 05:27:13 PM

Previous topic - Next topic

0 Members and 3 Guests are viewing this topic.

avasarin

Quote from: Bradley on July 03, 2013, 03:47:12 PM
Sandisk Extreme 60 MB/s 400x 64GB card.
I can do a little less than 55MB/s in raw video mode.

I don't know how you guys got that screen shot of your results, so here is the text from the bench.log file
It's saved in the CF card, in the main folder.
5dmk2 - Nikkor set(20-28-35-50-105mm), Vivitar 85-105 - BMPCC
http://www.frabiatofilm.com
https://www.facebook.com/stringssenzatempo

ch_d

So. Now i know why i can´t record with 70mb/s...
I have the Komputerbay 128GB card. With the AJA System Test i can only get around 67mb/s in writing ... looks like komputerbay can´t keep the 1000x speeds like other cards.

5D MII

Doyle4

Quote from: chadsky on July 05, 2013, 08:14:54 AM
so many days without updates ...

Not at all.... check the change log, always work going on on Magic Lantern that you dont see  ;)

Doyle4

Quote from: ch_d on July 05, 2013, 11:09:38 AM
So. Now i know why i can´t record with 70mb/s...
I have the Komputerbay 128GB card. With the AJA System Test i can only get around 67mb/s in writing ... looks like komputerbay can´t keep the 1000x speeds like other cards.

Fastest Komputerbay card is the 64gb apparently

Bradley

Quote from: avasarin on July 05, 2013, 10:36:46 AM
It's saved in the CF card, in the main folder.

The benchmark saves it on the CF in the main folder? when I run the benchmark it only creates a text file, and the only way I know to take a screenshot is from the menus, so when I go to take a screenshot it removes the benchmark results off screen.

Also I was wrong about my CF card doing 55MB/s the Sandisk extreme 64GB 400x will do 57.2-57.4MB/s which is pretty good I think for a 400x card. I can run 1600x900 for about 6GB worth of footage before the buffer overfills. I'm quite pleased with that as I don't have moneys for 1000x card and 1600x900 looks pretty great.


Also, I don't know if this is a understood bug, but when my raw videos go over 4GB magic lantern splits the file and then creates these .rar files.  I get an error on the original 4GB raw file about it not containing a footer and it won't work with the DNG creator. I also can't unrar the rar files either.

I'd love an option for it to just stop recording at 4GB until it is fixed because it basically makes any video that goes over 4GB unusable.

silvertonesx24

Using 6/29 build and an external monitor, crashed every time when trying to write with the external monitor attached. Attached crash logs for review

http://sdrv.ms/17XKStJ

bnvm


Quote from: Bradley on July 05, 2013, 04:50:16 PM
Also, I don't know if this is a understood bug, but when my raw videos go over 4GB magic lantern splits the file and then creates these .rar files.  I get an error on the original 4GB raw file about it not containing a footer and it won't work with the DNG creator. I also can't unrar the rar files either.

I'd love an option for it to just stop recording at 4GB until it is fixed because it basically makes any video that goes over 4GB unusable.

The file splitting is not a bug, once the 4 GB limit is reached it automatically starts recording to a new file then later on the files can be merged back into 1 file before exporting to dng's, the files must be merged back together as they are all incomplete on their own.  They are not rar files by the way they just use the same file extensions that split rar files use, they are RAW files. All this info is on the first post in this topic but here is how you join the files.

QuoteJoining files
WIN
    Start dialog: cmd
    1. cd C:\Users\my_destination_folder
    2. copy /B xyz.RAW+xyz.R00+xyz.R01 xyz.RAW

dariSSight#1

In the same fashion of the native H.264 from canon, is there anyway way ML firmware could allow ProRes 4444 or ProRes 422?

bnvm

Quote from: dariSSight#1 on July 05, 2013, 06:55:48 PM
In the same fashion of the native H.264 from canon, is there anyway way ML firmware could allow ProRes 4444 or ProRes 422?

We will need confirmation from one of the dev's but I am almost postive the answer will be no. The 5d2 cpu is not fast enough to do any kind of compression/encoding and there is no known way to change the compressor from h264 which I believe is handled by the DIGIC chip. Right now the only options are h264 from canon or just straight copying the raw data directly off the sensor to a file, the cpu is not even fast enough to convert the data to 12 or 10 bit before writing which would be a huge breakthrough allowing a compromise between bit depth and resolution. 14 bit is nice but a bit of overkill at times.

Doyle4

Quote from: dariSSight#1 on July 05, 2013, 06:55:48 PM
In the same fashion of the native H.264 from canon, is there anyway way ML firmware could allow ProRes 4444 or ProRes 422?

ProRes is an Apple codec... no chance it will happen,

dariSSight#1

I kind of thought that would be the answer, so that's it. I think once ML run thorough test to every function we might have a good understanding to this Miracle Firmware Called Magic Lantern RAW. I would like to thank the Magic Lantern Team for this Cinematic Break Through, I'm sure you might have more in store with your BETA and I'm on pins and needles.

athimbleofdan

wtf is this  :o Same results in video mode. Done after card format.

Komputerbay 64gb 1000x

reddeercity

Hi All  :)
Just Got My New 64 GB Lexar 1000x Card today so i tested with A_D_ June 29 & 27 Hack built
I did 6 tries at full 64GB card record.

After about 3 Hours of testing, i have found that at 42 GB there is a problem writing to card.
I was going after a full stable Card record of 64 GBs .
1856x1004 @ 24p or 23.976p it was continuous until i hit the 42 GB barrier , at that point
It when from "continuous Recording" with very little buffering to heavy buffer  "expected 77" @ 2.8MB/ss ?
Then stop recording @ 14,921 frames , 12,568, 9122, 14,171, 14,187,14,111
5 out of 6 tests stared to have problems @ about 42GB. ???

I also tried a Safe frame size that i know works.
1880x854 24p @70MB/s and it to had a problem at about 42 GB
but it did not stop recording , it displayed frames " 94 expected k" @ 5.9MB/ss ?
that continued to increase to "112 expected K" @ 15MB/ss
until 64 GB then stop, i'm still in the process of checking the 64GB file , will report later.
Plus all the over lays information was incorrect,
it displayed 59.5 GB remaining, when i just finish
14,000 Frames ? Time for recording displayed 21:12 Min. ?
I though it was a temperature issue but it never got over 65 degrees "C"
i would think that the 32 GB Card will not suffer from this but the 64 GB Card
may have a problem at lest on the Lexar 1000x 64GB card :(

On all of the tests except the 1880x854(70MB/s), the write speed to card was
no more then 75MB/s

I would recommend people Test your 64 GB Card and see if you truly
can record a Full card, even at smaller resolution.
I did this test on both june 27, 29 builts same problem with both.

Has anyone Done a 64 GB continuous Full card Record ??   
 

ted ramasola

Quote from: reddeercity on July 06, 2013, 07:04:38 AM
Hi All  :)
Just Got My New 64 GB Lexar 1000x Card today so i tested with A_D_ June 29 & 27 Hack built
I did 6 tries at full 64GB card record.

After about 3 Hours of testing, i have found that at 42 GB there is a problem writing to card.
I was going after a full stable Card record of 64 GBs .
1856x1004 @ 24p or 23.976p it was continuous until i hit the 42 GB barrier , at that point
It when from "continuous Recording" with very little buffering to heavy buffer  "expected 77" @ 2.8MB/ss ?
Then stop recording @ 14,921 frames , 12,568, 9122, 14,171, 14,187,14,111
5 out of 6 tests stared to have problems @ about 42GB. ???

I also tried a Safe frame size that i know works.
1880x854 24p @70MB/s and it to had a problem at about 42 GB
but it did not stop recording , it displayed frames " 94 expected k" @ 5.9MB/ss ?
that continued to increase to "112 expected K" @ 15MB/ss
until 64 GB then stop, i'm still in the process of checking the 64GB file , will report later.
Plus all the over lays information was incorrect,
it displayed 59.5 GB remaining, when i just finish
14,000 Frames ? Time for recording displayed 21:12 Min. ?
I though it was a temperature issue but it never got over 65 degrees "C"
i would think that the 32 GB Card will not suffer from this but the 64 GB Card
may have a problem at lest on the Lexar 1000x 64GB card :(

I would recommend people Test your 64 GB Card and see if you truly
can record a Full card, even at smaller resolution.
I did this test on both june 27, 29 builts same problem with both.

Has anyone Done a 64 GB continuous Full card Record ??   


is your auto power off set to=OFF ?
5DmkII  / 7D
www.ramasolaproductions.com
Texas

reddeercity

Yes, Auto power is set to "off"
i also had my AC adapter on the Camera

If any one can record full 64 GB card you will see About 28,000 Fames

Edit: i did try a 500 MB Warm up file to start before i did the continuous record.

ted ramasola

Quote from: reddeercity on July 06, 2013, 07:14:48 AM
Yes, Auto power is set to "off"
i also had my AC adapter on the Camera

If any one can record full 64 GB card you will see About 28,000 Fames

On the 5D2 1872 x 936 is the highest res that I tested to be continuous. Even if it would initially say to be "continuous ok" in higher resolutions, later on it will change.

For 16:9 AR its 1728 x 972. For now that's it, even with fast cards.
5DmkII  / 7D
www.ramasolaproductions.com
Texas

reddeercity

Quote from: ted ramasola on July 06, 2013, 07:30:43 AM
On the 5D2 1872 x 936 is the highest res that I tested to be continuous. Even if it would initially say to be "continuous ok" in higher resolutions, later on it will change.

For 16:9 AR its 1728 x 972. For now that's it, even with fast cards.

Ok,
my camera never when off "continuous ok" it always said "continuous ok"
But i understand what you are saying,  :)
i have always had better numbers then what i have read in this forum.
i will try the 1728x972 AR and see if this problems is still there.

But in the Short term i can record 1856x1003 for 14,000 frame ! that's 9.7 Mins  ;D

Update:
I just check the DNG's from the 64 GB full card record @ 1880x854 24p, 22,571 frames
Frame over ride on, small hack on , Photo small jpeg , ETTR = Off,
and i had the last 3 Images are corrupt, pink garbage frames
So i call that success ! with 22,568 Good frames 15.67 minutes on lexar 1000x 64GB card
If only i can get 1856x1003 to do 64 GBs (max is 42GB)


dariSSight#1

Quote from: reddeercity on July 06, 2013, 07:54:48 AM
Ok,
my camera never when off "continuous ok" it always said "continuous ok"
But i understand what you are saying,  :)
i have always had better numbers then what i have read in this forum.
i will try the 1728x972 AR and see if this problems is still there.

But in the Short term i can record 1856x1003 for 14,000 frame ! that's 9.7 Mins  ;D

Update:
I just check the DNG's from the 64 GB full card record @ 1880x854 24p, 22,571 frames
Frame over ride on, small hack on , Photo small jpeg , ETTR = Off,
and i had the last 3 Images are corrupt, pink garbage frames
So i call that success ! with 22,568 Good frames 15.67 minutes on lexar 1000x 64GB card
If only i can get 1856x1003 to do 64 GBs (max is 42GB)

Do I have this process theory right or wrong, Because of the line skipping process from the DiGiC chip we have been shorted 266 continuous pixel for every frame 40 from the 1920 width and 226 from the height. I'm sure I might have something wrong, I was just wondering what was your opinion on 1880x854 for the Mark II vs 1920x1080 for the Mark II?

Redrocks

Quote from: reddeercity on July 06, 2013, 07:04:38 AM

Has anyone Done a 64 GB continuous Full card Record ??   


I just filled my 64GB Komputerbay and speed dropped from 68 MB/s continuous to 2.1Mb/s 110 expected at the 42 GB point. The buffer stayed the same at barely a bar. 1856 x 742 26531 frames. All I can offer is the 42GB point is around the time the tenth file is written?

mageye

I have done a full card record on the 32Gb Komputerbay 1000x

I know it's not reallly going to help you much but I didn't have any problems with that; apart from it was never able to write the file footer (because it filled the card) so I had to patch it. But it did indeed work. :-\
5DMKII | 500D | KOMPUTERBAY 32GB Professional 1000x |Canon EF 50mm f/1.8 II | Samyang 35mm f/1.4 ED AS UMC | Canon EF 75-300mm f/4-5.6 III | Zoom H2 (4CH. audio recorder) | Mac OS X 10.9.2 | Photoshop CC | After Effects CC | Final Cut Pro 7

reddeercity

Quote from: Redrocks on July 06, 2013, 06:28:57 PM
I just filled my 64GB Komputerbay and speed dropped from 68 MB/s continuous to 2.1Mb/s 110 expected at the 42 GB point. The buffer stayed the same at barely a bar. 1856 x 742 26531 frames. All I can offer is the 42GB point is around the time the tenth file is written?
Hey Thanks i though i was the only 1  :)
i was wondering if you have tried  1856x1003 24 with you 64GB Komputerbay?
How many frames  can you get ?
Best i can get is 14,921 with ETTR=Off
So 42 GB is a Barrier for 64 GB card with larger frame size.

Can only one explain?  "2.1Mb/s 110 expected at the 42 GB point"
and it always happen @ "42GB" evey time

reddeercity

Quote from: dariSSight#1 on July 06, 2013, 01:50:00 PM
Do I have this process theory right or wrong, Because of the line skipping process from the DiGiC chip we have been shorted 266 continuous pixel for every frame 40 from the 1920 width and 226 from the height. I'm sure I might have something wrong, I was just wondering what was your opinion on 1880x854 for the Mark II vs 1920x1080 for the Mark II?

:)
On the 5D2 the Max-with from the sensor is 1880
Canon upscale the image to 1920 for h264 with software.
It really depends on what your Project calls for.
Being that the image is very scale able meaning , re-framing, punching-in.
I like to use Max amount of the sensor then crop out sides .
the other reason i like it is because of the reduce height for a more Film look & feel !

It also easier to Write to the card @ 68.5 MB/s
That's at lest in my case, I think if with can keep frame data close to the best Hexadecimal 
it should write quicker, but i'm Not a programmer so that a guess.

But with 1856x1003 it very close to HD @ 1:85.1 AR
that would be the ticket, there again re-framing etc...
I will settle for 1856x1003 for  HD Work & for Documentary
I would use 1880x854 or even 1880x940 if you can do it.

Stop thinking about line skipping and all the stuff, you will always have problems
with that line skipping for panning etc..
But think of you camera as a "Film camera" to capture Positive Film Stock (but More)
It's Not a Video Camera, because with are capturing Frames like "true Film" Stock
I personally turn off everything on the camera & use manual focus,
use proper exposing Technics, "Use Meter on camera" i don't use the "ETTR" function.
but i have a Variable ND and  Stop it up or down for scene.         


Doyle4

Could someone please explain clearly please how to join a split files on a mac please? been stuck over an hour now and getting no where :(

i have a .RAW and a .R00, iv seen command's on here but it doesn't say how to actually do it, iv tired draggin in the files to terminal and the folder that they are in and keep getting message "No directory found"

Cheers,

ted ramasola

Quote from: Doyle4 on July 06, 2013, 10:16:45 PM
Could someone please explain clearly please how to join a split files on a mac please? been stuck over an hour now and getting no where :(

i have a .RAW and a .R00, iv seen command's on here but it doesn't say how to actually do it, iv tired draggin in the files to terminal and the folder that they are in and keep getting message "No directory found"

Cheers,

Post processing for mac links:

http://www.magiclantern.fm/forum/index.php?topic=6218.0

http://www.magiclantern.fm/forum/index.php?topic=5508.0
5DmkII  / 7D
www.ramasolaproductions.com
Texas

Doyle4

Quote from: ted ramasola on July 06, 2013, 10:29:31 PM
Post processing for mac links:

http://www.magiclantern.fm/forum/index.php?topic=6218.0

http://www.magiclantern.fm/forum/index.php?topic=5508.0

Cheers dude, RAW2DNG wont let me add the .R00 or .RAW still, get an error every time, i love RAW2DNG, but the terminal thing is a brain killer, would love to know how to merge them using terminal, not so keen on RAWmagic.