Free video surveillance software for linux

Video::Frequencies is a Perl module that has many, many frequency constants and lists.

SYNOPSIS

use Video::Frequencies;

while (my($name,$list) = each %CHANLIST) {
print "$namen";
while (my($channel,$freq) = each %$list) {
printf " %-4s %9dn", $channel, $freq;
}
print "n";
}

This module exports (yes, exports!) frequency constants as well as hashes with channel => frequency relations for digital and analog video and audio broadcast. Another, shorter way to put it is "worldwide channel/frequency list". All frequencies are given in kHz.

Its a good idea to use perldoc -m Video::Frequencies to get an idea on how the various constants and lists look like.

Video::Xine is a Perl interface to libxine.

SYNOPSIS

use Video::Xine;

# Create and initialize the Xine object
my $xine = Video::Xine->new(
config_file => "$ENV{HOME}/.xine/config",
);

# Load a video driver
my $video_driver = Video::Xine::Driver::Video->new($xine,"auto",1,$x11_visual);

# Create a new stream (put your video driver under $DRIVER)
my $stream = $xine->stream_new(undef,$DRIVER);

# Open a file on the stream
$stream->open(file://my/movie/file.avi)
or die "Couldnt open stream: ", $stream->get_error();

# Get the current position (0 .. 65535), position in time, and length
# of stream in milliseconds
my ($pos, $pos_time, $length_time) = $stream->get_pos_length();

# Start the stream playing
$stream->play()
or die "Couldnt play stream: ", $xine->get_error();

# Play the stream to the end
while ( $stream->get_status() == XINE_STATUS_PLAY ) {
sleep(1);
}

A perl interface to Xine, the Linux movie player. More properly, an interface to libxine, the development library. Requires installation of libxine.

Xine by itself does not provide a user interface, and neither does this interface. Instead, you must set up the window using your own windowing code, and pass the window information to Xine.

PSP Video Converter project is a simple graphical frontend to ffmpeg to allow you to easily convert your videos to PSP compatibile format. Works for me, thought I may share.

Note: Created with Kommander 1.3, not sure if it works with earlier Kommander.

Note: There is no error checking for now, so make sure you have a working ffmpeg with necessary codecs installed.

Note: Looks like some PSPs cant open h264 videos encoded with ffmpeg.

Video Related Picture Editor is a gtk2 GUI frontend for batch-manipulating images using ImageMagick, MPlayer and transcode.

Its also the name of the infamous VRPE Team who paid me for hacking this together quickly because they needed it.

The name

Why "video related picture encoder" ? Because I didnt find a better name :) Any suggestions are welcome. With v0.1 the project was called "gFader" because all it did was "morphing" single frames to slow-down a video (giving a "fade-like effect") as batch-job with nice gui so poor Windows users could use it ;) My customer then wanted gFader to also do crop and scaling of multiple image files which rendered "gFader" as projectname useless. So i tried to make up some general name, which still fits if the application-range grows.

What can it do?

VRPE is able to do batch image-processing on a large set of images providing a way to move between images and giving a preview of the current, the previous and the next frame all with a nice GUI.

Different effects can be applied to the image-set (e.g morph, crop). Some of the effects support variable parameters so an effect can change with the image position.

VRPE can load several image formats (the ones supported by gtk2 and ImageMagick) or can convert almost any video to single frames using mplayer. It exports single images but also can render a videofile using mencoder or transcode. You can even launch mplayer to look at what youve done.

Other Features are:

Tooltip explainations almost everywhere
Nice wiki
quite fast

Drawbacks at this time:

lousy hacked together code
somewhat static filename handling
no "project" cababilities (images from previous sessions get imported if directory is not cleared etc.)
morph-curve gets lost
many more...

Linux Video Studio is a simple/small application to make the capturing of video on MJPEG-hardware CODEC boards easier.
The application uses the MJPEG-tools, a set of programs to capture video and do lots of things with this. You need to have MJPEG-Tools installed before trying to install Linux Video Studio (also see installation notes) ! Linux Video Studio also uses the Xvideo extension in XFree 4.x to see what youre recording.
But that is not all. I want more than just capturing. My dream is to create one big application that does all the work at once. Not just one application for capturing, one for editing (xlav?), etc. No, my dream is to have one application doing it all. I hope Linux Video Studio can be part of that.
Installation:
You need Gtk to use this application. You also need the MJPEG-Tools installed. Besides that, you now also need an X-server with the Xvideo extension installed (i.e. you need XFree 4.x). In the XF86Config file, add the line Load "v4l" in the modules-section. Next, restart X (you must have the zoran drivers loaded before staring X, or the V4L-module wont work!). For some distros, you might have to install this module first (RedHat 7.0: you need the XFree86-V4L-.... RPM).
From source:
# tar -zxf linuxvideostudio-x.y.z.tar.gz
# cd linuxvideostudio-x.y.z
# ./configure
# make
# make install
From binary RPM:
# rpm --install linuxvideostudio-x.y.z-n.i386.rpm
You can also use GnoRPM or another convenience tool.
From Source RPM:
# rpm --rebuild linuxvideostudio-x.y.z-n.src.rpm
# cd /usr/src/redhat/RPMS/i386/
# rpm --install linuxvideostudio-x.y.z-n.i386.rpm
Enhancements:
- some GList related preferences save bugfixes
- bugfixes where the extension of a file (.mp2, .m1v) precedes the filename, but that path doesnt exist

