Initially this thread was about my lv_rec module that allowed recording YUV422 and RAW video on an experimental basis.
In this module I found out a lot about the EDMAC (DMA controller) and wrote it down in our wiki. (http://magiclantern.wikia.com/wiki/Register_Map
Since then we were able to use this high speed engine to copy portions of the image into our own buffers.
Meanwhile alex refactored all the code and optimized buffering, so that we are able to record 14 bit raw bayer data.
the result is a module named 'raw_rec' which he highly optimized to get the maximum out of our beloved canon cameras.
Since then we are constantly trying to improve the usability.
Our focused target is the 5D Mark III, but the devs are porting it to other models as you can see (thanks 1%, coutts, nanomad)
Yet this code is EXPERIMENTAL. It will cause any random failures that lead from data loss to crashing cameras.
As you know, ML is very stable, but sometimes code at this early stage causes unforseen problems.
Prepare yourself for that before you go shooting. (a backup CF card, ML-free SD card)Key ingredients:
- canon has an internal buffer that contains the RAW data
- we understand the high speed DMA controller "EDMAC" a lot better now and know how to crop areas out of an image
- we know how to get the maximum rate out of the CF card and so achieve to get up to 90MiB/s
- we provided a reference tool that converts the Magic Lantern .RAW movie into single .DNG frames plus a MJPEG script
All together sums up to the most advanced 14-bit RAW recording system people can get for less than 3 kEUR.
We will prepare a full article as soon we see this code being stable enough for public testing.Again. This is EXPERIMENTAL, so:
- bloody beginners and non-geeks should not touch
the whole thing. wait until it is "beginner-proof". we will tell you on the website.
- you know that you are a bloody beginner, when you read the whole thread and you still cannot get it to work.
- DON'T be disappointed if it doesn't work or we figure out the whole thing is unstable and/or unusable
- NO, there is no manual yet
- NO, there is no all-in-one tool that fits every use case
- NO, we don't have tutorials how to use it
- NO, not all models are supported yet
- we are just at the moment testing how good it works and what we have missed and what to improve
- you are welcome
to post comparisons, experiences (both good and bad), or even deep analysis or just cool videos
- if you are a programmer and you see potential for improvements, grab the source and support As always we want to remind you of these things:
- Magic Lantern Team will not be responsible or liable for any kind of direct or indirect damage to your camera. (nothing new anyway)
- The software provided for download is not related to Canon in any way
- Do not contact Canon about issues related with this software
- Do not blame Canon for not-implementing this feature! Why? This is no feature that is stable enough so that a company like Canon would ever release.
- Prepare for footage loss due to frame drops, tinted frames, corrupted frames etc.
- THIS IS EXPERIMENTAL. Deal with it. Don't blame anyone.About sensor heating rumors:
The only thing that could get warmer is DIGiC and the CF circuitry, but i am sure that the power dissipation that reaches the sensor
through all that plastic housing will not have any noticeable temperature raise.detailed
: when doing that much DMA transfers and CF writing, we may cause a bit more current drain (which causes squared power dissipation)
but we do not encode any H.264 while recording, so we use less power there.
its *possible* that the CF writing will consume less energy than the encoding with H.264, which will result in *less* power consumption.
raw is being produced by the DIGiC for every single frame anyway. we "just" save it away.
still this is a *theory*, but i expect the consumption and the temperatures not to raise at all.
Currently i am working on a module that records YUV422 data to card.
This code will only work when compiled from repository (there is no release yet)
5D3: can record 1904x1274 @ 12.5 fpshere some example video:https://docs.google.com/file/d/0BwQ2MOkAZTFHdU1tR1pITXFVVXM/edit?usp=sharing
(not sure how to make it look better and not take 600MiB)here some sample images:https://docs.google.com/file/d/0BwQ2MOkAZTFHdFFsV1BGU0Nmd2s/edit?usp=sharing
there are three major options
- Frame skipping: record every n-th frame. choose 2 on 5D3 in 25 fps mode to record with 12.5 fps *continuously*
- Single file: save some processing time by writing a single file. you have to split it later on your computer. (maybe the 422 converters will somewhen support this?)
- RAW mode: not working yet, just saving gibberish
right now the module is not user-friendly. press start and it will record 2000 frames.
it will abort if the buffers are exhausted.
you can also abort by removing battery
All questions regarding RAW VIDEO POST PROCESSING
on any OS
All questions regarding RAW_REC MODULE COMPILATION/INSTALLATION/USAGE
And this thread here should from now on just be used for video results, and open discussion.
NOT for any installation or processing help.