We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 1083 - SDL changes copies front channel volume to master volume
Summary: SDL changes copies front channel volume to master volume
Status: RESOLVED ENDOFLIFE
Alias: None
Product: SDL
Classification: Unclassified
Component: audio (show other bugs)
Version: 1.2.14
Hardware: x86_64 Linux
: P1 normal
Assignee: Ryan C. Gordon
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-06 13:26 UTC by Maurice van der Pot
Modified: 2015-08-25 09:38 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maurice van der Pot 2010-12-06 13:26:17 UTC
I have experienced both with gnash and with smpeg's plaympeg that the master volume is modified and the front channel volume is reset to its maximum.
With gnash it looks like the front channel volume setting is copied to the master volume before being reset.

Testing with plaympeg shows that the problem only occurs when SDL_AUDIODRIVER=pulse. I won't get sound, but the volume settings will be altered:
  SDL_AUDIODRIVER=pulse plaympeg some.mpg 
  socket(): Address family not supported by protocol
  Warning: Couldn't init SDL audio: No available audio device
  Will ignore audio stream

If I set SDL_AUDIODRIVER=alsa, then there's no problem.

If something else is already using sound (for instance mplayer playing an mp3), then the mixer channels are not touched.

Without specifying SDL_AUDIODRIVER, plaympeg will print the above error message about the address family, will modify the volume settings and then presumably default to alsa (giving me sound).

If you need any kind of logging/strace/debugging, please ask for it.
Comment 1 Jen Spradlin 2011-04-12 20:06:35 UTC
Thank you for your bug report!

We're busy working on getting SDL 1.3 ready for a high quality release, and want to make sure as many things are fixed there as possible.
Could you check to see if your bug is resolved by the latest SDL 1.3 snapshot?
http://www.libsdl.org/tmp/SDL-1.3.zip

Thanks!
Comment 2 Ryan C. Gordon 2011-12-30 01:25:50 UTC
Bumping priority on a few bugs that I would like examined more closely before 1.2.15 is finalized. This is not a promise that a bug will be fixed. We may close it with WONTFIX or WORKSFORME or something, but I just want to make sure attention is paid.

--ryan.
Comment 3 Ryan C. Gordon 2015-08-25 09:38:24 UTC
Hello, and sorry if you're getting several copies of this message by email, since we are closing many bugs at once here.

We have decided to mark all SDL 1.2-related bugs as RESOLVED ENDOFLIFE, as we don't intend to work on SDL 1.2 any further, but didn't want to mark a large quantity of bugs as RESOLVED WONTFIX, to clearly show what was left unattended to and make it easily searchable.

Our current focus is on SDL 2.0.

If you are still having problems with an ENDOFLIFE bug, your absolute best option is to move your program to SDL2, as it will likely fix the problem by default, and give you access to modern platforms and tons of super-cool new features.

Failing that, we _will_ accept small patches to fix these issues, and put them in revision control, although we do not intend to do any further official 1.2 releases.

Failing that, please feel free to contact me directly by email (icculus@icculus.org) and we'll try to find some way to help you out of your situation.

Thank you,
--ryan.