unsilence fails if output path is in a new directory about unsilence HOT 4 CLOSED

I think I leave it like it is, as it seems to be the default way this is handled.
Also, this avoid typos, where you tried to place the output file in an existing folder, but because of the misspelling, you created a new, unwanted folder that you need to deal with later.

from unsilence.

I would argue it is very much standard/expected behaviour for tools like this to only function if the output is in an already existing directory.

Ffmpeg itself, for example, will also fail if you supply it with a path in a non-existent directory

from unsilence.

Ok, maybe... I'm not used to this behavior.
Compilers, for example, create /build if it doesn't exist. Same for tools like yarn with /node_modules etc.

from unsilence.

Close this issue if it is not to be changed.

from unsilence.