Free dual layer dvd software for linux

dxr3Player is a lightweight, command-line DVD player for Linux and the DXR3 (aka Hollywood+) MPEG-2 decoder boards. This software supports all major DVD features, including: menus, navigation, fast forward and backward playback, subtitles and camera angle changes.
The player is very conservative on memory usage and tries very hard (and mostly succeeds) to keep video and audio in sync.
dxr3Player also plays DVDs on any X Window System display using the Simple DirectMedia Layer (SDL) library.
The software relies on the following other pieces of software:
- The dxr3 (em8300) drivers developed for Linux by the dxr3 project at Sourceforge. It is needed to access the decoder board.
- The libmpdvdkit library from MPlayer (which is actually a modified copy of the libdvdread and libdvdcss libraries). It is incorporated into the sources, and is used to access the DVDs.
- The liba52 library also from MPlayer (which is actually a modified copy of liba52, an A-52 decoding library). It is incorporated into the sources, and is used to decode AC-3 audio streams.
- If you turn on LIRC support, the LIRC library.
- If you want to play MPEG audio, the MAD library.
- The Simple DirectMedia Layer library for displaying on an X Window display without hardware support.
- The libmpeg2 library for decoding MPEG video streams when not using the DXR3 board or the Unichrome chipset.
Main features:
- DVD menus
- navigation: jumping to previous and next chapter and menus
- fast forward and backward playback, pausing
- subtitles
- camera angle changes
- support for full-screen VGA "overlay"
- infrared remote control support via LIRC
- playback of AC3, Linear PCM and MPEG audio streams
- digital audio output (both PCM and AC-3)
- joystick as input device
- dump of complete DVDs to hard disks and playback from there
Version restrictions:
- of Linear PCM streams, only 48 kHz, 16-bit stereo ones are played
- as you can see, this homepage is quite rudimentary. However, I do not hope to change it soon anymore

SYNOPSIS

#####
# Subroutines
#
use Tie::Layers qw(is_handle config);

$yes = is_handle( $file_handle );

($key, $old_value) = config(%options, $key);
($key, $old_value) = config(%options, $key => $new_value );

####
# Config default startup options
#
@old_options_list = config(%options, @option_list);
@old_options_list = config(%options, @option_list);
@old_options_list = config(%options, %option_list);

#####
# Class interface
#
require Tie::Layers;

#####
# Using support methods and file handle with
# the file subroutines such as open(), readline()
# print(), close()
#
tie *LAYERS_FILEHANDLE, Tie::Layers, @options
$layers = tied *LAYERS_FILEHANDLE;


#####
# Using support methods only, no file subroutines
#
$layers = Tie::Layers->TIEHANDLE(@options);

($key, $old_value) = $layers->config($key);
($key, $old_value) = $layers->config($key => $new_value );

@old_options_list = $layers->config(@option_list);
@old_options_list = $layers->config(@option_list);
@old_options_list = $layers->config(%option_list);

$data = $layers->fin($filename, @options);

$data = $layers->fout($filename, $data, @options);

$yes = $layers->is_handle( $file_handle );

If a subroutine or method will process a list of options, @options, that subroutine will also process an array reference, @options, [@options], or hash reference, %options, {@options}.

The Tie::Layers program module contains the tie file handle Tie::Layers package. The Tie::Layers package provides the ability to insert a stack of subroutines between file subroutines print and realine and the underlying $file. The syntax of the subroutines of each layer of the readline stack and the print stack must comply to the the requirements described herein below.

This is necessary so that the Tie::Layers READLINE and PRINT subroutines know how to transfer the output from one layer to the input of another layer. The stacks are setup by supplying options with a reference to the subroutine for each layer in the print stack and the readline stack. The Tie::Layers are line orientated and do not support any character file subrouintes.

The getc, read, and write file subroutines are supported by the Tie::Layers package. The seek routines are line oriented in that the seek and tell subroutine positions are the line in the underlying file and not the character position in the file.

JideBuilder is a Groovy builder for the open source JIDE Common Layer. The project is based on the original SwingBuilder.

The goal of the project is having a builder for swing apps that seamlessly integrates default swing and jide components.

