KDE-Apps.org Applications for the KDE-Desktop 
 GTK-Apps.org Applications using the GTK Toolkit 
 GnomeFiles.org Applications for GNOME 
 MeeGo-Central.org Applications for MeeGo 
 CLI-Apps.org Command Line Applications 
 Qt-Apps.org Free Qt Applications 
 Qt-Prop.org Proprietary Qt Applications 
 Maemo-Apps.org Applications for the Maemo Plattform 
 Java-Apps.org Free Java Applications 
 eyeOS-Apps.org Free eyeOS Applications 
 Wine-Apps.org Wine Applications 
 Server-Apps.org Server Applications 
 apps.ownCloud.com ownCloud Applications 
 KDE-Look.org Artwork for the KDE-Desktop 
 GNOME-Look.org Artwork for the GNOME-Desktop 
 Xfce-Look.org Artwork for the Xfce-Desktop 
 Box-Look.org Artwork for your Windowmanager 
 E17-Stuff.org Artwork for Enlightenment 
 Beryl-Themes.org Artwork for the Beryl Windowmanager 
 Compiz-Themes.org Artwork for the Compiz Windowmanager 
 EDE-Look.org Themes for your EDE Desktop 
 Debian-Art.org Stuff for Debian 
 Gentoo-Art.org Artwork for Gentoo Linux 
 SUSE-Art.org Artwork for openSUSE 
 Ubuntu-Art.org Artwork for Ubuntu 
 Kubuntu-Art.org Artwork for Kubuntu 
 LinuxMint-Art.org Artwork for Linux Mint 
 Arch-Stuff.org Art And Stuff for Arch Linux 
 Frugalware-Art.org Themes for Frugalware 
 Fedora-Art.org Artwork for Fedora Linux 
 Mandriva-Art.org Artwork for Mandriva Linux 
 KDE-Files.org Files for KDE Applications 
 OpenTemplate.org Documents for OpenOffice.org
 GIMPStuff.org Files for GIMP
 InkscapeStuff.org Files for Inkscape
 ScribusStuff.org Files for Scribus
 BlenderStuff.org Textures and Objects for Blender
 VLC-Addons.org Themes and Extensions for VLC
 KDE-Help.org Support for your KDE Desktop 
 GNOME-Help.org Support for your GNOME Desktop 
 Xfce-Help.org Support for your Xfce Desktop 
openDesktop.orgopenDesktop.org:   Applications   Artwork   Linux Distributions   Documents    Linux42.org    OpenSkillz.com   


- Content .- Fans (2) .- Knowledge Base  . 



Amarok Script

Score 82%


Link:  http://
Downloads:  17666
Submitted:  Jul 3 2005
Updated:  Oct 20 2007


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


kdebase3 (kdialog and dcop), python 2.3 or later, and UTF8 filesystem character set (to use national characters in the filename).
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.

Miguel Angel


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

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

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

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

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

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

Added context menu shortcut to change replaygain mode

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

German, french and hungarian translations

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

Fix problems with special shell characters in filenames

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

Fix encoding strings headache caused by gettext not returning unicode strings

Couple of small fixes

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

(replaygain (amaroK Script))
Send to a friend
Other  Apps  from maacruz
Report inappropriate content

