Output pipe is supportable but would require the entire output to be cached until the header has been updated. Shouldn't be an issue for the vast majority of use cases
chocolate42 opened this issue · comments
Output pipe has been implemented but only in a cache-entire-output way so that the header can be updated. An extra step would be a --fast-output-pipe option that disables MD5 and accurate blocksize min/max and frame size stats in the header, writing output frames to stdout as soon as the output queue has encoded them.
--no-seek allows the pipe to be a proper pipe that outputs ASAP, barring any bugs this is complete