Free flv software for linux

FLV::Tag is a flash video file data structure.

This is a subclass of FLV::Base.

$self->parse($fileinst)

Takes a FLV::File instance and extracts an FLV tag from the file stream. This method then multiplexes that tag into one of the subtypes: video, audio or meta. This method throws exceptions if the stream is not a valid FLV v1.0 or v1.1 file.

At the end, this method stores the subtag instance, which can be retrieved with get_payload().

There is no return value.

$self->get_payload()

Returns the subtag instance found by parse(). This will be instance of FLV::VideoTag, FLV::AudioTag or FLV::MetaTag.

$pkg->serialize($tag, $filehandle)
$self->serialize($tag, $filehandle)

Serializes the specified video, audio or meta tag. If that representation is not complete, this throws an exception via croak(). Returns a boolean indicating whether writing to the file handle was successful.

FLV::Info is an extract metadata from Flash Video files.

SYNOPSIS

use FLV::Info;
my $reader = FLV::Info->new();
$reader->parse(video.flv);
my %info = $reader->get_info();
print "$info{video_count} video framesn";
print $reader->report();

This module reads Macromedia FLV files and reports metadata about those files.

FLV::ToSWF is a Perl module to convert an FLV file into a SWF file.

SYNOPSIS

use FLV::ToSwf;
my $converter = FLV::ToSWF->new();
$converter->parse_flv($flv_filename);
$converter->save($swf_filename);
See also flv2swf.

Transcodes FLV files into SWF files. See the flv2swf command-line program for a nice interface and a detailed list of caveats and limitations.

FLV::Header is a flash video file data structure.

METHODS

This is a subclass of FLV::Base.

$self->parse($fileinst)

Takes a FLV::File instance and extracts the FLV header from the file stream. This method throws exceptions if the stream is not a valid FLV v1.0 or v1.1 file. The interpretation is a bit stricter than other FLV parsers (for example FLVTool2).

There is no return value.

$self->serialize($filehandle)

Serializes the in-memory FLV header. If that representation is not complete, this throws an exception via croak(). Returns a boolean indicating whether writing to the file handle was successful.

$self->has_video()

Returns a boolean indicating if the FLV header predicts that video data is enclosed in the stream.

This value is not consulted internally.

$self->has_audio()

Returns a boolean indicating if the FLV header predicts that audio data is enclosed in the stream.

This value is not consulted internally.

Yet Another MetaData Injector (yamdi) is a metadata injector for FLV files. It adds the onMetaData event to your FLV files. yamdi should run under *BSD and Linux (tested with FreeBSD, MacOSX and Ubuntu) and is published under the BSD license.
Why?
For a current project I have to add metadata to quite large FLV files (over 1GB). The other known free tools (flvmdi and flvtool2) are not suitable for that job because they read the whole file into memory. Because Im not very familiar with ruby (in order to modify flvtool2) and flvmdi is not open source I took the FLV specs and implemented a metadata injector in C. yamdi uses less memory and is faster.
Yet Another MetaData Injector for FLV injects the following metadata into your FLV files:
- creator
- metadatacreator
- hasKeyframes
- hasVideo
- hasAudio
- hasMetaData
- canSeekToEnd
- duration
- datasize
- videosize
- videocodecid
- audiosize
- audiocodecid
- audiosamplerate
- audiosamplesize
- stereo
- filesize
- lasttimestamp
- lastkeyframetimestamp
- lastkeyframelocation
- keyframes (filepositions, times)
- width
- height
- framerate
- videodatarate
- audiodatarate
Installation:
Download the source code and extract it with tar:
tar xzf yamdi-1.0.tar.gz
Change into the yamdi directory and compile the source code with:
cd yamdi-1.0
gcc yamdi.c -o yamdi -O2 -Wall
yamdi accepts four paramters:
-i The source FLV file.
-o The resulting FLV file with the metatags. If the output file is - the FLV file will be written to stdout.
-c A string that will be written into the creator tag. This parameter is optional
-h Displays a description of the available parameters
Examples:
yamdi -i sample.flv -o sample_with_metadata.flv
yamdi -i sample.flv -o - > sample_with_metadata.flv
yamdi -i sample.flv -o sample_with_metadata.flv -c "John Doe"
Enhancements:
- [Fix] Width and height calculation of ScreenVideo stream was wrong
- [Add] onLastSecond event with option -l

