[MPlayer-dev-eng] [PATCH] More accurate af_volume

[Diego Biurrun]

Diego Biurrun writes:
> Zoltan Hidvegi writes:
> > 
> > I've also added printing the maximum volume for the integer case to
> > match the float case.  Also, the float filter did not print the max
> > volume if you did not use -af-adv force=4.
> 
> BTW, could you please document "-af-adv force=4" or tell me what it
> does so I can document it?

As I just noticed as I set out to finally move the rest of the audio
filter documentation from the XML to the man page, this *IS*
documented, but unfortunately the XML and the man page contradict each
other :-(

I'd appreciate if someone could tell me which of the two is correct,
I'm not able to figure out where libaf parses the -af-adv option..

man page:


-af-adv <force=(0-3):list=(filters)> (also see -af)
  Specify advanced audio filter options:

    force=<0-3>
      Forces the insertion of audio filters to one of the fol-
      lowing:
        0: completely automatic filter insertion (default)
        1: Optimize for accuracy.
        2: Optimize for speed.
        3: Turn off automatic filter insertion.


XML:


The overall execution of the filter layer is controlled using the
-af-adv option. This option has two suboptions:

force is a bit field that controls how the filters are inserted and
what speed/accuracy optimizations they use:


0

    Use automatic insertion of filters and optimize according to CPU
    speed.

1

    Use automatic insertion of filters and optimize for the highest
    speed. Warning: Some features in the audio filters may silently
    fail, and the sound quality may drop.

2

    Use automatic insertion of filters and optimize for quality.

3

    Use no automatic insertion of filters and no
    optimization. Warning: It may be possible to crash MPlayer using
    this setting.

4

    Use automatic insertion of filters according to 0 above, but use
    floating point processing when possible.

5

    Use automatic insertion of filters according to 1 above, but use
    floating point processing when possible.

6

    Use automatic insertion of filters according to 2 above, but use
    floating point processing when possible.

7

    Use no automatic insertion of filters according to 3 above, and
    use floating point processing when possible.


Thanks

Diego