I'm using software volume control in smplayer (in the audio preferences), with a max amplification of 200, so that I can make quiet videos louder. After upgrading to version 15.11.0, this feature breaks the player, the error message being: The volume option must be <= 100.000000: 160 Error parsing option volume (parameter is outside values allowed for option) Setting command line option '--volume=160' failed. I don't know where the 160 comes from. I'm using mpv-0.9.2-r1. smplayer-14.9.0.6994 was working PERFECTLY, but it was removed from portage. smplayer-14.9.0-r1 does not work at all (at least with mpv). Reproducible: Always
Could you please narrow the set of configurations where this problem occurs. There are several versions of smplayer, mpv and mplayer in tree and I cannot reproduce this issue with =smplayer-15.11.0 and =mpv-0.14.0-r1, for example.
(In reply to Coacher from comment #1) > Could you please narrow the set of configurations where this problem occurs. I did provide the versions of the programs I am using. But you are right, smplayer-15.11.0 seems to work fine with mpv-0.14.0-r1 I guess I should have tried that first…
(In reply to aditsu from comment #2) > I did provide the versions of the programs I am using. Indeed, thank you. But you've also mentioned that with some other versions of these programs the problem was not reproducible. This is why I asked you to provide more info. > But you are right, smplayer-15.11.0 seems to work fine with mpv-0.14.0-r1 > I guess I should have tried that first… It seems the problem you have is due to changes in mpv, see http://forum.smplayer.info/viewtopic.php?f=2&t=8103#p14266 and https://www.assembla.com/spaces/smplayer/subversion/commits/7002 and https://github.com/mpv-player/mpv/commit/68bbab0e42e141896545f1f6e9699bcad2d685f8 Some version combinations of mpv and smplayer are not well synchronized. In this case you'll need smplayer >= 15.9.0 and mpv >= 0.10.0 to make soft volume work properly.
I've raised the mpv dependency in smplayer-16.4.0-r1, but I can't touch 16.1.0 because it's being stabilized and latest stable mpv is only at 0.9.2-r1... so I guess we need to stabilize a newer mpv.
(In reply to Davide Pesavento from comment #4) > I've raised the mpv dependency in smplayer-16.4.0-r1, but I can't touch > 16.1.0 because it's being stabilized and latest stable mpv is only at > 0.9.2-r1... so I guess we need to stabilize a newer mpv. Thank you. Agreed. I am going to commit mpv-0.17.0-r1 later today, which should be stabilized then after the standard 30 days delay.
(In reply to Coacher from comment #5) > Agreed. I am going to commit mpv-0.17.0-r1 later today, which should be > stabilized then after the standard 30 days delay. Do we really have to wait for -r1? Can't we stabilize 0.17 asap? smplayer-16.1.0 is already stable on some arches and is affected by this bug AFAIU.
(In reply to Davide Pesavento from comment #6) > Do we really have to wait for -r1? Can't we stabilize 0.17 asap? > smplayer-16.1.0 is already stable on some arches and is affected by this bug > AFAIU. There are multiple prerequisites for 0.17.0(-r0) stabilization: - delay period ends on May, 12; - bug #579742; - bug #579834; - bug #570510; - bug #558596. I could forget smth else, but these things alone amount to a significant time frame.
(In reply to Coacher from comment #7) > (In reply to Davide Pesavento from comment #6) > > Do we really have to wait for -r1? Can't we stabilize 0.17 asap? > > smplayer-16.1.0 is already stable on some arches and is affected by this bug > > AFAIU. > There are multiple prerequisites for 0.17.0(-r0) stabilization: > - delay period ends on May, 12; > - bug #579742; > - bug #579834; > - bug #570510; > - bug #558596. > I could forget smth else, but these things alone amount to a significant > time frame. Sure, let's wait for those stabilization and see which version of mpv we can stabilize when those are done. But you can already get started by filing a stablereq for mpv *without* CC'ing arches. And please don't remove 0.17.0 when you add -r1. wrt bug 558596, only sparc is missing there... why do you care about sparc? mpv is not stable on that arch...
(In reply to Davide Pesavento from comment #8) > Sure, let's wait for those stabilization and see which version of mpv we can > stabilize when those are done. But you can already get started by filing a > stablereq for mpv *without* CC'ing arches. That was the plan once the -r1 is in tree. > And please don't remove 0.17.0 > when you add -r1. Ok. > wrt bug 558596, only sparc is missing there... why do you care about sparc? > mpv is not stable on that arch... mpv isn't stable on sparc because of this very bug, see bug #558600.
(In reply to Davide Pesavento from comment #8) > Sure, let's wait for those stabilization and see which version of mpv we can > stabilize when those are done. But you can already get started by filing a > stablereq for mpv *without* CC'ing arches. And please don't remove 0.17.0 > when you add -r1. I filed a stablereq against mpv-0.17.0. Ideally mpv-0.17.0-r2 should be stabilized instead. I understand that you want a recent mpv version stabilized ASAP. So do I, but please don't CC arches as soon as delay period ends if you see that most of the deps in that stablereq are still not resolved by that time.
I'll leave the CC'ing of the arches to you... I don't maintain mpv :)
mpv-0.18.0 was stabilized, which doesn't have this problem, and should be compatible with recent smplayer versions. Please update to mpv-0.18.0.
