Etiquette, expectations, entitlement...@autoexec_bin | #magiclantern | Discord | Reddit | Server issues
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 timesResolution -- A1ex -- a.d. jun 25 pink fix Vanilla jun 251X1872 x 1054 -- 390/528 -- 395/5011872 x 1012 -- 840/709 -- 882/822 1872 x 936 -- 3667/2009 -- 2389/33591872 x 850 -- continuous -- continuous1856 x 1044 -- 510/436 -- 612/573 1856 x 928 -- 3989/5177 -- 8675/2445 /3321/6452 /9101/99271728 x 972 -- continuous -- continuous1472 x 1104 -- continuous -- continuous 3X Crop mode 2144 x 1076 -- 188/235 -- 234/237 2144 x 1072 -- 221/218 -- 211/2412144 x 974 -- 487/376 -- 353/373 1920 x 1076 -- 416/386 -- 402/4111856 x 1044 -- 736/748 -- 677/794 1728 x 972 -- continuous -- continuousResults are close except for that in 1856 x 928
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.
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
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?
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.
@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.
@ted: are you sure the overlays are enabled in both builds while recording?
Ted thanks for your extensive information, after your testing so far which build are you using?
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)
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.
Thats for 5D mkii direct from A1ex himself
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.
