Free artists software for linux

Data is fetched from audioscrobbler web services. In this version it shows nine views: top artists, top tracks, top albums, systems recomendations and recent tracks, etc. Data is updated every five minutes or clicking on refresh button.

Use: First write your last.fm user name on the input box and click the apply button. After a moment, use arrows button for select the view.

The GRP Playlist is a Noatun playlist plugin. It is a playlist inspired by ZInf, in which you can organize your multimedia files in groups based on the files meta information (Artist, Album, etc).

aTunes is an app to manage and play mp3 files.
Main features:
- Mp3 player
- Reads ID3v1, ID3v1.1 and ID3v2 tags (only essential information)
- Tag editor
- Show pictures of song: pictures inside ID3v2 tag, or in the same folder
- Load / save play list in m3u format
- Navigate through songs sorted by tag information or by folder
- Filters for fast find what you want
- Songs, albums or artists can be marked as favorites, and viewed through a special view
- Full view with all controls
- Simple view, with just essential controls
- Tiny view, to place window in a square of window
- Sticky borders for Simple and Tiny views
- Always on top property
- OSD (like amaroK)
- Five languages supported: english, spanish, french, german and portuguese
- State saved: repository, play list, last played song, shuffle, repeat, position in desktop, size, type of view...

amaroK Last.fm tags script fetches your tags from Last.fm for artists, albums, and tracks. It stores them as id3v2 COMM tags in your music files and appends them to the comment for the given track in amaroKs collection where they can be used to contruct smart playlists.

So far this script only fetches your tags, it doesnt syncronize changes you make locally back to Last.fm. Probably this feature should wait until the implementation of "labels" which is coming in amaroK 1.5.

Also so far it is only possible to fetch tags for a selection within a playlist. The other context sub-menus just provide helpful messages saying that this feature isnt implimented yet.

As usual this software comes with no warrenty, it might eat your lunch, etc.. That said it works for me.

I owe a large debt of gratitude to Miguel Angel Alvarez whoes amaroK Replaygain script served as the skeleton of this one. Thanks Miguel!

Battery77 project is a remake of the Battle City game. Play the game right at the Battery homepage.
Looking for 2d sprite artist (designer) to redraw the tiny gfx.
Enhancements:
- Level 5 added.
- Attempt to fix socket bug.
- Players tank shot interval is 300.

DaemonRip runs as a Unix daemon and polls a CD drive to see if an audio CD is inserted.

When an audio CD is detected, it will automatically connect to a CDDB server to determine the name, artists, and tracks of the CD, and begin to rip and encode the CD using your preferred ripping and encoding applications.

When finished ripping the disc, it will be ejected from the drive, allowing you to insert a new one to continue the process. No other user interaction is required.

DaemonRip project also can keep statistics about your ripping and encoding times, and logs all of the actions to a log file.

otto is a web based mp3 database and jukebox which can gracefully organize a very large number of albums. it is suitable for home or office workgroup use, or as an interface to a streaming internet radio station.

otto is written in perl. it requires perl5, mysql, the DBI and DBD::mysql perl modules (and a few others), and apache. mod_perl is optional. otto runs under linux and could easily be ported to other versions of unix. mpg123 or icecast are used to play or stream your music.

otto was designed with two purposes in mind:

1) to act as an easy interface to all my cds which ive encoded into mp3s. i use otto at home to act as a jukebox which is always playing music from my collection. i rarely put a cd into my cd player anymore, i simply use otto instead.

2) to be a multi-user network streaming jukebox for a group of people to upload and share their music. you could, for example, use this at work with everyone having separate accounts for accessing otto, and everyone having separate upload/download areas for music which they own. people all over the office can share and listen to the same music and everyone can have the pleasure of acting as dj for everyone else.

otto is always playing music. otto keeps a queue of songs to be played. you can add requests to the queue, change the order of requests, delete songs from the queue, or even kill the currently playing song. when there are no songs left to play, otto will add 20 random songs to the queue. requests always play ahead of the random songs otto has picked.

otto is geared toward people who have ripped+encoded entire albums. the otto database groups together tracks from an album and keeps them in album order. whole albums can easily be played, or shuffled together with tracks from other albums.

otto does search

otto tries to pack a lot of information on to a single page. at first this means otto is not always the simplest thing to use. however, once you get the hang of it, otto makes browsing and using your mp3 collection a straightforward task and it tries to stay out of your way as much as possible.

an example of this is the otto search function. if you type a search term into the search form, otto will show search results in three separate areas indicating search matches against artist names, album names, and song titles.

otto does lists

otto lets you create lists of songs that interest you. you can create as many lists as you like. once you have picked a list to work with, icons appear next to all song titles while browsing the database allowing you to easily add or delete songs to the list.

a special trash list allows you to select songs which otto should avoid when it is randomly picking songs. if you dont like the currently playing song, there is a trash icon for quickly adding the current song to the trash list so you never have to hear it again.

otto is multi-user

you can issue a separate username and password to each of your otto users. this is useful in a office workgroup environment. if you organize your mp3s such that each users mp3s are in a separate directory, then otto can keep track of whos albums are whos. otto displays the albums owner next to the album title while you are browsing the database. the currently playing track also has the owner displayed so you know who to blame.

when a user is browsing a song which is tagged as being owned by them, a download link appears next to that song allowing it to be saved locally on the users machine. if desired, this feature can be disabled so any user can download any song.

otto keeps a list of the 30 most recently loaded albums so you can easily see what has been recently loaded by your fellow users.

you can also choose to configure otto not to prompt for a username + password at all. this can be handy when using otto at home where multi-user features dont make as much sense.

otto as radio station

otto makes a fine front end for an internet radio station. instead of using mpg123 to play the music out of your soundcard, otto can use icecast to stream your mp3s over the network. you can even combine mpg123 and icecast to play music and stream to the network at the same time.

the front page for otto is a public page which does not require a username or password. it shows whats playing and whats coming up. otto also parses the icecast stats file and shows how many people are currently listening. on the request interface, you can also see a list of the last 30 icecast listeners and how long they were connected.

if your users log into the web interface from the same machine they use to listening to the stream, otto automatically associates that username with the icecast listener address. this way you can tell who is behind a given icecast connection.

otto as database

one of the design goals for otto was to be able to gracefully browse and search a very large database of mp3 files. otto is a pleasure to use even if you load 20,000 tracks into it. as part of dealing with so many songs, otto has a few options for controlling the organization of your database.

you can arrange for artists with multiple pseudonyms to be filed together under one name. AFX and Caustic Window can be filed under Aphex Twin, for example. or maybe you would like to file a related artist somewhere other than under their own name, Morrissey under The Smiths perhaps.

if you identify specific artists names as proper names, you can have otto file them under their last name instead of their first. like Charlie Parker under P instead of C.

otto also has a separate various artists section and a separate soundtracks section. if you tell otto how to parse the song and artist names from each of your various artists collections, you can have all your Banco de Gaia tracks appear under Banco de Gaia including all his appearances on numerous various artists collections.

other stuff

otto has support for running multiple icecast channels at once. each channel is configured with a different database of songs and has a separate icecast stream associated with it. all from a single otto installation.

otto has some international language support. it can be configured to use an arbitrary character set encoding. it also has an alternate navagation bar containing the greek alphabet in the iso-8859-7 character set. if you want to support another language this will provide a great starting point.

it is easy to write small scripts that fetch the currently playing song and the upcoming song queue. as long as you have mysql installed and the mysql perl module available, the script can run either on the same machine that runs otto, or on a remote machine. this is great for driving non-web based displays (like lcd displays attached to the serial port). a rough example script is included.

otto was originally inspired by the globecom jukebox. if otto doesnt quite do it for you, then perhaps the globcom one will. please see http://www.globecom.net/jukebox/

otto thanks

otto would like to send props out to its peeps. a special thank you to willg (otto logo and general look), jas (suggested the name), mbletsas, rmadams, bfitz, jfinks, mikeg, kasco, tschroed, dbrandon, nfields, spero, and sgunn. thank you all for your help, feedback and encouragement. i hope i didnt forget anyone, im bad that way.

MP3Cattle is a Java based GUI for a database that contains mp3 information. MP3Cattle allows a user to build a play list based upon rankings/genres/labels or by selecting from the available artists/albums/songs. MP3Cattle allows multiple users to have different rankings/genres for one collection of mp3s, allow different playlists to be generated based upon the current user. Users can also limit playlists with a query based on a size or time limit.


Currently MP3Cattle only supports MySQL. I was using v3.22.27 and v3.22.32 of MySQL during testing and development, which is a bit old but I dont think newer versions should give users any trouble.