Difference between revisions of "Demlo"

From ArchWiki
Jump to: navigation, search
(Typos and clarifications)
(Remove spurious newline)
Line 31: Line 31:
  
 
The user script folder has precedence over the system script folder: if two scripts share the same basename, the user script will be used.
 
The user script folder has precedence over the system script folder: if two scripts share the same basename, the user script will be used.
 
  
 
== Usage ==
 
== Usage ==

Revision as of 09:04, 2 February 2018

Demlo is a batch music tagger and library organizer powered by Lua and FFmpeg. It supports transcoding, case checking, cue sheets, online tagging with MusicBrainz, manual tag editing with you favorite editor, cover downloading and processing, and more.

Installation

Install the demloAUR package from the AUR.

Configuration

The package provides a configuration sample. It is a good idea to start from there:

 $ install -Dm644 /usr/share/demlo/demlorc -t ~/.config/demlo

Scripts

By default Demlo only previews changes. Use the -p commandline flag to confirm.

Demlo runs a chain of Lua scripts of the files passed as arguments. You can select which scripts from the config file or at run-time.

Each script can access an <t>input</t> table and modify an <t>output</t> table with information such as the path, tags, covers and encoding properties.

Demlo comes with its set of official scripts to choose from.

If you want to write a temporary script (for instance a script that makes sense for one album only), you can create a script in the local folder, call it from command line, then remove it.

For more persistent user scripts, you can store them in Demlo's configuration folder.

You can derive your scripts from the official ones as for the configuration:

 $ install -Dm644 /usr/share/demlo/scripts/tag.lua -t ~/.config/demlo/scripts/

The user script folder has precedence over the system script folder: if two scripts share the same basename, the user script will be used.

Usage

Run Demlo over a set of file to preview the changes:

 $ demlo *.ogg album/ other-album/*.flac

Set the script chain to change the result:

 $ demlo -s tag -s ./my-script.lua -s encoding <input-files>

If you need fine-grained tuning, you can run Lua commands before and after the script chain from command line:

 $ demlo -pre 'o.artist="John Doe";o.disc=output.filename:match("Disc (\d+)")' -post 'output.format="ogg"' <input-files>

To process the files, use the -p parameter. Demlo uses all available cores by default. You can restrict it:

 $ demlo -cores 2 -p <input-files>

If you just want to fetch covers online:

 $ demlo -c -s cover -s 90-rmsrc -p <input-files>

If you want to edit tags or properties manually (in case scripts would not be able to fix them automatically), you can export the changes to an index file:

 $ demlo <some-tuning> <input-files> >> ./index.json

You can stack different output to the same index file, Demlo does not mind. You can edit this file with your favorite editor. To apply the changes, call Demlo over the desired set of files with the -i option. Scripts can still be called or they can be left out if you do not want to perform any additional change.

 $ demlo -i ./index.json -r  -post 'o.artist,o.album_artist=o.album_artist,artist' <input-files>

Index files can be used to interface Demlo with other programs, both as input and output.

See demlo -h and the demlo manual.

See also