[feature] stdout writing

[jamesb93]

Adds support for setting the output to stdout.

Interface isn't great and is not very "UNIX"y, however, it works.

For example, you can specify output like this:

fluid-noveltyfeature -source infile.wav -features stdout

This will write the values out with commas inbetween them.

---

Why?

The major benefit of this format is that you don't need to manage, cleanup and parse an intermediary file if you have the CLI tools embedded elsewhere. My selfish reason is to remove those needs from ReaCoMa. It would also facilitate viewing results more easily in the terminal if you want to prototype there fast.

[weefuzzy]

That seems relatively painless. Would suggest using -- as the marker for using std out, to be more unixy. And we should think about whether we'd want to enable input from stdin for pipey goodness.

[jamesb93]

That seems relatively painless. Would suggest using -- as the marker for using std out, to be more unixy. And we should think about whether we'd want to enable input from stdin for pipey goodness.

stdin is an idea! I think it would let you do, for example, ffmpeg -> flucomathing. In terms of using -- do you mean instead of stdout? AFAIK, and I am likely to be wrong here, -- signifies "don't read any more args" rather than stdout.

[jamesb93]

That seems relatively painless. Would suggest using -- as the marker for using std out, to be more unixy. And we should think about whether we'd want to enable input from stdin for pipey goodness.

stdin is an idea! I think it would let you do, for example, ffmpeg -> flucomathing. In terms of using -- do you mean instead of stdout? AFAIK, and I am likely to be wrong here, -- signifies "don't read any more args" rather than stdout.

Ah yes, but I see how it makes sense. Like if you want to tell git diff that foo is a path and not a commit with git diff -- foo. So -- kinda means, "no output file".