Since I couldn’t find a way to convert vCard / .vcf files to the FritzBox phone book format, I wrote one:
source code
releases for Win/Mac/Linux
As of today, I think I have finally found a “suitable” (enough…) solution to record and edit my YouTube videos. It’s not pretty:
I bought an Elgato HD60S on the cheap to hook up my old DSLR to my computer. It does not work with Linux. This doesn’t matter, because OBS Studio does not offer hardware encoding on my Linux setup anyway. So I have to use Windows no matter what. After tinkering with the settings in OBS Studio, I think the only viable recording option is to go with “lossless quality”. Out comes a big .avi encoded with UT Video. I tried the advanced settings and constant bitrate with high values, but OBS kept crashing. The .avi files have an a/v sync mismatch of 200ms. Because ffmpeg’s itsoffset does NOT work with .avi files - unfortunately, it doesn’t tell you and just acts as if successful - I have to convert them to .mkv first. Just a matter of ffmpeg -i VID.avi -c copy VID.mkv
. I can then use my delayaudio script. I cut and edit the files in kdenlive afterwards. Seems to work pretty ok. Apart from infrequent crashes… so I hit Ctrl+s all the time. Important: The project settings (resolution, frame rate, etc) have to be set before anything else is done, or the program will behave oddly. For rendering, I found the Generic - HD options to be too poor, even with best quality settings. Lossless/HQ > H.264 (libx264+aac) seems to work fine. Leads to fairly big output, of course.
Taken from Nessmuk’s Woodcraft
I’m pretty sure that this is cancerous, so don’t try this at home.
Three ounces pine tar, two ounces castor oil, one ounce pennyroyal oil.
Simmer all together over a slow fire, and bottle for use. You will hardly need more than a two-ounce vial full in a season. One ounce has lasted me six weeks in the woods. Rub it in throughly and liberally at first, and after you have established a good glaze, a little replenishing from day to day will be sufficient.
Waterproofing of tent material - he was not a fan of oil cloth.
To 10 quarts of water add 10 ounces of lime, and 4 ounces of alum; let it stand until clear; fold the cloth snugly and put it in another vessel, pour the solution on it, let it soak for 12 hours; then rinse in luke-warm rain water, stretch and dry in the sun, and the shanty-tent is ready for use.
I started playing around with dwm, dmenu, st and surf from suckless.org on the weekend. My changes and setup can be found on git.fireandbrimst.one. Each repo contains a description of changes in ‘CHANGES’. I altered dwm pretty heavily from the vanilla version, the other tools not so much.
Note to self: To add dwm to lightdm and similar display managers add the following to /usr/share/xsessions/dwm.desktop :
[Desktop Entry]
Name=dwm
Comment=dwm
Exec=/usr/local/bin/dwm
Type=Application
I pushed a program to git.fireandbrimst.one/dmenu_charinput/unicodedata.go that allows you to select codepoint ranges from the unicode standard and print them out with description. This can be useful as input for dmenu if you want a general way to enter special characters.
For example, if we wanted to provide a selection menu with all egyptian hieroglyphs and emoticons, we could write the following:
unicodedata -ranges "13000..1342F 1F600..1F64F" |
dmenu -i -l 10 |
awk '{print $1}' |
tr -d "\n" |
xclip -selection clipboard
… and afterwards the selected character is in the clipboard for pasting. Better yet, use it with dmenu_charinput and interactively select first the codepoint block and then the character.