Skip to content
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

KeyframeSelection: Flag outputExtension attribute when it is set to "none" for video inputs #2163

Merged
merged 2 commits into from
Aug 28, 2023

Conversation

cbentejac
Copy link
Contributor

Description

This PR follows #2141 and extends the validValue and errorMessage parameters to "Choice" attributes. It additionally ensures that the validValueChanged signal is emitted whenever the attribute's value is updated so it can be re-evaluated, even if validValue itself has not changed.

The outputExtension attribute from the KeyframeSelection node, which determines whether the selected keyframes should be written on disk (and the file extension they should be written on disk with), gets its validValue and errorMessage parameters to get flagged whenever a video input is part of the list of inputs while outputExtension is set to "none". Indeed, if it is set to "none" for video inputs, no frame will ever be written on disk and, as a consequence, no SfMData file will be written (since it needs a location of the frames on disk), meaning that whole score computation and keyframe selection process will have been done for nothing.

ChoiceParams can now also have their `validValue` and `errorMessage`
parameters.

The `validValueChanged` is also emitted whenever a parameter's value
changes. This ensures that the `validValue` parameter is always re-
evaluated when the attribute is updated, even if `validValue` itself does
not change.
If at least one of the inputs is a video, then the `outputExtension`
attribute should never be set to "none": if it is, no frame will ever be
written on disk, and as a consequence, no SfMData file will be written,
meaning that the whole score computation and keyframe selection process
will have been done for nothing.
@cbentejac cbentejac added this to the Meshroom 2023.3.0 milestone Aug 22, 2023
@cbentejac cbentejac self-assigned this Aug 22, 2023
@mugulmd mugulmd merged commit 2bea35d into develop Aug 28, 2023
2 checks passed
@mugulmd mugulmd deleted the dev/keyframeVideoOutput branch August 28, 2023 12:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants