The "Normalize" plugin (which sets consistent sound levels between tracks) in Brasero should NOT be enabled by default on new installs of Ubuntu because the plugin alters/changes the burned file appearing on the CD from the original file that exists on the HDD.
Because the original file being burned is changed/altered by the Normalize plugin, it should be something that users have to enable manually if they want it.
Many users make a "backup" of files on their HDD. When they make a backup, they want an exact copy of the files on their HDD without any changes being made to the files being burned to the CD. The Normalize plugin prevents this. Users that do use the Normalize plugin often keep an "original/unaltered" file separate from normalized versions. Many new users burning backup copies of their music will not know their burning activity is changing the sound level of their music data. And they may delete the original file thinking they have an exact copy burned onto CD, not realizing they have burned a "normalized" version.
To protect users that are unaware of the Normalize plugin, it should be disabled (unticked) by default. Users that use this plugin will know what it does and will know they need to enable it should they want normalization to occur.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: brasero 2.30.2-0ubuntu1.1
ProcVersionSignature: Ubuntu 2.6.32-33.70-generic 2.6.32.41+drm33.18
Uname: Linux 2.6.32-33-generic i686
Architecture: i386
Date: Thu Jul 28 18:11:03 2011
ExecutablePath: /usr/bin/brasero
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
ProcEnviron:
LC_TIME=en_GB.UTF-8
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: brasero
XsessionErrors:
(polkit-gnome-authentication-agent-1:1292): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
(brasero:2102): GConf-CRITICAL **: gconf_client_set_string: assertion `val != NULL' failed
Status changed to 'Confirmed' because the bug affects multiple users.