Magic Lantern enables 14-bit RAW CinemaDNG on 5D

thanks skital and squig!

i wounder if it will work for rebel line someday, that would be even cheaper than bmpcc, and most of my lenses are for canon, so i don't need to spend additional money on glass.

edit: squig, you could try "wine" for windows emulation..thou i never tried it as i'm not on mac.


@Ted "exe" is a windows only executable file...naturally.
 
Last edited:
You must be a happy man, heh Anthony?

It hasn't really hit me yet but wow how cool, I knew it would come one day just thought it wasn't gonna come in time for the first feature. I've had a couple of crashes switching between screens but it's been recording so far without a hiccup. The 64 terabyte raid is going to be a bit of an investment but it will be worth it. Who needs a 1DC when you can get a 5DR.
 
thanks skital and squig!

i wounder if it will work for rebel line someday, that would be even cheaper than bmpcc, and most of my lenses are for canon, so i don't need to spend additional money on glass.

edit: squig, you could try "wine" for windows emulation..thou i never tried it as i'm not on mac.


@Ted "exe" is a windows only executable file...naturally.

There's a dev already working on the 600D

Wine oh gawd, I had to use that with the GF1 hack, painful. Oh well wine it is I suppose.
 
* for those still wondering about image quality, comparison of ML-RAW vs a downsampled RAW still:
http://www.similaar.com/aarchive/800_lv.jpg
http://www.similaar.com/aarchive/800_st.jpg
http://www.similaar.com/aarchive/3200_lv.jpg
http://www.similaar.com/aarchive/3200_st.jpg
Nearly as sharp, nearly the same DR (just a bit more noise in the shadows).

* line skipping: I'm not sure the 5D3 is line-skipping or not; the image we're getting could be achieved by line-skipping or by in-sensor pixel binning; if you compare the noise, it would seem like it is line-skipping (noise similar to that of a RAW still that is first downsampled 3:1 vertically using nearest neighbor, then 3:1 horizontally using bicubic); but an increase in read-out noise because of the in-sensor binning could also give similar results; in any case, this is different on the 5D2, but on the 5D3 I haven't seen any aliasing/moire issues

* the PC utility is not debayering the image (if it is debayered, it is no longer RAW); it is rearranging the data and putting the correct headers and footers so standard software can read it
 
I'm guessing for backup, we could convert to cineform raw?

This is amazing. Looking forward to following developments further
 
* the PC utility is not debayering the image (if it is debayered, it is no longer RAW); it is rearranging the data and putting the correct headers and footers so standard software can read it

Ahh ok gotcha, too much going on today for my buffer to write.
 
I'm guessing for backup, we could convert to cineform raw?

the problem with CFR is that CineForm's debayering methods are a lot worse than what Adobe Camera RAW uses, so, even though compression itself is preserving your footage quite well, the end result is a lot worse. You do get 10x faster playback times (15fps instead of 1.5 fps). Check my tests with the BMC here:
http://www.similaar.com/foto/blackmagic-workflow/index.html
 
I don't know whether it's lineskipping or don't and to be honest I don't care, the resolution has gone from 700 lines to something like 900 or more, it's got the detail of a downscaled RAW still, we're talking C300, 1DC killer here and with a fast card you can shoot 2k RAW! With anamorphic lenses it might be able to manage 4k! But I could care less about 4k. All I ever dreamed of was 2k RAW. Who says dreams don't come true, the MK3 RAW well and truly is a baby Alexa except it shoots VistaVision!

I'm playing with it now and I'm getting continuous 1080p recording with a 600x Lexar card. I can't do anything with the files until someone writes a mac debayer utility :cry:

There's no codec as such just RAW data which has to be debayered with software then output to DNG, CinemaDNG, or JPEG. The software is still in development, everything is still in development.

Can't wait for a stable release for the MK3! I was really disappointed going from the MK2 to a MK3 with the video sharpness. I was already looking for going to a BMCC but I like the fact that a 5DIII has an internal removable battery and flashcard.
 
the problem with CFR is that CineForm's debayering methods are a lot worse than what Adobe Camera RAW uses, so, even though compression itself is preserving your footage quite well, the end result is a lot worse. You do get 10x faster playback times (15fps instead of 1.5 fps). Check my tests with the BMC here:
http://www.similaar.com/foto/blackmagic-workflow/index.html

wow, yea... quite a difference, especially on that 2nd shot
 
Can't wait for a stable release for the MK3! I was really disappointed going from the MK2 to a MK3 with the video sharpness. I was already looking for going to a BMCC but I like the fact that a 5DIII has an internal removable battery and flashcard.

Join the club, it was an improvement on the MK2 but obviously not anywhere near as improved as it could have been. Some people hate the form factor, I love it. I've got a scene in my feature that takes place on a remote mountain in a snowstorm, with any other camera I'd have to shoot it in the studio, but now I can shoot it on the mountain.
 
wow, yea... quite a difference, especially on that 2nd shot
Yes, you have to suffer the DNG workflow but it's worth the pain


****

