Free summer camp software for linux

Somamddd come from Soma MetaData Daemon and is a daemon that gets input from the current song scheduled by somad and updates the icecast (1 and 2) flags. So, the clients can show info about the current song of your radio.

Soma project started in summer 2003 to manage the digital version of an acitvists radio old spools.

The first release just gave just the chance to play random some audio files in a directory using an external program (at that time mpg123). In despite of that this software was never used, i kept on thinking about soma project for some weeks, until i started directly to work with a group called Reload, which was experimenting at the time a project called "eterete" and creating a place for a web radio at Pergola Tribe (a selfmanaged house in Milan).

We used, of course, a release, which was a little bit better to manage the radio-playlist and of course we implemented the software itself. From september till december soma became a software suite, configurable through file and (remote administration...). Thats thanks to the relationships and the inputs that such a community like Reload can create.

A group of passionate activists was able to make broadcastings and broadcast schedules, to find out new problems and to give implementation advices. They also suggest me the idea that soma (originally a simple play-list manager) could become a programs suite, which has a player, a software for deferred broadcasting, a more user friendly admininstration, documentation and distribution.

Some time after came soma player and soma admin. The player was still very behind compared to my implementation ideas. Somadmin was straight away on line and advertised on radio.inventati.org/somadmin/

In January 2004 we showed Soma at the first italian (web and air-waves) radio meeting in Naples.The meeting was technologically and politically profitable and it was an attempt to build up a real radio-network. Radio.inventati.org was actually the only example od direct cooperation among even very different people: individuals, improvised groups, very old and movement radios and experiences from overseas countries.

On the web site there are occasional streamings, weekly streamings, and 24hrs music flows.

The object of the technical research was a digital environment, which could let individuals or whole communities gain access to a common schedule with resum?s,
repetitions, deferred programs, live broadcastings, regular broadcastings as one national and international network. Soma could satisfy this need and could be easly managed through the web thanks to somadmin, which could update the soma admin in real time.

The developments went on. Somaplayer is now reality. The only music player which can stream directly an mp3, an ogg vorbis, a wav, a track from an audio cd or a streaming directly on an icecast server (icecast 2 or shoutcast) or just play it on a computer using sound drivers or sound daemons.

At the moment more other people work at this project, who debug the software, write docs, work at the website and make installation packages (for debian).

Soma is a suite of programs that let you play and schedule audio files from the Web.
Soma suite supports extra utilities using run-time loadable modules and includes a broadcasting scheduler, a tool to control it via TCP/IP, and an utility to check configuration file syntax.
Soma project started in summer 2003 to manage the digital version of an activists radio old spools.
The first release just gave just the chance to play random some audio files in a directory using an external program (at that time mpg123). In despite of that this software was never used, i kept on thinking about soma project for some weeks, until i started directly to work with a group called Reload, which was experimenting at the time a project called "eterete" and creating a place for a web radio at Pergola Tribe (a selfmanaged house in Milan).
We used, of course, a release, which was a little bit better to manage the radio-playlist and of course we implemented the software itself. From september till december soma became a software suite, configurable through file and (remote administration...). Thats thanks to the relationships and the inputs that such a community like Reload can create.
A group of passionate activists was able to make broadcastings and broadcast schedules, to find out new problems and to give implementation advices. They also suggest me the idea that soma (originally a simple play-list manager) could become a programs suite, which has a player, a software for deferred broadcasting, a more user friendly admininstration, documentation and distribution.
Some time after came somaplayer and somaadmin. The player was still very behind compared to my implementation ideas. Somadmin was straight away on line and advertised on radio.inventati.org/somadmin/
In January 2004 we showed Soma at the first italian (web and air-waves) radio meeting in Naples.The meeting was technologically and politically profitable and it was an attempt to build up a real radio-network.
Radio.inventati.org was actually the only example od direct cooperation among even very different people: individuals, improvised groups, very old and movement radios and experiences from overseas countries.
On the web site there are occasional streamings, weekly streamings, and 24hrs music flows.
The object of the technical research was a digital environment, which could let individuals or whole communities gain access to a common schedule with resum?s, repetitions, deferred programs, live broadcastings, regular broadcastings as one national and international network.
Soma could satisfy this need and could be easly managed through the web thanks to somadmin, which could update the soma admin in real time.
The developments went on. Somaplayer is now reality. The only music player which can stream directly an mp3, an ogg vorbis, a wav, a track from an audio cd or a streaming directly on an icecast server (icecast 2 or shoutcast) or just play it on a computer using sound drivers or sound daemons.
At the moment more other people work at this project, who debug the software, write docs, work at the website and make installation packages (for debian).
Enhancements:
- This release fixes three bugs related to group permissions, the 31st of months, and an error in libsoma related to buffers and protocols.

