Messages

Yes get the 5D2 over the eos m , faster write speed (CFcard) full frame
just a better looking image , it has a better user experience ,no bugs .
Soon it will have lossless compression (being trying to finish it from last year @ 90% done)
just finishing up with crop_rec now so by the end of the mouth I should be working on lossless .
Plus I'll be looking at overclocking the cf card bus for faster write speeds = to 5d3 @ 120MB/s.
just haven't had time to dig very deep , so yea the future looks very bright for 5d2 .
Oh did I mention 5d2 can do 48fps in 3x3 (FHD) 1856x1120 & 1920x818 45fps for in 3x crop_mode (in the crop_rec branch)

Hi reddeercity, Do you have a thread to follow your builds ? I'm back on video with my 5d2. I'd stayed since 2013 with the old RAW FW (just to have 1880). I want to try again mlv with sound now and try what's possible nowadays with 5D2. Cheers 

Sorry about that, I didn't follow the last 5D2 build, I've only seen the 5D3 news on eosHD. I don't know exactly the CF writing speeds of 5D3 but as RAW capabilities were close with 5D2... 

Hi a1ex,

Any hope for a 4k 10bit support on a next 5D2's builds ? 

There's something very strange about performance with 128GB cards.

It's obvious that we can't compare 256GB to 64GB reliability. It's like all 128GB cards have some issues to achieve good performance continuously. Maybe there's something like SSD's nand module, with pair number of Nand modules connected to controller ? Maybe not the same type of RAM used

Perhaps KB support can clear it up, in asking directly factory engineering staff ?

I'd like to bought 1000x 64Gb, but It's not cheap and really short to record about 15Min on just one card a time. In fact, I use something like 90 Gb for one session

Anyone tried the new 256Gb 1066x ? I contact KB support and they tell me the 256 is 5D2 compatible but I want to be shure there's no issue before ordering one (400$)

I tried 3x   128gb 1066x - all are about the same, pretty tightly.

Just installed 1.1.3 firmware and ML, it bumped up my writing rates by 2-3 mb/s (85-90mb/s, GD ON, movie). But 30fps 1080P with spanning still doesn't work (MLV).

Frames still get re-queued.

You're on 5D3 ? Hope to reach 75-80Mb/s on 5D2 comparing to 65MB/s with my old 128Gb 1000x

I just orderer an 128Gb 1066x and hope to reach the 64Gb's 1000x capabilities on 5D2 with this 1066x. In fact, I believe it depend heavily on the DSLR you use, maybe the difference on 5D3 will be more importante between 64 1000x & 1066x.

