You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A detector must be specified currently for scenedetect to perform any actions on the input. Ideally this should not be the case - a default detector should be chosen if one is omitted, and the user should be able to set it in the config file.
Solutions
Allow commands of the form:
scenedetect -i video.mp4 split-video
The default will be detect-adaptive, but the user should also have a config file option with the name of the detector to use, e.g. in the config file:
[global]
default-detector = detect-threshold
One particular issue I ran into when trying to fix this by handling this in the controller is that some erroneous commands still result in the input being processed, e.g.:
Scene detection proceeds due to the current design, and the error doesn't get printed until after detection was done and the video was split. The command should not run at all if any subcommand has an error when processing options, or an unrecognized subcommand is provided.
The text was updated successfully, but these errors were encountered:
Allow commands of the form `scenedetect -i video.mp4 split-video` for example.
Uses detect-adaptive as the current default.
TODO: Add a config option to control which detector to use.
Issue: #329
Usage examples have been greatly simplified in the upcoming version, and nearly all examples of commands can now be copied and pasted directly into a terminal.
Problem/Use Case
A detector must be specified currently for
scenedetect
to perform any actions on the input. Ideally this should not be the case - a default detector should be chosen if one is omitted, and the user should be able to set it in the config file.Solutions
Allow commands of the form:
The default will be
detect-adaptive
, but the user should also have a config file option with the name of the detector to use, e.g. in the config file:One particular issue I ran into when trying to fix this by handling this in the controller is that some erroneous commands still result in the input being processed, e.g.:
Scene detection proceeds due to the current design, and the error doesn't get printed until after detection was done and the video was split. The command should not run at all if any subcommand has an error when processing options, or an unrecognized subcommand is provided.
The text was updated successfully, but these errors were encountered: