3 ms·

Thanks for the update and continuing to share this project. What does the roadmap look like into the future?

steelbrain 8mo ago
I am thinking of adding a Windows application with an installer and a tray icon that you can use for some basic settings like changing port or password, or toggling automatic startup. For linux, I am thinking of adding convenience helpers around systemd service installation
- toomuchtodo 8mo ago
  Very cool. Peertube supports remote runners [1] [2], might take a look for inspiration. As a distributed compute enthusiast, big fan of of this model for media processing. [1] https://docs.joinpeertube.org/maintain/tools#peertube-runner https://docs.joinpeertube.org/maintain/tools#peertube-runner [2] https://docs.joinpeertube.org/admin/remote-runners https://docs.joinpeertube.org/admin/remote-runners
  - steelbrain 8mo ago
    Very cool! Thank you for sharing! I didn't know this existed, so now I'm curious how they solved it :) My usecase is just-in-time media transcoding, I'll see if PeerTube remote runners support it
    - utopiah 8mo ago
      Roughly what you'd expect https://docs.joinpeertube.org/contribute/architecture#remote-vod-live-transcoding https://docs.joinpeertube.org/contribute/architecture#remote... basically a request queue that gets periodically queried by trusted runners, fulfilled, updated.
  - bastiao 8mo ago
    Very nice. Could this concept be applied to have ffmpeg running in webassembly, and over HTTP?
    - toomuchtodo 8mo ago
      Similar to https://github.com/ffmpegwasm/ffmpeg.wasm https://github.com/ffmpegwasm/ffmpeg.wasm ?
      - bastiao 8mo ago
        Exactly - but can transcoding be remote?
pastescreenshot 8mo ago
This is neat. The thing I would most want in the README is a benchmark section showing where it wins and where it does not. My guess is long GPU bound transcodes look great and tiny file churn workloads probably do not. Having that boundary spelled out would make adoption a lot easier.

I am thinking of adding a Windows application with an installer and a tray icon that you can use for some basic settings like changing port or password, or toggling automatic startup. For linux, I am thinking of adding convenience helpers around systemd service installation

toomuchtodo 8mo ago
Very cool. Peertube supports remote runners [1] [2], might take a look for inspiration. As a distributed compute enthusiast, big fan of of this model for media processing. [1] https://docs.joinpeertube.org/maintain/tools#peertube-runner https://docs.joinpeertube.org/maintain/tools#peertube-runner [2] https://docs.joinpeertube.org/admin/remote-runners https://docs.joinpeertube.org/admin/remote-runners
- steelbrain 8mo ago
  Very cool! Thank you for sharing! I didn't know this existed, so now I'm curious how they solved it :) My usecase is just-in-time media transcoding, I'll see if PeerTube remote runners support it
  - utopiah 8mo ago
    Roughly what you'd expect https://docs.joinpeertube.org/contribute/architecture#remote-vod-live-transcoding https://docs.joinpeertube.org/contribute/architecture#remote... basically a request queue that gets periodically queried by trusted runners, fulfilled, updated.
- bastiao 8mo ago
  Very nice. Could this concept be applied to have ffmpeg running in webassembly, and over HTTP?
  - toomuchtodo 8mo ago
    Similar to https://github.com/ffmpegwasm/ffmpeg.wasm https://github.com/ffmpegwasm/ffmpeg.wasm ?
    - bastiao 8mo ago
      Exactly - but can transcoding be remote?

pastescreenshot 8mo ago

This is neat. The thing I would most want in the README is a benchmark section showing where it wins and where it does not. My guess is long GPU bound transcodes look great and tiny file churn workloads probably do not. Having that boundary spelled out would make adoption a lot easier.