Re: [Xpert]Using Xv to display odd/even fields from a TV camera

2002-05-11 Thread Paul Robertson

  On Fri, 10 May 2002, Paul Robertson wrote:
 
   I have some software which uses Xv to render images acquired from a TV
   camera in something like realtime.
   Currently we only capture even fields, and we scale the image
vertically by
   200%. It looks OK.
  
   Now we need to start working with both odd and even fields. If we do
that
   with our current software, the picture wobbles up and down.
   If I write some code to adjust the position of the odd field, the
picture
   still looks wrong, particularly if nothing is moving in the picture.
   If I write code to reconstitute a full frame by interlacing the odd
and even
   fields, then I see nasty artefacts when there is horizontal motion in
front
   of the camera.
  
   We actually use ATI Rage and the r128 driver at the moment, but a
while ago
   we evaluated the i815 graphics controller.  I remember that it
supported a
   number of different hardware scaling methods including Up
interpolation
   and Down interpolation, and I wondered if I could use these modes to
get a
   better quality picture.

 ATI hardware does support this but the driver does not do this (yet?).
 What software do you want to use this with ? Is the source available for
 download ?

  Vladimir Dergachev

Its closed source commercial stuff I'm afraid.

It looks like this topic has been the subject of quite some discussion in
the past
before momentum was lost. I'll try to stay in the loop this time in case
there is
anything I can do to help move things along.

--
Paul


___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]Using Xv to display odd/even fields from a TV camera

2002-05-11 Thread Paul Robertson

Can I butt in with some basic questions?
I'd just like to understand what kinds of applications will benefit from
this proposal.

We have lots of DVD players, the ubiquitous Brooktree framegrabber,
and esoteric stuff like my ADV601.

I know for sure it would help me.

The Bt chips normally produce 25/30 interlaced frames/sec which might
look lousy when displayed if there is horizontal motion.
They can be programmed to decimate the frame, so you would only see say
25/30 even fields/sec
Can they also be programmed to deliver 50/60 fields/sec?
Does v4l support all this?
Do v4l apps usually have the Bt chip writing the YUV image directly into
video memory? Would Xv, or the graphics driver support odd/even fields
in this case?

DVD players I know nothing about. What do they do?

--
Paul

