Skip to main content

I made a GIF!

Multiple VOB files to a single AVI or MP4

A few multimedia containers (MPEG-1, MPEG-2 PS, DV) allow you to join video files by merely concatenating them.  Hence you may concatenate your multimedia files by first transcoding them to these privileged formats, then using the humble cat command.  As an example:


#!/bin/bash

# Divx5 (hq) output for DVD player compatibility
videoparams1="mpeg4 -mbd rd -flags +4mv+aic -trellis 2 -cmp 2 -subcmp 2 -g 300 -sameq -b 1000k"
# MP3 (stereo) for DVD player compatibility
audioparams1="libmp3lame -ac 2 -ab 128k"
outputfile=~/Videos/ffmpeg-`date +%Y%m%d-%H%M%S`.avi
cat *.VOB | ffmpeg -i - \
-vcodec $videoparams1 \
-acodec $audioparams1 \
$outputfile
 I tried the 2 pass method and consistently encountered errors w/ missing output logs.  This is apparently a known bug w/ my FFMpeg version.  Since the shipping version w/ Ubuntu excludes non-free codecs, I complied my own and have no desire to re-do that process.  Note that you can test by directing the output to NULL with outputfile="-f AVI -y /dev/null" .  This is handy when tweaking parameters like video bitrate "-b".  The VOB bitrate can be 9801K (yikes!).  If omitted, even w/ same quality "-sameq", the bitrate defaults to 200k (garbage).  Find your own satisfactory value.  The other video perameters were lifted from the FFMpeg FAQ.

Comments

Popular posts from this blog

Cisco ASA ICMP packet-tracer

Occasionally devices fail to respond to a ping.  This can result from devices being off-line, having a local firewall enabled or the perimeter firewall configuration.  The Cisco ASA ICMP packet-tracer options differ from the TCP or UDP command options.  An example is below: packet-tracer input outside icmp A.B.C.D 8 0 E.F.G.H The ICMP type is "8" (echo request) with code"0" (none).  There are no options on destination IPv4 address E.F.G.H. Complete ICMP documentation at URL http://www.iana.org/assignments/icmp-parameters/ Complete Cisco ASA packet-tracer documentation at URL http://www.cisco.com/en/US/docs/security/asa/asa80/command/reference/p.html#wp1878788

Xfce4 lock screen not working

Xfce4 would not start a screensaver on my Linux system.  Researching it, it ran xflock4 from the command line ad received an error: Property "/general/LockCommand" does not exist on channel "xfce4-session". To fix this, additional configuration needed, but no hacks. First, verify xflock4 and xfconf-query are available. $ which xflock4 xfconf-query /bin/xflock4 /bin/xfconf-query Next  install a lock screen package that provides 'xlock', 'slock', 'i3lock' or similar.  $ sudo yum install -y xlockmore-gtk i3lock Last, add an executable (with options) as /general/LockCommand in the xfce4-session settings. $ xfconf-query -c xfce4-session --create -p /general/LockCommand --set "xlock -mode matrix" --type  string $ xfconf-query -c xfce4-session --create -p /general/LockCommand --set "i3lock -c 000000" --type string Test by running xflock4 from the command line or through the GUI.

X11 Forwarding issue solved

TL;DR Disabling IPv6 necessitates SSHd AddressFamily is "inet" for X11 Forwarding to work. Issue OpenSSH assumes both IPv6 and IPv4 protocols are enabled, and default SSHd AddressFamily value "any" is valid. Quickly skimming the OpenSSH source code, it was not obvious why SSHd does not fail gracefully, selecting only an available IP address family. Therefore, for X11 Forwarding to work correctly, in /etc/ssh/sshd_config we must choose: Defaults - IPv6 enabled and SSHd AddressFamily value " any " Custom - IPv6 disabled and SSHd AddressFamily value " inet " Background PuTTY was not creating a $HOME/.Xauthority file on ssh login and no X11 applications would run, despite setting $DISPLAY.  PuTTY was correctly configured with: X11 Forwarding enabled X display location empty Remote authentication protocol MIT-Magic-Cookie-1 X authority file for local display empty On the initial ssh login there should be a .Xauthority notic