The layer extract plug-in is a Gimp plug-in that creates a new image/film by periodically extracting layers from another image.

It takes one interval (number of sequent layers) every period. The number of periods can be limited.

"< Image >/Filters/Animation/Layer Extract"

GuiLoader/C++ is a C++ binding to GuiLoader library.

GuiLoader/C++ is a convenience layer that simplifies development of GuiLoader based applications written in C++ language by introducing exception safety, binding GTK+ objects defined in GuiXml to C++ variables and type-safe dynamic connection to signals.

Lua-Sqlite3 project is a binding of Sqlite3 for Lua.
Lua-Sqlite3 is unique in contrast to other database bindings that it consists of two layers.
The first layer translates the SQLite 3 implementations C API to Lua. The first layer is called the backend.
The second layers are frontend layers, written in Lua. These layers provide a nice and smart view of the database
Currently, Lua-Sqlite3 implements two frontends:
- A specialiced frontend which provides all sqlite3 capabilities.
- A LuaSQL compatible frontend as used on the Kepler Project.
Enhancements:
- Lua 5.1 support was added, and 5.0 is still supported.
- An autoconf configure script is provided.

RULI stands for Resolver User Layer Interface. Its a library built on top of an asynchronous DNS stub resolver. RULI provides an easy-to-use interface for querying DNS SRV resource records. The goal is to promote wide deployment of SRV-cognizant software. RULI aims to fully support SRV-related standards. There are bindings for PHP, Perl, Guile/Scheme, Java, and Lua. IPv6 is supported.

Now you can understand the benefits of SRV records and please see how RULI can help you.

SRV records are more complex than A records

Handling DNS SRV is not as simple as to deal with ordinary address records. When one performs a query for A records by calling gethostbyname(), he gets a list of addresses which should be contacted in the same order as they were received. For SRV records, there is an additional logic that must be applied to the records, based on their weight and priority, to discover the correct sequence for contacting them.
RULI can handle SRV records for you

The SRV logic is described in RFC 2782. Those who intend to use SRV benefits in their application are expected to implement that exact behavior. RULI can help here: it automatically performs all the SRV logic for you.
Keep focus on your application logic

Application developers probably want to spend time on their business logic; not dealing with the details of the DNS protocol or implementing the SRV specification.

RULI is a tested framework designed to properly fetch SRV records. It saves you time and head aches.
RULI is free as in free beer and in free speech

PHP MySQL Database Layer Class is a php class providing some very useful methods to work with a mySQL database.
Main features:
- connects you to a mySQL host and select a database in a single call (opposed to PHPs native functions which requires two steps)
- has a "query" method that has the same role as PHPs mysql_query but this one will tell you about the affected rows (through the "affectedRows" property) when executing an INSERT, UPDATE, DELETE query and about the found rows (through the "foundRows" property) when executing a SELECT query - the "foundRows" property tells you how many records would the query return if there was no LIMIT applied to it - very useful when creating listing so you dont have to do a query to determine how many records you have in a database and the again a query to show only the records from a page
- has an "escape_string" method that will "mysql_real_escape_string" your string weather the magic_quotes are on or not
- has a "dlookup" method that i am sure you will find VERY useful once you get to know it: it return data from a single table cell based on standard mySQL WHERE criteria - see the manual for detailed info! (yes, it acts exactly like the function with the same name from microsft access)
- provides you with a very useful debug interface which shows you each query your script is running, for how long, the total number of queries made, the total execution time of your queries, errors of your queries and what are the values of $_GET, $_POST, $_COOKIES and $_SERVER superglobal variables. The debug interface is template driven and supports localisation.
- it will notify you if a specific query is executed more than once and will advise you to optimize the script
- you can instruct it to send you an email if a query runs longer then a specified time
- the code is heavily documented so you can easily understand every aspect of it and even maybe use it as a php tutorial
Enhancements:
- the state of $_FILES and $_SESSION superglobals are now also shown in the debug window
- better integration with XTemplate (previously, there was a variable assigned to each entry in the language file now the XTemplates feature to handle arrays is used)
- properties will now have default values in PHP 4