5D2 RAW video Builds 14-Bit

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

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

a1ex

I did not say anything about camera speed. I only said I had trouble with non-round resolutions in other cameras, and I see no good reason for adding an exception on 5D2 just because it seems to work.

a1ex

@ted: are you sure the overlays are enabled in both builds while recording?

dariSSight#1

Quote from: ted ramasola on June 27, 2013, 09:30:34 AM
Comparing Vanilla (5d2-fac94f686d23-pink-debug ) and a.d. pink fix jun 25 (d07dab0ba6c2)

Ran tests 2 times consecutive for each resolution except in 1856 x 928, ran it 4 times



Resolution     --  A1ex             --  a.d. jun 25 pink fix
                      Vanilla jun 25
1X

1872 x 1054  --  390/528       --  395/501
1872 x 1012  --  840/709       --  882/822
1872 x 936    --  3667/2009   --  2389/3359
1872 x 850    --  continuous   --  continuous
1856 x 1044  --  510/436       --  612/573
1856 x 928    --  3989/5177   --  8675/2445
                            /3321/6452      /9101/9927

1728 x 972    --  continuous   --  continuous
1472 x 1104  --  continuous   --  continuous
   
3X Crop mode
   
2144 x 1076  --  188/235       --  234/237
2144 x 1072  --   221/218      --  211/241
2144 x 974    --   487/376      --  353/373
1920 x 1076  --   416/386      --  402/411
1856 x 1044  --   736/748      --  677/794
1728 x  972   --  continuous   --  continuous

Results are close except for that in 1856 x 928

Ted thanks for your extensive information, after your testing so far which build are you using?

Doyle4

im currently using 5d2-fac94f686d23-pink-debug which A1ex posted earlier, so far so good :) best one so far, not all features there but i added the ETTR module my self and seems a'ok, nice n stable.

guentergunter

Quote from: a1ex on June 27, 2013, 10:13:41 AM
I did not say anything about camera speed. I only said I had trouble with non-round resolutions in other cameras, and I see no good reason for adding an exception on 5D2 just because it seems to work.

Quote from: a1ex on May 30, 2013, 01:43:02 PM
Noticed that frame sizes multiple of 512 are a little faster to write (credits: CHDK and confirmed with my benchmark; also DMA block size is 512, so it makes sense). So, I've rounded things to 64x32 or 128x16, to make sure frame size is multiple of 512.

And indeed, according to my benchmark, 1920x1088 is a little faster to save than 1920x1080.

Now it's your job to calm down the guys who will flood the forum asking where did 1920x1080 disappear ;)

Anyway, I can definitely understand your point and might behave just as.
5D2 ML RAW + VAF-5D2b: http://vimeo.com/69350650

dariSSight#1

Quote from: Doyle4 on June 27, 2013, 11:59:54 AM
im currently using 5d2-fac94f686d23-pink-debug which A1ex posted earlier, so far so good :) best one so far, not all features there but i added the ETTR module my self and seems a'ok, nice n stable.

These post you guys are referring to are for the 5D Mark III?

Doyle4

Quote from: dariSSight#1 on June 27, 2013, 02:52:26 PM
These post you guys are referring to are for the 5D Mark III?

Thats for 5D mkii direct from A1ex himself :)

Yaros525

Hello a.d.,
After Effects CS4, nor Photoshop CS5 can't parse dng's created with raw2dng from June,14 (yours latest build for WIN).
But, I still have yours older June,8 build and it works perfectly fine.
Thnx for your work.

andrus

Quote from: Yaros525 on June 27, 2013, 03:21:11 PM
Hello a.d.,
After Effects CS4, nor Photoshop CS5 can't parse dng's created with raw2dng from June,14 (yours latest build for WIN).
But, I still have yours older June,8 build and it works perfectly fine.
Thnx for your work.

Same problem here, cannot import in After Effects CS4 "Import module could not parse the file" or something similar, but I can open them with Photoshop CS5 and Camera Raw 6.7 (Win XP SP3)
5D MkII | Sigma 50mm f1.4 | Komputerbay 32Gb 1000x | A spare battery :D

bnvm

@A1ex sorry I am sure this info is somewhere else but I am kind of new here, where do I get the current builds for your version? Thanks.

Doyle4

Quote from: bnvm on June 27, 2013, 04:44:48 PM
@A1ex sorry I am sure this info is somewhere else but I am kind of new here, where do I get the current builds for your version? Thanks.

Its on page 26 on this topic at the top,

ted ramasola

Quote from: a1ex on June 27, 2013, 10:32:24 AM
@ted: are you sure the overlays are enabled in both builds while recording?

Yes I am sure.

When I was doing the tests for optimum frame count and malloc tests I had GD=off. preview=hacked, FPS override.

For the tests I did for the pink debug, using (1)vanilla jun 25, (2) a.d. jun 25, (3) a.d. jun 26, I had GD=ON, preview=auto, FPS override.
5DmkII  / 7D
www.ramasolaproductions.com
Texas

ted ramasola

Quote from: dariSSight#1 on June 27, 2013, 11:35:19 AM
Ted thanks for your extensive information, after your testing so far which build are you using?

