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

ceplm

15 years ago

s/lib/lib\/amarok/

Report

ceplm

15 years ago

And BTW, just to emphasize (although I mentioned it in one of the previous messages) -- debian amarok doesn't have /usr/bin/amarokapp, but /usr/lib/amarokapp.

Report

ceplm

15 years ago

Chmmm, this is my log:

PATH=/home/matej/.bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games:/usr/sbin
:/sbin
dcop call time:0.0617711279127Amarok engine:xine-engine
crossfade:False
crossfade time:3.0
osd:True
osd duration:5.0
Amarok engine:xine-engine
crossfade:False
crossfade time:3.0
replaygain config:{'no_peak': 'false', 'use_slider': 'false', 'no_osd': 'true', 'smo
oth': 'true', 'pregain': '6.0', 'mode': 'album', 'smooth_time': '0.5'}
Amarok signal:configure
Amarok engine:xine-engine
crossfade:False
crossfade time:3.0
osd:True
osd duration:5.0
Terminated

Report

C

maacruz

15 years ago

Mmmmm (scratchs head)
Really weird, /usr/bin is there in the path
Appart from the messages, does work the script with mp3 and ogg? I mean, does it adjust the volume according to the replaygain info?
Just guessing... the permisions on mp3gain/vorbiscomment are 755 ?

Report

C

maacruz

15 years ago

Thanks for pointing this out.
The next release will use os.system()>>8 to get the right exist status.

Report

ceplm

15 years ago

I am not sure, how to find out, whether it works, but it does something about the volume when amarok is start up.

Concerning rights of the programs:

chelcicky:~$ ls -l `which mp3gain`
-rwxr-xr-x 1 root root 90460 2005-10-01 08:37 /usr/bin/mp3gain
chelcicky:~$ ls -l `which vorbiscomment`
-rwxr-xr-x 1 root root 19144 2006-01-16 17:32 /usr/bin/vorbiscomment
chelcicky:~$

OK, so now about your script. I took a look and it seems to me that you've fallen into the same trap with os.system I did couple of years ago. Are you aware of the fact, that return value of os.system IS NOT errorlevel or return value you get in bash? So, I actually don't understand how it was possible that your script would work anywhere. This condition:

if os.system('which vorbiscomment')!=0:

must fail almost everywhere, because os.system returns the same value as os.wait, which returns value is defined in the library documentation thus:

`wait()'
Wait for completion of a child process, and return a tuple
containing its pid and exit status indication: a 16-bit number,
whose low byte is the signal number that killed the process, and
whose high byte is the exit status (if the signal number is zero);
the high bit of the low byte is set if a core file was produced.
Availability: UNIX.

I.e., it almost never is equal to zero. You have to preprocess the return value and split low and high byte, to get real return value.

Best,

Matej

Report

Interneci

15 years ago

Hi!

I have many Oggs a some few MP3s which are vorbisgain / mp3gain tagged. Using this cool script I just found it finally has an even if playing on my PC, which is more than cool! :-)
However, it does not yet have quite the effect I wanted it to:

While (using radio gains) all Ogg songs sound about equally loud and all mp3s as well, the MP3s sound much louder compared to the Oggs. This cript chooses around 50% (+/- 10%) loudness setting for Oggs and about 80% (+/- 10%) fpr MP3s - what am I doing wrong?

Pointers to FAQs are greatly appreciated! :-)

Greetings,

Interneci

Report

C

maacruz

15 years ago

Hi,
Obviously that should happen.
Please tell me which release of mp3gain and vorbisgain you are using and which commands did you use to tag your files.
It would be of great help if you could send me a sample mp3 and ogg to see whats going on.

Report

Interneci

15 years ago

Whops, sorry... Seems to have been a typical case of PEBKAC... In fact the script chooses 40-50% volume for Oggs and around 80-85% for MP3s, but actually it sounds ok. I had a few MP3s which accidentially where not mp3gain-Tagges at all, these were also played at 85% but sounded much to loud. After running mp3gain on them it seems to be ok. (Although your replaygain script winding up the volume from 35% to 85% on a song change looks and sounds funny... :-)

Thanks for your fast response and sorry for the confusion caused,

Interneci

Report

C

maacruz

15 years ago

I think you may be running mp3gain with the '-r' switch, and this modifies the mp3 file instead of simply writing the tags. This would explain the big volume jump (the modified mp3 files doesn't need volume adjustment).
If you run "mp3gain -u" on your mp3 files to restore them and then "mp3gain " (with no switches) on them again only the tags will be written, then you'll see they are played at the same volume as ogg files (depending on the file, of course)

Report

Interneci

15 years ago

Ah, ok. I used "-a" which also changed the mp3 file per-frame data instead of just adding tags. I'm currently plaing a bit with mp3gain, but it sounds good so far. Thanks for your help!

Report

C

maacruz

15 years ago

HAPPY NEW YEAR FOR EVERYONE!

Report

ianegg

15 years ago

A feature that would be very useful (for me at least) would be an option to automatically switch between Album and Track mode depending on wether Random Mode is on or off.

I mostly listen to random tracks, but I often like to listen to a whole album, and changing it every time can be a bit of a pain.

Report

C

maacruz

15 years ago

Hi,
I have added a context menu shortcut to change the mode. Hope this is ergonomic enough.

Report

ianegg

15 years ago

WOW! Amazing response time, thanks! It's not the ultimate lazy man's solution, but it makes life a lot easier :)

I had a breif look through the amarok scripting wiki, and it looks like amarok doesn't notify of inessential details, so I assume what I suggested would currently be inpossible?

Report

ianegg

15 years ago

This is an amazing script and it just keeps getting better. When I moved to Linux from Windows, Replaygain (and many other Foobar features!) was very difficult to live without, until I discovered this gem.

I'd just like to know if it's possible to dump a list of tracks that haven't had replaygain applied? Foobar could just go through the collection and do it all for me, but manually sorting through my mess of music folders to check each album is a PITA.

Report

C

maacruz

15 years ago

Hi,
the script will be able soon to apply replaygain tags by itself.
In the meanwhile you can use the commands as explained above in this web page.
What I have done is to put them in a little script to scan my entire collection by clicking an icon on the desktop.

Report

ianegg

15 years ago

I saw that in the todo list. Will it handle albums properly?

I treid scripting it, but I'm not sure how to get it to skip already tagged files, and I'm not sure how to get it to recursively go through all my folders.

Report

C

maacruz

15 years ago

Hi,
Edit a new file with your favourite text editor, and put the following two lines in it:

#!/bin/sh
find $1 -type d -exec sh -c "mp3gain \"{}\"/*.mp3; vorbisgain -afs \"{}\"/*" \;

Save it as /usr/local/bin/replaygain.sh (or ~/bin/replaygain.sh)
Make it executable:
chmod +x /usr/local/bin/replaygain.sh (or chmod +x ~/bin/replaygain.sh)
(you'll need to be root to copy/change files in /usr/local/bin)

This script will do what you need for mp3 and ogg, and tagged files will be skipped (files tagged with foobar will be tagged anyways because the tag format is different)
Different albums need to be on different folders, so album tags are right.

Let's suppose your music folder is ~/music
You can invoke it by typing on console:
replaygain.sh ~/music

Now create on your kde desktop an application link (by right clicking on the desktop). On the "application" tab, "command" field, put
replaygain.sh ~/music
Click on the "advanced" button and set "Run on terminal" and "Don't close on exit"

Now you'll be able to scan your collection with a single click

Report

ianegg

15 years ago

Excellent! Thanks very much for your help.

Report

noosphere

15 years ago

Hello,

Thanks for the great work on your script, but I'm having some problems.

After I installed your script amarok worked fine until I actually ran mp3gain on my mp3 files. Then I started experiencing drop-outs when listening to mp3s. It would happen whether I played them with amarok or with xmms, and whether the mp3 in question had had mp3gain applied to it or not.

I found that the drop-outs always occured shortly after amarokapp or the postgres thread amarok was communicating with spiked in CPU usage. It seemed that these drop-outs would happen at least once a minute (though I didn't time them to see if they occured with precise regularity).

I tried setting my buffer_size to 65536 in my $HOME/.asoundrc, restarting amarok and playing my mp3s again, but continued to experience the drop-outs and CPU usage spike just like before. Playing them in xmms was no different.

I then uninstalled the replaygain script and restarted amarok. From then on every time amarok would start I'd hear a crashing sound and amarok's splash screen would not go away.

So then I had to kill amarok, removed my $HOME/.kde/share/config/amarokrc and the problem went away. So it seems like the replaygain script was the culprit, though I haven't tried reinstalling it to see if I could reproduce the problem.

I am running Amarok version 1.3.6 using KDE 3.4.3, and mp3gain 1.4.6 on a box running Gentoo, kernel version 2.6.11, on an AMD Athlon 64 3000+, with 1GB of memory.

Thanks again for your effort in developing this useful script.

Report

C

maacruz

15 years ago

Hi,
Thank you very much for you feedback.
Those problems you experienced can't be caused by the script. It doesn't use the amarok config file (except as read only on amarok 1.3.1 and lower) at all, and any communication with amarok is done through the dcop interface, and it runs as a separate background process.
Running mp3gain also shouldn't cause any problem, since all it does is to write some information tags to the mp3 file (though if you run it with '-r' or '-a' it will modify your mp3 files by changing the gain of all frames).
If those problems happened in the same session they could be caused by some hung process (probably amarokapp).
Please try again, and if you experience the same problem close amarok and kill any amarok process, and then restart it and see if the problem has gone.

Report

bugmenot

15 years ago

This script lacks help about how to use it. I was unable to find clear/"directed-to-non-geek-end-user" information about what is the meaning of the settings pre-gain and the mode.
I think this kind of info should be "prioritarialy" displayed in the "about" or in some help text, not even "refearing" "dB" or any other "geek-term".

Report

C

maacruz

15 years ago

Hi,
I agree some help is needed, and the development version already has it, as tooltips in the pygtk interface.
But, if you don't understand what a "dB" (decibels) is, it is your fault. It is the most used sound measurement unit, and saying it is "geeky" is like saying "m" (meters) is geeky. Please read and inform yourself, google and wikipedia are just a click away.

Report

tenco

15 years ago

while version 0.5.5 worked, version 0.6 is broken. The script stops with the following error:

---------
Traceback (most recent call last): File "/home/martin/.kde/share/apps/amarok/scripts/amarok_replaygain/amarok_replaygain.py", line 259, in ? osd_duration = float(amarok_configparser.get('OSD','Osd Duration'))/1000 File "/usr/lib/python2.4/ConfigParser.py", line 520, in get raise NoOptionError(option, section)ConfigParser.NoOptionError: No option 'osd duration' in section: 'OSD'
----------

Perhaps that's because i haven't turned OSD on...

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 14
System Tags addon