unsilence fails if output path is in a new directory

[pilattebe]

Describe the bug
unsilence folder1/input.mp4 folder2/output.mp4 fails if folder2 does not exist.

To Reproduce
Steps to reproduce the behavior:

1. create folder1/input.mp4
2. run unsilence folder1/input.mp4 folder2/output.mp4
3. OSError: Parent directory not found

Expected behavior
It should create folder2.

Desktop (please complete the following information):

• macOS 11.0.1
• Python 3.9.0
• FFMPEG version 4.3.1

[alexkeizer]

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

[pilattebe]

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.

[pilattebe]

Close this issue if it is not to be changed.

[lagmoellertim]

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.