Bug#548611: gnash: please add a configuration setting for initial volume level

[Gabriele Giacone]

On 08/31/2010 08:22 PM, Francesco Poli wrote:
> Hence, I should block Flash cookies, shouldn't I?
> 
> Well, sorry for not telling explicitly before (it didn't come up to me
> that my problem had to do with cookies!), but I am convinced I am
> already blocking Flash cookies!
> 
> After installing mozilla-plugin-gnash, I edited /etc/gnashrc by
> uncommenting the following line:
> 
>   set SOLSafeDir /dev/null
> 
> The reason is that I kind of hate cookies, in general.
> I always refuse them, even in web browsing, unless they are strictly
> needed for specific tasks (for instance, for a limited number of
> websites which require authentication).
> As a consequence, I saw that option and thought "I don't want Flash
> cookies, let's disable them!".

Well, I hadn't thought about flash cookies and consequently nor to
block them.
I told you the yt-cookies story because at the moment is the most
frequent topic. I wanted to exclude cookies from possible causes list
and I see that you already exclude them all, even the flash ones :)

> Since I block cookies, I have no ~/.gnash directory at all (no one
> created it!).
> That seems to be the reason why my volume settings are lost each time
> I start to watch a new video!
> 
> Anyway, I think the lack of a default value (which means that gnash has
> to rely on cookies for such settings) is a suboptimal situation.
> 
> As I requested in this very wishlist bug, I would like to have some
> configuration option to set the default initial volume and then leave
> to cookies other possible adjustments (for people who like accepting
> cookies), but still providing a sensible and configurable default (for
> people who do *not* like cookies).

I propose this workaround:
1) comment out SOLSafeDir option
2) access to yt, set volume level you want as initial level, close your
browser
3) uncomment out SOLReadOnly, the latter denies future changes.
Same workaround can be done at user level, by right-clicking on a clip,
"Edit - Preferences - Security" and ticking "Do not write Shared Object
files". This sets solReadOnly to true in ~/.gnashpluginrc

Alternative workaround could be something such as:
3) # chmod -R 500 ~/.gnash/SharedObjects
   # chmod 600 ~/.gnash/SharedObjects/s.ytimg.com/soundData.sol
so that gnash can also remember volume level.

> Which levels? The alsamixer ones?
> 
> They are fine for all the other applications I use, why should I mess
> up with them just to adapt to gnash?!?

I can't figure out yet how gnash can set volume higher than volume set
by your mixer.
I mean ok, yt player starts with maximum level but why that maximum
level is higher than usual. For example, why higher than your audacious
maximum level? It's higher, isn't it?

Doesn't it simply depend on the source? Hence the reason is that all
video you're watching are _recorded_ louder than we'd like they were?
It would make sense doing some comparisons.