Closed GoogleCodeExporter closed 8 years ago
Also, I'm seeing this on verbose output
Selected audio codec: [a52] afm: liba52 (AC3-liba52)
==========================================================================
[export] Exporting to file: /tmp/mplayer-af_exportajrtvi
[export] Memory mapped to file: /tmp/mplayer-af_exportajrtvi (0xb68e3000)
[export] Exporting to file: /tmp/mplayer-af_exportajrtvi
[export] Memory mapped to file: /tmp/mplayer-af_exportajrtvi (0xb68e3000)
AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample)
[export] Exporting to file: /tmp/mplayer-af_exportajrtvi
[export] Memory mapped to file: /tmp/mplayer-af_exportajrtvi (0xb68e3000)
[export] Exporting to file: /tmp/mplayer-af_exportajrtvi
[export] Memory mapped to file: /tmp/mplayer-af_exportajrtvi (0xb68e3000)
ID_AUDIO_CODEC=a52
[Mixer] No hardware mixing, inserting volume filter.
[export] Exporting to file: /tmp/mplayer-af_exportajrtvi
[export] Memory mapped to file: /tmp/mplayer-af_exportajrtvi (0xb68e3000)
It looks related since I don't see anything to indicate volnorm being used such
as
[libaf] Adding filter volnorm
and plain mplayer doesn't output anything like that.
Original comment by ccri...@gmail.com
on 18 May 2009 at 10:11
Where are you setting this extra filter? Did you try adding it to the Extra
options
in the Mplayer tab in preferences?
The export filter is used for the audio meter and has nothing to do with that.
Original comment by kdeko...@gmail.com
on 18 May 2009 at 10:13
I tried setting them in ~/.mplayer/config under the right profile (other options
work) and in the extra options gui. Neither work.
Original comment by ccri...@gmail.com
on 19 May 2009 at 12:51
Found that I used -af instead of -af-add when adding the export audio filter
in. So
this was removing the existing af chain. I also found that unless you use the
-v with
mplayer, you don't see the audio filter chain, unlike the video filters.
Original comment by kdeko...@gmail.com
on 19 May 2009 at 12:57
Original comment by kdeko...@gmail.com
on 19 May 2009 at 1:00
Original issue reported on code.google.com by
ccri...@gmail.com
on 18 May 2009 at 10:06