On Mon May 29 21:19:06 2023 +0000, Rémi Bernon wrote:
Applications have been seen building custom decoding pipelines by composing sources and decoders, because they can, among other reasons. Therefore we can expect applications to build encoding pipelines, for the same reasons. Is this really so stretched out? Anyway, there's even more reasons to do so with encoding, as you very often need to configure the encoder components to fit your needs. I'm confident that having individual components is even more a requirement there.
What I think is add something like wg_unknown(I not sure that its name should be) to wingstreamer which represent the muxer component. Then we have 3 components in winegstreamer:
1. wg_parser to demux and decode. 2. wg_transform to decode and encode. 3. wg_unknown to mux (and maybe encode).
Now, the question is: should wg_unknown contain encoding pipeline like wg_parser who contains decoding pipeline? If do, it behaves like a opposite of wg_parser, then maybe we could make use of encodebin plugin? If not, it only does mux stuff.