Want to watch Youtube video, but you dont have Flash plugin? (ex: gnu/linux ppc os), so try this great script to watch STREAMING VIDEOS from Youtube! You dont need to download video on your disk, you can stream directly the FLV videos from Youtube!

MPlayer Youtube Video Streamer lets you watch YouTube videos even if you dont have the flash plugin.

Usage: myvs [options] video_url

Options:

-h, --help print this help text and exit
-v, --version print program version and exit
-u USERNAME, --username=USERNAME account username
-p PASSWORD, --password=PASSWORD account password
-o FILE, --output=FILE output video file name
-q, --quiet activates quiet mode
-s, --stream do not download video, but stream directly by mplayer
-C, --cache set a cache of 300k, for slow connection
-c, --cycle cycle 20 times while youtube redirect to vo.llnwd.net (that streams .flv)
-t, --title use title in file name
-n, --netrc use .netrc authentication data
-O, --streamonly Force the script to stream only, if it doesnt find a valid stream server simply quit

Who to use it with Firefox:

Now I will explain you how to get it working with Firefox,

First we need a Firefox extension called: Lanchy,
this extension give us the ability to open directly from Firefox Youtube video on youtube webpage (not on all webpages that have a youtube video!

You ALWAYS need the youtube videos webpage! After you have installed Launchy (from firefoxs addon site), restart Firefox, now it will ask you to insert a Launchys button on your toolbar (DO IT! so open Youtube videos will be very simply), after that go on the preferences/option of this extension and uncheck the option: "search automatically programs".

Now copy the "launchy.xml" file that you found on the package and copy it on your directory:
".mozilla/firefox/YOUR_ID.default/chrome/" , after copied it, please dont forget to edit it with your myvs.py COMPLETE PATH, and add or delete oppurtune option to pass to the script.

Now restart again firefox an watch if it recognise the command (by pressing the G).

Go on youtube.com, open a video webpage, click on the G button-> Open in Mplayer Youtube Video Streamer.

Video::TeletextDB is Perl extension to manage a telextext database.

SYNOPSIS

use Video::TeletextDB;

$tele_db = Video::TeletextDB->new(%options);
# Possible options are:
# cache_dir => $directory
# mkpath => $boolean
# umask => $mask
# creat => $boolean
# RW => $boolean
# page_versions => $number
# channel => $string
# stale_period => $seconds
# expire_period => $seconds

$access = $tele_db->access(%options);
# Possible options are:
# umask => $mask
# creat => $boolean
# RW => $boolean
# page_versions => $number
# channel => $string
# stale_period => $seconds
# expire_period => $seconds

$cache_dir = $tele_db->cache_dir;
$channel = $tele_db->channel;
$old_channel = $tele_db->channel($new_channel);
@channels = $tele_db->channels;
$nr_channels = $tele_db->channels;
$boolean = $tele_db->has_channel(?$channel?);
$db_file = $tele_db->db_file;
$lock_file = $tele_db->lock_file;
$tele_db->lock;
$page_versions= $tele_db->page_versions;
$umask = $tele_db->umask;
$old_umask = $tele_db->umask($new_umask);
$RW = $tele_db->RW;
$old_RW = $tele_db->RW($new_RW);
$stale_period = $tele_db->stale_period;
$old_stale_period = $tele_db->stale_period($new_stale_period);
$expire_period = $tele_db->expire_period;
$old_expire_period = $tele_db->expire_period($new_expire_period);
$user_data = $tele_db->user_data;
$old_user_data= $tele_db->user_data($new_user_data);

$tele_db->delete(%options);

The idea behind a teletext database is to separate the process of collecting teletext pages from the process of presentation. This makes programs both shorter (you dont have to implement the side yourre not interested in) and more flexible (you can read teletext pages long after the collector stopped running and you dont have to be tuned in to the channel you want to read).

In fact, the simple script TeleCollect coming with this package will be good enough for most teletext collection purposes, so that you can concentrate on the page processing.

This modules provides you with methods to both store and retrieve pages into a database and some rudimentary support to manage a set of databases (typically one for each channel). The pages will be stored in raw form so that a client can decide for itself how to handle things like transmission errors (there are of suggested methods provided in the module though, so you dont have to reinvent the wheel every time).

It (currently) use a Berkeley DB with an external lockfile for the actual storage. It only uses the version 1.85 features, so it should work almost everywhere. There will be one database and lockfile for each channel and all channel databases and locks will normally be collected in one directory.