zenbot-sim-runner
distributed-transcode | zenbot-sim-runner | |
---|---|---|
2 | 5 | |
- | 12 | |
- | - | |
- | 9.0 | |
- | over 2 years ago | |
PHP | ||
- | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
distributed-transcode
-
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
zenbot-sim-runner
-
Ask HN: Have you created programs for only your personal use?
I built a currency trading backtesting and bot monitoring framework [1]. At times I vaguely considered turning it into a product, but for a number of reasons decided not to. However, I am running it successfully, hosted on my own server and am quite proud of what I achieved :)
[1] https://github.com/jefc1111/zenbot-sim-runner
-
Autoscaling Laravel Horizon queues (on AWS?)
Zenbot: https://github.com/DeviaVir/zenbot Zenbot Sim Runner (my app): https://github.com/jefc1111/zenbot-sim-runner
- I'm building a sim run / backtesting automator for Zenbot
What are some alternatives?
m4b-tool - m4b-tool is a command line utility to merge, split and chapterize audiobook files such as mp3, ogg, flac, m4a or m4b
laravel-aws-eb - Ready-to-deploy configuration to run Laravel on AWS Elastic Beanstalk.
nitter - Alternative Twitter front-end
sidecar - Deploy and execute AWS Lambda functions from your Laravel application.
polybar-clockify - Control Clockify through Polybar
Mad-Money-Backtesting - Backtesting recommendations from Mad Money and "The Cramer Effect/Bounce"
ppp_thing - A poorly written, minimum viable PPPoE client with session handoff between redundant FreeBSD routers
libgossamer - Public Key Infrastructure without Certificate Authorities, for WordPress and Packagist
fastmod - A fast partial replacement for the codemod tool
epanet-js - Model a water distribution network in JavaScript using the OWA-EPANET engine
cmdg - Command line Gmail client