Template::Plugin::MP3 is a Perl interface to the MP3::Info Module.

SYNOPSIS

[% USE mp3 = MP3("Montana.mp3") %]

[% mp3.title %]
[% mp3.album %]

# perldoc MP3::Info for more ideas

Template::Plugin::MP3 provides a simple wrapper for using MP3::Info in object oriented mode; see MP3::Info for more details.

Lemonldap::Portal::Cda is a Cross Domain Authentification Perl extension for Lemonldap SSO.

SYNOPSIS

use Lemonldap::Portal::Cda;
my $stack_user= Lemonldap::Portal::Cda->new(type=> master);
or my $stack_user= Lemonldap::Portal::Cda->new(type=> slave);

Lemonldap is a SSO system under GPL. Sometimes you have two or more domains (.bar.foo and .bar.foo2) The CDA :Cross Domain Authentification manages and centralize all credentials on all domains . CDA works with redirection in order to catch the credential cookie.

You may use an objet "master" domain with a "slave" domain . All authentification needed for the "slave" domain will be redirected on the "master" domain

METHODS

new (type => master|slave);

process (param => %params, bar => foo );

The process method alway return an error 8 (message = CDA requested) .

The master CDA just do a redirection with the id_session in the params of url GET . The slave CDA uses the id_session send by master for put on fly a cookie on slave domain.
see directory examples.

(url_encoded,url_decoded) : getAllRedirection

return the initial request encoded in Base64 and plaintext url

string : getSession

return the id_session or false .

string : message() ;

return the text of error

int : error() ;

return the number of error

mp3cue cuts an input MP3 file according to the information stored in a .cue file (for example multiple tracks of DJ mix), and writes the output to multiple MP3 files.

poc is a mp3 and ogg streamer supporting following protocols:

HTTP (mp3 and ogg)
RTP (RFC 2250) (mp3 only)
RTP (RFC 3119) (mp3 only)
homegrown FEC protocol (mp3 only)

It should work under any POSIX platform, and does not require any additional library. You need a C99 compiler though.

poc is still beta software, ipv6 and ogg support was not tested extensively.

poc includes mp3cue, a mp3 CUE cutter, and mp3cut, a mp3 command-line editing tool.

MP3::Find::Filesystem is a File::Find-based backend to MP3::Find.

SYNOPSIS

use MP3::Find::Filesystem;
my $finder = MP3::Find::Filesystem->new;

my @mp3s = $finder->find_mp3s(
dir => /home/peter/music,
query => {
artist => ilyaimy,
album => myxomatosis,
},
ignore_case => 1,
);

Bundle::MP3 is a bundle to install all MP3-related modules.

SYNOPSIS

perl -MCPAN -e install Bundle::MP3

CONTENTS

MP3::Info - For MP3::Info by Chris Sandor

Digest::MD5 - Used by MP3::Napster

MP3::Napster - For MP3::Napster by Lincoln Stein

Bundle::Xmms - For Xmms by Doug MacEachern

This bundle installs a bunch of modules related to sharing and playing MP3 files, including MP3::Info by Chris Sandor, MP3::Napster, by Lincoln Stein, and the Xmms bundle by Doug MacEachern.

Apache::MP3::Sorted is a Perl module to generate sorted streamable directories of MP3 files.

SYNOPSIS

# httpd.conf or srm.conf
AddType audio/mpeg mp3 MP3

# httpd.conf or access.conf
< Location /songs >
SetHandler perl-script
PerlHandler Apache::MP3::Sorted
PerlSetVar SortFields Album,Title,-Duration
PerlSetVar Fields Title,Artist,Album,Duration
< /Location >

Apache::MP3::Sorted subclasses Apache::MP3 to allow for sorting of MP3 listings by various criteria. See Apache::MP3 for details on installing and using.

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.

Here are some key features of "MP3 Streamer":

· 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).

Limitations:

· 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.

AudioFile::Info::MP3::ID3Lib is a Perl extension to get info from MP3 files.

This is a plugin for AudioFile::Info which uses MP3::ID3Lib to get data about MP files.
See AudioFile::Info for more details.

METHODS

new

Creates a new object of class AudioFile::Info::MP3::ID3Lib. Usually called by AudioFile::Info::new.

MP3::Tag::ID3v2 is a Read / Write ID3v2.x.y tags from mp3 audio files.

SYNOPSIS

MP3::Tag::ID3v2 supports * Reading of ID3v2.2.0 and ID3v2.3.0 tags (some ID3v2.4.0 frames too) * Writing of ID3v2.3.0 tags

MP3::Tag::ID3v2 is designed to be called from the MP3::Tag module.

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

# read an existing tag
$mp3->get_tags();
$id3v2 = $mp3->{ID3v2} if exists $mp3->{ID3v2};

# or create a new tag
$id3v2 = $mp3->new_tag("ID3v2");

See MP3::Tag for information on the above used functions.

* Reading a tag

$frameIDs_hash = $id3v2->get_frame_ids(truename);

