Pavel yekm

This script add Categories to Automatically add torrents from per Monitored Folder

👉 This script is in flux, as it may be implemented into qBittorrent in the future.

savecategory expects the user's watch directories to look similar to something like this:

It's based off the popular wiki for setting up hard linking Docker and other torrent grabbers.

Problem Description

We have a smol server at home which is among others responsible for music. This is accomplished by mpd.

I wanted to change the output from pulseaudio, because it was making pops every time the playlist was finished and it released the sound card. Also I wanted to have networked audio, so we can watch/listen occasionally on the speakers from our desktop PCs.

Without further explanation:

install packages

Foreward

This document was originally written several years ago. At the time I was working as an execution core verification engineer at Arm. The following points are coloured heavily by working in and around the execution cores of various processors. Apply a pinch of salt; points contain varying degrees of opinion.

It is still my opinion that RISC-V could be much better designed; though I will also say that if I was building a 32 or 64-bit CPU today I'd likely implement the architecture to benefit from the existing tooling.

Mostly based upon the RISC-V ISA spec v2.0. Some updates have been made for v2.2

Original Foreword: Some Opinion

The RISC-V ISA has pursued minimalism to a fault. There is a large emphasis on minimizing instruction count, normalizing encoding, etc. This pursuit of minimalism has resulted in false orthogonalities (such as reusing the same instruction for branches, calls and returns) and a requirement for superfluous instructions which impacts code density both in terms of size and

Using Raspberry Pi Camera with ffmpeg

Capturing video from the rpi camera with ffmpeg can vary from less than 5% to 100% of the CPU (rpi zero) depending on ffmpeg using the hardware acceleration or not.

On many github issues one finds the suggestion of using h264_omx codec to use the gpu - but it does not ship with the default ffmpeg on Raspbian.

Instead I found that one can use the v4l2 driver provided by raspbian to get hardware accelerated h264 output. Also setting the video size will save one from using a (cpu) scale filter.

ffmpeg

capture h264 video from rpi camera

	#!/usr/bin/env python

	import json
	from datetime import datetime

	print("Parsing input data...")
	records = json.load(open("./Takeout/Location History/Records.json"))['locations']
	print("Done.")

	def convert_conn(record):

	#!/usr/bin/env python
	import sys
	import json
	import datetime

	# Feed me with output of:
	# ffprobe -f lavfi -i movie=INPUT.mov,ocr -show_entries frame=pkt_dts_time:frame_tags=lavfi.ocr.text -of json
	input= sys.argv[1]
	id = 0
	old_time = '00:00:00,000'

	### JHW 2018
	import numpy as np
	import umap



	# This code from the excellent module at:
	# https://stackoverflow.com/questions/4643647/fast-prime-factorization-module

	import random

	HTTPPort 8090
	HTTPBindAddress 0.0.0.0
	MaxHTTPConnections 200
	MaxClients 100
	MaxBandWidth 500000
	CustomLog -

	<Feed camera.ffm>
	File /tmp/camera.ffm
	FileMaxSize 200M

	# kudos to dzaku at consolechars.wordpress.com

	### MOUNT qcow2 image with lvm partitions

	# ensure nbd can handle that many partitions
	sudo modprobe nbd max_part=8

	# present image as block device through NBD
	sudo qemu-nbd --connect=/dev/nbd0 <image.qcow2>

	#!/bin/bash

	gdb -p "$1" -batch -ex 'set {short}$rip = 0x050f' -ex 'set $rax=231' -ex 'set $rdi=0' -ex 'cont'