goto page: prev   1  2  3  4  5  6  7  8  9  10  11  12  13  14  15 ...


 It crashes on me :(

 by stuffcorpse on: Sep 17 2006
Score 50%

Hi I'm running amarok from svn and when I press OK on the configure dialogue I get this error:

The script 'amarok_replaygain.py' exited with error code: 1

Traceback (most recent call last):
File "/home/rick/.kde/share/apps/amarok/scripts/amarok_replaygain/amarok_replaygain.py", line 760, in ?
if amarok_has_readconfig: read_amarok_config()
NameError: name 'amarok_has_readconfig' is not defined

Reply to this


 Re: It crashes on me :(

 by maacruz on: Sep 18 2006
Score 50%

It's a bug that crept in beta6. Should be fixed now.

Reply to this


 can't apply tag

 by jetpeach on: Sep 18 2006
Score 50%

i ripped a CD to flac files, played it in amarok, then tried adding replaygain tags using right click 'scan file in track mode'
it seems to scan the flac files, but after it finishes it says simply "The following files failed:file:///home/jet/Shared/asdf.flac"
it works for mp3s still, but not flac i guess.

any ideas? i have the flac ability to play and edit tags installed, i changed the tags on the flac files no problem.

let me know if you don't already know about this problem and i will try to provide more debug info for you.

amarok 1.4.3
kubuntu dapper kde 3.5.4

also, this did not, as far as i remember, happen with the previous replaygain before 0.9

Reply to this


 Re: can't apply tag

 by maacruz on: Sep 18 2006
Score 50%

It works for me (flac 1.1.2).
flac is rather picky about sampling rates and replaygain, as it documentation states:
The sample rate must be one of 8, 11.025, 12, 16, 22.05, 24, 32, 44.1, or 48 kHz.
Please check your files (metaflac --list or even mplayer will give you enough information). Check file permissions too.
If everything is right, you should send me a sample file.

Reply to this


 Re: Re: can't apply

 by jetpeach on: Sep 20 2006
Score 50%

on further fiddling, they are at 44.1khz, but it seems the default setup for encoding my flac files in kde caused a corruption at the end of the files. they play fine and i wouldn't have known, but testing them they fail the CRC at 99%, so i'm sure this must be the reason replaygain fails. i tested a trimmed version and replaygain worked fine as well.

sorry to take your time! i love replaygain and look forward to getting it on these flac files once i fix their corruption.

Reply to this



 by crux on: Sep 29 2006
Score 50%


I'd like to know if the option "Apply Replaygain -> To entire collection using album tags" is, as I assume, going to apply replaygain in album mode to every album in my collection telling them apart by the Album field of the ID3 tag.

I'm not sure about this and I've made a couple of tests on .mp3 files and I see mp3gain executing on a pair (always 2) files but without the -a switch. I have the script set in album mode though.

If you can enlighten me on this topic I'd very much appreciate it. And maybe the info can be added to the documentation for others like me :9

Thanks and well done with this script!

Reply to this


 Re: Description

 by maacruz on: Oct 1 2006
Score 50%

Yes, scanning the whole collection will use album mode.
The only restriction is that all files in an album must be same filetype (either mp3, ogg, or whatever)

Reply to this


 Re: Re: Description

 by crux on: Oct 1 2006
Score 50%

Thanks for your answer! I'm going to try it out now.

Reply to this



 by dogfin on: Oct 16 2006
Score 50%

I noticed that the script (0.9.0-beta7) doesn't preserve the date/time of the files it analyzes. There are options for the analyzers you use that will attempt to preserve the date and time. I put it the '-p' option on aacgain and '--preserve-modtime' for metaflac.

I don't have the other programs, vorbisgain and replaygain, so I don't know what their option is. My collection isn't large (under 500 files), but it spans 7 years+, I almost caused all those dates to be altered. It would be sweet if you could add that in. Thanks for a great script!

dogfin -

Reply to this


 Re: date/time

 by maacruz on: Oct 16 2006
Score 50%

Thanks for your suggestion. I'll have a look into it.
It's unfortunate you have lost all those dates.

Reply to this


 Complains about depe

 by dotancohen on: Oct 17 2006
Score 50%

Thanks. It seems a good script, but it keeps complaining that it wants kdebindings3-python and I can't seem to find it:
dotancohen@ubuntu:~$ sudo apt-get install kdebindings3-python
Reading package lists... Done
Building dependency tree... Done
E: Couldn't find package kdebindings3-python
dotancohen@ubuntu:~$ sudo apt-get install kdebindings-python
Reading package lists... Done
Building dependency tree... Done
E: Couldn't find package kdebindings-python

Reply to this


 Re: Complains about depe

 by maacruz on: Oct 18 2006
Score 50%

I think in (k)ubuntu/debian it is called python-kde3
If you don't want to install it you may safely check the "Don't ask again" checkbox.

Reply to this


 Re: Re: Complains ab

 by dotancohen on: Oct 18 2006
Score 50%

Thanks, got it installed. Without this, it would not function on mp3 (and other formats) files.

Great work.

Reply to this


 Re: Re: Re: Complains ab

 by maacruz on: Oct 21 2006
Score 50%

It should work regardless if those bindings are installed or not. If it doesn't work, then probably there is a bug, so please, tell me if really didn't worked at all.

Reply to this


 python 2.4, configur

 by jetpeach on: Oct 20 2006
Score 50%

I'm wondering if there are plans to move replaygain to python 2.4 and possibly remove the gtk dependencies. Currently, I'm running Kubuntu and after bringing up the Kdialog to configure it, I select one and click configure, but it just exits then. On my other computer, I have ubuntu-desktop installed as well as kubuntu so all the gtk libaries and gnome junk are installed, and it works there.

I went through tons of libraries trying to find which gtk dependency is missing, but I don't know which it is. Looking over your dependency list, I have all those, I've checked and double checked, but still there is no configuration screen...
I'd really rather not have to completely install gnome to get the screen to show up, any advise is appreciated.
Thanks, great script!

Reply to this


 Re: python 2.4, configur

 by maacruz on: Oct 21 2006
Score 50%

Replaygain is developed with python 2.4. It works with python 2.3 too, and should work with python 2.5 (although I have not tested it).

The gtk dependencies are voluntary, you don't need them to do a basic usage of the script, it should use the kdialog interface instead.

To run the gtk interface you need only two dependences, the gtk libraries (obviously) and the python-gtk (aka pygtk) python package. Not gnome at all, just plain gtk. It is developed with gtk 1.2.10 and pygtk 2.8, but I think it should work on any later version.

The kdialog interface should work, at least it works for me with no trouble.
Are you running the latest script release? Which kde release?

Reply to this


 Re: Re: python 2.4,

 by jetpeach on: Oct 25 2006
Score 50%

yes, running the latest beta7 and using kde 3.5.5, amarok 1.4.3
so i removed python2.3 since that isn't needed (i have 2.4) but i still no luck.

when amarok starts at the terminal, i notice this message
amarok: [ScriptManager] [ERROR!] amarok_replaygain.py:
amarok: Failed to open device

not sure what that's all about.

when i click configure, i get a KDialog popup with the choice of what to configure. then, choosing Pregain, i get the message window passive popup in the top left saying "Replaygain script warning
some utilities not found, replaygain will not work on,..."
and it states aacgain and replaygain are not installed.
but after this popup, nothing happens. on the terminal, the following is output:

hmm it's a little long for a comment here. i don't see anything that says error though.
any advice? i can send more debugging info.

Reply to this


 Re: Re: Re: python 2.4,

 by maacruz on: Oct 26 2006
Score 50%

>> It is developed with gtk 1.2.10 ---That's me sleeping, I mean gtk 2.6 :)
It seems that, for some reason, the kdialog combobox doesn't return the expected string when you select one option, so it miss and return. You may safely ignore the popup (it opens after the configuration is done).
Please, send me the file replaygain.log located in ~/.kde/share/apps/amarok/scripts/scripts-data
May be I can get some more info there.

Reply to this

goto page: prev   1  2  3  4  5  6  7  8  9  10  11  12  13  14  15 ...

Add commentBack

How do you like Plasma 5?
 The best KDE Desktop ever.
 Definitely a nice improvement.
 Not decided yet. Haven't tried it yet.
 I do not like some of the changes.
 KDE is taking the wrong way.
 I am still sticking with KDE 3.5.
 I have no opinion, but wanted to vote anyway.

 Who we are
More about us
Frequently Asked Questions
Updates on identi.ca
Updates on Twitter
Content RSS   
Events RSS   

Add App
Public API
About KDE-Apps.org
Legal Notice
Spreadshirt Shop
CafePress Shop
Sponsor us
Report Abuse

Copyright 2003-2016 KDE-Apps.org Team  
All rights reserved. KDE-Apps.org is not liable for any content or goods on this site.
All contributors are responsible for the lawfulness of their uploads.
KDE and K Desktop Environment are trademarks of KDE e.V.