Free mood software for linux

Domo is a music organizer which indexes digital audio sources, extracts all information and inserts into a database.
Domo is in the first place a music organizer. Domo indexes audio sources, extracts all possible information (mpeg headers, ID3 tags, MusicBrainz,...) and inserts everything into a relational database. In this database you can then query, export and compare with other sources (playlist, music cd, ...).
Main features:
- Song based comparison of 2 input sources (see compare page)
- Convertion between different playlist formats
- mp3, ogg meta data extraction & setting
- Retrieval of meta information for unknown songs through TRM audio fingerprints
- Retrieval of Audio CD meta information through the MusicBrainz service
- Maintaining of a wishlist
- Specify your own album format (eg: %genre/%artist - %title (%year))
- Specify your own custom track format (eg: %artist - %trackno - %title)
- Query tracks and albums on artist, title, filename, album title,...
- Easy interface to the internet or other applications through a relational database (MySQL, PostgreSQL, ODBC, SQLITE...)
- Create a backup copy of the music database
- Powerfull song filename/metatag cleanup
- Generate statistics like "top 10 artists", "number of duplicate songs", etc
- Group songs in the database into collections (per user)
- Platform independent
- Assign a mood to tracks (eg: happy, sad, in love, ...)
- Give tracks, albums, ... a score out of 10
- Easy browsing of your collection per Genre or per CD
Enhancements:
- replaced id3lib with taglib
- added and integrated settings which allow choosing metainfo preference (filename or metatag) and which allow the user to specify a custom track format
- writing of metatags is now supported
- bugfixes
- added right-click context menu to score tracks, set mood, delete CDs & rename
- albums
- increased possible query fields
- possible to query albums
- consistency dialog much, much improved (supports genre, album, etc...)
- finally fixed mysql database/account creation permission issues, newly created account
- should be fairly restricted.
- added a genre-centric browse list (in addition to the CD centric one)
- updated statistics to reflect mood popularity and best scoring artists

Smart DJ lets you find tracks based on how similar they sound to each other.

Smart DJ can also automatically add new tracks to your playlist based on how similar they are to what youve been listening to.

You already know how powerful amaroKs search and playlist management capabilities are. Just imagine how cool it would be to find songs that sounds like the one youre listening to, right now. Similar genre, similar sound, similar tempo. Now imagine this: you start playing one of your favorite songs, and, as time goes by, amaroK adds similar songs to your playlist, maintaining the mood. Not just "songs someone else found similar", but songs that truly sound alike, same genre, same mood, same tempo.

Thats what Smart DJ does. Start with a good song, and let amaroK Smart DJs Auto DJ do the rest. Or scratch on your favorite DJ program, and Smart DJ will let you find what to play next real quick. Or build fantastic playlists, sorted by tempo, or song similarity, the sky is the limit. Or simply take any of Smart DJs suggestions for similar songs in the Context browser. Thats the greatest way to discover an entire music collection.

This plug-in is perfect for people who hate making playlists, or hate the predictibility of hearing a playlist, or hate amaroKs Dynamic mode tendency to add songs that ruin the mood. This plug-in is also for people who want to discover the lost and unknown good songs in their own collection. Finally, this plug-in is perfect for DJs who want to plan good sets of songs and playlists for live performance.

eJourn is an application designed to help you track a journal or diary.
The general purpose of a journal, outside of a place to express frustrations, is to track events. Sometimes you keep a journal to track what you did today, maybe for your code, maybe for your general life: My great grandpa kept a very boring journal tel ling about things like "I went to town today."
Main features:
- Search functionality to help you find things based on keyword.
- Multiple Journals, to help you seperate things: Like keep a journal for a project, and a totally seperate personal one.
- Chronological ordering: Your paper does this, if you were careful; I promise to force you to
- Meta information, what was the weather like, how was your mood, when did you actually write the entry, does it relate to anything?
- Links/Relations to other journal entries, searches, or web URLs; and maybe more to come. These look like links in editable text.
Command line access:
- Ability to post data by piping into the running program
- Ability to pipe the current entry or selected text out of the program

