ReplayGain

Amarok 1.x Scripts

Source (link to git-repo or to original if based on someone elses unmodified work): Add the source-code for this project on opencode.net

1
5.7
Description:

amaroK replaygain
v1.0.0-beta5 by Miguel Angel Alvarez (maacruz at gmail.com)
October 20, 2007

An amaroK script to normalize volume using the replaygain method
Now on your language: english, spanish, german, hungarian, french, russian, slovak, finnish, polish, portuguesse, italian, turkish, swedish
(more translators wanted!!!)

Using replaygain will make all your songs have the same perceived volume, making unnecesary to adjust the volume on each song change (specially if they are from different albums/artists)


--Release Notes--
1.0.0beta5: Workaround for amarok saving playlist with non valid utf8 characters, which in turn would cause the script to crash. The internal scanner for wma/asf files is now x10 faster.
1.0.0-beta series:
Major enhancements and new features.
Support for streams: now streams can be scanned. The scan must be manually started in track mode. It will rip 60 seconds and set the gain accordingly, so some variance can be expected. The stream must broadcast normalized somewhat for this to have any sense. Requires mplayer.
Support for wma: Using a new internal scanner (only for wma for now, but soon to be expanded for all filetypes). It is quite experimental but since beta5 it is very fast and will use 3dnow on AMD cpu's. Requires mplayer.
Autoscan mode: now replaygain will autoscan the playlist when it is modified (files are added or removed). The autoscan only can do track mode. Streams are not autoscanned (by now). The autoscan starts after a configurable amount of time once the playlist has changed, to avoid putting the cpu under high load during track change in dynamic playlists. Autoscan runs in a separated thread, so replaygain works while the scan is in progress; beware that the manual scan still runs in the main thread (the script will not work on anything else). Autoscan can be enabled/disabled using the playlist context menu, if you want to stop a running autoscan simply disable it; starting a manual scan will also stop a running autoscan; changing the playlist while autoscan is running will let it finish the current file and start a new autoscan. Requires amarok>=1.4.6 and python-xml
New anti-lag meassure: the script follows the playlist and will guess the next track to be played, avoiding to query amarok. Only works if amarok is not playing in random track mode. Requires amarok>=1.4.6 and python-xml.
Minor improvements:
The scripts keeps you informed while a scan is in progress (previous versions only informed when the scan started and finished).
The configuration dialog now informs you of what's supported and any dependency unmet.
Memory usage has been reduced
Files are checked if writeable before scanning them (many thanks to dAniel hAhler http://daniel.hahler.de/ for suggestion and patch)
Volume is updated if the current playing file hadn't replaygain tags after it is scanned (manually or automatically)
More bugs
--End of notes--

Please report any bug

Files supported:
vorbis (ogg), mp3, aac (mp4/m4a), flac, musepack (mpc), wma/asf

Dependencies:

Needed:
kdebase3 (kdialog and dcop), python 2.3 or later, and UTF8 filesystem character set (to use national characters in the filename).
Optional:
pygtk (python-gtk) for the advanced configuration interface.
python-xml for easy playlist album scanning, autoscan, lag-reduction
mplayer, oggenc (vorbis-tools), vorbisgain for streams and wma support.
kdebindings3-python for lag-reduction
The following external utilities:
. metaflac (flac): to apply replaygain tags on flac files. This is likely a standard package on your distribution
. vorbisgain: to apply replaygain tags on vorbis ogg files
. aacgain: to apply replaygain tags on mp4/m4a aac files (works for mp3 too)
. mp3gain: to apply replaygain tags on mp3 files. Not needed if you have aacgain
. replaygain (musepack): to apply replaygain info on mpc (musepack) files.
. mplayer plus oggenc (vorbis-tools) and vorbisgain: to apply replaygain tags on wma/asf files and streams.

Where you can get the needed utilities:

Check your distribution's software repositories first.
Guru's page for SuSE Linux has mp3gain and vorbisgain. (http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=Sound/)
Packman has musepack packages (they include replaygain) for SuSE Linux (http://packman.links2linux.de/)
Musepack home page (http://www.musepack.net/index.php?pg=lin)
Vorbisgain home page (http://sjeng.org/vorbisgain.html)
mp3gain home page (http://mp3gain.sourceforge.net/download.php)
aacgain home page (http://altosdesign.com/aacgain/).
mplayer home page (http://mplayerhq.hu

How to use
First you need to analyze all your song files using replaygain. The replaygain algorithm calculates a perceptual volume (gain) for each track (track mode) and album (album mode) and uses this information to correct the playback volume so all tracks or albums sound equally loud. In album mode the relative differences between tracks of an album are preserved, so more quiet tracks will sound more quiet, and louder tracks will sound louder. Album mode is better for live recordings and albums meant to be more than a collection of tracks, while track mode is better for heterogeneus mixes and compillations.
This analysis will not change your file's sound data, it will store the information in tags.

You can analyze a stream, file, album or your whole collection from the playlist's context menu:
Apply Replaygain tags->
-- To selected files in track mode: tag one or more files (as selected in playlist) with their respective track gain (track mode).
-- To playlist in album mode: tag all files in the playlist with both album and track gain tags (album mode), as if the playlist is one album.
-- To entire collection using album tags: the script will group the files in the database using their "Album" tag, and scan each group in album mode.
-- Autoscan: if this is activated, files in the playlist will be automatically tagged (track mode tags only).
It is recommended to have python-xml installed for album tagging (if not installed, playlist tagging as such and autoscan will not be available).

Once a file is tagged with replaygain data, the script will be able to read such tags and it will update the volume as needed.

The mode tags used are selected from the playlist context menu:
- Replaygain mode: which mode will use (track or album)

If a file doesn't have replaygain tags or it is of an unsupported type, it will be played at the default gain.

You can configure the script's operation in the configure script dialog. The most important parameters are:
- Pregain: this is the reference gain in dB (from the 0 point set at 55% volume in amarok). The range goes aproximately from 11 dB to -17 dB. Any replaygain volume correction will be relative to this gain, so you should leave enough space in the range for the script to work. The recommended value is 6.0 dB.
- Peak protection: If enabled, the volume may be adjusted to avoid clipping.
- Default gain: this is the assumed gain for files with no replaygain information. A good value could be -6.0 dB.
- Autoscan delay: amount of time in seconds between the playlist change and the autoscan start. Avoids reacting too quickly to manual playlist changes, and most important, clogging the CPU at track change when using dynamic playlists.

Crossfade is supported, so the volume changes slowly when crossfading.
You have also the option of sudden or smooth volume change when crossfade is disabled in amarok.

Lag reducing howto
Some people are affected by large lag between track change and the replaygain volume update
Lag seems caused by amarok itself by taking too much time to return from dcop calls.
This has been related to high cpu load caused by sqllite and cover image rendering.
So, if you are affected, what can you do?
In amarok 1.4.6 and later the script keeps track of playlist changes, to guess what the next song is and tell amarok to adjust volume inmediatly, needs python-xml and only works if track are played secuentially.
The cpu load for using sqllite has been reduced in 1.4.0 and later, and if you are using 1.3.9 you can apply the patch included in the amarok replaygain script package. Install either of those. Using a external database may be a good idea if you have a large collection, too.
Install kdebindings3-python to take advantage of new script's code.
If you are using the script's OSD control (the "Disable OSD during...." option) disable the OSD or uncheck the script option, it couldn't be optimized because of bugs in pykde
To see how cover rendering affects you, you can move your covers elsewere (try with an author or two) so they are not found. Large cover files may have a big impact, if this is the case, use gimp to reduce them.
Run amarok minimized in the tray, it will not update visual elements saving much time.
Resource intensive software affects too (some screensavers, p2p, ...)
During this beta release debug output is enabled. Have a look at your lag (in seconds) by typing in a konsole/xterm:
tail -f ~/.kde/share/apps/amarok/scripts-data/replayggain.log|grep time
As a reference, my lag is well under 0.1 s (usually 0.01-0.05)


Feedback appreciated.

Enjoy!
Miguel Angel
Last changelog:

13 years ago

0.1-0.3.3
Old vorbisgain releases

0.5-beta "Reborn"
Major rewriting, now it is python
Renamed to replaygain
Add Album and peak support
New nice pygtk interface
Thanks to Kevin Radloff and Jocke "Firetech" for their suggestions and testing

0.5
Uses the new (since amarok 1.3.2) readConfig dcop calls if available, now the script is aware of amarok configuration changes
Added support for musepack (mpc) files

0.5.5
Added support for AAC (mp4/m4a) files
The script checks for external utilities when closing the configure dialog

0.6 "Clean OSD"
New option to disable osd updates during volume changes solving the annoying quick osd changes
Changed detection of external utilities since mp3gain has different behaviour depending on its version (thanks Jocke for pointing this out)
Settings are reread only when the engine starts playing, not at every song change
Fixed the check for external utilities so it solves the "mp3gain not found" missleading message, and a typo which prevented using aacgain when present.
Fixed flac on latest flac releases (thanks Gary Virta)
Changed the "utility not found" dialog to a less annoying notification
Many optimizations and speedups
Thanks Jocke and Roberto for all your testing

0.6.1
Hotfix: fix script breaking on amarok older than 1.3.2 when osd is disabled

0.7
Many new configuration options, not all can be accesed through the kdialog interface
Clipping protection may be disabled so volume doesn't go to 0 on some broken mp3 files
Pregain (volume reference level) may be adjusted by moving the volume slider
Pregain is now adjusted to tenths of dB instead of integer dB
The volume transitions may be smoothed over any specified amount of time when crossfade is disabled
Accurate timing so crossfaded/smoothed volume changes don't take longer than they should
Pygtk interface now has help as tooltips
Changes in script configuration take effect inmediately instead of waiting till next song
Script configuration is saved when amarok stops playing

0.7.1
Added support for mp3 files tagged with foobar (id3v2 tags), it requires id3v2 installed
SIGTERM handler

0.7.2
Added context menu shortcut to change replaygain mode

0.8.0
Internacionalization. Spanish translation.
New option to set the gain (volume) for files without replaygain info (or unsupported files).
Context menu options to apply/delete replaygain tags to playlist/collection. It is recommended to have python-xml installed for almbum tagging.
Some bugfixes

0.8.1
German, french and hungarian translations

0.8.2
Hotfix: do not break while scanning collection if unsupported file has no album tag.

0.8.3
Fix problems with special shell characters in filenames

0.8.4
Fix breaking if enviroment LANG variable is not set (assumes ISO8859-1 charset)

0.8.5
Fix encoding strings headache caused by gettext not returning unicode strings

0.8.6
Couple of small fixes

0.9.0
This release is designed to reduce lag (thanks Stewie for all your testing). Requires installing kdebindings3-python (aka python-kde) to take advantage of new code. Uses pykde for dcop calls if possible
Finnish GUI translation thanks to Samu Voutilainen
Slovak GUI translation thanks to Jozef Ří­ha
Russian translation thanks to Anton Chumak.
Reworked kdialog interface to fix problems caused by X error messages
Corrects collection scanning if using dynamic collection (patch by Frederic Dinh).
Use mutagen-1.4 library (http://www.sacredchao.net/quodlibet/wiki/Development/Mutagen) to read tags, except on mp4/m4a and mpc. Code for mpc and mp4 tag reading thanks to Justus Pendleton and QuodLibet player (needs ctypes python module). Dropped dependency on external utilities for tag reading.
Added support for RVA2 tags (used by QuodLibet and normalize)
Many bugfixes

0.9.1 Add portuguesse and polish GUI translations, updated finnish translation, thanks to Candido Lopes, Jaroslaw Gorny and Samu Voutilainen.

0.9.2: Add italian and turkish GUI translations. Many thanks to Davide "DuffyDac" and Fatih í‡iroglu

0.9.3: Add swedish GUI and README translation. Many thanks to Göran Jartin

flyingeagle2

15 years ago

Again with (hopefully) better formatting I think LANG is set to de_DE: [fe2@marvin ~]$ echo $LANG de_DE I even tried to set the LC varible in amarok_replaygain.py to 'de_DE' or 'de_DE.utf8' (if LC == 'de': LC='de_DE.utf8') but there is always the 'LookupError:unknown encoding:' error message with 'de_DE' or 'de_DE.utf8' unknown. How does LC have to be set to get the german encoding?

Report

unclegimpy

15 years ago

Hi.

Trying out version 0.83 for the fix for special characters in filenames.

Unfortunately I can't run the script, it fails with the included error.
Note that if I make a bogus aacgain executable I still get the set_mode_submenu() error.

Version 0.80 is working fine, except for the special characters, haven't tried intervening versions.


which: no aacgain in (/usr/kde/3.4/bin:/usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/3.4.4:/opt/ghc/bin:/opt/blackdown-jdk-1.4.2.03/bin:/opt/blackdown-jdk-1.4.2.03/jre/bin:/usr/qt/3/bin:/usr/kde/3.4/bin:/usr/games/bin)
Traceback (most recent call last):
File "/home/bob/.kde3.4/share/apps/amarok/scripts/amarok_replaygain/amarok_replaygain.py", line 398, in ?
set_mode_submenu()
File "/home/bob/.kde3.4/share/apps/amarok/scripts/amarok_replaygain/amarok_replaygain.py", line 393, in set_mode_submenu
mode_submenus=['"*'+SUBMENU_MODE_TRACK.encode(LC)+'"', '" '+SUBMENU_MODE_ALBUM.encode(LC)+'"']
TypeError: encode() argument 1 must be string, not None

Report

C

maacruz

15 years ago

Should be fixed now.
Delete any bogus aacgain or your mp3 and mp4 files will not work

Report

unclegimpy

15 years ago

Small syntax error in the script, line 39 is
if LC = None...
should be
if LC == None...

Once I make that change it seems to work fine for files with ` in them.
Haven't tested with any other special characters though.

Thanks for the script.

Report

cmaessen

15 years ago

Apllying the script to the entire collection gives me an error, and the script quits running. This is the detailed message:

==== LOG TRUNCATED HERE ====

Traceback (most recent call last):
File "/home/caspar/.kde/share/apps/amarok/scripts/amarok_replaygain/amarok_replaygain.py", line 606, in ?
scan_collection()
File "/home/caspar/.kde/share/apps/amarok/scripts/amarok_replaygain/amarok_replaygain.py", line 483, in scan_collection
os.system(replaygain_command[song_url.split('.')[-1]][0]+'"'+song_url.replace('"','\\"')+'"')
KeyError: ''


Whats wrong, and what to do about it?

--
Caspar.

Report

C

maacruz

15 years ago

Happened on files with no album tags and unsupported file type
Fixed in 0.8.2
It should now open a popup after the scanning.

Report

cmaessen

15 years ago

The problem is solved, anyway it doesn't reoccur, after I let amaroK reread the collection.

--
Caspar.

Report

Arubis

15 years ago

The same happens to me.

Is there an easy way to find out what song ReplayGain is failing on?

Report

burna

15 years ago

The script always tells me: "This song has no replaygain info" when playing flac files replaygained with Foobar. Is this a bug in this script or Foobar?

Burna

Report

C

maacruz

15 years ago

It seems Foobar is not following the standard.
Retag the files with the script, it should not change the foobar tags.

Report

burna

15 years ago

That's what I have done so far after deleting the old tags. Foobar does also read the new tags. But after all, who needs Foobar now that Amarok and Replaygain fit together. Thanx for sharing your script!

Report

alatriste

15 years ago

This a a really good tool, but I'm experiencing a problem. The RG tags of my music were calculated with the Foobar replaygain scanner, and when I use this plugin and a new song starts, there is a delay of near three seconds till the volume is changed. This can be really annoying if next song volume level is high.

Do I have to configure something to avoid this or is it some sort of bug?

Note: The computer is fast, so it's not the issue.

Thanks in advance.

Report

C

maacruz

15 years ago

By the way, you don't need to know programming to help. Just run some scripts and commands.

Report

C

maacruz

15 years ago

Hi,

I have some other reports of this problem, but still nobody has stepped in to help me in investigating it.
I think it may be related to your distribution (others who reported are on ubuntu).
I'm running SuSE (9.1 and 10.0) and the delay is most of the time unnoticeable (under 0.1 s), even under load. The machine is an athlon 2800 512MB.
Please, contact me by email if you want to help me investigate (and may be find a sollution).

Report

netwolfuk

15 years ago

I am having the same problem on my Fedora Core 4 install. I am happy to help you test/debug it.

NOTE: I am not running KDE. I am running amaroK under XFCE 4. I don't think it should make a difference, but it might be worth being aware of.

Report

visit0r

15 years ago

How about automatically calculating the replaygain for the next items that don't have replaygain value in the playlist? This way it would be unnecessary to run the replaygain calculation manually for the songs.

Report

C

maacruz

15 years ago

Thanks for your suggestion. This was an idea I have since the firsts script's releases, someday I'll implement it.

Report

Kalimero

15 years ago

Replaygain isn't applied when the filename contains a " as in (10" version) for example. Pregain is applied so I suppose the script doesn't find the tags because it tries to access the wrong file or some error happens and so 0dB is assumed.

Report

C

maacruz

15 years ago

Thanks, it will be solved in the upcoming 0.8.0 release (it is almost ready)

Report

unclegimpy

15 years ago

Hi, Miguel.

Great script.

I'm running 0.80 and it still seems to not find the REPLAYGAIN tags when the filename, or path, contains the ` character.
Note that that is a backtick, not a single quote which works ok.

E.g. /music/Artist/Artist`s First Album/01.mp3
won't work because of the backtick in the path.
Having backticks in the other tags doesn't seem to be a problem.

Again, nice work.

Report

C

maacruz

15 years ago

Hopefully this time is fixed once and for all

Report

ceplm

15 years ago

Hi,

trying to use your script with amarok 1.3.8 on Debian/sid and not much luck -- when leaving configuration dialog, it says that neither vorbiscomment nor mp3gain are installed (which is not true), and then when I play some tracks with the script running, whole amarok freezes. There is nothing interesting in ~/.xsession-errors.

Any ideas how to troubleshoot this?

Matej

Report

C

maacruz

15 years ago

The script uses the "which" command to detect the utilities.
Are mp3gain and vorbiscomment on the search path? (in a directory listed in the PATH enviroment variable)
Open a konsole/xterm and run amarok from there. Do you still have the problem?
About amarok freezing, it can't be related to the script, because it is a different process and only communicates with amarok using dcop. You may have a problem somewere else (may be the engine?)

Report

ceplm

15 years ago

chelcicky:~$ which mp3gain
/usr/bin/mp3gain
chelcicky:~$ which vorbiscomment
/usr/bin/vorbiscomment
chelcicky:~$

Works OK, when running directly /usr/lib/amarok/amarokapp, but not when running /usr/bin/amarok.

Report

C

maacruz

15 years ago

Quite unusual.
It seems amarokapp doesn't receive the same enviroment as /usr/bin/amarok
You could edit the script and find the lines
debug = False
flog = file('replaygain.log','w')

And chage them to
debug = True
flog = file('replaygain.log','w')
flog.write('PATH='+os.environ['PATH']+'\n')

Then see what's happening in the file ~/.kde/share/apps/amarok/scripts-data/replaygain.log

Report

13 years ago

0.1-0.3.3
Old vorbisgain releases

0.5-beta "Reborn"
Major rewriting, now it is python
Renamed to replaygain
Add Album and peak support
New nice pygtk interface
Thanks to Kevin Radloff and Jocke "Firetech" for their suggestions and testing

0.5
Uses the new (since amarok 1.3.2) readConfig dcop calls if available, now the script is aware of amarok configuration changes
Added support for musepack (mpc) files

0.5.5
Added support for AAC (mp4/m4a) files
The script checks for external utilities when closing the configure dialog

0.6 "Clean OSD"
New option to disable osd updates during volume changes solving the annoying quick osd changes
Changed detection of external utilities since mp3gain has different behaviour depending on its version (thanks Jocke for pointing this out)
Settings are reread only when the engine starts playing, not at every song change
Fixed the check for external utilities so it solves the "mp3gain not found" missleading message, and a typo which prevented using aacgain when present.
Fixed flac on latest flac releases (thanks Gary Virta)
Changed the "utility not found" dialog to a less annoying notification
Many optimizations and speedups
Thanks Jocke and Roberto for all your testing

0.6.1
Hotfix: fix script breaking on amarok older than 1.3.2 when osd is disabled

0.7
Many new configuration options, not all can be accesed through the kdialog interface
Clipping protection may be disabled so volume doesn't go to 0 on some broken mp3 files
Pregain (volume reference level) may be adjusted by moving the volume slider
Pregain is now adjusted to tenths of dB instead of integer dB
The volume transitions may be smoothed over any specified amount of time when crossfade is disabled
Accurate timing so crossfaded/smoothed volume changes don't take longer than they should
Pygtk interface now has help as tooltips
Changes in script configuration take effect inmediately instead of waiting till next song
Script configuration is saved when amarok stops playing

0.7.1
Added support for mp3 files tagged with foobar (id3v2 tags), it requires id3v2 installed
SIGTERM handler

0.7.2
Added context menu shortcut to change replaygain mode

0.8.0
Internacionalization. Spanish translation.
New option to set the gain (volume) for files without replaygain info (or unsupported files).
Context menu options to apply/delete replaygain tags to playlist/collection. It is recommended to have python-xml installed for almbum tagging.
Some bugfixes

0.8.1
German, french and hungarian translations

0.8.2
Hotfix: do not break while scanning collection if unsupported file has no album tag.

0.8.3
Fix problems with special shell characters in filenames

0.8.4
Fix breaking if enviroment LANG variable is not set (assumes ISO8859-1 charset)

0.8.5
Fix encoding strings headache caused by gettext not returning unicode strings

0.8.6
Couple of small fixes

0.9.0
This release is designed to reduce lag (thanks Stewie for all your testing). Requires installing kdebindings3-python (aka python-kde) to take advantage of new code. Uses pykde for dcop calls if possible
Finnish GUI translation thanks to Samu Voutilainen
Slovak GUI translation thanks to Jozef Ří­ha
Russian translation thanks to Anton Chumak.
Reworked kdialog interface to fix problems caused by X error messages
Corrects collection scanning if using dynamic collection (patch by Frederic Dinh).
Use mutagen-1.4 library (http://www.sacredchao.net/quodlibet/wiki/Development/Mutagen) to read tags, except on mp4/m4a and mpc. Code for mpc and mp4 tag reading thanks to Justus Pendleton and QuodLibet player (needs ctypes python module). Dropped dependency on external utilities for tag reading.
Added support for RVA2 tags (used by QuodLibet and normalize)
Many bugfixes

0.9.1 Add portuguesse and polish GUI translations, updated finnish translation, thanks to Candido Lopes, Jaroslaw Gorny and Samu Voutilainen.

0.9.2: Add italian and turkish GUI translations. Many thanks to Davide "DuffyDac" and Fatih í‡iroglu

0.9.3: Add swedish GUI and README translation. Many thanks to Göran Jartin

12345678910
1
product-maker LazyKent Dec 09 2010 9 excellent
Be the first to comment
thoughtcrime
Jul 20 2009
File (click to download) Version Description Downloads Date Filesize DL OCS-Install MD5SUM
*Needs pling-store or ocs-url to install things
Pling
0 Affiliates
Details
license
version
1.0.0-beta5
updated Oct 20 2007
added Jul 03 2005
downloads 24h
0
mediaviews 24h 0
pageviews 24h 11
System Tags addon