FFAStrans forum

Hello,
I understand your demand but I think it is really useful to try to make this own workflow alone. In this way, you have to look for the better solution and you learn so much.
I've create many workflow with some very simple and other extremely complicated. Not sure some examples can help because you have ALWAYS to edit a workflow to match with your own workflow. If you understand the "structure" of FFASTRANS, create a encode workflow is so easy that you don't need example.
So, it's that I think but maybe I'm wrong
CHeers.

Benjamin

Benjamin made some extremely good point from perspecitve of a workflow engine.

Besides that i have to say that any "encoding" related topic is very problematic. As we all know, ffastrans current messaging targets brodacast related need, so most or all users are from the broadcast industry.. it also clearly states that it is about FFMPEG AND AVISYNTH. But what most users don't know is the licensing situation.
Did you know that you can only use e.g. the H.264/x.264 encoding of ffmpeg (and therefore ffastrans) in case you produce freely available content (that excludes most content of public broadcasters), except you are using nvidia(nvenc) ,intel(quicksync) or amd(vce) for encoding?

Sure it would be cool to add all the interesting encoding profiles that broadcasters typically invest multiple 10 thousand dollars into but those "web delivery" examples would only hit 1-5 percent of users of ffastrans, how much sense does that really make? ...the more instructions how to do illegal stuff we make, the more we are in the target line of MPEG-LA.

OK, sorry for the hard words but it just had to be mentioned. Maybe we can use this platform to finally find a way to get out how and if there is a way to get a license for commercial use of open source implementations of protected codecs.

[EDIT] Here the related comments from ffmpeg maintainers, read the 2 last questions: https://www.ffmpeg.org/legal.html

Cheers,
emcodem