Hacker News Reader

Comment by amelius | Hacker News Reader

I suppose this only works if you have some shared filesystem. Or does this work with piping too?

the original poster's project also requires shared filesystem.

as for bash-ssh solution, you don't need shared FS, if you don't need intermediate results. you can use SCP to get the final result after transcoding has finished. something like:

  alias ffmpeg-over-ip='ssh myserver "ffmpeg \"\$@\" /tmp/output/"'
  alias download-results='scp myserver:/tmp/output/*.* .'

  ffmpeg-over-ip <args> && download-results

my meta point being is, before engineering something with programming language, and handrolling webservers, with auth, and workers - just try to implement your system with bash scripts.

Martin Klepmann created an entire database using just bash aliases in his book "Designing Data Intensive Applications"

Even the temporary file is optional. Ffmpeg supports a number of network protocols. For instance, you could read from one port and write to another with

    ffmpeg -f webm -i tcp://[::]:55601?listen -c copy -f webm tcp://[::]:55602?listen

There's also UDP, SFTP, and more convenient protocols such as SRT or the long-in-the-tooth RTMP. I expect it will eventually add WHIP/WHEP as well.

I experimented a bit with piping, but it turned out that mp4 doesn't always like to be streamed.

Reply on news.ycombinator.com