#532 Wrong volume set for the first played file

version_14.*
open
nobody
general (155)
5
2014-12-01
2012-10-09
Einhard
No

When I open a first file with smplayer the volume is wrongly set (too high). If I reload the same file or play another one without closing smplayer then everything works fine. Log included. What's surprising, the same mplayer command is parsed for the first time (wrong volume) and after reloading (correct volume)

/usr/bin/mplayer -noquiet -nofs -nomouseinput -vc ffh264vdpau,ffmpeg12vdpau,ffwmv3vdpau,ffvc1vdpau, -lavdopts threads=2 -sub-fuzziness 1 -identify -slave -vo vdpau -ao pulse -nokeepaspect -dr -double -input nodefault-bindings:conf=/dev/null -stop-xscreensaver -wid 52428894 -monitorpixelaspect 1 -ass -embeddedfonts -ass-line-spacing 0 -ass-font-scale 1 -ass-styles /home/andrzej/.config/smplayer/styles.ass -fontconfig -font Arial -subfont-autoscale 0 -subfont-osd-scale 16 -subfont-text-scale 16 -subcp enca:pl:UTF-8 -vid 0 -aid 0 -subpos 100 -volume 48 -cache 5000 -ss 95 -osdlevel 0 -idx -noslices -channels 2 -af scaletempo -softvol -softvol-max 200 -af equalizer=2:1.5:1:0.5:0:0.5:0:-0.5:-1:-1.5

So the problem probably lies in Smplayer and setVolume.

The same thing happens with alsa, without equalizer, global volume, amplification, etc. I have checked many combinations but wrong volume for the first file is still there.

This line in log is interesting
Core::playNewFile: volume: 40, old_volume: 40
From how file sounds I can guess that volume is set to 40 and sec later to old_volume+volume (40+48 in this case) and it stays there until file is reloaded. If I close smplayer and open the same file again the problem comes back.

My system is Arch Linux x86_64 KDE 4.9.2

This problem doesn't occur in smplayer2 with identical configuration [url]https://github.com/lachs0r/SMPlayer2[/url]

Discussion

  • Einhard
    Einhard
    2012-10-09

     
    Attachments
    log