Free convert audio files software for linux

flac2mp3 project is a tool to convert audio files from flac to mp3 format.

Perl Audio Converter (PAC) is a tool for converting multiple audio types from one format to another. It supports MP2, MP3, Ogg Vorbis, FLAC, Shorten, Monkey Audio, FAAC (AAC/M4A/MP4), Musepack (MPC), Wavpack (WV), OptimFrog (OFR/OFS), TTA, LPAC, Kexis (KXS), AIFF, AC3, Lossless Audio (LA), AU, SND, RAW, VOC, SMP, RealAudio (RA/RAM), WAV, and WMA.
It can also convert audio from the following video formats/extensions: RM, RV, ASF, DivX, MPG, MKV, MPEG, AVI, MOV, OGM, QT, VCD, VOB, and WMV. A CD ripping function with CDDB support, batch and playlist conversion, tag preservation for most supported formats, independent tag reading/writing, and extensions for Konqueror and amaroK is also provided.
Enhancements:
- Added: MP4::Info dependency IO::String to pacpl-install
- Updated: License GPLv3
- Bug Fix: Directory conversions. pacpl was claiming the directory was empty and prompting to use the --recursive option...Thanks to John Meyer for the report.

Audio Format Converter is a an Amarok script that allows you to convert the audio format of the tracks in the playlist. The script takes a snapshot of the current playlist. Once the conversion has started, you can go back to using amaroK normally.

Supported files for both input and output include .flac, .ogg, .mp3, .mpc, .m4a, and .wav. Additionally, .wma, .ra, and are supported for input. (See below for the required packages.)

I dont know how to do anything with metatags from .wma or .ra. All I know is tags will get transferred to the output file if and only if the tags show up in the amaroK playlist. If they arent there, I suggest converting the files, then using a real tag editor like Easy Tag to put them in to the converted files.

This has only been tested on amaroK 1.2.4, but it should work on any amaroK>=1.2

The original files are NOT deleted. If the output file will overwrite an existing file, a dialog will appear to ask you whether to go ahead and overwrite or to skip the track. If you try to convert a file into the format its already in, a dialog will ask you how to handle this situation.

Depending on the number of tracks and the speed of your computer, this can take a long time to run. With each track, a passive popup will let you know what track its processing. At any time, you can stop the script by clicking stop in the amaroK script GUI.

Entagged project provides a convenient way of changing the value of these fields, either manually, or automatically via the freedb database.
The freedb database is a server to wich you can connect, and ask about a precise CD (album, or compilation), if this CD is found in the database, it returns all the data needed to correctly tag your audio files. Originally it used only with CD, but it can also be used with audio files as soon as it only need the length (in seconds) of the files.
Entagged can also do a lot of organization work. You can rename your files from their tag in any way you like, including complex directory structures. You can also tag the files from their filename, this avoid copying all the information by hand.
Best of all, Entagged hides all the different format complexity, with one unique interface, you can work with mixed file formats eg. you can use freedb with a mixed album of WMA, MP3 and OGG files without worrying!
Enhancements:
- Add a database (HSQLDB)
- Add a search engine
- Add a duplicate files and error names finder
- Create playlist easily

