### Installing global Python & Pip
Use Brew
brew install python
That'll install both Python, PIP and setuptools. If for some reason it didn't install PIP you can do via
curl https://bootstrap.pypa.io/get-pip.py > get-pip.py
sudo python get-pip.py
| ### | |
| ### | |
| ### UPDATE: For Win 11, I recommend using this tool in place of this script: | |
| ### https://christitus.com/windows-tool/ | |
| ### https://github.com/ChrisTitusTech/winutil | |
| ### https://www.youtube.com/watch?v=6UQZ5oQg8XA | |
| ### iwr -useb https://christitus.com/win | iex | |
| ### | |
| ### OR take a look at | |
| ### https://github.com/HotCakeX/Harden-Windows-Security |
### Installing global Python & Pip
Use Brew
brew install python
That'll install both Python, PIP and setuptools. If for some reason it didn't install PIP you can do via
curl https://bootstrap.pypa.io/get-pip.py > get-pip.py
sudo python get-pip.py
The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the
| #!/bin/bash | |
| # Raspberry Pi stress CPU temperature measurement script. | |
| # | |
| # Download this script (e.g. with wget) and give it execute permissions (chmod +x). | |
| # Then run it with ./pi-cpu-stress.sh | |
| # | |
| # NOTE: In recent years, I've switched to using s-tui. See: | |
| # https://github.com/amanusk/s-tui?tab=readme-ov-file#options | |
| # Variables. |
| #!/usr/bin/env bash | |
| set -Eeuo pipefail | |
| trap cleanup SIGINT SIGTERM ERR EXIT | |
| script_dir=$(cd "$(dirname "${BASH_SOURCE[0]}")" &>/dev/null && pwd -P) | |
| usage() { | |
| cat <<EOF | |
| Usage: $(basename "${BASH_SOURCE[0]}") [-h] [-v] [-f] -p param_value arg1 [arg2...] |
Hanging out in subtitling and video re-editing communities, I see my fair share of novice video editors and video encoders, and see plenty of them make the classic beginner mistakes when it comes to working with videos. A man can only read "Use Handbrake to convert your mkv to an mp4 :)" so many times before losing it, so I am writing this article to channel the resulting psychic damage into something productive.
If you are new to working with videos (or, let's face it, even if you aren't), please read through this guide to avoid making mistakes that can cost you lots of computing power, storage space, or video quality.