I was sending this to Squig on a PM, but I thought it would be useful to others too:


If I had to edit a feature shot on 5D3-RAW, this is what I'd do:
* build a fast workstation with relatively standard hardware: an intel 3470 or 3770 with 32GB of RAM, an SSD drive and a single 3TB internal HDD
* put something like this in it: http://www.ebay.com/itm/New-3-5-SAT...Rackmount_Cabinets_Frames&hash=item232a14247e
(I love my case, and it came with one of those already in place: http://www.silentpcreview.com/cm-silencio550)
* buy an army of big HDD drives (right now, for me, they would be Western Digital 3TB drives, my preferred brand is Samsung but they're not in good shape lately; I would avoid Seagate because of personal bad experience)
* divide your project into several chunks, put each chunk on a drive, label the drives (and their backups), swap HDD when you want to work on a different chunk

If you use 6 chunks of 3TB each, with a full backup that's updated weekly and a half-size backup that only has the original footage, you need 15 drives, total cost of storage around $2K, and that's for a 100 minute feature with a very generous 20:1 shooting ratio and a 2:1 post-overhead ratio.
It allows several people to work at the same time on the project... as long as they're working on different chunks. Everybody is working locally on a SATA drive (no additional controller to add latency), so it's quite fast (even compared to an external RAID).

THIS REQUIRES THAT EVERY PERSON TOUCHING THE DRIVES IS A VERY WELL ORGANIZED PERSON, OTHERWISE IT WILL BE A NIGHTMARE.
I know I could pull this off, and I also know people that would bring this to disaster in less than a week.
 
Last edited:
I'm cutting it on my quad core 17" macbook pro with 16Gb of ram and a 480Gb internal SSD with a reasonably well calibrated 24" samsung LED display. I'm gonna get 4x 16 terabyte esata raid 5 arrays @ $1600 each. Cutting proxies in FCPX, grading in Adobe raw and filmconvert. That's the plan so far but there may be some changes.

Where can I find these well organised people you speak of?
 
attachment.php
 
Where can I find these well organised people you speak of?
Rare as unicorns, I know :)

And I don't think Magic Lantern will help you with that.



edit: btw, for what you describe, an eSATA dock would work just like the internal SATA one I would use in a tower: http://www.amazon.com/Thermaltake-BlacX-eSATA-Docking-Station/dp/B001A4HAFS/ref=sr_1_22?ie=UTF8&qid=1368442842&sr=8-22&keywords=3.5"+dock+esata
 
Last edited:
I'm a little puzzled (And a lot exited!)

Andrew at EOS HD is saying the format is 14 bit YUV 4:2:2 Uncompressed, but surly Raw is Raw, not 4:2:2 YUV anything?

Sorry, I might be being a bit dim here (Not the first time), but I only just saw this thread and jumped to the last few pages.

I could be persuaded to cancel my MFT BMCC order.
 
I'm a little puzzled (And a lot exited!)

Andrew at EOS HD is saying the format is 14 bit YUV 4:2:2 Uncompressed, but surly Raw is Raw, not 4:2:2 YUV anything?

Sorry, I might be being a bit dim here (Not the first time), but I only just saw this thread and jumped to the last few pages.

I could be persuaded to cancel my MFT BMCC order.

Because Andrew Reid, while having a very nice blog with updates, doesn't have enough technical background. He's suffered from foot-in-mouth disease before.
 
Yes, you have to suffer the DNG workflow but it's worth the pain


****

I was sending this to Squig on a PM, but I thought it would be useful to others too:


If I had to edit a feature shot on 5D3-RAW, this is what I'd do:
* build a fast workstation with relatively standard hardware: an intel 3470 or 3770 with 32GB of RAM, an SSD drive and a single 3TB internal HDD
* put something like this in it: http://www.ebay.com/itm/New-3-5-SAT...Rackmount_Cabinets_Frames&hash=item232a14247e
(I love my case, and it came with one of those already in place: http://www.silentpcreview.com/cm-silencio550)
* buy an army of big HDD drives (right now, for me, they would be Western Digital 3TB drives, my preferred brand is Samsung but they're not in good shape lately; I would avoid Seagate because of personal bad experience)
* divide your project into several chunks, put each chunk on a drive, label the drives (and their backups), swap HDD when you want to work on a different chunk

If you use 6 chunks of 3TB each, with a full backup that's updated weekly and a half-size backup that only has the original footage, you need 15 drives, total cost of storage around $2K, and that's for a 100 minute feature with a very generous 20:1 shooting ratio and a 2:1 post-overhead ratio.
It allows several people to work at the same time on the project... as long as they're working on different chunks. Everybody is working locally on a SATA drive (no additional controller to add latency), so it's quite fast (even compared to an external RAID).

THIS REQUIRES THAT EVERY PERSON TOUCHING THE DRIVES IS A VERY WELL ORGANIZED PERSON, OTHERWISE IT WILL BE A NIGHTMARE.
I know I could pull this off, and I also know people that would bring this to disaster in less than a week.

Don't forget the LTO tape drive for backup.
 
Back
Top