The following is an excerpt from a poster presented at the American Astronomical Societys 2000 Summer meeting in Rochester, NY.

ADS roughly 1,000,000 scanned pages contain numerous diagrams and figures for which the original data sets are lost or inaccessible. Having scans for the figures invites digitizing the data points to recover at least a part of these data.

Performing this digitization automatically is still beyond the capabilities of current OCR systems, but the computer can ease this process for a human.

This was the starting point for Dexter, a Java applet that runs in the users browsers and provides an interface for selecting the part of the page that is of interest. On that selection, coordinate axes, points and error bars can be marked and, of course, corrected. [...]

In the future, we plan to implement some recognition algorithms that would, e.g., trace a line for the user or automatically search for markers.

CQL::Parser is a Perl module that compiles CQL strings into parse trees of Node subtypes.

SYNOPSIS

use CQL::Parser;
my $parser = CQL::Parser->new();
my $root = $parser->parse( $cql );

CQL::Parser provides a mechanism to parse Common Query Language (CQL) statements. The best description of CQL comes from the CQL homepage at the Library of Congress http://www.loc.gov/z3950/agency/zing/cql/

CQL is a formal language for representing queries to information retrieval systems such as web indexes, bibliographic catalogs and museum collection information. The CQL design objective is that queries be human readable and human writable, and that the language be intuitive while maintaining the expressiveness of more complex languages.

A CQL statement can be as simple as a single keyword, or as complicated as a set of compoenents indicating search indexes, relations, relational modifiers, proximity clauses and boolean logic. CQL::Parser will parse CQL statements and return the root node for a tree of nodes which describes the CQL statement. This data structure can then be used by a client application to analyze the statement, and possibly turn it into a query for a local repository.

Each CQL component in the tree inherits from CQL::Node and can be one of the following: CQL::AndNode, CQL::NotNode, CQL::OrNode, CQL::ProxNode, CQL::TermNode, CQL::PrefixNode. See the documentation for those modules for their respective APIs.

Here are some examples of CQL statements:

george
dc.creator=george
dc.creator="George Clinton"
clinton and funk
clinton and parliament and funk
(clinton or bootsy) and funk
dc.creator="clinton" and dc.date="1976"

An MP3 LEnder is a simple MP3 server written in C.
AMPLE is short for "A MP3 LEnder" (interesting name just to make a good abbreviation?)
I wrote AMPLE one summer when I was coding for a company and got fed up with having to FTP over all my MP3 files from my home server to the computer at work just to listen to them. And the other "MP3 servers" I could find didnt fit my needs for one of the following reasons:
Depended on libfoo, libbar, python, perl, php3, Apache, libssl, etc, etc, etc...I just wanted to listen to the files
Had a lot of features for "DJ:ing" etc that I really didnt need
Well....it was fun to write too :)
So whats good with AMPLE?
Small, standalone (written in C using no external libraries)
Portable (I think), I often try to compile it on the SourceForge compile farms
Allows you to listen to your own MP3s away from home, nothing more, nothing less
This is beginning to sound like marketing cr*p so Ill just stop right there, check out the links on the left for more info.
Enhancements:
- Make ID3v2 code understand versions 2.2.0 -> 2.4.0 (all currently existing versions)
- Reformat HTML output somewhat
- Fix search-and-replace error in libwrap code
- Made servername a config option
- Renamed -r to -n (NON-recursive)
- Changed the DEF_LOGFILE (it pointed to ample.conf instead of ample.log)
- Much work on autoconf stuff, should work much better now
- Some more testing on other architectures (Ive compiled it on everything from Tru64 to Linux to *BSD)

SomaList is a part of the Soma project.

Soma project started in summer 2003 to manage the digital version of an acitvists radio old spools.

The first release just gave just the chance to play random some audio files in a directory using an external program (at that time mpg123). In despite of that this software was never used, i kept on thinking about soma project for some weeks, until i started directly to work with a group called Reload, which was experimenting at the time a project called "eterete" and creating a place for a web radio at Pergola Tribe (a selfmanaged house in Milan).

We used, of course, a release, which was a little bit better to manage the radio-playlist and of course we implemented the software itself. From september till december soma became a software suite, configurable through file and (remote administration...). Thats thanks to the relationships and the inputs that such a community like Reload can create.

