<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>aargh_aargh</author><text>Specification of ffmpeg commands can get quite complex, especially once you get to filters.&lt;p&gt;I never understood why it hasn&amp;#x27;t grown a DSL to specify the input&amp;#x2F;output&amp;#x2F;transformation. Could be JSON-based for what I care. Then we could have nice things like easy programmatic generation of these scripts and schema verification (for each particular ffmpeg version).&lt;p&gt;Also, when I looked at how LosslessCut (an Electron app) does the timeline preview thumbnails, it just calls the ffmpeg CLI app however many times it needs (once per thumbnail). With the number of heavy users of ffmpeg, I&amp;#x27;m wondering how nobody has yet started a project to run ffmpeg in-memory as a server and avoid the process startup cost as I&amp;#x27;m sure LosslessCut isn&amp;#x27;t the only one who does this.</text><parent_chain></parent_chain></comment><story><title>StreamPot: Run FFmpeg as an API with fluent-FFmpeg compatibility, queues and S3</title><url>https://github.com/StreamPot/StreamPot</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>jackbridger</author><text>Jack from StreamPot here. So happy to see it shared here. We&amp;#x27;d love you to try it out and give us any feedback or requests.</text><parent_chain></parent_chain></comment><story><title>StreamPot: Run FFmpeg as an API with fluent-FFmpeg compatibility, queues and S3</title><url>https://github.com/StreamPot/StreamPot</url></story>