foreach my $frame (keys %$frameIDs_hash) {
my ($name, @info) = $id3v2->get_frame($frame);
for my $info (@info) {
if (ref $info) {
print "$name ($frame):n";
while(my ($key,$val)=each %$info) {
print " * $key => $valn";
}
} else {
print "$name: $infon";
}
}
}
* Adding / Changing / Removing / Writing a tag
$id3v2->add_frame("TIT2", "Title of the song");
$id3v2->change_frame("TALB","Greatest Album");
$id3v2->remove_frame("TLAN");
$id3v2->write_tag();
* Removing the whole tag
$id3v2->remove_tag();
* Get information about supported frames
%tags = $id3v2->supported_frames();
while (($fname, $longname) = each %tags) {
print "$fname $longname: ",
join(", ", @{$id3v2->what_data($fname)}), "n";
}

AudioFile::Info::MP3::Tag is a Perl extension to get info from MP3 files.

This is a plugin for AudioFile::Info which uses MP3::Tag to get or set data about MP3 files.

METHODS

new

Creates a new object of class AudioFile::Info::MP3::Tag. Usually called by AudioFile::Info::new.

MP3-Database project is a tool to organize your MP3 collection. If you insert a CD with MP3 files in your CDROM drive, MP3DB can read all ID3 tags of the MP3 files.

With this information MP3DB creates a database which can be searched for a specific song, artist, or CD.

A GUI makes it easy to use the program. Any title found in the database can easily be added to a playlist or can instantly be played by XMMS.

Here are some key features of "MP3 Database":

· MySQL (Is needed as database backend)
· Perl5
· Perl Modules:
· Tk
· Tk-MesgBox
· Tk-LabFrame
· Tk-Pane
· DBI
· MP3-Info
· Msql-Mysql-modules
· To play MP3 files the MP3 player XMMS should be installed on your system. MP3-Database can easily be adapted to other MP3 players

Whats New in This Release:

· NEW Data Structure: The MySQL database is much more complex than before. I used 3 Tables for Artists, Albums and Titles to store the data. This ensures that I have no redundancies in the tables. This has also enabled me to store additional fields in the database (for example the date of birth of an artist, or the release year of an album).
· NEW Temporary Database: I added some tables to store all new artists, albums and titles in a temporary database. This enables the user to check the new entries before adding them to the permanent database.
· NEW FEATURES: Additional Artist and Album information can be stored in the database, MP3DB can now create a random playlist and a playlist with the top 20 MP3 titles, MP3DB can show you a statistic how many artists, albums and titles are stored in the database.

Apache::MP3 is a Perl module that can generate streamable directories of MP3 and Ogg Vorbis files.

SYNOPSIS

# httpd.conf or srm.conf
AddType audio/mpeg mp3 MP3
AddType audio/playlist m3u M3U
AddType audio/x-scpls pls PLS
AddType application/x-ogg ogg OGG

# httpd.conf or access.conf
< Location /songs >
SetHandler perl-script
PerlHandler Apache::MP3
< /Location >

# Or use the Apache::MP3::Sorted subclass to get sortable directory listings
< Location /songs >
SetHandler perl-script
PerlHandler Apache::MP3::Sorted
< /Location >

# Or use the Apache::MP3::Playlist subclass to get persistent playlists
< Location /songs >
SetHandler perl-script
PerlHandler Apache::MP3::Playlist
< /Location >
A demo version can be browsed at http://www.modperl.com/Songs/.

This module makes it possible to browse a directory hierarchy containing MP3, Ogg Vorbis, or Wav files, sort them on various fields, download them, stream them to an MP3 decoder like WinAmp, and construct playlists. The display is configurable and subclassable.

NOTE: This version of Apache::MP3 is substantially different from the pre-2.0 version described in The Perl Journal. Specifically, the format to use for HREF links has changed. See Linking for details.

PyMM is an MP3 Manager written in Python. With it you can easily create playlists, edit ID3 tags and search your collection.

I used to use the windows program MP3 Manager to manage my MP3s. I have since migrated my MP3 collection to Unix, and I therefore needed something similar on that platform. The project also gave me an opportunity to get aquainted with wxPython, which I must say is a quite suberb windowing toolkit.

You can use the program to manage your collection, create playlists, control the XMMS player, edit ID3 tags and so forth.

You can install the program in two ways:

1. run "python setup.py install". This requires write access to the python installation tree. It will install a startup script in the python bin directory. Then just type "pymm" to start the program.
This requires Python 2.0/1.6 or that you have Distutils installed.

2. Just put this directory somewhere and start the program with "python pymm.py". I made a link to the pymm.py script in a bin directory (i.e something like "ln -s /pymm.py /usr/local/bin/pymm").

Whats New in This Release:

· pymm.py (Timer.Notify): Added total time of track to statusbar.
· xmms.py (Xmms): Added get_playlist_time(pos).

Template::Plugin::MP3::Tag is a Perl interface to the MP3::Tag Module.

SYNOPSIS

[% USE tag = MP3("path_to_mp3_file") %]

[% tag.title %]
[% tag.album %]

# perldoc MP3::Tag for more ideas

Template::Plugin::MP3::Tag provides a simple wrapper for using MP3::Tag in object oriented mode; see MP3::Tag for more details.

Although Template::Plugin::MP3 can fetch MP3 files, but it Supports only ID3v1. When you have to fetch MP3 files ID3v2, I recommend you to use this module.

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.