Messages

Ginger uses a simplified debayer in halfres to enable realtime playback. Maybe this explains the difference.  Also if you want to work in 32bit  depth in premiere you have to enable maximum bit depth and render at maximum bit depth for that sequence and then only use 32bit effects in that timeline. You can also use accelerated effects if you have a mercury playback enabled card because mercury accelerated effects work in 32bit.

Komputer Bay 1050X 128GB  I just ran 24 FPS  1920x1080 for a continuious 128.3 GB without a dropped frame, June 28 build, 5D Mark 3 global drawing off. This is a new card just released not to be confused with the previous 1000X 128 GB.

What about 25fps?

Works on my 5Dmk III too but there is a bug with the "aspect ratio frame" not placed correctly. Hopefully this will be corrected as development goes on.
Otherwise its a joy recording raw with my zacuto evf. By enabling and tweaking ML focus peak in combination with canon picture profile with digital sharpness turned up and zacutos own digital sharpen at value one I have no problems seeing where my focus is at. =)

Komputerbay 64GB Card continuous at 1920x1152 25fps

Bought two komputerbay 64GB cards both records 1920x1152 continous at 25fps =)

I will check this out

Hi Markus,

In theory, there is no loss of data.  The difference is that you are using my custom debayer and processing instead of Adobe Camera RAW's.  Most people consider ACR's debayer to be pretty good.  In my opinion, my debayer is pretty good too, but I might be a little bit biased.  (-:

Also, ACR does lots of other things without telling you.  In addition to debayering, it's also adding contrast, clamping your blacks, clamping your whites, sharpening, and reducing chroma noise.  If you want to see ACR without the extras and see a true comparison then you have to set these values:

From Basic:
Blacks: 0
Brightness: 0
Contrast: 0

From Detail:
Sharpening - Amount: 0
Noise Reduction - Color: 0

Btw, even if you decide that Ginger HDR is not for you and you would rather stick with ACR, I'd highly recommend that you always set blacks/brightness/contrast to zero.  Otherwise you're just throwing away good dynamic range.

Sounds good, will check it out tomorrow =). And great that I can turn all baked in settings off! The only thing that seems to be missing is a manual white-balance setting where I can type in kelvin numbers and a tint slider like in ACR. To pick a color will work for some clips but will be a frustrating way to work in the long run. All the rest of color correction and sharpening I prefer to do in one set of tools outside this solution. To have a two stage color correction workflow as with ACR is not a good way to do it. You have to start compensating for your secondary correction in dumb ways. But white balance and ceiling of course is great to be able to set before. And I guess the baked in functions might be useful to have as a temporary correction for editing. 

Awesome! Exactly what i was hoping for. Love native workflows! Is there any kind of quality loss to this process compared to ACR-import?

Have anyone tested if having a SD-card in the 5D MK III slows down CF write speeds? I guess it should not if you don't write to both but it would be nice to be certain. I would try it myself but it seems you need to load the software from SD in the latest versions.

http://www.canonwatch.com/why-you-should-better-not-use-an-sd-card-with-the-eos-5d-mark-iii/

All these solutions coming out is great now that we have nothing else but if we could get native support everything would be so much easier. The data rates would be within the bounds of a new harddrive for realtime playback. I don't know what kind of cpu power is required for realtime debayering but if they can do it on the r3d-files I bet they can do it on these raw-files. They wold have to write some code to get the dng-data from the raw-files but since this is a format that they are already supporting in i bunch of there programs i can't see that this would be too difficult for them.
This would be great even if you decide to edit with proxies because then you could just relink to the native files before export.

I tought it would be good for this to start before everything is finished. Maybe they would have some requests themselves on the format for this to work.

I just submitted a suggestion that Adobe contact Magic Lantern developers and exploring the possibility to implementing native support for these new 14bit raw-files. My dream would be a feature like the one they have for Reds r3d-files. If other people would send in similar requests maybe there is a small chance of this dream coming true =). I think publicity vice this is a great publicity opportunity for Adobe!

If you wish to do as I have the link below will take you to adobes feature request form.

https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

Some dreams come true  =)

When i get som time I will do that.

I love the alpha 2 with all the new features enabeld. But when recording a long clip testing the new version the second 4gig file was corrupted about 4 minutes in. Recording format 1080 All I-frames 25P. I could not copy this file to my computer even though it played around the corrupted part.
This could be unrelated with magic lantern but i have not come across this problem before and I have filmed a lot with this camera and SD Card.

Has anyone else had this problem?

Would it be easier to make this work if you set it all up in the menu and then just set the iso at auto iso mode? Like if I set up iso 640 in the magic lantern menu with a autoiso range of +-1 stop? (320-1250iso) and then the auto iso would be restricted to this range? 

A function that I would love was if you could have a auto iso mode that only went a number of stops from the one you set up in manual mode. So you could enable this mode and set a auto iso range in +-stops from the one you have selected. This would be great in combination with a mechanical iris in situation with extremely wearying light.