Dave Malone dave-malone

Introduction

Hi everyone! Today I'm going to be giving you a crash course in video processing using Python. Coming out of this talk, you'll be able to take video from pretty much any source, decode it, apply visual effects, and display it on-screen. To do this, we're going to be using a library named GStreamer, an incredibly powerful and versatile framework. This is the same tool that the pros use, but don't feel intimidated! GStreamer actually makes it very easy to do impressive things with video and you'll be well on your way to making something great in just the time it takes to watch this talk.

If you fall behind at any point during the live presentation, don't worry! I have a text version of this talk available with the same content and more. There should be a link in the description.

Installing Dependencies

Let's start by installing everything we'll need to start using GStreamer in Python. This is probably the hardest part, so if you managed to do it before this talk, it's all smooth sailing fro

Gstreamer Pipeline Samples
Media File

Gstreamer Pipeline Samples
Media File

UPDATE (March 2020, thanks @ic): I don't know the exact AMI version but yum install docker now works on the latest Amazon Linux 2. The instructions below may still be relevant depending on the vintage AMI you are using.

Amazon changed the install in Linux 2. One no-longer using 'yum' See: https://aws.amazon.com/amazon-linux-2/release-notes/

Docker CE Install

sudo amazon-linux-extras install docker
sudo service docker start

If you are like me you find yourself cloning a repo, making some proposed changes and then deciding to later contributing back using the GitHub Flow convention. Below is a set of instructions I've developed for myself on how to deal with this scenario and an explanation of why it matters based on jagregory's gist.

To follow GitHub flow you should really have created a fork initially as a public representation of the forked repository and the clone that instead. My understanding is that the typical setup would have your local repository pointing to your fork as origin and the original forked repository as upstream so that you can use these keywords in other git commands.

Clone some repo (you've probably already done this step)
```
git clone [email protected]
```

To generate a self-signed cert, do the following:

openssl req -config 12factor.req -new -nodes -x509 -newkey rsa:2048 -sha256 -keyout 12factor.key -out 12factor.cert -days 3650

Where 12factor.req is:

[ req ]
default_bits        = 2048
default_keyfile     = 12factor.key

	#include <iostream>
	#include <stdio.h>
	#include <stdlib.h>
	#include <linux/ioctl.h>
	#include <linux/types.h>
	#include <linux/v4l2-common.h>
	#include <linux/v4l2-controls.h>
	#include <linux/videodev2.h>
	#include <fcntl.h>
	#include <unistd.h>

	# This script prints out the /healthz and /varz connection info
	# for your running Cloud Foundry jobs.
	#
	# The nats_uri variable should be updated to suit your deployment.
	# The default nats_uri value will work for a standard bosh-lite deployment.

	require 'json'
	require 'nats/client'

	nats_uri = 'nats://nats:[email protected]:4222'

	{
	"snippets": [
	{
	"match": {"global": true, "pkgname": ".", "fn": ".*_test.go"},
	"snippets": [
	{"text": "func Test", "title": "", "value": "func Test${1:ObjectName}${2:TestName}(t *testing.T) {\n\t$0\n}"},
	{"text": "func Benchmark", "title": "", "value": "func Benchmark${1:ObjectName}${2:BenchmarkName}(b *testing.B) {\n\n\tb.StopTimer()\n\n\t$0\n\n\tb.StartTimer()\n\n\tfor i := 0; i < b.N; i++ {\n\t\t\n\t}\n\n}"},
	{"text": "func Example", "title": "", "value": "func Example${1:ObjectName}${2:ExampleName}() {\n\n\t$0\n\n\t// Output:\n\t// \n\n}"}
	]
	}

	#!/bin/bash

	host=http://localhost:8080
	url=/pluginManager/installNecessaryPlugins

	# git plugin https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin
	curl -X POST -d '<jenkins><install plugin="[email protected]" /></jenkins>' --header 'Content-Type: text/xml' $host$url

	# artifactory plugin https://wiki.jenkins-ci.org/display/JENKINS/Artifactory+Plugin
	curl -X POST -d '<jenkins><install plugin="[email protected]" /></jenkins>' --header 'Content-Type: text/xml' $host$url