Free high output light bulbs software for linux

Audio Input-Output Library (libaio) is meant to solve the problem of differing digital audio platforms once and for all.

JACK is unnecessarily complex for most applications, and while libaos support for file output is cool, it limits what the API can do and is therefore inadequate for any kind of real time application.

libaio provides a clean application interface and a simple compile-time driver switching decision, yielding a lightweight way to use the local sound hardware without having to care what it is.

Libaios first sparkle was when I, Hod McWuff (alias, of course), found myself trying to debug ALSA implementations for libao and madplay, and another audio-related project Id been working on. That project needed multiplatform audio support of its own, with latency management, which libao lacked.

It also seemed that libao shouldnt have been trying to be both a hardware abstraction *AND* an output abstraction, and also that it seemed more intuitive as an output (live vs file) abstraction.

Enter libaio. All it does is abstract the local sound hardware platform, to present a clean, uniform interface to playing and capturing digital audio, with facilities for basic latency management. It was written from scratch around its developing ALSA driver, from many many reference sources including libao and Robert Leslies excellent madplay MP3 decoder, and of course the ALSA documentation and examples.

Libaios distinction comes from its build-time decisionmaking. It only compiles and links the best driver available for the given platform. Therefore, selecting and loading a driver no longer applies; and well it shouldnt, theres never more than one correct choice anyway.

Libaio is not intended to replace libao; rather it is intended to supplement it. The key argument is, why would anyone EVER have more than one running sound platform type on any single machine? Sure, they might have ESD or ARTS, but they more resemble file output than a live device. Theres also the OSS emulation in ALSA, but given a good ALSA driver, whod use OSS?

Then theres the fact that applications have to tell libao what "plugin" to use, and all the drivers in libao have different parameters. That means the application has to know more than it should about what it shouldnt have to see. The app shouldnt have to say more than "give me the local device for playback with *** format" or something to that effect, and start writing.

Finally, plugins for stuff like proprietary file formats, ESD et al, but there shouldnt be any need for more than one of (ALSA|OSS|SUN|WIN32|MACOSX ) on any given distribution. Therefore, binary distribution of a compiled-in driver is possible, even preferred.

It is proposed that all of the hardware drivers in libao, and madplay, and several other places, be reviewed and ported to libaio. Then, they can be removed from those packages in favor of an AIO interface.

Installation:

## building
./configure
make


## installing (as root)
make install

Simple utility that turns your monitor into a configurable strobe light.

Source code is included alongside the executable "strobelight" in the archive.

Template Lite is a smaller, faster alternative to the Smarty template engine.
For the most part, it is a drop in replacement for Smarty but uses around half of the memory and is considerably faster and far less CPU intensive when compiling and displaying templates.
Template lite was originally created by Paul Lockaby as a smaller replacement for Smarty. The original package was called Smarty Light. Even though Smarty is an Open Source project the creators of Smarty decided to trademark the name Smarty. Because of this trademarking of the name they contacted Paul Lockaby and told him he could nolonger use Smarty in the name for the package.
Paul Lockaby gave me permission to fork the project if I wanted as he was closing down support and developement for Smarty Light. The initial release of Template Lite contains a few minor bug fixes and some extra features.
I plan on adding more features to Template Lite over the next few months. For the most part Template Lite is a drop in replacement for Smarty. The nice thing about this package is how it uses around half of the memory of Smarty and it is considerably FASTER and far less CPU intensive when compiling and displaying templates.
Enhancements:
- register_resource and unregister_resource support was added.
- Different resources are supported by everything except for cached template output.
- The _get_resource internal function was added for processing "file:" and absolute tag resources.
- The resize_image plugin was added.
- Support for absolute paths to template files was fixed.

Sys::OutPut is a Perl module to help make output easier.

SYNOPSIS

usage Sys::OutPut;

talk $fmtstr [, @args];

out $fmtstr [, @args];

put $fmtstr [, @args];

err $fmtstr [, @args];

debug $fmtstr [, @args];

$Sys::OutPut::quiet = $::quiet;

$Sys::OutPut::debug = $::debug;

These subroutines will make generating output to STDOUT and STDERR easier.

All of the routines treat the $fmtstr argument as a printf format string, with @args as the format string arguments.

The talk routine generates output to STDERR only if the variable $Sys::OutPut::quiet is non-null and non-zero.

The out routine generates output to STDOUT, with a newline appended to , if it is not already terminated with one.

The put routine generates output to STDOUT, without any additional trailing newline.

The err routine generates output to STDERR, with a newline appended if needed.

The debug routine generates output to STDERR only if the variable

$Sys::OutPut::debug is non-null and non-zero, which is also returned as the result.

This allows for convenient usages such as in the following example:

sub foo {
...
return if debug "Stopping now.";
...
next if debug "Skipping further processing";
...
}

If not defined by the user, the $Sys::OutPut::quiet and $Sys::OutPut::debug variables are initialized from their corresponding main variables $::quiet and $::debug, respectively, unless they are already defined.

Aurora-Imetal-Light 0.2 provides you with a nice GTK theme for GNOME users, based on the Aurora engine. It is actually a mod of the Aurora-steel and Imetal themes.

GNOME is an international effort to build a complete desktop environment the graphical user interface which sits on top of a computer operating system entirely from free software. This goal covers creating software development frameworks, selecting application software for the desktop, and working on the programs which manage application launching, file handling, and window and task management.

GNOME is part of the GNU Project and can be used with different Unix-like operating systems, most notably Linux, and as part of Java Desktop System in Solaris.

Enhancements:

• 2 x gtk themes 1 x emerald
• Includes a second panel.bg for those who use global menu!
• Standard is non global menu.

Requirements:

• Aurora Gtk Engine

Q Light Controller 2 (QLC) aims to be a free alternative to commercial lighting software and hardware. The main emphasis is to build a software that can be used to control any kinds of lighting equipment.
QLC uses the dmx4linux driver suite to access various hardware interfaces. Currently DMX512, Analog 0-10V and MIDI control systems are being supported by dmx4linux. Refer to dmx4linux interfaces for more information on supported interfaces.
Q Light Controller is free software licensed under the GNU General Public License.
Main features:
- Easy to use device-oriented interface
- Control up to 512 DMX/Analog channels thru DMX4Linux
- Use one of the ready-made fixture definitions, or
- Define your own fixtures with the device class editor
- Create fast changing or smoothly fading scenes, chasers and sequences
- Easy programming of moving lights thru a pattern generator
- Conjure your favourite lighting desk layout with the virtual console