Amarok is playing mp3 files with Suse 10 well, but after each track played it sets the PCM level in KMix to zero. So I have to move the PCM up and hear the next track. Why does amarok set the level of PCM to zero and what can I do to avoid it.

Can anyone help

Thanks

Robert wrote:

Amarok is playing mp3 files with Suse 10 well, but after each track played it sets the PCM level in KMix to zero. So I have to move the PCM up and hear the next track. Why does amarok set the level of PCM to zero and what can I do to avoid it.

Can anyone help

Thanks

I am allso haveing the same problem with Novell Suse 10 any help with this would be appreciated:S

its helpful if you identify the engine you are using... but since you say \"Novell suse\" I\'ll assume you\'re using the commercial suse version, and therefore quite likely the helix engine. there is a known problem with helix core libraries from Real where it will reset the mixers to the state they were in when you start the player. Xine also has a setting \'remember something\' that will cause simlar behavior. Set the mixer unmuted and at some PCM volume that you find comfortable and exit amarok (completely) without playing any tracks. Then, make sure it is still like that, and start amarok again. If the problem remains, try a different engine.

You were right that I was using commercial \"Novell suse 10\" in a standard configuration with helix.

Unfortunately I could not solve the problem with setting PCM volume and exiting amarok (completely) without playing any tracks. I have also updated to helix 1.3.8-6 and installed amarok 1.3.8 without success. Thanks anyway for your help. I will further try with different engines as you said. Perhaps I will have success and let you know.

Finally it works. I did update helix to 1.3.8-6. Then I updated to amarok 1.3.8. When I reinstalled amarok I was wondering why the Suse Linux DVD was again required. But obiously the helix driver gets installed again. PCM still went to Zero. I installed again helix 1.3.8-6. Still didn\'t work, but after I restarted the computer it worked. Now it plays even if PCM is at Zero. The loudness only depends on the internal speaker now.

Enjoying amarok

Robert wrote:

Finally it works. I did update helix to 1.3.8-6. Then I updated to amarok 1.3.8. When I reinstalled amarok I was wondering why the Suse Linux DVD was again required. But obiously the helix driver gets installed again. PCM still went to Zero. I installed again helix 1.3.8-6. Still didn\'t work, but after I restarted the computer it worked. Now it plays even if PCM is at Zero. The loudness only depends on the internal speaker now.

Enjoying amarok

Hope I do not bother someone with coming up again on the matter above. But as quite a number of you have been looking up this issue I thought it might be interesting to know for Novell Suse 10 users that the helix engine seems to be changed when software is installed from the Suse DVD. After installing KDE develop and the gnu gcc compiler I had the same error again. After installing helix 1.3.8-6 again and restarting the computer it worked again.

Came across a work around that seems to work on my Dell 8400 with SB.

Mel over at linuxcompatible.org posted it

http://www.linuxcompatible.org/Suse_10_sound_need_help_t33431.html#167378

This works for me on all SUSE distros I\'ve tried including 10.0.

Go to
Control Center/Sound and multimedia
unselect "Autosuspend if idle for [5 sec.]
(Default is 5 seconds which means sound is turned
off 5 seconds after startup.)
Click "apply"
Go back to Control Center and select "System Notifications".
Check "Apply to all Applications"
Click "Turn on all [sounds]
Click apply

From main menu
select "volume control"
push sliders for master,Master Mono and PCM all the
way up.
click "Apply"

Restart computer and use the speaker icon to adjust volume>

It\'s very good to read this post, as I\'m experiencing the same problem with the PCM level on SuSE 10.0.

I tried upgrading to 1.3.7 of the player and helix engine, but still have the problem. Can anyone tell me what the problem was, like with the helix engine, and exactly what release in which it was fixed? One report says it works in a particular version, but I\'m tired and frustrated of randomly trying versions without knowing why one should work and another won\'t.

-TR

Well, despite the lack of response to my question, I was able to surmise at least one solution from a number of sources here and elsewhere.

The problem, basically, is related to the Helix engine. Okay. Upgrading Helix and Amarok to a 1.3.7-2 didn\'t fix the problem. Next.

I noticed from using another sound app, as well as Amarok, that the Xine engine which ships with SuSE 10.0 is broken. Thanks, guys. Anyway, herein lies the solution, apparently. Upgrading to the newest Xine lib using the following RPM should do the trick for Amarok 1.3.1:

libxine1-1.1.2cvs-060325.i686.rpm

After selecting this engine in Amarok, I\'m now enjoying this beautiful app. I hope this saves someone else some trouble.

-TR

Note that this didn\'t work reliably for me with SuSE 10.0. Upgrading the xine engine which ships with the distro to the latest one, and using it, did fix the problem, as noted in my separate post in this thread.

-TR