nvidia-patch
patchy
| nvidia-patch | patchy | |
|---|---|---|
| 4 | 1 | |
| 46 | 167 | |
| - | - | |
| 10.0 | 8.3 | |
| over 2 years ago | 12 days ago | |
| Python | Python | |
| - | MIT License |
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.
nvidia-patch
-
Plex Hardware Transcoding, Explained
If they're using a consumer grade nvidia GPU I would recommend suggesting they use this driver patch to remove the artificial session limit on transcodes that nvidia enforces. https://github.com/Snawoot/nvidia-patch
-
My opinion
GeForce cards are limited to 3 NVENC sessions, you can bypass the restriction by modifying the driver so it thinks it's a Quadro.
-
Hardware Acceleration (You guys probable get alot of these types of questions)
I use a 1650 myself and it works great, and it's worth noting that there is a very simple driver hack that removes the artificial 3 simultaneous encoding limit on consumer cards.
patchy
-
I still Lisp (and you should too)
One great upside of s-expressions for me is that you can do some cool things like 'find and replace' for whole subexpressions (for monkey patching third party code, for example). I use `el-patch` [0] in my emacs config and `advice-patch` for surgically changing the default behaviors of some org-mode functions to compile my blog [1].
That said a similar sort of thing is possible, for example, in python with `patchy` [2], and perhaps many other languages? But I guess it's not as organic as in lisps, e.g. `advice-patch` implementation is less than 100 LOC, whereas in case of python you have to rely on existing heavy lifting done by `ast` module.
As of simple syntax, it really gets in the way sometimes, e.g. I'm always annoyed by constant quoting in Elisp because the same type of brackets (only `()`) is used. In comparison, in Clojure it's much more readable with (), [], {} (and more).
> Lisp is not an interpreted language. It is not slow
A bit of nitpicking, but... which Lisp? :) For example,
> all implementations come with lots and lots of levers to tweak performance for most programs. In some cases the programs might need assistance from faster languages like C and C++ because they are closer to the hardware, but with faster hardware, even that difference is becoming irrelevant.
Well, this is true of most languages.
[0] https://github.com/raxod502/el-patch#el-patch
[1] https://github.com/karlicoss/beepb00p/blob/a4fd7cb95e1705412...
[2] https://github.com/adamchainz/patchy#patchy
What are some alternatives?
LOLDrivers - Living Off The Land Drivers
KatawaShoujoHD - Unofficial HD patch for visual novel Katawa Shoujo.
closh - Bash-like shell based on Clojure
nvidia-patch - This patch removes restriction on maximum number of simultaneous NVENC video encoding sessions imposed by Nvidia to consumer-grade GPUs.
OneByteWallhack - CS:GO wallhack achieved by patching one byte of game memory. Written in Python 3.
sublime-text-4-patcher - Python 3 patcher for Sublime Text v4107-4169 Windows x64
ips-patcher - IPS Patching Utility written in Python
awesome-lisp-companies - Awesome Lisp Companies