7D Raw Thread

[Ozgur]

Hi people,

* Does anybody know what exactly is missing in 7D raw from the Raw shooting feature that is available for Mark III?
* I read someone saying it will never record continuous full HD in 7D because of the speed of its CF card reader or something?
* What exactly is this silent picture, and how is it different than RAW video capture?

Thank you!!

[hbr]

@Ozgur

* continous raw recording is still missing, and higher resolutions are still missing (for now only 600px height works) - this will eventually be fixed
* CF speed on 7D is fast enough so , yes it will be able to shot continuous HD, if not 1980p then something really close to it (don't forget that 2.5K works in 7D)
* silent picture burst mode means that camera takes 24 pictures in one second (silent because mirror is locked) and keeps on taking this pictures until the buffer is full, then it stops. Difference between raw video is that you get number of picture files that you need to make as a video (like time lapse videos), and you can only record a certain numbers of pictures (until buffer gets overloaded), raw video on the other hand gives you one raw video file that you can process afterwards and can provide continuous shooting

[Digital Corpus]

Some benchmarks on the 7D show write speeds of about 88 MB/sec. Reliably though, 80 MB/sec is what others are getting. Now, despite this, the silent pic mode isn't able to write out files at this speed on a regular basis. I don't know why specifically, wish I didn't have my embedded project taking up my time so I could help, but the silent pics are writing out slower than 80 MB/sec in some cases.

According to this, the data rates come out to (in MB/sec)
24 fps & 30 fps
1728 x 576 - 39.87,  49.83
1600 x 534 - 34.22,  42.78
1472 x 626 - 36.91,  46.14
1344 x 610 - 32.84,  41.05
1280 x 582 - 29.84,  37.30
1152 x 622 - 28.70,  35.88

60 fps
1728 x 308 - 53.29
1600 x 382 - 61.20
1472 x 420 - 61.91
1344 x 436 - 58.68
1280 x 486 - 62.29
1152 x 464 - 53.53


Though for higher resolutions, assumed 24 fps, we have (in MB/sec):
1736x1156 - 80.38
2520x1200 - 121.12


Now, if we assume 80 MB/sec our top end speed, @ 14 bits, gives us:
~1.997 MP pixels a frame @ 24 fps
~1.6 MP pixels a frame @ 30 fps
~0.8 MP pixels a frame @ 60 fps

For the following aspect ratios, assuming that we can achieve a continuous ~80 MB/sec +/- 0.5 MB/sec, the maximum frame sizes are:
FR      3:2         16:9         2.35:1
23.976   1728 x 1152   1892 x 1056   2176 x 920
29.97   1550 x 1032   1696 x 944   1944 x 824
59.94   1088 x 736   1192 x 672   1368 x 584

Just demonstrating theoretical in case anyone has the time to test and push the boundaries of our hardware.

[emmikiruba]

Thanks a lot Alex! It is excellent - Digic peaking - perfect for focusing, But how we are going to solve the Live View issue? Excitement increased manifold but waiting at the peak! few more moments .... to perfect the excitement.

[emmikiruba]

Is that 'focusing distance' a new script or was existing there?

[_iLiam]

https://vimeo.com/72525066

Quick little test at 1600x600 continuous. I was using a sandisk 60mb/s however I have just received a 1000x card in preperation 

The full res render in after effects looks insanely sharp, I had to compress the size down for vimeo but it still looks so much better than anything we had before!

[britom]

Lets try to continue working on this.

The current raw_rec module for the 7D freezes the liveview when recording is started. It happens in any preview mode. When taking silent pics in burst mode, we still have liveview while the images are being recorded to the buffer, but when recording video with the raw module, the buffer instantly saves the images to the card and the liveview freezes is causing this, might be because of the way the 7d is engineered.

Anybody has something to comment on this? Am i on drugs?

[mucher]

the great g3gg0 is busy with the mlv writing. his goal is probably writing 2.5k to cf only. when that is achieved. we might hope that the write module can be used to write lv to cf.

the most promising thing for me is to compress lv to 10bit..then all camera will have decent 2.5k raw output. but g3gg0 is too busy.

so we can only be patient

[arrinkiiii]

Lets try to continue working on this.

The current raw_rec module for the 7D freezes the liveview when recording is started. It happens in any preview mode. When taking silent pics in burst mode, we still have liveview while the images are being recorded to the buffer, but when recording video with the raw module, the buffer instantly saves the images to the card and the liveview freezes is causing this, might be because of the way the 7d is engineered.

Anybody has something to comment on this? Am i on drugs?

hahah    im on drugs and i can say it's true. Let's hope that some dev grab this and continuous the work. More a little bit and we got 1080 raw.

the great g3gg0 is busy with the mlv writing. his goal is probably writing 2.5k to cf only. when that is achieved. we might hope that the write module can be used to write lv to cf.

the most promising thing for me is to compress lv to 10bit..then all camera will have decent 2.5k raw output. but g3gg0 is too busy.

so we can only be patient

2.5k in 10bit it will be wonderful 

[chroma]

Is it possible to run the dual iso, raw burst and raw modules on the 7D without the "risky" autoboot?  Maybe I'm just plain stupid, but I've read these 7D threads up and down, followed various instructions and can't get the "Modules Tab" to appear. 

And I can't seem to get (or find) that nice Benchmark Test that everyone posts their results with (mine only does two or three lines and that's it! FYI using a Komputerbay 1000x 64gb).

