alicevision / Meshroom

3D Reconstruction Software
http://alicevision.org
Other
11.15k stars 1.08k forks source link

software not importing photos #208

Closed vettorazi closed 5 years ago

vettorazi commented 6 years ago

Machine: surface book 2

error: in the startup of the software:

lugins loaded:  CameraCalibration, CameraConnection, CameraInit, CameraLocalization, CameraRigCalibration, CameraRigLocalization, ConvertAnimatedCamera, ConvertSfMFormat, DepthMap, DepthMapFilter, ExportAnimatedCamera, ExportMaya, ExportUndistortedImages, FeatureExtraction, FeatureMatching, ImageMatching, ImageMatchingMultiSfM, KeyframeSelection, MeshDecimate, MeshDenoising, MeshFiltering, MeshResampling, Meshing, PrepareDenseScene, Publish, SfMAlignment, SfMTransform, StructureFromMotion, Texturing
[QtOIIO] Plugin Initialized
[DepthMapEntity] DepthMapEntity
Failed to download scene at QUrl("")

on the import:```

ERROR:root:Error while building intrinsics : Traceback (most recent call last): File "f:\tmp\meshroom\meshroom\ui\reconstruction.py", line 384, in buildIntrinsics File "f:\tmp\meshroom\meshroom\nodes\aliceVision\CameraInit.py", line 129, in buildIntrinsics RuntimeError: CameraInit failed with error code 3221225477. Command was: "aliceVision_cameraInit --sensorDatabase "C:......."

rgoupil commented 6 years ago

I had the same problem here, on a workstation running Win10 with 16Go of RAM. I was trying to import several images of 2988x5312. When I downscaled them to 2656x1494 it could correctly imported them. I assume this is related to the amount of RAM and the size of your image (5312x2988x3 != 45Go vs 2656x1494x3 ~= 11Go).

vettorazi commented 6 years ago

Ohh good idea! I tried import one by one and didnt work. Downscale could work, i will test it. Thanks!

Em seg, 27 de ago de 2018 07:48, rgoupil notifications@github.com escreveu:

I had the same problem here, on a workstation running Win10 with 16Go of RAM. I was trying to import several images of 2988x5312. When I downscaled them to 2656x1494 it could correctly imported them. I assume this is related to the amount of RAM and the size of your image (5312x2988x3 != 45Go vs 2656x1494x3 ~= 11Go).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/alicevision/meshroom/issues/208#issuecomment-416188335, or mute the thread https://github.com/notifications/unsubscribe-auth/AHR-j8nAzdLLEEYsDqo-ZkR8elzupdyxks5uU855gaJpZM4WM1Bw .

vettorazi commented 6 years ago

hey! thanks! worked great!

yann-lty commented 6 years ago

Image size should not be a problem to initialize the project. They are never all loaded simultaneously in memory (only 3 at the same time). Could you share a few images from your (original scale) dataset to see what goes wrong?

McSmithe commented 6 years ago

It did not import images for me as well, but if I just open them and resave them it did. Doesn't need to resize, something about the image format from the phone makes it break

natowi commented 6 years ago

I had the same problem, but figured it out: The import module from AliceVision seems to be really sensitive to corrupted image files. Some mobile phone cameras and small cameras like the CGO3+ from Yuneec produce images which are not valid. Most image viewers and editing software can handle minor inconsistencies. Use tools like Bad Peggy to check for errors in your image files. In my case it was "...extraneous bytes before marker 0xdb". To fix this problem, you need to bulk convert your dataset (this is why downscaling worked too). You can use IrfranView File->Batch Conversion or Imagemagick. Make sure you set the quality to 100%. Now you can add the images to Meshroom (assuming the camera is in the sensor db).

Maybe the Meshroom image importer will be more tolerant with corrupted files in the future.

rgoupil commented 6 years ago

Interesting, I will check my original pictures if I still have them. The importer should probably be more exlicit when hitting this kind of issue: "could not parse image" would already be a much better error message than the current one IMO.