Using? Like in real project? I would not recommend one at this point since development by the ML team is moving so fast.

For testing, I recommend you follow the current builds and draw your own conclusions based on the CF cards you are using.

5DmkII  / 7D
www.ramasolaproductions.com
Texas

ted ramasola

Quote from: andrus on June 27, 2013, 03:33:13 PM
Same problem here, cannot import in After Effects CS4 "Import module could not parse the file" or something similar, but I can open them with Photoshop CS5 and Camera Raw 6.7 (Win XP SP3)

Same problem with CS3.

CS5 is ok.
5DmkII  / 7D
www.ramasolaproductions.com
Texas

a.d.

Hmm.. old versions of CS seem not support opcode
@andrus
Version from 2013/06/08
5D2_WIN_raw2dng.zip

mgm

Hello all. Noticing improvement from June 19 to June 27 version

June 19 build
1880x940@24p max recording time : 1:30 seconds

June 27 build
1880x940@24p max recording time : 2:33 seconds

Write speed 69.8 MB/sec on Lexmark 1000x 32GB.

Keep up the great work guys!

ted ramasola

Currently testing the jun 27 build and with 1872 x 1054, I did 2 takes and I found one clip containing "vertical" noise in all frames.
The 2nd clip is clean.

Whole frame:


enlarged portion:
5DmkII  / 7D
www.ramasolaproductions.com
Texas

Yoshiyuki Blade

The new hack option puts my 600x Sandisk 16GB card just into continuous levels at 1880x854! Write speed seemed to stick around 64.7 MB/s. Gonna inspect the frames to see if I get anything like ted ramasola is seeing. I'll also have to account for the fact that I left the unofficial 1880 option on as well...

edit: It was probably a bad idea to record my LCD screen for this test due to the moire lol. I don't see anything wrong, but I'll test it again later.

Whoa, I pushed the res a little higher to see where the write speeds will top off and it seems to be at around 67.5 MB/s @ 1880x940 24.000 FPS. It started off at 68.5 MB/s for a good 10 seconds or so, but dropped. We've come a long way since the early days where I couldn't get more than 53 MB/s. :D

Redrocks

I have been experiencing vertical noise. First noticed it a few days ago after taking a bunch of photos. It went away after recording a video and then it appeared again yesterday when I first fired up my camera.

a1ex

Can you upload the first DNG from the clip?

vikado

Quote from: Yoshiyuki Blade on June 27, 2013, 08:16:27 PM
The new hack option puts my 600x Sandisk 16GB card just into continuous levels at 1880x854! Write speed seemed to stick around 64.7 MB/s. Gonna inspect the frames to see if I get anything like ted ramasola is seeing. I'll also have to account for the fact that I left the unofficial 1880 option on as well...

edit: It was probably a bad idea to record my LCD screen for this test due to the moire lol. I don't see anything wrong, but I'll test it again later.

Whoa, I pushed the res a little higher to see where the write speeds will top off and it seems to be at around 67.5 MB/s @ 1880x940 24.000 FPS. It started off at 68.5 MB/s for a good 10 seconds or so, but dropped. We've come a long way since the early days where I couldn't get more than 53 MB/s. :D
im getting the same results here.
im on a transcend 600x 16gb.
continuous recording at 1872x796.
peaking at 68mb/s and averaging around 64mb/s.

well done gentlemen :)

ps-do we still have to put the camera mode on C1/C2/C3 mode for more buffer?
5d2 user

Redrocks

I didn't save the clip. I figured it was due to me stressing the camera (I was taking lots of bursts) and the 2nd time it happened there was no evidence of it after I pressed record, what puzzled me was why it happened to a camera that was 'cold'. The noise in Ted's image seems more uniform than what I saw. I'm using your latest build and no noise so far.


"ps-do we still have to put the camera mode on C1/C2/C3 mode for more buffer?"

Correct me if I'm wrong, but I think the perceived effect of the C modes was down to photo settings and switching them down.

dariSSight#1

Quote from: Doyle4 on June 27, 2013, 03:17:04 PM
Thats for 5D mkii direct from A1ex himself :)

How are they receiving 1920x1088 or 1920x1080, are those reads from crop option?

dariSSight#1

Quote from: ted ramasola on June 27, 2013, 06:56:10 PM
Using? Like in real project? I would not recommend one at this point since development by the ML team is moving so fast.

For testing, I recommend you follow the current builds and draw your own conclusions based on the CF cards you are using.

I was referring to which build has the most stable frame increase, but I get your point all builds are from a growing improvement. Going to test out the June 27 build.

intrinsic

Just tested latest build (06/27) with Transcend 1000x 16Gb
with "small hacks" on
vs 06/25:
1880x1058 FPS 23.9 > 265/330
1880x1058 FPS override 20 > 807/2269 (write speeds up avg from 60 to 64 Mb/s)
1728x972 FPS 23.9  > 686/1720


Indeed huge performance breakthrough!
Still wonder, why lowering FPS significantly increases write speed, any ideas?
Anyway, 1880x1058 @20fps looks very good for me )