multimedia/mplayer breakage?
Nagilum
freebsd at nagilum.org
Thu May 19 09:42:34 PDT 2005
Damian Gerow wrote:
>I sup'ed my ports tonight, and forced an upgrade of mplayer (I hadn't
>bothered checking to see if anything had changed), and now suddenly I can't
>read DVDs:
>
> % mplayer dvd://1
> MPlayer 1.0pre7-3.4.2 (C) 2000-2005 MPlayer Team
> CPU: Advanced Micro Devices Opteron Sledgehammer (Family: 8, Stepping: 10)
> Detected cache-line size is 64 bytes
> MMX supported but disabled
> MMX2 supported but disabled
> SSE supported but disabled
> SSE2 supported but disabled
> 3DNow supported but disabled
> 3DNowExt supported but disabled
> CPUflags: MMX: 0 MMX2: 0 3DNow: 0 3DNow2: 0 SSE: 0 SSE2: 0
> Compiled for x86 CPU with extensions:
>
>
> Playing dvd://1.
> Reading disc structure, please wait...
> libdvdread: Invalid main menu IFO (VIDEO_TS.IFO).
> Can't open VMG info!
>
>
> Exiting... (End of file)
> %
>
>Anything else that uses libdvdread (xine, vobcopy, lsdvd, dvdbackup, etc)
>seems to work just fine.
>_______________________________________________
>
>
I can confirm this also for mencoder:
mencoder dvd://2 -dvd-device . -ovc xvid -oac copy -o film.avi
-xvidencopts
fixed_quant=4:cartoon=off:gmc=on:hq_ac=on:vhq=4:max_key_interval=300:trellis:qpel=on:max_bframes=4:bf_threshold=100:chroma_me:chroma_opt=on
-vf crop=720:560:0:6,scale=720:400
MEncoder 1.0pre7-3.4.2 (C) 2000-2005 MPlayer Team
CPU: (Family: 5, Stepping: 0)
Detected cache-line size is 32 bytes
CPUflags: Type: 5 MMX: 1 MMX2: 0 3DNow: 0 3DNow2: 0 SSE: 0 SSE2: 0
Compiled for x86 CPU with extensions: MMX
66 audio & 176 video codecs
File not found: 'frameno.avi'
Failed to open frameno.avi
libdvdread: Couldn't find device name.
Reading disc structure, please wait...
libdvdread: Invalid main menu IFO (VIDEO_TS.IFO).
Can't open VMG info!
Cannot open file/device.
Exiting...
The same script with the same files used to work with 1.0pre6!
There is definitively something broken here, I confirmed this on two
machines, both running FreeBSD, so I can't tell if it's mplayers or the
ports fault.
Kind regards,
Alex.
More information about the freebsd-ports
mailing list