-
Any help on telling me what I'm doing wrong would be appreciated.
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi @saripsis, TL;DR: setting the "Ouptut Extension" parameter to anything but "none" should fix your problem. By default, the keyframes are not written on disk, only the SfMData files are (one containing the list of selected keyframes, one with the list of frames that were not selected). Those SfMData files use the paths of the input frames, which are already present on disk when you use the Keyframe Selection with sequences of images. In the case of video inputs, the frames from the videos are not already written on disk, so the SfMData files cannot be written as such. The SfMData file containing the list of selected keyframes can be written if you select another option than "none" for the "Output Extension" parameter: the selected keyframes will be written on disk (with the selected file extension), and the SfMData will be correctly written (but the SfMData file containing the frames that were not selected will never be written for video inputs). In the next version of Meshroom, the "Output Extension" parameter will be highlighted if it is set to "none" while the input is a video, specifically to prevent running into this issue. |
Beta Was this translation helpful? Give feedback.
Hi @saripsis,
TL;DR: setting the "Ouptut Extension" parameter to anything but "none" should fix your problem.
By default, the keyframes are not written on disk, only the SfMData files are (one containing the list of selected keyframes, one with the list of frames that were not selected). Those SfMData files use the paths of the input frames, which are already present on disk when you use the Keyframe Selection with sequences of images.
In the case of video inputs, the frames from the videos are not already written on disk, so the SfMData files cannot be written as such. The SfMData file containing the list of selected keyframes can be written if you select another option than "none" for t…