-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug] #601
Comments
I think this problem is related to your synthetic images. How to you generate these images? |
OK, I think the JPG files are corrupted (the file format or the metadata). Converting them to PNG works. |
Thanks for the quick answer. If the files are indeed corrupted, why could I then import either of them without errors? To me, this suggests that corrupted files are not the root cause. Maybe even that the two files are not corrupted, seen from a Meshroom point of view. |
The import module from AliceVision has problems parsing some "abnormal" image files (invalid file formats, custom/unexpected Metadata fields/values) Some cameras (also virtual cameras) use extra EXIF fields which cause an error when importing images to Meshroom. You could try to strip all uncommon EXIF information and add/keep camera, make, focallength only . (I think the 35 mm equivalent focal length in your image metadata can not be 35mm when the focal length is 35mm https://en.wikipedia.org/wiki/35_mm_equivalent_focal_length) What software and camera exporter do you use? |
I use a PBR render software. I set the software to write tif images. Afterwards, I add the specs of the virtual camera to tif file using the following home grown python function:
It took some time to figure out which meta data was acceptable by pyexiv2 and needed by Meshroom. But the tif+metadata have since then worked reliably in Meshroom 2019.1.0. It therefore came as a annoying surprise that the same files could not be imported in Meshroom 2019.2.0. It is easy to reproduce. Just download this zip with two tif images and drag and drop into both versions of Meshroom. You'll see that Meshroom 2019.2.0 does not accept these images simultanerouly and produce the bug I describe above. On a greater level, the lack of feedback from Meshroom is quite frustrating when trying to debug these kind of import problems. But that doesn't change the fact, that Meshroom is a great piece of open source software in my mind! BR |
I can import both tif images in Meshroom 2019.2 I get the following Metadata error message in the cli: CameraInit report: I´d recommend using ExifTool/ExifToolGUI to add the metadata. ExifTool is known to create valid metadata fields. |
It is odd you cannot reproduce. |
I just ran into this issue. For me, removing LensSerialNumber and BodySerialNumber "solved" the problem. Its like having a matching serial number stopped the image from being added to the list. |
Hi Heptazane, |
Meshroom uses the LensSerialNumber and BodySerialNumber to differentiate cameras/lens combinations (to avoid applying the same parameters for different setups). If you are using the same camera + lens for your dataset (or add a completely different model/make), you don´t need this info. |
@jensdk3, Here is how we create the UID for the input image: It should use the file date/time if the metadata is not there. So the UID should be unique for each image. So I'm not sure what is your issue coming from. Best, |
Describe the bug
I have a problem with getting more than a single image file to show in the Images Pane of Meshroom 2019.0.2.
If I drag and drop either one of these two files, the chosen image will show up in the Images Pane. But if I drag both of them from File Explorer, only one will show up.
To Reproduce
Steps to reproduce the behavior:
Open Meshroom 2019.2.0 in Windows 10
Drag the two attached images from File Explorer to Meshroom Image Pane
Error is that only a single image appears in the Images Pane
Expected behavior
I would expect both images to appear in Image Pane.
Screenshots
If applicable, add screenshots to help explain your problem.
Log
Terminal output when importing 1 of the two images:
Terminal output when importing both images
Desktop (please complete the following and other pertinent information):
Additional context
The problem is identical in Meshroom 2019.1.0
The text was updated successfully, but these errors were encountered: