Skip to content

silences --threshold and --min-silence are accepted, ignored, and the defaults reported back as if they were the request #67

Description

@Railly

vcut silences --threshold -80 --min-silence 800 runs, exits 0, and reports the defaults back:

thresholdDb: -30, minSilenceMs: 250

No error, no exit 2, no warning that the flags were not understood. The command answers a different question than the one asked and looks like it succeeded.

Found while verifying #66: measuring dead air at the deadAir pass's own parameters required dropping to raw ffmpeg silencedetect, because the verb would not accept them.

This is the wrong-answer-without-warning class. An agent reading that JSON has no way to tell it measured at -30dB when it asked for -80dB, and every downstream number inherits the error silently.

Either parse the flags or reject them with exit 2. Accepting and ignoring is the one option that produces a confident wrong answer.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions