Bug 59434 - noatun sets volume to 100% temporarily on startup
Summary: noatun sets volume to 100% temporarily on startup
Status: RESOLVED FIXED
Alias: None
Product: noatun
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Multimedia Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-06 17:12 UTC by richard
Modified: 2004-01-14 23:49 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description richard 2003-06-06 17:12:28 UTC
Version:            (using KDE KDE 3.1.2)
Installed from:    Gentoo Packages
Compiler:          gcc 3.2.3 
OS:          Linux

Every time it starts, noatun temporarily sets the PCM volum to 100% before restoring it to the previous level. This is a problem when something else is playing.
Comment 1 Charles Samuels 2003-07-25 18:44:54 UTC
Subject: kdemultimedia/noatun/library

CVS commit by charles: 

don't change the volume on startup twice, fixes #59434.

CCMAIL: 59434-done@bugs.kde.org


  M +4 -3      engine.cpp   1.92


--- kdemultimedia/noatun/library/engine.cpp  #1.91:1.92
@@ -423,5 +423,5 @@ bool Engine::initArts()
         {
                 d->server = Arts::Reference("global:Arts_SoundServerV2");
-                int volume = d->volumeControl ? d->volumeControl->volume() : 100;
+                int volume = d->volumeControl ? d->volumeControl->volume() : -1;
                 delete d->volumeControl;
                 d->volumeControl=0;
@@ -538,4 +538,5 @@ bool Engine::initArts()
                         d->globalEffectStack.insertBottom(d->visStack, "Visualization Stack");
                         d->volumeControl=VolumeControls::volumeControl(this);
+                        if (volume != -1)
                         d->volumeControl->setVolume(volume);
                 }


Comment 2 neerolyte 2004-01-14 23:49:22 UTC
My volume seems to stay at 100% sometimes, I think it only happens when Noatun is loaded from a session restore when I log in.