[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#365885: Video playback fails



Hi Michel,

On 5/6/06, Michel Dänzer <daenzer@debian.org> wrote:
On Sat, 2006-05-06 at 13:33 +0530, Toufeeq Hussain wrote:
>
> On 5/5/06, Michel Dänzer <daenzer@debian.org [5]> wrote:
> > On Fri, 2006-05-05 at 11:00 +0530, Toufeeq Hussain wrote:
> > >
> > > I've made sure the "VideoRam" Option is set to "32678" but there is
> > > not fix for this
> > > problem. I tried various VideoRam options(8M-32M) but no luck. I'm
> > > attaching portions from my xorg.conf file.
> >
> > As requested before, please provide full config and log files.
>
> Adding both Xorg.conf and Xorg.0.log files.

Thanks.


> (II) I810(0): Tweak BIOS image to 12288 kB VideoRAM
> (--) I810(0): Pre-allocated VideoRAM: 892 kByte
> (**) I810(0): VideoRAM: 131072 kByte

This looks like the VideoRam directive is working, but I'm not very
familiar with the i810 driver.

Cool.

Please post the output of xvinfo.

xvinfo output
==

X-Video Extension version 2.2
screen #0
 Adaptor #0: "Intel(R) Video Overlay"
   number of ports: 1
   port base: 73
   operations supported: PutImage
   supported visuals:
     depth 24, visualID 0x23
     depth 24, visualID 0x24
     depth 24, visualID 0x25
     depth 24, visualID 0x26
     depth 24, visualID 0x27
     depth 24, visualID 0x28
     depth 24, visualID 0x29
     depth 24, visualID 0x2a
   number of attributes: 4
     "XV_COLORKEY" (range 0 to 16777215)
             client settable attribute
             client gettable attribute (current value is 66046)
     "XV_BRIGHTNESS" (range -128 to 127)
             client settable attribute
             client gettable attribute (current value is 0)
     "XV_CONTRAST" (range 0 to 255)
             client settable attribute
             client gettable attribute (current value is 64)
     "XV_DOUBLE_BUFFER" (range 0 to 1)
             client settable attribute
             client gettable attribute (current value is 1)
   maximum XvImage size: 1920 x 1088
   Number of image formats: 4
     id: 0x32595559 (YUY2)
       guid: 59555932-0000-0010-8000-00aa00389b71
       bits per pixel: 16
       number of planes: 1
       type: YUV (packed)
     id: 0x32315659 (YV12)
       guid: 59563132-0000-0010-8000-00aa00389b71
       bits per pixel: 12
       number of planes: 3
       type: YUV (planar)
     id: 0x30323449 (I420)
       guid: 49343230-0000-0010-8000-00aa00389b71
       bits per pixel: 12
       number of planes: 3
       type: YUV (planar)
     id: 0x59565955 (UYVY)
       guid: 55595659-0000-0010-8000-00aa00389b71
       bits per pixel: 16
       number of planes: 1
       type: YUV (packed)

Do other video players show the same results, e.g. xine or vlc?

Yes. I'm able to reproduce the same problem with vlc,xine and totem.

Please note that my screen resolution is 1024 x 768 and the video file
in question is also encoded at 1024 x 768 using istanbul. The file
encoding seems to be good as the same file plays fine on Windows using
vlc. IMHO, the video players seem to maximize while playing this file
and seem to get a terminate signal from X.

Thanks.

-Toufeeq
--
blog @ http://toufeeq.blogspot.com



Reply to: