Sander Ploegsma sanderploegsma

The goal of this exercise is to get pitch shifting (changing the pitch of music up or down) working with Spotify on Windows 10 using native-compiled open source software. This solution does not require any VMs or Linux at all.

For this solution, the actual sound playback will be occurring on your Windows PC using your soundcard, but there are other components of the solution that do some audio processing. I'll explain each.

Requirements

A Spotify Premium account
The 64-bit build of MSYS2 from https://www.msys2.org/ -- get the default installer and install with default options.

Overview of the Working Solution

Client-side SSL

For excessively paranoid client authentication.

Original: https://gist.github.com/mtigas/952344

Convert SSL certificate from CRT format to PEM

openssl x509 -in server.crt -out server.der -outform DER
openssl x509 -in server.der -inform DER -out server.pem -outform PEM

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

General rules

Follow standard conventions.
Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
Boy scout rule. Leave the campground cleaner than you found it.
Always find root cause. Always look for the root cause of a problem.

Design rules

If you have a package where a lot of people are still using a legacy version of it you might want to keep pushing (security-)fixes to that "branch".

Let's say the "latest" version of your package is "5.4.0", but there is as significant amount of people still using "4.7.4" – the last version you released before doing "5.0.0".

You found a critical bug in "5.4.0" and push it as out as "5.4.1", but it applies to "4.7.4" as well and so you want to do "4.7.5".

Assuming you have semantic-release already set up, you can follow these steps to get that "4.7.5" legacy support release out.

Go to the relevant commit: git checkout v4.7.4
Create a new branch from it: git checkout -b 4.x (You can choose any branch name, just make sure to use the same in step 3)

	import time
	import redis
	from locust import Locust, events
	from locust.core import TaskSet, task


	class RedisClient(object):
	def __init__(self, host="localhost", port=6379):
	self.rc = redis.StrictRedis(host=host, port=port)

	# Add these lines to your dockerfile, before `npm install`

	# Copy the bitbucket private key to your docker image
	COPY ./bitbucket_ssh_key /opt/my-app

	# Copy the ssh script to your docker image
	COPY ./ssh-bitbucket.sh /opt/my-app

	# Tell git to use your `ssh-bitbucket.sh` script
	ENV GIT_SSH="/opt/map-project-tile-server/ssh-bitbucket.sh"

	import java.io.FileDescriptor;
	import java.io.FileOutputStream;
	import java.io.IOException;
	import java.io.OutputStream;
	import java.io.PrintStream;

	public class HelloWorld{
	private static HelloWorld instance;
	public static void main(String[] args){
	instantiateHelloWorldMainClassAndRun();

	install:
	- sudo apt-get install texlive-latex-recommended texlive-latex-extra texlive-fonts-recommended
	- sudo apt-get install chktex

	script:
	- make
	- chktex -W # Print version information.
	- chktex -q -n 6 .tex chapters..tex 2>/dev/null \| tee lint.out
	# If lint output is non-empty report an error.
	- test ! -s lint.out