oh yes, I forgot: it depends on DSLR you're using... on 5D2, it's very difficult to get more than 65 with 128GB card... Some bench have been done last summer on 5D2, and the best buy for the bucks for the mk2, are the 64Gb 1000x because of internal controller limits. Even 1200x are limiting. (there's difference in crop mode where we can reach better bitrates)

I precise that 65 mb/s give me consistent results @ 2.20 format  (1880x854 24p continuous) As I don't use ML bench because for bitrates capabilities

Just to be precise about KB cards. I have had 6/7 of them and my main card is an old (june 2013) 128GB 1000x. With this one, I have consistent results, but there's some issue depending on parameters and fork I use. Sometimes, for what reason, it starts with a maxed 25-30MB/s for a while, and will become consistent after 30 seconds @ 65mb/s...

My point is that it depend on :

- first : space available on the card (fragmentation if you prefer)
- alignement of the partitions
- FAT type
- Card / DSLR / ambient temperatures
- ML release
- Parameters (liveview / modules loaded /  hacks etc etc) on ML

We can handle that there's some issues with recent Compact Flash, depending on UDMA controller and some USB card readers can definitively damage some cards (I got two 128GB deadly damaged with my old USB2 reader).

Maybe some a.d., Pravdomil or 1% statement ? Does the "official" releases includes some of their work ?   

And if keeping 1888 may slowdown RAW/MLV developpement for 5D2, I completely agree to only keep 1856...

[in order to keep 1872, one has to either add 5D2-specific exceptions in the code]

The reason for changing the resolution is portability: in order to keep 1872, one has to either add 5D2-specific exceptions in the code, or remove the safeguard in some other cameras (e.g. both 6D and 5D3 are known to crash on resolutions that are not multiple of 32 pixels, and this crash is a memory overflow that may result in anything, including permanent camera bricking).

I can choose between 1856 and 1888 with no coding effort. Between these 2 numbers there are no values that respect the alignment restrictions from EDMAC (it happens to work on 5D2, but I don't want to rely on this for all other cameras).

Camera-specific exceptions are not always desirable (they make the code harder to maintain and they have a negative effect on testing coverage). I've asked you to convince me that the extra effort to add the exception (and to maintain that exception from now on!) is worth it. I'm trying to simplify things, since this will reduce the burden of maintaining the code base (and this is one of these things that can be kept simple and portable).

In fact, there's something to clarify : I understand that exceptions where to maintain 1872, but maybe I've missed something in the third part...

Stating uppon 3 screens...

Aside that, I'm not a pixel peeper, but 1880 to 1856, there's a loss of 24 pixels (something about 1.3%). It's very few, I definitly agree, but there's a loss... what the point ?

As it's seems possible (and relatively easy to add), I still don't understand why not including the option ?

To me :

C1 - 1880 (The BG's screw looks sharper to me)

B1 / B2 - can't figure out

A1 - 1880 (upper windows looks sharper to me)

Yes I agree, it's very difficult to be shure and I may be easily wrong, but I stay my point : what the trouble to keep the max resolution available if there's no coding effort ?

To be honest, there's something I don't get : what the trouble to just add 1888 (if it's not too much complex to add in code) : All people who do not want to post-prod crop still can use 1856, and others can use max resolution ? (perhaps some notice in the readme file to warn about black border on 5D2, and that's all)

To a1ex :

Just to be precise : Actually, I (we ?) don't know clearly the history of ML developpement team and I can't really figure what's the involvement or deserving of every dev' in digging Canon code. BUT I can clearly figure that for the original core of the team it can be very painfull to see other people forking, using the original code you'd share, without following your guidelines, and I clearly understand your concern about portability.

I REALLY don't want to be fresh or misrepectfull about your work, I've only tried to honestly answer your question about max resolution on 5D2.

I very like your work. Landscapes made for DSLR... 

5D2 RAW footage shooted last WE in my garden
AE / PP CS6 (encoding in Black Magic 10Bits 4/4/4)
lens : Canon 50 1.4 / Sigma DG-OS 105 MACRO

Music : "Inverno Grigio" - Paolo Fresu / Omar Soza

Looking to ted's test, I thought about VAF on 5D2 and the difference between 2048 crop downscale and the 2 other non crop resolution. The aliasing seems to me really so huge and I was asking myself in which ways decreasing resolution for upscaling will play.

To me the 1880 looks sharper than 1856 and 2048 look clearly sharper than the 2 others. I made some tests in RAW mode last summer with an old 600x compact flash @ around 1580 then upscale to 1920. the diffence with 1880 upscaled was really huge. 

I agree that between 1856 and 1880, the difference is not important, but if I'm asked between 2 resolutions : I definitively vote for the maxima.

As far as I can come with my fresh judgement about 1856/1872/1880, I agree with Reddeercity : I always shoot with the maximum resolution I can get (that's why I bought this 2000€ camera for a hobbyist, instead of 1000€ like my brain should have). I obviously continue to use RAW beside MLV (and because I don't really use audio) just to get 1880 instead of 1872. But I really understand the coder's positions and portabilities arguments. To be honest, I think I will stay with last releases as I have found some compromises and because the present work (performances / reliability) seem's to me already convenient.

And as always : a massive thank for that...

I should mention that right now the fastest stable MLV+Audio build comes from the nightly build
(magiclantern-v2.3.NEXT.2014Feb16.5D2212)
1872x936 2:1 23.976p + audio, Is continuous with 1000x card on 5d2 fill buffer set to "0"
I will be using this tomorrow on a News-story/interview 

Edit: I do my audio syncing in A.E., but I also record a master track on a Zoom 4Hn
I just use the audio in mlv to sync with master. Resolve is Ok, but ACR plugin is the best out there,
Its just a slower workflow but better result, at least that's what I think anyways.

To get the full potential on the 5D2 I recommend the 64gig 1000x, the 1050x will function on the 5d2 BUT due to its write speeds you get smaller resolutions that are continuous. But yes, it will function but you might not get longer record times.

For synchro, use resolve. It is faster and do not go the after effects route, its time consuming and the acr is not designed for long videos but photos. Its just ok for short clips but in the long run, resolve is designed from the ground up for raw videos.

To sync audio refer to pages 122-124 of the resolve manual.

To extract MLV videos with wav, use either g3gg0's MLV browser ro tonybeccar's mlv converter.
http://www.magiclantern.fm/forum/index.php?topic=8447.0

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

Thank's for both of you 

thank's Ted, I will see further on MLV. I've read the topic of reddeer to extract RAW+wav, but I need a topic for synchro in after effect or premiere. So 1050x cards are full functionnal on 5D2 ?

I just find out : the black borders only appear with MLV module, not in RAW module anymore... I'm used to record in 1880x854, and 1880 isn't in MLV module, that's why I do not use MLV. I have to choose... I'm pretty happy with RAW module and RAWinizer... I'm not very familiar with MLV tools

Hi Ted , so finally the 1050x work with 5D2 ?

For the black mask, I have try the old release from 24/10/2013 and I have the mask in the RAW menu named recording frame (with the choice between black bar or white rectangle) but I can't find it in the it in the last releases. I have only load all modules to find this, I don't usually load them aside RAW modules.

The black mask border is still there in both raw_rec and mlv. Looking at Mar 2 nightly.

Thank's Ted. i don't really understand how to active it, as I have all modules activated. I will see further. 

Do you have some feedback about reliability of KB CF for RAW since last summer ? My 128Gb still work very nicely (even I got some issue yesterday...), but I don't use it as professionnal work like U do.