A group of passionate activists was able to make broadcastings and broadcast schedules, to find out new problems and to give implementation advices. They also suggest me the idea that soma (originally a simple play-list manager) could become a programs suite, which has a player, a software for deferred broadcasting, a more user friendly admininstration, documentation and distribution.

Some time after came soma player and soma admin. The player was still very behind compared to my implementation ideas. Somadmin was straight away on line and advertised on radio.inventati.org/somadmin/

In January 2004 we showed Soma at the first italian (web and air-waves) radio meeting in Naples.The meeting was technologically and politically profitable and it was an attempt to build up a real radio-network. Radio.inventati.org was actually the only example od direct cooperation among even very different people: individuals, improvised groups, very old and movement radios and experiences from overseas countries.

On the web site there are occasional streamings, weekly streamings, and 24hrs music flows.

The object of the technical research was a digital environment, which could let individuals or whole communities gain access to a common schedule with resum?s,
repetitions, deferred programs, live broadcastings, regular broadcastings as one national and international network. Soma could satisfy this need and could be easly managed through the web thanks to somadmin, which could update the soma admin in real time.

The developments went on. Somaplayer is now reality. The only music player which can stream directly an mp3, an ogg vorbis, a wav, a track from an audio cd or a streaming directly on an icecast server (icecast 2 or shoutcast) or just play it on a computer using sound drivers or sound daemons.

At the moment more other people work at this project, who debug the software, write docs, work at the website and make installation packages (for debian).

Storable package contains persistence for Perl data structures.

SYNOPSIS

use Storable;
store %table, file;
$hashref = retrieve(file);

use Storable qw(nstore store_fd nstore_fd freeze thaw dclone);

# Network order
nstore %table, file;
$hashref = retrieve(file); # There is NO nretrieve()

# Storing to and retrieving from an already opened file
store_fd @array, *STDOUT;
nstore_fd %table, *STDOUT;
$aryref = fd_retrieve(*SOCKET);
$hashref = fd_retrieve(*SOCKET);

# Serializing to memory
$serialized = freeze %table;
%table_clone = %{ thaw($serialized) };

# Deep (recursive) cloning
$cloneref = dclone($ref);

# Advisory locking
use Storable qw(lock_store lock_nstore lock_retrieve)
lock_store %table, file;
lock_nstore %table, file;
$hashref = lock_retrieve(file);

The Storable package brings persistence to your Perl data structures containing SCALAR, ARRAY, HASH or REF objects, i.e. anything that can be conveniently stored to disk and retrieved at a later time.

It can be used in the regular procedural way by calling store with a reference to the object to be stored, along with the file name where the image should be written.

The routine returns undef for I/O problems or other internal error, a true value otherwise. Serious errors are propagated as a die exception.

To retrieve data stored to disk, use retrieve with a file name. The objects stored into that file are recreated into memory for you, and a reference to the root object is returned. In case an I/O error occurs while reading, undef is returned instead. Other serious errors are propagated via die.

Since storage is performed recursively, you might want to stuff references to objects that share a lot of common data into a single array or hash table, and then store that object. That way, when you retrieve back the whole thing, the objects will continue to share what they originally shared.

At the cost of a slight header overhead, you may store to an already opened file descriptor using the store_fd routine, and retrieve from a file via fd_retrieve. Those names arent imported by default, so you will have to do that explicitly if you need those routines. The file descriptor you supply must be already opened, for read if youre going to retrieve and for write if you wish to store.

store_fd(%table, *STDOUT) || die "cant store to stdoutn";
$hashref = fd_retrieve(*STDIN);

You can also store data in network order to allow easy sharing across multiple platforms, or when storing on a socket known to be remotely connected. The routines to call have an initial n prefix for network, as in nstore and nstore_fd. At retrieval time, your data will be correctly restored so you dont have to know whether youre restoring from native or network ordered data. Double values are stored stringified to ensure portability as well, at the slight risk of loosing some precision in the last decimals.

When using fd_retrieve, objects are retrieved in sequence, one object (i.e. one recursive tree) per associated store_fd.

If youre more from the object-oriented camp, you can inherit from Storable and directly store your objects by invoking store as a method. The fact that the root of the to-be-stored tree is a blessed reference (i.e. an object) is special-cased so that the retrieve does not provide a reference to that object but rather the blessed object reference itself. (Otherwise, youd get a reference to that blessed object).