Messages

[What can we do, if already upgraded with the 1.0.4 firmware. Will we have a ML for that firmware... Thank you]

What can we do, if already upgraded with the 1.0.4 firmware.   Will we have a ML for that firmware...  Thank you   

There is no way to downgrade to 1.0.1. So you just have to be patient.

... and basically the current status is unchanged. THEORETICALLY the dots should be removed, but PRACTICALLY a few of them survive. I guess I'll release the new version anyway, because I need your feedback and a few more sample pictures to hunt down the bug...

Thanks for this new version.

I made a few tests and it seems to work perfect with rawmagic.

I'll make more tries this evening after work.

Were can i get the lates build?

Read the first post.

Well if I use raw2dng and then PDR I can't edit it in Davinci Resolve. Is there a way how to get rid of pink mess and also convert it to CinemaDNG?

Yes, just be patient. RawMagic is producing CinemaDNG. Mixer2 and foorgol are working to adapt the tool for it.

Short update on the dot remover:

  * Changed algorithms to support EOS M better

  * Fine-tuning EOS-M dot location database

  * First promising tests on DNGs created with RawMagic; used talosectos' file for testing and have almost all dots removed


Mixer2 and me are currently optimizing and testing, but we should have a new version in a few days!

[Edit:]

I just took a short clip at that resolution and it removed the dots for me. Did you maybe select EOSM by mistake?

Edit: But then when I tried it on YOUR file, it did what it did for you, made it 10 times worse.

but if I open your original in Rawtherapee and apply the dead pixels profile, it acts normally (for that program)

Ok thanks for your answer

The only thing I noticed at a first glance is that your original image contains weird meta data. Looking at the tags model, manufacturer, software, bits per pixel and DNG version, I would expect "Canikon", "Canon", "Magic Lantern", 14 and "1.3.0.0", whereas your file reports nothing, nothing, "Rarevision RAWMagic 1.0", 16 and "1.1.0.0".

What's most striking is the difference between the "normal" 14 bit color depth and the 16 bit in your file.

So, frankly speaking, your source file doesn't seem to come straight from a 650D. Is that true?

My program is somehow tailored to the 650D-files. Maybe this is part of the problem.

Ok, I think that the problem comes from the tool I used to convert the raw (RawMagic), this part was done on my Mac.

I'm going to try with another tool and let you know the result.


Edit:
I've tried with raw2dng, and this time it works perfect.
I should have check that before, sorry 

Thanks foorgol!

Second edit
The matter is that RAWMagic convert into CinemaDNG files (that can be used directly into Resolve) whereas raw2dng convert into photo-dng.
Some differences between the two formats that cause problems with the PinkDotRemove tool and CinemaDNG files.

Hi there,

Thank you for the great job 

I've got a problem with the tool (I'm certainly doing something wrong  ).

Here's the link for an original frame:
https://www.dropbox.com/s/y3jb96kyp6sc2zs/M26-1615_00000.dng
The resolution of the raw video was set at 1472x626 (2.35:1), shot with the ML build from 2013-06-26.

When I use the tool (on W7), I get this: https://www.dropbox.com/s/nna78o9qw1r4xry/_M26-1615_00000.dng

What am I doing wrong?