Messages

That's good to hear! There is a very simple dead pixel detection/hiding I put in a while ago when I was doing something with raw from a 60D. I'm glad it's still working.

In old version 1.1.2 i've tested but bad pixel still exist. This is the news of the day man. I was waiting this fix since raw shooting is released.

[finally]

FOR DAVINCI RESOLVE WORKFLOW:

with last version of Mlrawviewer (1.1.3) finally you export in cdng (16 bit) and import in resolve without any bad pixel.
Tested.

1.1.3 now available

• Now exports 16bit DNGs with per-frame metadata. Should directly import into PremierePro as well as Resolve/AE.
• S key switches between different anamorphic squeeze ratios (viewing only)
• MOV/DNG icon made clearer
• Mark line red instead of white so it shows up in bright scenes

See top post: http://www.magiclantern.fm/forum/index.php?topic=9560.msg91165#msg91165

GREAT JOB!!! this version resolves the bad pixel problem in Davinci Resolve importing (cdng) with some camera. (60D)
Thanks. 

baldand can you integrate the code posted by escho here http://www.magiclantern.fm/forum/index.php?topic=9700.msg98302#msg98302 for dng extraction? This tool removes cold pixel usefull in Davinci Resolve workflow with some cameras (like 60D) affected by this problem.

OObner absolutely agree with you.

I've compare a raw shot at 960x540 hd with a full hd H.264 shot.
Rescaling the raw to 1080, two shots have the same quality but raw contrast (in small detail) was much better then h.264.

default setting. It just a test for compare ACR or Resolve workflow.
In davinci camera raw is set on Clip, As Shoot, Rec 709, sharpness:10.
These artifacts looks like the highlight chroma fringing in old raw_rec module.

If i set BMD log and split chroma and luminance (with layer node), apply a blur on the chroma node and well...i achieve a little suppression of these artifacts (however visible at 400 % zoom)
But the ACR quality is better. Why?

I've tested with cs2x2 or cs5x5 but no changes.

Remark: you may get one or two strange pink frames at the beginning of a shot, just cut them out in resolve or your NLE.

I haven't pink frames. But strange chroma artifacts.
See this http://www.magiclantern.fm/forum/index.php?topic=10669.0
The problem of bad pixel in my case is fixed by a special version of raw2dng developed by escho.
http://www.magiclantern.fm/forum/index.php?topic=9700.msg98302#msg98302

I've tried to work with mlv file, dumped and import before in After Effects (left) and after in Resolve (right).
But in Resolve i've these strange artifacts on image. Is there someone can explain me the problem?

Conformed and graded on davinci resolve, and then upscaled to UHD (3840x2160) with some tweaking on resolve "Image Scaling" section. otherwise, no effects or sharpening were applied.

Can you post your workflow? i've tried to work on resolve but i've strange pink artifacts.

escho your code resolves definitely the 60D bad pixel problem with raw shooting. (without ACR workflow - i use davinci Resolve).
But I would use new MLV rec module and chroma smoothing function included in mlv_dump doesn't fix the pixel.
If you (or someone) could include your code in mlv_dump, make converting process more easy. (without generating raw and reconvert in dng)

It's strange. The correct shutter angle with 1/25 frame interval (25 fps) and 1/50 exposure is 180° according this:

Shutter Angle = (exposure Time/frame interval) * 360

FINALLY 60D users can work with resolve.

This modified version of raw2dng by escho http://www.magiclantern.fm/forum/index.php?topic=9700.msg98302#msg98302 works great. In my case it removes all bad pixel.

Another solution is mapping the bad pixels in a external file and apply an interpolation filter effect directly on resolve (OpenFX):
http://www.playtool.com/pages/pixelpatcher/pixelpatcher.html

LV_AF_RAW is not necessary anymore. 

Marekk can you try this solution? If you believe this is the definitive solution at the moment, could you post it on first thread?

high temp for me too  with stable release or october night build i've no problem (global draw ON with histogram only)

Seems normal to me. The degrees are converted from that previous number.

Then this value is normal or it is a malfunction in my camera and could overheat?

Hi guys. With last night build my camera reaches over 63 °C (marked in red to the top-middle bar).
With stable realease 2.3 the raw temperature is around 175-180.

Is it normal? Or it is a problem of my camera?

hi guys. With last night build my camera reaches 63 °C (marked in red in the top-middle).

It's normal?

if you want work in resolve follow this:
1. convert raw file with raw2dng
2. import file in after effects as raw sequence in ACR but without any changes
3. export the sequence in apple pro res 422 or any lossless format
4. import your video in resolve (you can't use cameraraw tab i think)
5. Grade your shot
6. Export final video

This workflow is too long and frustrating for me. For now ACR is only solution.

No solution for this problem yet then no way to use resolve without ACR processing before.
Resolve ver. 9 (and 10 too) doesn't include bad pixel opcode like ACR.   

hey guys updating my 60D to last version of ML, the temperature indicator shows over 60 ° C and changes in red color (in h264 shot). Is it normal?
What is the normal sensor temperature for this camera?

as you can see i have a lot of bad pixel there is a way to remove them?

Bad pixel is a common problem not resolved yet. Only way to hide these pixels is working in adobe products (After Effects or Photoshop).
Please post your workflow.

P.S. (i'm italian too, contact me in pvt)

just released beta version of davinci resolve 10. But no badpixel opcode support. The badpixel problem still exist and no chance to change workflow from ACR to resolve. 

UPDATE

no more pink highlight with resolve 10 beta. This is a good news. But with lv_af active, too much artifacts and with lv_af off...bad pixels.
Is there some c programmer able to remove this last (but very annoying) issue? I'm sure that A1ex can explain to him a possible solution.

I want share with you this fantastic resource. It is a complete basic tutorials of Resolve (from interface to delivering). Hope this help.

http://ae.tutsplus.com/tutorials/workflow/davinci-resolve-fundamentals-part-1/

What's the benefit of using Resolve over Lightroom?

Resolve is a professional color correction software oriented to video. It has many feature like tracker, power window designed specially to have more control on your project. Lightroom is used for still photo. It works good anyway. However the really difference is in operator and not in the software ;-)

I've just installed Davinci Resolve. I have to figured out how to "develop the raw".

Imported the DNG as sequence, playback it's smooth (just 7s), much better than expected with an AMD card. But when I sized-up the preview, got this result with ML-RAW-60D-hourly_2013-07-12_13-00, Resolve 9.1.5
http://i.imgur.com/tXZ5oDZ.jpg

Lots of bad pixeles..

yes it isn't a problem of resolve. Your dng sequence is always full of bad pixel..but using ACR you can't see becouse the software automatically removes the bad pixels thanks to a special tag in dng file. Resolve doesn't support this tag then you see it again 

Is only 60D affected by this problem? in 5d mkIII this problem i've never seen.

I've got bad pixeles before with other builds and high iso. But latest test doesn't show "bad pixeles", I need futher test.

Wich version you use? You have no bad pixel with Resolve too? ACR remove bad pixel itself by opcode tag but resolve doesn't support this tag. Maybe you have bad pixel or stuck pixel but you can't see becouse you use ACR. Right?