Am I missing something here...?  Pathetic, I know, but if someone could help, I would be eternally grateful!  Love ML and my 7D, just can't seem to get the latest and greatest up and running!

[Walter Schulz]

AFAIK you can't set the camera's bootflag using a card with 64 GByte capacity.
I had the same benchmark problem with the non-bootable alpha 2 version.

My advice: Buy a cheap slower card (up to 32 GByte) and use this one for initialization and first tests.

Ciao
Walter

[stevelucky]

AFAIK you can't set the camera's bootflag using a card with 64 GByte capacity.
I had the same benchmark problem with the non-bootable alpha 2 version.

Is this accurate? I thought the issue was only with 128gb cards. This is the first I've heard that 64gb cards can be a problem.

[Walter Schulz]

http://wiki.magiclantern.fm/install#step_1_preparing_your_camera
"For first install, use a simple SD/SDHC/CF card (32 GB or smaller). 64GB cards and larger will not work for first install (but you can use them with ML, see below)."

I read about compatibility hickups with some Komputerbay 128 GByte cards. Looks like some information mixup ...

Ciao,  Walter

[ted ramasola]

Is this accurate? I thought the issue was only with 128gb cards. This is the first I've heard that 64gb cards can be a problem.

There is no problem with 64gig 1000x cards. You can use them run ML.

[Walter Schulz]

Does this mean you can use it without limitations? Including camera initialization (setting bootflag)?
If so: The installation docu needs an update.

Ciao
Walter

[chroma]

Thanks for the words of advice.  Got it up and running with my 16gb 500x.

I think my Komputerbay 1000x 64gb may be one of the "duds."  When I benchmarked it, the Write speeds were 45 to 61 MB/sec and the Read speeds were 41 to 67 MB/s.  Seems to be WAY OFF what others here get with the same CF card!

[Walter Schulz]

Contact Komputerbay's support and ask for replacement. I read this procedure worked very well for other people with this problem.

Ciao
Walter

[dklamie]

Does this mean you can use it without limitations? Including camera initialization (setting bootflag)?
If so: The installation docu needs an update.

Ciao
Walter

Had no problem setting bootflag with Transcend 400X 64 GB... Just remembered I used EOS Util... somebody else verify it.

[arrinkiiii]

New test in raw with 1728x576 px

   


Workflow: from raw i use batchelor (raw2dng) that give me the dng's. From dng's i open in after effects, adjust some setting in ACR and make proxy's and after i edit and color correction/grade. Then just export in h.264.

First time that i work with proxy's and i love it.

I got some flicker in the sky, any one knows why? (going investigate)

Card: Sandisk 8GB - 60MB/s
Recorded: ISO 100

[Ozgur]

New test in raw with 1728x576 px

   


Workflow: from raw i use batchelor (raw2dng) that give me the dng's. From dng's i open in after effects, adjust some setting in ACR and make proxy's and after i edit and color correction/grade. Then just export in h.264.

First time that i work with proxy's and i love it.

I got some flicker in the sky, any one knows why? (going investigate)

Card: Sandisk 8GB - 60MB/s
Recorded: ISO 100

U get flicker all around the picture, there is not a single line without flicker :S

[arrinkiiii]

@Ozgur

Flicker in exposure ? In the video just noted in one clip or two. I think is from ACR.

[Ozgur]

@Ozgur

Flicker in exposure ? In the video just noted in one clip or two. I think is from ACR.

Aliasing on the lines of the court and the basketball pole and the frame... I don't know the workflow for RAW video but It looks like exporting error.

[ted ramasola]

Had no problem setting bootflag with Transcend 400X 64 GB... Just remembered I used EOS Util... somebody else verify it.

just verified it. I have tested it. Using 64gig, 128gig 800x Komputerbay and 32gig, 64gig and just last night a 128gig 1000x Komputerbay CF.

We just verified that CAPACITY is not the limitation but cf card firmware.
On the 128gig Komputerbay, we were trying to find out which firmware on what chip controller works.
We just found that older firmware makes the camera "see" the bootflag enabe on the cf card compared to newer versions on the same card.

Until that's sorted out stick to 32 and 64 gig cards.

[ted ramasola]

Flicker on the lines of the court and the basketball pole and the frame... I don't know the workflow for RAW video but It looks like exporting error.

That is NOT called Flicker but its called Aliasing. Flicker is usually a temporal term.

[Ozgur]

That is NOT called Flicker but its called Aliasing. Flicker is usually a temporal term.

Absolutely! My fault, I meant Aliasing...