[MPlayer-users] SBLive and Dolby Surround

[Jeremy Mann]

I just read documentation and finally got dolby surround decoding
working.  In my testing I used -vo null -ao null and saw that it decoded
from 2ch->4ch appropriately.  However when trying to apply this to alsa9
+ sblive it can't set the channels(when using spdif).  I know this has
been addressed in the past, but I was curious if there was any
workaround of any kind? Alternatively will dolby surround get
automagically decoded by a hardware receiver?

Command line: mplayer file.avi -aop list=surround -ao alsa9:hw:0,1 -vo
xvidix -fs -double -y 540 

Output:
AVI file format detected.
VIDEO:  [XVID]  640x352  24bpp  23.98 fps  1014.1 kbps (123.8 kbyte/s)
Clip info:
 Software: Nandub v1.0rc2
========================================================================
==
Opening audio decoder: [mp3lib] MPEG layer-2, layer-3
MP3lib: init layer2&3 finished, tables done
AUDIO: 48000 Hz, 2 ch, 16 bit (0x10), ratio: 16000->192000 (128.0 kbit)
Selected audio codec: [mp3] afm:mp3lib (mp3lib MPEG layer-2, layer-3)
========================================================================
==
No vidix driver name provided, probing available ones!
vo: X11 running at 1920x540 with depth 24 and 32 bpp ("debian:0.0" =>
remote display)
[mga] No supported cards found
[mga] No supported cards found
[radeon] Found chip: Radeon R100 QD [Radeon 64 DDR]
libdha: DHA kernelhelper failed: No such file or directory
libdha: DHA kernelhelper failed: No such file or directory
[radeon] Video memory = 32Mb
[radeon] Set write-combining type of video memory
[radeon] Saved overlay colorkey settings
VIDIX: Description: BES driver for Radeon cards
VIDIX: Author: Nick Kurshev
========================================================================
==
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
Selected video codec: [ffodivx] vfm:ffmpeg (FFmpeg MPEG-4)
========================================================================
==
Checking audio filter chain for 48000Hz/2ch/16bit ->
48000Hz/2ch/16bit...
AF_pre: af format: 2 bps, 2 ch, 48000 hz, little endian signed int
AF_pre: 48000Hz 2ch Signed 16-bit (Little-Endian)
pl_surround: init input rate=48000, channels=2
pl_surround: 20msec surround delay, rate 48000 - buffers are 1982 bytes
each
alsa-init: testing and bugreports are welcome.
alsa-init: requested format: 48000 Hz, 4 channels, Signed 16-bit
(Little-Endian)
alsa-init: soundcard set to hw:0
alsa-init: unable to set channels: Invalid argument
Could not open/initialize audio device -> no sound.
Audio: no sound
Starting playback...
VDec: vo config request - 640 x 352 (preferred csp: Planar YV12)
VDec: using Planar YV12 as output csp (no 0)
VO: [xvidix] 640x352 => 640x540 Planar YV12  [fs]
[radeon] Restored overlay colorkey settings

Exiting... (Quit)

Jeremy Mann
IT Manager 
IntegraCare Home Health
315 Harwood Rd.
Bedford, TX 76021
V: 817-514-8088 x225
F: 817-514-7709
email: jmann at integracarehh.com


-----Original Message-----
From: mplayer-users-bounces at mplayerhq.hu
[mailto:mplayer-users-bounces at mplayerhq.hu] On Behalf Of
ephemeron at softhome.net
Sent: Tuesday, May 06, 2003 7:02 PM
To: mplayer-users at mplayerhq.hu
Subject: Re: [MPlayer-users] Conflict between -vf and -vop suboption
parsing


[Automatic answer: RTFM (read DOCS, FAQ), also read
DOCS/bugreports.html] On Tue, 6 May 2003 13:24:57 -0400, D Richard
Felker III wrote:
> 
> On Tue, May 06, 2003 at 12:09:19PM +0800, ephemeron at softhome.net 
> wrote:
> > Which is obsoleted, -vf or -vop?  Both options work with my cvs 
> > version of MPlayer. However, -vop ${SCALE},${CROP} works like -vf 
> > ${CROP},${SCALE}.  For example, -vop ${CROP},${SCALE} will bail out 
> > if the "cropped area is out of original".  To produce a similar 
> > "crash" with -vf I have to reverse the suboptions to -vf 
> > ${SCALE},${CROP}.  Shouldn't the two options produce the same 
> > results?  Shouldn't mplayer at least parse their suboptions in the 
> > same order?  Better yet, why not do away with the other option?  
> > It's confusing!
> 
> No, that's the whole point of -vf. -vop has always been backwards and 
> that was confusing, and the name was dumb/inconsistent to begin with, 
> so -vf was added to replace it and do things in the forward order.  
> BUT, -vop was left in for backwards compatibility with old scripts and

> whatnot. So you should use -vf now. -vop is deprecated.

Thanks for the clarification.  So am I right in assuming that the proper
place for suboption "pp=" is now before "scale=" and "crop="?

-vf ${PP},${CROP},${SCALE}

Sorry, if I'm belaboring the obvious.

_______________________________________________
RTFM!!!  http://www.MPlayerHQ.hu/DOCS
Search:  http://www.MPlayerHQ.hu/cgi-bin/htsearch
http://mplayerhq.hu/mailman/listinfo/mplayer-users