Paloma is a program to manage a database of digital music files and facilitate their retrieval and playback in interesting ways. It works with music files of any form--mp3 files, ogg files, MIDI files, whatever youve got a player for--and file formats can be freely intermixed. Its intended to replace a traditional CD player/changer system. Paloma makes it easy to rip your entire CD collection (or even your favorite vinyl records) and store it on your hard disk for instant random access.
However, Paloma is more than a virtual CD player. There are already dozens of these in existence, and I have no interest in competing with them. In fact, Paloma works nicely together standalone jukebox programs.
What Paloma adds is the management of your music in a relational database, instead of a more traditional hierarchical database. A physical CD collection, for instance, is hierarchical: you might have your CDs on the rack grouped together by artist, so that for each artist, you have a number of CDs to choose from, and from each CD, you can play a number of songs.
This is not a bad system. It works well for finding a particular song (providing you remember what CD it was on) or for playing a particular artist (you might put a couple of Tori Amos CDs in your CD player, for instance, and push "random"). Most jukebox programs provide a functionally similar interface, by storing the songs hierarchically in this way in some kind of directory structure.
Paloma can do this too, although its not as slick as a specialized jukebox program. But with a relational database, you can also do a lot more. You could play all the songs by Frank Sinatra (for instance) in your collection, even if you dont own a single Frank Sinatra CD--it will pull together all the Sinatra songs from all the different lounge compilations you might have. Or you can bring up all the songs written by Jim Steinman, which would include those sung by Meat Loaf as well as those sung by Bonnie Tyler. Or maybe, if youre in a romantic mood, all the songs that have the word "love" in their title. Or all the classical music pieces shorter than five minutes. Or for a rainy Sunday, nothing but jazz--a good mix of all the jazz songs in your collection. Or if youre feeling nostalgic, all the songs you own that were recorded between 1975 and 1985. You get the point.
Paloma will soon support personal customization of your database, allowing the addition of fields and custom queries by the user. (Actually, it supports this now; it only lacks a GUI to easily define these custom fields.) So youre not restricted just to the sorts of things I wanted to query my database on.
This early release of Paloma is fully functional, although there is of course much room for future development. If you find it useful, or if you have further suggestions for extensions, please dont hesitate to drop me a line!
Enhancements:
- Added the new "Contexts" tab to the Configure page, which allows specialization of commands and file paths for different OSs and/or machines on the network. This allows, for instance, a Windows machine to access a Paloma database stored on a Linux
- server, even though the file path on the Windows machine to the volume store will be different from the path on the Linux machine to the same volume store, and even though a different set of commands may be needed on the Windows machine to play and/or verify these soundfiles.
- Added "AudioTron TOC file" to the list of supported playlist types. This allows you to export a "playlist" file to the top of your volume store that is really just a complete list of files for a connected AudioTron device (see http://www.turtlebeach.com/site/products/audiotron/producthome.asp) to scan.
- Added "AudioTron play" to the list of supported playlist types. This is a special "playlist" that actually communicates directly to a connected AudionTron device and starts playing the songs immediately. Specify password@hostname as the playlist filename.
- Added prompts to switch disks if necessary when exporting a playlist, allowing you once more to store your collection of song files on a stack of CDs, which you can rotate in as necessary to play songs.
- Added support for Python 2.3.4.

LJ::Simple is a Perl module to provide a simple OOP-based API for accessing the LiveJournal system.
Main features:
- Log into LiveJournal
- Post a journal entry
- Edit a journal entry
- Delete a journal entry
Example
The following example posts a simple message into the test LiveJournal using the LJ::Simple::QuickPost method.
use LJ::Simple;
LJ::Simple::QuickPost(
user => "test",
pass => "test",
entry => "Just a simple entry",
) || die "$0: Failed to post entry: $LJ::Simple::errorn";
The next example shows how to post an entry into the test LiveJournal using the complete, object-based, interface:
use LJ::Simple;
my $lj = new LJ::Simple ({
user => "test",
pass => "test",
});
(defined $lj)
|| die "$0: Failed to log into LiveJournal: $LJ::Simple::errorn";
my %Event=();
$lj->NewEntry(%Event) ||
die "$0: Failed to create new entry: $LJ::Simple::errorn";
my $entry=SetMood(%Event,"happy")
|| die "$0: Failed to set mood: $LJ::Simple::errorn";
$lj->Setprop_nocomments(%Event,1);
my ($item_id,$anum,$html_id)=$lj->PostEntry(%Event);
(defined $item_id)
|| die "$0: Failed to post journal entry: $LJ::Simple::errorn";

BuddySpace is an instant messenger with four novel twists: (1) it allows optional maps for geographical & office-plan visualizations in addition to standard buddy lists; (2) it is built on open source Jabber, which makes it interoperable with ICQ, MSN, Yahoo and others; (3) it is implemented in Java, so it is cross-platform; (4) it is built by a UK research lab, so it is 100% free with full sources readiily available. But BuddySpace is about more than just messaging, as we explain below.

One of the key factors that led to the widespread popularity of Instant Messaging applications from 1997 onwards (including ICQ, AOL, Yahoo!, MSN, Odigo, and Jabber messengers) was the concept of pushed presence: the automatic notification of the appearance of friends and colleagues online.

However, Instant Messaging (IM) is just one of many possible presence-related and presence-dependent applications. For example, presence-enabled applications can facilitate safety-tracking of children by mobile phone, support for emergency services, blind-date radar, group teleconference management, multiplayer games, and anything involving the collaboration of individuals separated in space and time.

Why phone a contact only to receive an engaged tone or pre-recorded message, when the telephone network already knows what state your contact is in, and could indicate this directly on your contact list? All of these concepts embody varying degrees of what we refer to as enhanced presence management.

The concept of presence has matured in recent years to move away from the simple notion of online/offline/away, towards a rich blend of attributes that can be used to characterise an individuals physical and/or spatial location, work trajectory, time frame of reference, mental mood, goals, and even intentions! Our challenge is how best to characterise presence, how to make it easy to manage and easy to visualise, and how to remain consistent with the users own expectations, work habits, and existing patterns of Instant Messaging and other communication tool usage.

BuddySpace generalizes the concept of Buddy List (popularised by Instant Messaging tools such as AOL Instant Messenger, ICQ, MSN Messenger, and Yahoo Messenger) to provide multiple views of collaborative workgroups according to users needs and tastes. Our aim has been to provide a personal dashboard or radar screen so that one can observe the availability and interaction state of colleagues worldwide in a manner that exhibits the following desirable properties:

* immediate: real-time updates need to be pushed instantly to users rather than pulled in by request -- the push approach helps keep updates more palpable and informative
* peripheral and therefore non-intrusive: users lead busy lives, and dislike being bombarded with yet more information, so we aim to keep awareness of colleagues available in a compact manner that can be noticed peripherally
* customisable: some people prefer simple or hierarchical lists, some prefer visual maps, some prefer status lights, and so on; some prefer a Windows look-and-feel, some a Mac-- we need to cater for diverse user preferences and capabilities
* scaleable: we have to provide ways to indicate the presence of potentially enormous numbers of people, even given that these numbers will be filtered down for personal use -- researchers inhabit workspaces with many hundreds of colleagues around the globe; the Open University has well over 150,000 students online; large peer-spaces like music swapping communities have many millions of users connected simultaneously
* interoperable: with several hundred million users of the Big Four (AIM/ICQ/MSN/Yahoo!), it is crucial that any approach allow interopebility with systems to which our users already subscribe; this is one of the many reasons we built BuddySpace entirely on top of Jabber (www.jabber.org), which provides gateways to the Big Four products.
* cross-platform: we need to service a community not only on Windows, Unix/Linux, and Mac desktop and notebook configurations, but also on PDAs and mobile phones -- we therefore develop entirely in Java
* XML-literate: for future intelligent applications, communication transport needs to be about more than just string-transmission; another we adopted Jabber is that it is based entirely on a generic XML transport architecture, ideally suited for this purpose.
* open source: for the research community to join us and to gain leverage via our research output, we have ensured that BuddySpace is open source, available on SourceForge.
* clean: BuddySpace adheres rigorously to the Jabber specification, which means that it interoperates with other Jabber clients and servers without danger of the rogue behaviour that non-standard implementations inadvertently allow (e.g. the semantics of users inhabiting multiple groups is undefined in some clients, and can cause crashes).
* extendable: BuddySpace deploys a plug-in architecture which means that additions, such as new visualizations, and new concepts such as gaming interfaces, are readily achievable

BuddySpace fulfills all the above criteria, and provides a compelling user interface that can be highly compact, yet provide users with an important feel-good factor, akin to seeing nearby office lights turned on when entering ones office building at night. By studying the semantics of presence, we can also augment the existing impoverished presence states in a principles manner, providing capabilities that are more representative of the way real users work. Forthcoming capabilities will include automatic location updates via mobile devices, and the use of semantic matchmaking via intelligent profile handling, in order to help users quickly find and filter colleagues of particular interest.

KLuJe is a client for the popular online journal site LiveJournal. The latest release is version 0.7 and is available as an RPM, SRPM, or in a source tarball. Development code is available via anonymous CVS at cvs.kluje.sourceforge.net. Check out module kluje. If you want to acces CVS see the informations above.
Main features:
- Posting with optional subject or mood
- Posting to multiple journals or communities
- Editing events in the past
- Systray icon, with menu of quick links
- Auto polling for friends posts, w/animated systray icon alert
- Integrated spell checking
- Fast server support (for paid accounts)
- MD5 password storage/transmission
Enhancements:
- Fixed bug with incorrect server request encoding. Implemented correct LJ protocol encoding: http://www.livejournal.com/doc/server/ljp.csp.guide.intro.html
- Fixed bugs with non-english languages (UTF-8 everywhere).
- Get rid of deprecated KStdAction::showToolbar() call.
- Several major bugs with edit past events functionality.
- Removed support of faster LJ server because this functionality is completely outdated.
- LiveJournal URL changed to www.livejournal.com/interface/flat.
- Added editline in Preferences dialog with server URL line.
- Added new authors to about box.
- Fixed bug with LiveJournal menu corruption after GUI rebuild (i.e. toolbar changed)
- Fixed bug with KConfig object change notification (weve tried to read entries from incorrect configuration group).
- Re-wrote and expanded docs in doc/en/index.docbook