-
-
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
[question] Unable to open the video #1291
Comments
Did you download the Linux version from Releases or from another source (maybe it was not built with opencv)? Edit: #1215 |
The version I have is the downloadable one from the home page |
[11:12:41.285857][fatal] Unable to open the video : /Volumes/scratch2/a_HDR_inventory/bronte_creek_pp_house/0_source/photogrammetry_source/GX010850_prores.mov note the file extension is .mov and not .mp4 btw the new release is now available. |
Same for me :( I tried several videos with Ubuntu 18.04 when the 2020.1 release came out. I gave up and wrote my own external script for frame extraction based on sharpness and optical flow. |
@isolin Sorry, I don´t know why it did not work for you, i don´t have a linux environment at the moment to test this. TrojanGoats problem could have potentially been cause by the wrong file extension (unsupported codecs could also be a cause), but there have been a few reports of problems on linux in general (#1215 , #955) but nothing pointing to a bug so far (more likely to unsupported video file types/codecs/naming conventions). Could you share your script to provide an alternative for other users like you facing the same problem? |
I think I would be quite ashamed to publish it in the current state :) it's really messy and slow. But I will see what I can do. |
I tried the v2021 version, it's still the same error: "Unable to open the video" |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue is closed due to inactivity. Feel free to re-open if new information is available. |
stat("/home/mio/Downloads/DJI_0019.MP4", {st_mode=S_IFREG|0755, st_size=3759987582, ...}) = 0 ... stat("/home/mio/Downloads/Meshroom-2021.1.0-av2.4.0-centos7-cuda10.2/aliceVision/lib/libopencv_videoio_gstreamer*.so", 0x7fff0cce00b0) = -1 ENOENT (Bestand of map bestaat niet) ... stat("/home/mio/Downloads/Meshroom-2021.1.0-av2.4.0-centos7-cuda10.2/aliceVision/lib/libopencv_videoio_intel_mfx*.so", 0x7fff0cce00b0) = -1 ENOENT (Bestand of map bestaat niet) ... stat("/home/mio/Downloads/Meshroom-2021.1.0-av2.4.0-centos7-cuda10.2/aliceVision/lib/libopencv_videoio_msmf*.so", 0x7fff0cce00b0) = -1 ENOENT (Bestand of map bestaat niet) |
I still have this problem in 2024 with the version of Meshroom downloaded from the website. |
The bot closed this but it is still an issue. Can someone re-open it? |
Same problem with 2023.3.0 on Ubuntu 22.04. EDIT: Made a new video with my Sony Alpha 57 camera, also H.264 format, same problem. |
I find it frustrating that this issue is marked "question" and the linked one #1215 is marked "bug" but closed. Neither issue solves the problem. Please reopen one of them as a bug, since the problem has persisted now for years. Surely there are more people out there that would like to use video (and the automatic feature to extract good frames from video) and use Linux? |
I have the same problem on Meshroom 2023.3.0 and Ubuntu 22.04.2 LTS: The video is H.264 and it plays fine using the video player. I have also tried to convert it to MPEG-4 and MPEG-2 but the same error is reported. |
Description
Keyframe selection not working in Ubuntu.
I'm using footage from GoPro Hero 9 .MP4 file
I've also tried dnx and prores codecs and they don't work either.
Meshroom log reports: "Unable to open the video"
Using the same footage, it will work in windows.
To Reproduce
Steps to reproduce the behavior:
[11:12:41.285857][fatal] Unable to open the video : /Volumes/scratch2/a_HDR_inventory/bronte_creek_pp_house/0_source/photogrammetry_source/GX010850_prores.mov
The text was updated successfully, but these errors were encountered: