[SOLVED] Issue using raw DNG files from Phantom 4 Pro/Adv

Hi,

I am noticing a very big issue using the raw images from drones camera.

The cameras resolution is 20MP and the resolution is 5472x3078. The raw image in windows and in RC is showing 960x540 for some odd reason so its really skewing the alignment/reconstruction and texturing.

This seems to be a common issue with windows and these raw DNG files but when you load it in photoshop or any imaging software you see the full image.

The only work around right now is converting them to JPG’s and using those in RC but I would rather use the raw images.

Heres an example image:
https://drive.google.com/drive/folders/ … FdqcEh5SG8

THanks

I’ve just started using raws, but I gathered that if you use rwas directly in any software, then the standard settings of the camera are used for developing them within the software. That means that apart from distortion correction of the camera, you would end up with the same (or not much better) result as camera-jpegs.
Developing them in external software gives you much more control of the result, although of course you can’t tweak each and every image anyway, so there will always be some degree of automization/generalization.

Just looked at your sample - you are aware of the difficulties of the object/shot, right? :slight_smile:

Yeah I completely understand but my problem with this test is texturing and constructing in high or normal detail.

With this raw the 75 images took a few min to complete but th didn’t give that great of result on the car and the texture detail was awful no matter how I unwrapped and tried to get the most utilized textures. Oh and there is no distortion correction for this camera, it’s a flat image haha

Once I converted it to jpg the constructing detail tool 10x as long and I was able to get great detail in the textures.

Just hoping the dev’s can figure out why this is and patch something so I can use the raws =).

Good to hear it worked!
But I am surprised a bit due to the reflecting surface.
Mind sharing some screenshots?

And just out of curiosity:
What are you hoping to gain from using raw directly?
Just time saving or also bit depth?
Although your sample doesn’t seem like it has a very wide range…

Look what I found:
Raw files workflow and resolution

This was more of a test to see how well the drone works for photogrammetry and granted the images were not the most optimized, I am still playing around with the manual settings on the camera.

I was just trying to state that the DNG files are not working correctly. I get the detail when i open the pictures in windows 10 though the resolution is stated incorrectly. The detail is there in the image, its just RC is not registering the image in its full resolution and raw.

Should I be always using tiff files? instead of raw? I just assumed using raw was best for all work as you are keeping as much detail as possible in the image.

It all depends - on many factors.
I guess when you want a car for your granny so she can get some groceries, you would not buy her a ferrari.
Or when you want to plough a field, you might want something bigger than a smart car.

This thread opened my eyes a bit (mostly in astonishement): http://forums.culturalheritageimaging.o … he-cooked/
Also, here we discussed the use of jpegs: Accuracy and speed. I’m impressed. Might also be interesting because it starts with an awesome model made with images from a P4P.

I personally think that for most purposes, jpegs are sufficient. If you shot raws, you can also develop them into jpegs (at 90% quality or higher of course). The difference to Tiff is small, especially since RC does not support 16bit - although I’m not 100% positive if that is only for export or also for import. So using raws directly might make sence when you have a very high dynamic range, meaning bright sky as well as deep shadows (e.g. shooting inside a cave towards its opening or vice versa). If you have a well lit object (like your example), the dynamic range is not too great. Just look at the histogram of the raw - if the whole width is covered by the curve, you will lose information transforming it into 8 bit, if it is only about half, then not. At least that is how I understand it…

Mike Simone wrote:

Hi,

I am noticing a very big issue using the raw images from drones camera.

The cameras resolution is 20MP and the resolution is 5472x3078. The raw image in windows and in RC is showing 960x540 for some odd reason so its really skewing the alignment/reconstruction and texturing.

This seems to be a common issue with windows and these raw DNG files but when you load it in photoshop or any imaging software you see the full image.

The only work around right now is converting them to JPG’s and using those in RC but I would rather use the raw images.

Heres an example image:
https://drive.google.com/drive/folders/ … FdqcEh5SG8

THanks

Hello Mike,
this looks like a problem with image codecs.
Do yo have the latest codec for this image fromat installed?

Ill try downloading the Adobe codec from 2012 since they broke all their links on their website…

Hopefully that solves the problem, but why would RC care about a windows codec? does it not use its own built in reader?

Was that always the case with your installation of windows or is it new?
Did you install a custom codec once?
I read somewhere that windows updates can screw those up and they need to be reinstalled.

I have issues with my LX100 raws, which do not seem to be supported by windows Panasonic RW2 support?
Trying to find a solution, I came across this custom codec: Panasonic RW2 support?
Maybe it could help to solve your problem too, although I still hesitate to try it out.
Have you heard anything about it yet?

This is a problem with RC importing the file.

I have installed the latest Adobe codec 2.0 DNG for windows and its fixed all the problems with not having the right resolution and pixel format etc.(Still broken in RC)

I am just letting the developers here know that there is an issue with this raw format.

Hi Mike Simone

Its the same problem like with SONY RAW files ( on some cams, not all of them = Ar7 I. own experience ) RC just take what Windows RAW lib can read so its not RC issue but the RAW ( Windows ) libary. in SONY case it was a issue that SECONDARY image ( preview file - stored as a JPG ) is stored next to RAW data and as its a bit diff RAW format what could be NOT decoded so it can read only the secondary data.

To solve this ask the DRONE manufacturer on updated RAW libaries for your Windows version. Or you will be forced to develop the RAW data and use them as TIF of JPGs.

Mike Simone wrote:

This is a problem with RC importing the file.

I have installed the latest Adobe codec 2.0 DNG for windows and its fixed all the problems with not having the right resolution and pixel format etc.(Still broken in RC)

I am just letting the developers here know that there is an issue with this raw format.

Hello Mike,
thanks for letting us know.
We will take a look at it.

Perhaps others might have found a similar workaround, but I USED to convert my RAW images into JPGs for RC solving, however,  after reading that it was “possible” but finding I was unable to download/install the microsoft camera raw codecs, I opted to spend $10 per seat for

www.fastpictureviewer.com/codecs/  and THAT works like a champ so I can directly load Inspire RAW DNG frames or Sony raw frames into Reality Capture,  plus my windows machine can view the images without having to load them into PhotoShop or Bridge or Lightroom any more.