juhokuu

## h264-vs-vp8-test.md

      
              2 files
            
          
              1 fork
            
          
              11 comments
            
          
              38 stars
            
          
                Hupotronic
                / h264-vs-vp8-test.md
            
            
              Last active
              May 11, 2024 18:19
            
              
                H.264 & VP8 Quality Comparison And Some Words on Future Video Formats
              
          
    VP8 vs H.264 - Which One is Better?

So I was reading Hacker News and decided to read the comments in the thread about H.265 being approved. Pretty close to the top was this comment about VP9, Google's future video format. I have some words of my own about it and other future formats at the bottom of this post, but what jumped out from the comment to me was this part:

Many have already implemented VP8 (which is also slightly better than h.264 at this point)

The comparison linked to back up that statement is faulty for several reasons, such as not providing the source material used (hell, he doesn't even name the source material), exact encoding settings used (no, some random profiles are not enough), not providing the resulting encodes, only providing a

  
## websock.sh
#!/bin/bash
# WebSocket shell, start & browse to http://<Host>:6655/
# Requires bash 4.x, openssl.
# Author: rootshell@corelogics.de (which isn't me, apk)
coproc d { nc -l -p 6656 -q 0; }
nc -l -p 6655 -q 1 > /dev/null <<-ENDOFPAGE
	HTTP/1.1 200 OK

	<html><head><script language="javascript">
	  var url = location.hostname + ':' + (parseInt(location.port) + 1);

## live-mjpeg-stream.py
#!/usr/bin/python
#based on the ideas from http://synack.me/blog/implementing-http-live-streaming
# Updates:
# - 2024-04-24: Apply suggestions from @Pin80
# Run this script and then launch the following pipeline:
# gst-launch videotestsrc pattern=ball ! video/x-raw-rgb, framerate=15/1, width=640, height=480 !  jpegenc ! multipartmux boundary=spionisto ! tcpclientsink port=9999
#updated command line
#gst-launch-1.0 videotestsrc pattern=ball ! videoconvert ! video/x-raw, framerate=15/1, width=640, height=480 !  jpegenc ! multipartmux boundary=spionisto ! #tcpclientsink port=9999

from multiprocessing import Queue

## git-fix-author
#!/bin/bash
#
# Changes author and committer name and email throughout the whole repository.
# Uses a file with the following format:
#
# john.doe@hotmail.com=John Doe <john.doe@hotmail.com>
# jill.doe@hotmail.com=Jill Doe <jill.doe@hotmail.com>
#

if [ ! -e "$1" ]
	#!/bin/bash
	# WebSocket shell, start & browse to http://<Host>:6655/
	# Requires bash 4.x, openssl.
	# Author: rootshell@corelogics.de (which isn't me, apk)
	coproc d { nc -l -p 6656 -q 0; }
	nc -l -p 6655 -q 1 > /dev/null <<-ENDOFPAGE
	HTTP/1.1 200 OK

	<html><head><script language="javascript">
	var url = location.hostname + ':' + (parseInt(location.port) + 1);
	#!/usr/bin/python
	#based on the ideas from http://synack.me/blog/implementing-http-live-streaming
	# Updates:
	# - 2024-04-24: Apply suggestions from @Pin80
	# Run this script and then launch the following pipeline:
	# gst-launch videotestsrc pattern=ball ! video/x-raw-rgb, framerate=15/1, width=640, height=480 ! jpegenc ! multipartmux boundary=spionisto ! tcpclientsink port=9999
	#updated command line
	#gst-launch-1.0 videotestsrc pattern=ball ! videoconvert ! video/x-raw, framerate=15/1, width=640, height=480 ! jpegenc ! multipartmux boundary=spionisto ! #tcpclientsink port=9999

	from multiprocessing import Queue
	#!/bin/bash
	#
	# Changes author and committer name and email throughout the whole repository.
	# Uses a file with the following format:
	#
	# john.doe@hotmail.com=John Doe <john.doe@hotmail.com>
	# jill.doe@hotmail.com=Jill Doe <jill.doe@hotmail.com>
	#

	if [ ! -e "$1" ]