FlowPlayer project is a video player for Flash Video in FLV format. The UI is clean and simple.
The player is easy to configure and embed into your home page, site, or blog.
FlowPlayer.swf is a player that is ready to be used out-of-the box. FlowPlayer.html is an example of Web page that uses it. The name of the video file to be loaded by the player is specified in html page in the < object > tags flashvars attribute. This attribute is there in two places (both in < objec t> and < embed > tags) to maximize the number of supported Web browsers.
By default, the player loads the video file from the same location as it loads FlowPlayer.swf. The name of this variable is videoFile and the value should be the name of the video file with or without an extension.
There is also a way to specify a complete URL. This is done using the baseURL variable. When this mechanism is used the video files and FlowPlayer.swf may reside in different locations within the Web server or even in different servers.
autoPlay variable is used to specify whether playback should start immediately when the player has been loaded into the Web browser. Legal values for this parameter are true and false.
Please refer to FlowPlayer.html for descriptions of all HTML parameters used to control the player.
Enhancements:
- New FlowPlayer Skinning Kit to make skinning the player better than ever before.
- There is a new package in the downloads for this.
- Added all dependencies to the source distribution package and now its easier for new developers to start hacking.
- Fixes: VideoHeight does not have any effect in full screen mode any more, now resizes to fit the full area.
- Configured progress bar, buffering bar etc. colors were ignored and now work as espected.

Palabre is an open source (and free as in free beer) XML Socket Python Server.
It is meant to be used in replacement (for example) of the Macromedia Flash Communication Server. (which is lets admit it really expensive)
Of course, its much more limited, but has all the basic functionnalities for connecting Flash based Clients through Xml Sockets (sending and receiving messages).
So you can use it to create, multiuser applications like a Chat, (almost) Real Time Flash Games, Online support, ...
It does not include Video streaming functions ( FLV via RTMP ) instead of Flash Communication Server.
Main features:
- Have multiple Rooms
- Each Room can have any parameter you want ( A title, a lock, operators, any flag, ...)
- The creator of the room can change this parameters
- The room can have Sub rooms (or child rooms)
- For Example, you can host 10 games and chats on a server, and each game has a lobby room for chatting, and as many subrooms as wanted. Players can chat, start a new game, wait for people to join, and then start the game. (Then the child room of the game can be "locked" so that no one else joins it.
- Have multiple clients
- They are identified by a nickname (like on IRC)
- One client can be in multiple rooms / subrooms
- Clients can send messages to a room
- Clients can send messages to other clients (private messages)
- Clients can send a broadcast message (or reserve this to root)
- Clients can ping the server
- Clients can ask for a "room message" to be sent back to them. (to test latency, ...)
Enhancements:
- Database identification support (< connect nickname="X" password="Y" / >)
- Clients params (< clientparam name="X" value="Y" / >)
- SubXML nodes : (< msg toroom="X" >< position >< x >12< /x >< /position >< /msg >)
- Customizable nodes (< mynode toroom="X" anyparam="Y" >< AnyContent >< /mynode >)
- Joined/Left information (< client name="Nickname" joined="Lobby" / >)

Major Features:

1. Request dispatching: Map requests to handler-callables using URL-routes.
2. URL parameters: Use regular expressions /object/(?P[0-9]+) or simplified syntax /object/:id to extract data out of URLs.
3. WSGI abstraction: Dont worry about cgi and wsgi internals.
4. Input: request.GET[parameter] or request.POST[form-field]
5. HTTP header: response.header[Content-Type] = text/html.
6. Cookie Management: response.COOKIES[session] = new_key.
7. Static files: send_file(movie.flv, /downloads/) with automatic mime-type guessing.
8. Errors: Throw HTTP errors using abort(404, Not here) or subclass HTTPError and use custom error handlers.
9. Templates: Integrated template language.
10. Plain simple: Execute python code with %... or use the inline syntax {{...}} for one-line expressions.
11. No IndentationErrors: Blocks are closed by %end. Indentation is optional.
12. Extremely fast: Parses and renders templates 5 to 10 times faster than mako.
13. Support for Mako-Templates (requires mako).
14. HTTP Server: Build in WSGI/HTTP Gateway server (for development and production mode)
15. Currently supports wsgiref.simple_server (default), cherrypy, flup, paste and fapws3.
16. Speed optimisations:

Requirements:

• Python