Free music collection software for linux

C Comic Collection project is a GTK application for downloading, cataloging, and viewing Web comics. It uses a MySQL database.
To compile this software, just type "make".
It requires development libraries for gtk, gtk_imlib, cURL, mysql and pthreads. If youre on Linux these should come with your distrobution; I dunno for other OS. If you only have the runtimes and are using a 386 derivative (Pentium et al) you can get a binary from http://c-comiccollect.sourceforge.net.
Compilation will produce a binary called "gtk-cc"; copy this to your /usr/bin (youll need root privileges, copy to your ~/bin (you wont) or just run it from where it is (./gtk-cc &).
You can populate the database by running the included "comiccollection.sql" against an empty database. (mysql -u < username > < dbname > < comiccollection.sql). It even includes some comics to get you started!
Enhancements:
- Minor improvements - only really relevant if you view KeenSpace comics.
- Fixed file non-deletion problem
- Fixed KeenSpace file download problem

My cOLLection manager is a manager program for your collections. My cOLLection manager is a fast and easy to use frontend for gdbm with an ncurses interface.

The program was originally designed to organize a large music CD collection, but it is has no restrictions on the entry of any other large range of items. Its main goal is flexibillity.

comisat Games Collection is an all-in-one free collection of games written in gambas for unix-like system. They are available in italian and (not completely) in english.

comisat Games Collection is FREE SOFTWARE, released under the terms of the GNU General Public License Version 2 as published by Free Software Fundation. You can help the development of comisat Games Collection testing the software, mailing bugs, translating the project in different languages, correcting and improving the code.

JavaDoc Taglets Collection is set of general purpose taglets for use with the JavaDoc tool. It provides a standard set of new tags, and allows you to create new ones by configuration or using simple Java interfaces. The project has been tested with J2SE 1.4 and 1.5 and JavaSE 1.6.
Enhancements:
- First public release of the Taglets Collection.
- Completed documentation for release 2.
- Added demos to userguide and distribution.
- Added to do list and known bugs information.

Do you have many MP3 files? Do you spend more time organizing them then listening to them? Do you store them on CDs? Do you have a car stereo MP3 player?
If so, MusicMan will help you organize your MP3, Ogg, from the most obvious place: Konqueror file manager.
Main features:
- Standarize the filenames of your music files.
- Guess info and set ID3 tags from the files name. Can be done to several files in one shot.
- Rename many selected files based on their ID3 tags.
- Set ID3 tags in mass for the selected files, with options from copying ID3s from other files, and leaving some ID3 fields untouched.
- Rename _ to space and vice-versa.
- Create HTML and Text indexes of your collections, including total playing time etc. 100% cofigurable thru templates.
- Create nice CD cover with nice full listing of your music files. 100% configurable thru templates.
- Organize your music collection to create a CD.
- See the change log for details.

Top Music allows you to publish music (albums, songs, sound tracks, rankings, artists, etc.) to create an online music portal.

It features: A-Z list of bands; band information (name, photo, genre, biography, etc.); discography; album information (title, year, covers, band, etc.); albums songs lists; song information (title, album, number, lyrics, etc.); the ability to listen to tracks; searching; ranking lists (most visited, most voted, etc.); a voting system; an uploads system; themes; an easy configuration screen; many blocks; multi-language support; easy installation; and a support forum, mailing lists, and Sourceforge.net support (CVS, files, etc.)

MusicTree is a small collection of Python scripts that helps you manage a large collection of music files. The project was designed to work with Unix systems (tested only on SuSE Linux), but may also work on Windows. For normal use you also need Vorbis Tools* and rsync.
The scripts help you:
- Maintain a central collection of high-quality (typically FLAC) files.
- Backup this collection on a second disk/machine.
- Generate a parallel collection of lower-quality (but much smaller) compressed (typically Ogg) files.
- Select an arbitrary subset of the compressed files (a "playlist").
- Upload the playlist to a second machine.
The scripts do not assume any particular directory layout (except that the music files live under a single root directory - that is not really a restriction since you can always use a separate directory and links to tie various directories together). Nor do you have to use a particular format (by default the scripts assume archive files are FLAC and the compressed files are Ogg encoded, but you can operate on different formats by changing the relevant commands in the configuration file).
However, the scripts do assume a that you have a basic understanding of how to use Unix. There is no installer or GUI - you run these from the command line and combine them with other command line tools (like find and xargs).
Directories and Machines
This documentation will talk about two different computers: "server" and "client". The "server" is typically a desktop machine with a large disk (or set of disks). This machine stores the high-quality "archive" of your music - all the files, with no (lossy) compression. It may also store a backup copy on a separate disk.
The "client" is typically a laptop or portable music player with a smaller capacity. Because it has restricted space you load it with a selection of (lossy) compressed files.
Separating server and client allows you to keep a safe, "perfect quality" archive where space is available, but also listen to more songs on portable devices with restricted resources.
The scripts expect these directories on the server:
Archive
This is where the complete, high-quality collection of music is stored. For example, this might be where your CD ripping software places files (I use kAudioCreator with the default settings).
Compress
A mirror of the Archive directory with lower-quality files. This is generated from the Archive directory by running the mt-encode script.
Select
A subset of the Compress directory, containging a "playlist" that will be copied to the client.
Backup
An optional second copy of the Archive (typically on a separate disk).
Installation and Configuration:
There is no automatic install. Instead, copy the files to a suitable directory and extend your PATH to include them.
For example, to put the files in the new directory ~/musictree (assuming you use the bash shell):
> cd
> tar xvfz musictree.tgz
> export PATH="$PATH:~/musictree"
Youll want to redefine PATH in your .bashrc or equivalent.
You also need to edit the example configuration file (musictree in the distribution) and (usually) copy it to ~/.musictree.
Suggestions for how to use the various scripts (eg. running mt-encode via cron) are in the following sections.
Enhancements:
- Volume normalization is now supported either via metadata, or by directly scaling the compressed files.

Yahoo::Music::Ratings is a method for retrieving a Yahoo! Music members song ratings.

SYNOPSIS

use Yahoo::Music::Ratings;

my $ratings = new Yahoo::Music::Ratings( {
memberName => yahooMusicMemberName,
} );

# Fetch an arrayRef of all yahooMusicMemberName song ratings
# this may take a couple minutes...
my $arrayRef = $ratings->getRatings();

# Print out a nice tab seperated version so that we can easily
# read the list in a spreadsheet program (and then filter by
# artists etc). tab_output() will output in artists alphabetical
# order.
print $ratings->tab_output();

This module provides a way to retrieve a users list of song ratings from Yahoo!s Music service, including the LaunchCast and Unliminted services.

As Yahoo! do not provide an offical feed for a member to download their ratings, the methods used within this module are subject to change and simply may not work tomorrow. However at the time of writing this README i would suspect the methods used should be stable for atleast a few days :)