- Original Message -
From: Mark Vojkovich [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, May 10, 2002 11:34 PM
Subject: Re: [Xpert]Using Xv to display odd/even fields from a TV camera


 On Fri, 10 May 2002, Billy Biggs wrote:

The delay stuff is less important than the field flag.
 
  Mark Vojkovich ([EMAIL PROTECTED]):
 
   I'd like an XV_FIELD (or better named) attribute that indicates the
   next PutImage request should upload and display the field rather than
   the frame which is the default.  0 is top, 1 is bottom, per mpeg
   conventions.  It's a one-shot state that gets reset to frame after the
   next PutImage happens.
 
How does this work for full 50 or 59.94fps video?  Do I upload the
  same frame twice, or does this attribute just mean: only copy from the
  source frame the even/odd field, so that the whole frame isn't coped
  twice, only half of it?

It means that only the field is copied and only the field is
 displayed.


 
I'm also worried about switching from frame-mode to field-mode.  In my
  DVD player for example, I'll switch between 3:2 pulldown correction in
  software, or, if I lose the phase, go back to 60fps output.  Do you
  think video cards are going to have a problem switching the scaling
  width/height without artifacts?

NVIDIA cards won't have a problem with this.  I think some cheaper
 cards that don't double buffer their registers and have to be programmed
 during the retrace won't be able to do this very well.


 Mark.

 ___
 Xpert mailing list
 [EMAIL PROTECTED]
 http://XFree86.Org/mailman/listinfo/xpert

___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



[Xpert]Dualheading

2002-05-11 Thread Per Edin

Hello,

I have searched thru xfree.org but found nothting about dualheading a X11 
system. Where can I find such guide?
If it is just some simple changes in the XF86Config file that needs to be 
made, what file should I edit XF86Config or XF86Config-4 I have them both.

-- 
Best regards, Per Edin!
Sweden, Europe
Maintainer and Developer @ the KStorm project.
http://kstorm.sourceforge.net
ICQ: 151399739
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



[Xpert]PPC

2002-05-11 Thread Mariusz Mazur

I've recently compiled xfree 4.2 on ppc and was rather surprised that nvidia 
driver didn't compile. Could someone give me a list of all drivers that 
should compile on ppc (and if they should have dri enabled)?

-- 
Kady czowiek, ktry naprawd yje, nie ma charakteru, nie moe go mie.
Charakter jest zawsze martwy, otacza ci zgnia struktura przeniesiona z 
przeszoci. Jeeli dziaasz zgodnie z charakterem wtedy nie dziaasz w ogle
- jedynie mechanicznie reagujesz. { Osho }
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



[Xpert]Heavy problem with very recent hardware (KT333, GeForce4Ti)

2002-05-11 Thread Samuel Hornus


Hi all,

Here is the configuration of the machine.
(we have many machine exactly like this one,
and the bug is reproduced on two of them,
others haven't been tested)

- Motherboard : MSI KT333
- 1 Go of RAM (DDR 266)
- Athlon 1700+ (1467 Mhz)
- MSI GeForce4Ti 4400 128Mo DDR
- Mandrake 8.2 distribution
- nvidia 2880 drivers.

After a while, the Xserver hangs/crashes.
sometimes I can go back to a console, but the login
program hangs too. - reboot.
When an OpenGL application is running, the crash appears
more quickly. the debugguer tells that the segfault comes
from a function ?? called from nvidia's driver.
(__nv09937() in libGLcore.so)

I spent this week trying to hunt the bug with the help
of an Nvidia developper. Without success.

Since Xserver also crashes without openGL apps running.
I believe this comes from the XFree86 w/ GeForce4Ti.
(which is not in the supported list of videocards).

passing mem=nopentium ti the linux kernel does not solve
the problem.

Attached is the XFree86.0.log file from /var/log

Any help or idea to solve the problem would be greatly
appreciated !

Perhaps this may come from the mandrake 8.2 distribution.

Thanks,
-- 
Samuel Hornus
iMAGIS, laboratoire GRAVIR/IMAG (CNRS,INRIA,INPG,UJF)
tel 04 76 61 54 52-mail [EMAIL PROTECTED]


XFree86 Version 4.2.0 / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 23 January 2002
If the server is older than 6-12 months, or if your card is
newer than the above date, look for a newer version before
reporting problems.  (See http://www.XFree86.Org/)
Build Operating System: Linux 2.4.18-1mdksmp i686 [ELF] 
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: /var/log/XFree86.0.log, Time: Sat May 11 20:56:17 2002
(==) Using config file: /etc/X11/XF86Config-4
(==) ServerLayout layout1
(**) |--Screen screen1 (0)
(**) |   |--Monitor iiyama Vision Master Pro 512
(**) |   |--Device GLX
(**) |--Input Device wheel-ps2
(**) |--Input Device us-kbd
(**) Option AutoRepeat 250 30
(**) Option XkbRules xfree86
(**) XKB: rules: xfree86
(**) Option XkbModel pc105
(**) XKB: model: pc105
(**) Option XkbLayout us
(**) XKB: layout: us
(==) Keyboard: CustomKeycode disabled
(**) FontPath set to unix/:-1
(**) RgbPath set to /usr/X11R6/lib/X11/rgb
(==) ModulePath set to /usr/X11R6/lib/modules
(**) Option AllowMouseOpenFail
(--) using VT number 7

(II) Open APM successful
(II) Module ABI versions:
XFree86 ANSI C Emulation: 0.1
XFree86 Video Driver: 0.5
XFree86 XInput driver : 0.3
XFree86 Server Extension : 0.1
XFree86 Font Renderer : 0.3
(II) Loader running on linux
(II) LoadModule: bitmap
(II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a
(II) Module bitmap: vendor=The XFree86 Project
compiled for 4.2.0, module version = 1.0.0
Module class: XFree86 Font Renderer
ABI class: XFree86 Font Renderer, version 0.3
(II) Loading font Bitmap
(II) LoadModule: pcidata
(II) Loading /usr/X11R6/lib/modules/libpcidata.a
(II) Module pcidata: vendor=The XFree86 Project
compiled for 4.2.0, module version = 0.1.0
ABI class: XFree86 Video Driver, version 0.5
(II) PCI: Probing config type using method 1
(II) PCI: Config type is 1
(II) PCI: stages = 0x03, oldVal1 = 0x80008864, mode1Res1 = 0x8000
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 1106,3099 card 1106, rev 00 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 1106,b099 card , rev 00 class 06,04,00 hdr 01
(II) PCI: 00:07:0: chip 1106,3065 card 1186,1400 rev 43 class 02,00,00 hdr 00
(II) PCI: 00:11:0: chip 1106,3147 card 1106, rev 00 class 06,01,00 hdr 80
(II) PCI: 00:11:1: chip 1106,0571 card 1106,0571 rev 06 class 01,01,8a hdr 00
(II) PCI: 00:11:2: chip 1106,3038 card 0925,1234 rev 23 class 0c,03,00 hdr 00
(II) PCI: 00:11:3: chip 1106,3038 card 0925,1234 rev 23 class 0c,03,00 hdr 00
(II) PCI: 00:11:5: chip 1106,3059 card 1462,4720 rev 40 class 04,01,00 hdr 00
(II) PCI: 01:00:0: chip 10de,0251 card 1462,8711 rev a2 class 03,00,00 hdr 00
(II) PCI: End of PCI scan
(II) LoadModule: scanpci
(II) Loading /usr/X11R6/lib/modules/libscanpci.a
(II) Module scanpci: vendor=The XFree86 Project
compiled for 4.2.0, module version = 0.1.0
ABI class: XFree86 Video Driver, version 0.5
(II) UnloadModule: scanpci
(II) Unloading /usr/X11R6/lib/modules/libscanpci.a
(II) Host-to-PCI bridge:
(II) PCI-to-ISA bridge:
(II) PCI-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set)
(II) Bus 0 I/O range:
[0] -1  0x - 0x (0x1) IX[B]
(II) Bus 0 non-prefetchable memory range:
[0] -1  0x - 0x (0x0) MX[B]
(II) Bus 0 prefetchable memory range:
[0] -1  0x - 0x (0x0) MX[B]
(II) 

Re: [Xpert]Using Xv to display odd/even fields from a TV camera

2002-05-11 Thread Mark Vojkovich

On Sat, 11 May 2002, Paul Robertson wrote:

 Can I butt in with some basic questions?
 I'd just like to understand what kinds of applications will benefit from
 this proposal.
 
 We have lots of DVD players, the ubiquitous Brooktree framegrabber,
 and esoteric stuff like my ADV601.
 
 I know for sure it would help me.
 
 The Bt chips normally produce 25/30 interlaced frames/sec which might
 look lousy when displayed if there is horizontal motion.
 They can be programmed to decimate the frame, so you would only see say
 25/30 even fields/sec
 Can they also be programmed to deliver 50/60 fields/sec?
 Does v4l support all this?
 Do v4l apps usually have the Bt chip writing the YUV image directly into
 video memory? Would Xv, or the graphics driver support odd/even fields
 in this case?

In that case, no.  In the case of a decoder dumping data to 
the graphics controller via the VIP (CCIR 656) it's possible and
I'm currently looking at implementing a generic CCIR656 input
device for the NVIDIA driver (for NVIDIA Personal Cinema and the
like).  I will automatically bob the video in that case.  No
API changes are required for that.  You just tell the Xv adaptor
where to put the data and it will put anything coming through
the VIP port there.  It relies on another piece of software to
program the device that sends stuff through the VIP, whether that
is a TV decoder, DVD card, or other device.

  For cases where a Bt chip dumps YUV data to the framebuffer directly,
there are some synchronization issues that can't be solved unless
the Bt driver and overlay driver are the same driver.  Currently,
with Xv+V4L based solutions, the Bt control is in the kernel while
the overlay is in the X-server.  I don't see how to handle the 
synchronization in that case.


 
 DVD players I know nothing about. What do they do?
 

   Mpeg2 supports interleaved content.  Looks like crap if you 
display it as a weave.   We're mostly talking about that on this
list.  I think we merely need a standard XvPortAttribute hint
to tell the Xv adaptor if the next Xv(Shm)PutImage request
should be a field instead of the default frame behavior.  The
Xv adaptor only loads half of the data in that case and 
displays it with the correct offsets and scaling.



Mark.

___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert