Free mp3 file shrinker software for linux

w3t.org URL Shrinker is a small url generator via right-click. When you want to share a long URL (like on many news articles), just right-click on the page you want to link to and choose "Shorten this URL"; and youll get a super-short URL to use that forwards to the longer one.

The site now includes the ability to use custom URL "tags" like "ff" as in http://w3t.org/?c=ff The next version of the extension should include this new site feature.

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)

This module enables to listen to mp3-streams according to certain security policies (enabled user). The mp3s do not have to be in the web-servers document root.
Main features:
- XHTML compliant.
- Admin interface allows you to change position, visibility and title of the stream playlist Box.
- You dont have to fiddle around with config files. Interface is provided to configure the paths etc., user access and reset the access counter.
- Dynamic directory parsing for mp3-files
- mp3-file names are not held in a database as the File/Directory names are used to create the displayed Songs, album titles etc. as mp3 tags extraction capabilities are not included in php by default.
- Artist, Album, mp3-file browsable
- Playlist handling capabilities with playlist editor
- Demo mode for guests possible, e.g. streaming not enabled.
- Clicking on a Song will send a mpeg-url type information to the mp3-player application such as winamp or xmms. (Tested under linux with xmms only).
Version restrictions:
- The software only searches through 2 Directory structures. It is meant to go through: $mp3dir/Artist-Name/Album-Name/mp3-files.mp3 It however detects files in the Artist-Directory and shows these accordingly. As I didnt use this function, I dont know what it looks like though.

lxDVDshrink let you squeeze and backup your original DVDs to cheap one-layer DVD medium.

lxDVDshrink is fastnsimple DVD shrinker. It supports multi-title processing, arbitrary audio and subtitle tracks selection and, most of all, its a CONSOLE application! The recent gDVDshrink will become part of this package soon...

MP3::Tag::File is a Perl module for reading / writing files.

SYNOPSIS

my $mp3 = MP3::Tag->new($filename);

($title, $artist, $no, $album, $year) = $mp3->parse_filename();
see MP3::Tag

MP3::Tag::File is designed to be called from the MP3::Tag module.
It offers possibilities to read/write data from files via read(), write(), truncate(), seek(), tell(), open(), close(); one can find the filename via the filename() method.
parse_filename()

($title, $artist, $no, $album, $year) = $mp3->parse_filename($what, $filename);

parse_filename() tries to extract information about artist, title, track number, album and year from the filename. (For backward compatibility it may be also called by deprecated name read_filename().)

This is likely to fail for a lot of filenames, especially the album will be often wrongly guessed, as the name of the parent directory is taken as album name.

$what and $filename are optional. $what maybe title, track, artist, album or year. If $what is defined parse_filename() will return only this element.

If $filename is defined this filename will be used and not the real filename which was set by MP3::Tag with MP3::Tag-new($filename)>. Otherwise the actual filename is used (subject to configuration variable decode_encoding_filename).

Following formats will be hopefully recognized:

- album name/artist name - song name.mp3
- album_name/artist_name-song_name.mp3
- album.name/artist.name_song.name.mp3
- album name/(artist name) song name.mp3
- album name/01. artist name - song name.mp3
- album name/artist name - 01 - song.name.mp3

If artist or title end in (NUMBER) with 4-digit NUMBER, it is considered the year.
title()

$title = $mp3->title($filename);

Returns the title, guessed from the filename. See also parse_filename(). (For backward compatibility, can be called by deprecated name song().)

$filename is optional and will be used instead of the real filename if defined.

artist()

$artist = $mp3->artist($filename);

Returns the artist name, guessed from the filename. See also parse_filename()

$filename is optional and will be used instead of the real filename if defined.

track()

$track = $mp3->track($filename);

Returns the track number, guessed from the filename. See also parse_filename()

$filename is optional and will be used instead of the real filename if defined.

year()

$year = $mp3->year($filename);

Returns the year, guessed from the filename. See also parse_filename()

$filename is optional and will be used instead of the real filename if defined.

album()

$album = $mp3->album($filename);

Returns the album name, guessed from the filename. See also parse_filename() The album name is guessed from the parent directory, so it is very likely to fail.

$filename is optional and will be used instead of the real filename if defined.
comment()

$comment = $mp3->comment($filename); # Always undef

genre()

$genre = $mp3->genre($filename); # Always undef

Mp3 renamer 2006 by MiKe is a shell script for Linux. MP3 renamer goes by the Unix name of rename-mp3. It looks at MP3 files in a Directory and, using id3v2, will rename all the mp3 files in a nice format according to the id3 tags rename-mp3 will look at both v1 and v2 id3 tags, and will make the output file in a Title-Album-Artist.mp3 format.
It saves time, and not only will it read the id3 tags, but in the event that the MP3 file has no id3 tags, you will be given 4 options
1)abort 2)skip 3)rename 4)write id3 tags, and you are asked what you would like the id3 tag artist, track name and album to be.
This is great if you want the track to be easy to view and yet you still like having a library of music that is all tagged nicely!
Enhancements:
- New stuff: The INSTALLER now works, whereas before it wouldnt copy...

MP3::Splitter is a Perl extension for splitting MP3 files.

SYNOPSIS

use MP3::Splitter;
mp3split(xx.mp3, {verbose => 1}, [3, 356.25], [389, 615, lax => 10]);

mp3split_read(xx.mp3, xx.list, {verbose => 1});

The first two arguments of mp3split() is a name of an MP3 file and a reference to a hash of options, the remaining are descriptions of pieces. Such a description is an array reference with the start and duration of the piece (in seconds; or of the forms 03h05m56.45, 03h05m56.45s, or 03:05:56.45; any of the hours/minutes/seconds fields can be omited if the result is not ambiguous.

Alternatively, one can specify the start field as a relative position w.r.t. the end of previous piece (or start of file); to do this, prepend > to the field. Similarly, one can put end-of-the-piece in the duration field by prepending the time by =; if this field has a special value INF, it is assumed to go until the start of the next piece, or until the audio ends.

The remaining elements of a piece description should form a hash of piece-specific options (arbitrary user data can be stored with the key user).

Similarly, mp3split_read() takes names of an MP3 file and of a file with the description of pieces, followed by optional reference to a hash of options. Each line of the description file should be either empty (except comments), or have the form

START END # OPTIONAL_COMMENT

START and END are exactly the same as in the description of pieces for mp3split(); however, END may be omited (with the same meaning as INF). Note that this is a format of method output_blocks() of Audio::FindChunks.

MP3::Find is a Perl module to search and sort MP3 files based on their ID3 tags.

SYNOPSIS

# select with backend you want
use MP3::Find qw(Filesystem);

print "$_n" foreach find_mp3s(
dir => /home/peter/cds,
query => {
artist => ilyaimy,
title => deep in the am,
},
ignore_case => 1,
exact_match => 1,
sort => [qw(year album tracknum)],
printf => %2n. %a - %t (%b: %y),
);

This module allows you to search for MP3 files by their ID3 tags. You can ask for the results to be sorted by one or more of those tags, and return either the list of filenames (the deault), a printf-style formatted string for each file using its ID3 tags, or the actual Perl data structure representing the results.

There are currently two backends to this module: MP3::Find::Filesystem and MP3::Find::DB. You choose which one you want by passing its name as the argument to you use statement; MP3::Find will look for a MP3::Find::$BACKEND module. If no backend name is given, it will default to using MP3::Find::Filesystem.
Note: Im still working out some kinks in the DB backend, so it is currently not as stable as the Filesystem backend.

Note the second: This whole project is still in the alpha stage, so I can make no guarentees that there wont be significant interface changes in the next few versions or so. Also, comments about what about the API rocks (or sucks!) are appreciated.