- distributed-transcode VS m4b-tool
- distributed-transcode VS nitter
- distributed-transcode VS polybar-clockify
- distributed-transcode VS ppp_thing
- distributed-transcode VS fastmod
- distributed-transcode VS cmdg
- distributed-transcode VS rslurp
- distributed-transcode VS Keimeno
- distributed-transcode VS kondo
- distributed-transcode VS tiny-snitch
Distributed-transcode Alternatives
Similar projects and alternatives to distributed-transcode
-
Hasura
Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Av1an
Cross-platform command-line AV1 / VP9 / HEVC / H264 encoding framework with per scene quality encoding
-
m4b-tool
m4b-tool is a command line utility to merge, split and chapterize audiobook files such as mp3, ogg, flac, m4a or m4b
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
ppp_thing
A poorly written, minimum viable PPPoE client with session handoff between redundant FreeBSD routers
-
wsl-ssh-pageant
A Pageant -> TCP bridge for use with WSL, allowing for Pageant to be used as an ssh-ageant within the WSL environment.
-
zenbot-sim-runner
Discontinued A sim run batch aggregator / automator for Zenbot. Eases the process of backtesting and subsequent analysis of results.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
distributed-transcode reviews and mentions
-
Guide to Adopting AV1 Encoding
Back when I still cared about saving disk space, I made a cluster of NVidia Jetson Nanos running in a docker swarm configuration [1], but honestly even when you have six computers working at once, H264 on a single computer is still often faster.
On the Jetson Nanos I was lucky to get maybe 1fps in ffmpeg using VP9. Multiply that by six boards and that's about 6fps in total; ffmpeg running x264 in software mode was getting around 11fps on a single board, not even counting using the onboard encoder chip, meaning that I was getting better performance from one board using x264 than all six using VP9.
Now obviously this is a single anecdote on specific hardware, so I'm not saying that this applies to every single case, but it's a big reason why I personally have not used VP9 for anything substantial yet.
[1] https://gitlab.com/tombert/distributed-transcode
-
Ask HN: Have you created programs for only your personal use?
I have a fairly large blu-ray collection (~300 movies, ~15 complete TV series). I rip them and serve them with Jellyfin, which works, but due to codec annoyances, I need to transcode them to run on web browsers, and the SBC I'm running Jellyfin + ZFS on is not really fast enough to transcode in real time.
Since I have a ton of little SBCs sitting around my house, I decided to write a clojure app the queues up and transcodes my movies to H264. It uses Docker Swarm to handle distribution of nodes, RabbitMQ to queue up the movies, and core.async to handle local queuing within the application, and uses the Java NIO filesystem stuff to handle any kind of atomicity.
It's hardly the "first" or the "best" at what it does, but the advantage of writing your own is of course that you can tailor it exactly to your setup, and of course it was fun to write.
https://gitlab.com/tombert/distributed-transcode
Stats
Popular Comparisons
Sponsored