Lightspark 100% volume issue is now fixed


For some time I’ve received a few reports about lightspark rais­ing the sys­tem vol­ume to 100% (and “killing ears”) when­ever a YouTube clip was started. It took some time for me to fig­ure out what was going on, since I was not able to repro­duce the issue on my sys­tem and of course the code was not will­ingly touch­ing the sys­tem volume.

It turns out that the issue was caused by the recently intro­duced “flat-volume” sup­port in PulseAu­dio. When flat vol­ume is enabled the vol­ume of a stream is absolute and not rel­a­tive to the sys­tem vol­ume. Since the default vol­ume in flash is 100% by spec then Lightspark was unwill­ingly set­ting the sys­tem vol­ume to an extremely high value, and I’m really sorry for that.

I’ve just com­mit­ted a fix in git mas­ter that should fix this prob­lem for good by prop­erly vir­tu­al­iz­ing the vol­ume seen by flash and scal­ing it by the sys­tem vol­ume. I hope this helps peo­ple with flat vol­ume enabled.


Flattr this

,

  • Gabriele Gia­cone

    Ideal would be imple­ment­ing Local Shared Objects aka flash cook­ies that also con­tain vol­ume level.
    Gnash sup­ports LSO and stores them under ~/.gnash/SharedObjects. It could be taken as exam­ple http://wiki.gnashdev.org/Actionscript/SharedObject

  • Gabriele Gia­cone

    Ideal would be imple­ment­ing Local Shared Objects aka flash cook­ies that also con­tain vol­ume level.
    Gnash sup­ports LSO and stores them under ~/.gnash/SharedObjects. It could be taken as exam­ple http://wiki.gnashdev.org/Actionscript/SharedObject

  • apig­notti

     That must surely be done for com­plete YouTube sup­port, but the issue is actu­ally unre­lated. With the pre­vi­ous code any flash ad on the net could have played sound ad full vol­ume, while now the user choice of the sys­tem vol­ume is respected.

  • apig­notti

     That must surely be done for com­plete YouTube sup­port, but the issue is actu­ally unre­lated. With the pre­vi­ous code any flash ad on the net could have played sound ad full vol­ume, while now the user choice of the sys­tem vol­ume is respected.

  • Andrea Azz­ini

    bone headed back­wards inco­pat­i­bil­ity ftw... why oh why must these projects (refer­ring to PulseAu­dio) con­stantly con­firm that they lack any idea of a strategy.

  • Andrea Azz­ini

    bone headed back­wards inco­pat­i­bil­ity ftw... why oh why must these projects (refer­ring to PulseAu­dio) con­stantly con­firm that they lack any idea of a strategy.

  • apig­notti

     The rea­son­ing behind flat-volume is actu­ally cor­rect, what is weird is that effec­tively the inter­face exposed to the user is changed... and that is not so nice.

  • apig­notti

     The rea­son­ing behind flat-volume is actu­ally cor­rect, what is weird is that effec­tively the inter­face exposed to the user is changed... and that is not so nice.

Lightspark 100% volume issue is now fixed


For some time I’ve received a few reports about lightspark rais­ing the sys­tem vol­ume to 100% (and “killing ears”) when­ever a YouTube clip was started. It took some time for me to fig­ure out what was going on, since I was not able to repro­duce the issue on my sys­tem and of course the code was not will­ingly touch­ing the sys­tem volume.

It turns out that the issue was caused by the recently intro­duced “flat-volume” sup­port in PulseAu­dio. When flat vol­ume is enabled the vol­ume of a stream is absolute and not rel­a­tive to the sys­tem vol­ume. Since the default vol­ume in flash is 100% by spec then Lightspark was unwill­ingly set­ting the sys­tem vol­ume to an extremely high value, and I’m really sorry for that.

I’ve just com­mit­ted a fix in git mas­ter that should fix this prob­lem for good by prop­erly vir­tu­al­iz­ing the vol­ume seen by flash and scal­ing it by the sys­tem vol­ume. I hope this helps peo­ple with flat vol­ume enabled.


Flattr this

,