Media Tag Tools is as the name suggests a collection of tools to help you tag your audio files.
Rename them using the data present in their tags and/or categorise the files in folders automatically.
Installation:
You need the following packages to be able to compile mediatagtools: qt3 and taglib-1.4
If you have installed precompiled packages of these two libs, be sure to check if you have
also installed the -dev packages too.
Now unpack the archive and then inside the directory that was created the following commands (without the #):
# qmake
# make
and optionally if you want the program installed in /usr/local/bin:
# INSTALL_ROOT=/usr/local/ make install
Set INSTALL_ROOT to where you want to install the file. make install will then create a folder named bin and in there it will copy the program.
Have fun!
Enhancements:
- Fix selection of files after renaming them
- Fix segfault when opening a file with no tags
- Mtt can now take a dir as argument and add the media files for editing
- Add an application icon
- Add a .desktop file so that mtt appears in your menus automatically

Audio collection script is a script which can help you manage collections of audio files. For example, I have a directory with all my audio files in it, sorted by band/album. I also have an audio collections directory. Within that directory I have a few list files which contain patterns for songs that should be part of that collection. The script generates or updates a subdirectory for each list file present and creates links within those directories to all music files from my main audio directory that match the patterns in the list file.

An example:

Your music files are in /audio
Your collections are in /audio-collections
The file /audio-collections/funny.list has the following lines:

/audio-collections/funny/
#the next line matches all songs within a tripod directory
tripod/
monty*python
kevin*bloody*wilson
bill*clinton*miss*lewinsky*and*i

When run, it will process each .list file in the current directory. So for this example, when run from /audio-collections, it will create or clean out the directory /audio-collections/funny and create links inside it for any files found within /audio which match the specified patterns.

The first line in each list file specifies the directory to create and use for the links. The patterns in the file will match on the full path of a song.

Note: I am pretty sure it would not be a good path to put your collections inside your main audio directory.

movemetafs is a searchable filesystem metadata store for Linux that lets users tag local files (including image, video, audio, and text files) by simply moving the files to a special folder using any file manager.
It also lets users find files by tags using a boolean search query. The original files (and their names) are kept intact. movemetafs doesnt have its own user interface, but it is usable with any file manager.
In the name `movemetafs, `metafs means filesystem metadata store, and move refers to the most common way tags are added or removed: the user moves the file to be acted on to the `meta/tag/$TAGNAME or
`meta/untag/$TAGNAME special folder. When the target folder is such a special folder, the file is not removed from its original location (meta/root/**/*).
movemetafs is similar to LAFS (http://junk.nocrew.org/~stefan/lafs/)
(not tagji 1.1 by Manuel Arriaga). Most important differences:
- movemetafs uses MySQL instead of PostgreSQL (benefits: speedup, easier installation with pts-mysql-local).
- movemetafs doesnt require files to be explicitly added.
- movemetafs cannot list all untagged files quickly.
- movemetafs is written in Perl, so it is quite easy to extend and try out new features.
- movemetafs continues to work when files are renamed.
- movemetafs works with files with more than one hard link.
Main features:
- Use any file manager to tag files: move the file to the `meta/tag/$TAGNAME or `meta/tagged/$TAGNAME folder. The file is not removed from its original folder.
- Use any file manager to untag files: move the file to the `meta/untag/$TAGNAME. The file is not removed from its original folder.
- Specify search query by changing to the invisible `meta/search/$QUERYSTRING folder. Results are symbolic links into `meta/root.
- If you want to search for only a single tag, list the folder `meta/tagged/$TAGNAME. Results are symbolic links into `meta/root.
- Alternatively, you untag a file by removing the symlink `meta/tagged/$TAGNAME/$FILENAME.
- Alternatively, use POSIX extended attributes to retrieve (or even set) the tags associated to a file.
- Attach textual descriptions to files, and read the description once the file is found.
- Use POSIX extended attributes to get and set the textual description of a file.
- Create a recursive POSIX extended attribute dump (of tags and descriptions) from the database very quickly.
- Restore the created POSIX extended attribute dump with `setfattr --restore.
- Use versatile search query syntax (MySQL fulltext search) with the possiblity of boolean search (i.e. searching for files matching a combination of tags).
- Copy search results to make backups or to create collections.
- Searching is fast, because it uses a fulltext index.
- After installation, movemetafs can be used on an existing filesystem instantly: there is no migration needed to make an existing filesystem usable with movemetafs: data doesnt have to be copied, moved, touched etc.
- Untagged files dont have any negative effect on the speed of movemetafs, even if the filesystem contains millions of files.
- movemetafs nicely survives a system crash: non-cache data is stored in MySQL InnoDB tables (which use journaling), and even if the whole tag database is lost, the original filesystem remains usable without movemetafs.
- Stores tags in twice: once in a fulltext indexed column in a MyISAM table, and once in an InnoDB relational table. Uses the fast MyISAM table for searches, and the InnoDB table for data recovery.
- Treats file names as opaque 8-bit strings, thus it works with any filesystem character set, even when character sets are mixed in the middle of the filename.
- Uses UTF-8 for tag names and descriptions.
- Filenames in search results are automatically made unique when necessary.
- Following the Unix filesystem design, files with multiple hard links share a commond description and a common set of tags. If tags or the description are changed on one name, the changes also apply to other names, too.