Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 08-12-05, 11:52 AM   #1
cyberElvis
Registered User
 
Join Date: Apr 2005
Posts: 1
Default Issues with XV and mythtv

I am having some issues getting XV working with Myth, and any help would be appreciated.
XV works without issues in xine or mplayer.

Here is my setup:
Gentoo box with mythtv-0.18.1-r2 ebuild
6600GT card with 7667 nvidia drivers
PVR250 with ivtv-0.2.0_rc3 ebuild

I am running the DVI output directly from my 6600 to my projector.
When I turn on Bob deinterlace my CPU is pegged at 90+%, but it looks great.
If I can get XV working that will be one of the last steps before I can make this MythBox my primary tv watching device

Here is the error I see when I run mythfrontend:

2005-08-09 22:34:40.923 Using XV port 270
X Error: BadMatch (invalid parameter attributes) 8
Major opcode: 142
Minor opcode: 14
Resource id: 0x1aa
2005-08-09 22:34:40.939 Couldn't get the color key color, and we need it.
You likely won't get any video.

Here is the output of xvinfo:

X-Video Extension version 2.2
screen #0
Adaptor #0: "NV17 Video Texture"
number of ports: 1
port base: 270
operations supported: PutImage
supported visuals:
depth 24, visualID 0x21
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
depth 24, visualID 0x2b
depth 24, visualID 0x2c
depth 24, visualID 0x2d
depth 24, visualID 0x2e
depth 24, visualID 0x2f
depth 24, visualID 0x30
depth 24, visualID 0x31
depth 24, visualID 0x32
depth 24, visualID 0x33
depth 24, visualID 0x34
depth 24, visualID 0x35
depth 24, visualID 0x36
depth 24, visualID 0x37
depth 24, visualID 0x38
depth 24, visualID 0x39
depth 24, visualID 0x3a
depth 24, visualID 0x3b
depth 24, visualID 0x3c
depth 24, visualID 0x3d
depth 24, visualID 0x3e
depth 24, visualID 0x3f
depth 24, visualID 0x40
depth 24, visualID 0x41
depth 24, visualID 0x42
depth 24, visualID 0x43
depth 24, visualID 0x44
depth 24, visualID 0x45
depth 24, visualID 0x46
depth 24, visualID 0x47
depth 24, visualID 0x48
depth 24, visualID 0x49
depth 24, visualID 0x22
depth 24, visualID 0x4a
depth 24, visualID 0x4b
depth 24, visualID 0x4c
depth 24, visualID 0x4d
depth 24, visualID 0x4e
depth 24, visualID 0x4f
depth 24, visualID 0x50
depth 24, visualID 0x51
depth 24, visualID 0x52
depth 24, visualID 0x53
depth 24, visualID 0x54
depth 24, visualID 0x55
depth 24, visualID 0x56
depth 24, visualID 0x57
depth 24, visualID 0x58
depth 24, visualID 0x59
depth 24, visualID 0x5a
depth 24, visualID 0x5b
depth 24, visualID 0x5c
depth 24, visualID 0x5d
depth 24, visualID 0x5e
depth 24, visualID 0x5f
depth 24, visualID 0x60
depth 24, visualID 0x61
depth 24, visualID 0x62
depth 24, visualID 0x63
depth 24, visualID 0x64
depth 24, visualID 0x65
depth 24, visualID 0x66
depth 24, visualID 0x67
depth 24, visualID 0x68
depth 24, visualID 0x69
depth 24, visualID 0x6a
depth 24, visualID 0x6b
depth 24, visualID 0x6c
depth 24, visualID 0x6d
depth 24, visualID 0x6e
depth 24, visualID 0x6f
depth 24, visualID 0x70
number of attributes: 3
"XV_SET_DEFAULTS" (range 0 to 0)
client settable attribute
"XV_ITURBT_709" (range 0 to 1)
client settable attribute
client gettable attribute (current value is 0)
"XV_SYNC_TO_VBLANK" (range 0 to 1)
client settable attribute
client gettable attribute (current value is 1)
maximum XvImage size: 2046 x 2046
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: 0x59565955 (UYVY)
guid: 55595659-0000-0010-8000-00aa00389b71
bits per pixel: 16
number of planes: 1
type: YUV (packed)
id: 0x30323449 (I420)
guid: 49343230-0000-0010-8000-00aa00389b71
bits per pixel: 12
number of planes: 3
type: YUV (planar)
Adaptor #1: "NV05 Video Blitter"
number of ports: 32
port base: 271
operations supported: PutImage
supported visuals:
depth 24, visualID 0x21
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
depth 24, visualID 0x2b
depth 24, visualID 0x2c
depth 24, visualID 0x2d
depth 24, visualID 0x2e
depth 24, visualID 0x2f
depth 24, visualID 0x30
depth 24, visualID 0x31
depth 24, visualID 0x32
depth 24, visualID 0x33
depth 24, visualID 0x34
depth 24, visualID 0x35
depth 24, visualID 0x36
depth 24, visualID 0x37
depth 24, visualID 0x38
depth 24, visualID 0x39
depth 24, visualID 0x3a
depth 24, visualID 0x3b
depth 24, visualID 0x3c
depth 24, visualID 0x3d
depth 24, visualID 0x3e
depth 24, visualID 0x3f
depth 24, visualID 0x40
depth 24, visualID 0x41
depth 24, visualID 0x42
depth 24, visualID 0x43
depth 24, visualID 0x44
depth 24, visualID 0x45
depth 24, visualID 0x46
depth 24, visualID 0x47
depth 24, visualID 0x48
depth 24, visualID 0x49
depth 24, visualID 0x22
depth 24, visualID 0x4a
depth 24, visualID 0x4b
depth 24, visualID 0x4c
depth 24, visualID 0x4d
depth 24, visualID 0x4e
depth 24, visualID 0x4f
depth 24, visualID 0x50
depth 24, visualID 0x51
depth 24, visualID 0x52
depth 24, visualID 0x53
depth 24, visualID 0x54
depth 24, visualID 0x55
depth 24, visualID 0x56
depth 24, visualID 0x57
depth 24, visualID 0x58
depth 24, visualID 0x59
depth 24, visualID 0x5a
depth 24, visualID 0x5b
depth 24, visualID 0x5c
depth 24, visualID 0x5d
depth 24, visualID 0x5e
depth 24, visualID 0x5f
depth 24, visualID 0x60
depth 24, visualID 0x61
depth 24, visualID 0x62
depth 24, visualID 0x63
depth 24, visualID 0x64
depth 24, visualID 0x65
depth 24, visualID 0x66
depth 24, visualID 0x67
depth 24, visualID 0x68
depth 24, visualID 0x69
depth 24, visualID 0x6a
depth 24, visualID 0x6b
depth 24, visualID 0x6c
depth 24, visualID 0x6d
depth 24, visualID 0x6e
depth 24, visualID 0x6f
depth 24, visualID 0x70
number of attributes: 2
"XV_SET_DEFAULTS" (range 0 to 0)
client settable attribute
"XV_SYNC_TO_VBLANK" (range 0 to 1)
client settable attribute
client gettable attribute (current value is 0)
maximum XvImage size: 2046 x 2046
Number of image formats: 5
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: 0x59565955 (UYVY)
guid: 55595659-0000-0010-8000-00aa00389b71
bits per pixel: 16
number of planes: 1
type: YUV (packed)
id: 0x30323449 (I420)
guid: 49343230-0000-0010-8000-00aa00389b71
bits per pixel: 12
number of planes: 3
type: YUV (planar)
id: 0x3
guid: 03000000-0000-0010-8000-00aa00389b71
bits per pixel: 32
number of planes: 1
type: RGB (packed)
depth: 24
red, green, blue masks: 0xff0000, 0xff00, 0xff

Thanks for any help!
cyberElvis is offline   Reply With Quote
Old 08-12-05, 01:18 PM   #2
Sean84
Registered User
 
Join Date: Jul 2004
Posts: 13
Default Re: Issues with XV and mythtv

nvidia removed the video overlay in 6600 series cards, also for the 7800,
and possibly some/all of the pcie 6800 versions(nv41,nv45),
nv40 still has it(agp 6800 series)
nvidia hasn't responded to which chips are missing the overlay

you can still use mythtv, ignore the colorkey error,but you wont have any video controls, brightness,contrast,etc (look forward to adjusting your monitor for the life of this card...)

I returned my 6600gt, now I'm looking for another card...
Sean84 is offline   Reply With Quote
Old 02-09-06, 10:11 AM   #3
dpelisse
Registered User
 
Join Date: Feb 2006
Posts: 5
Default Re: Issues with XV and mythtv

It seems that NVIDIA also remove the overlay on the FX serie.
I have a FX1400 and a FX4500 and I can't see XV_COLORKEY when running xvinfo.

Anybody to confirm this ??
dpelisse is offline   Reply With Quote
Old 02-09-06, 03:27 PM   #4
davemoore
Registered User
 
Join Date: Sep 2004
Posts: 50
Default Re: Issues with XV and mythtv

XV is still implemented in these cards, it just doesn't use overlay anymore. Instead it uses video texture (part of the 3D engine). If MythTV insists on modifying the color key, that's a bug in MythTV.
davemoore is offline   Reply With Quote
Old 02-09-06, 09:25 PM   #5
treblid
Registered User
 
Join Date: Sep 2005
Posts: 13
Default Re: Issues with XV and mythtv

Quote:
Originally Posted by davemoore
XV is still implemented in these cards, it just doesn't use overlay anymore. Instead it uses video texture (part of the 3D engine). If MythTV insists on modifying the color key, that's a bug in MythTV.
So what you expect MythTV to do? use Video Texture for newer chips, and then modify the color key for old cards?

I have been very quiet about this issue for a long time.. I personally believe this is a BUG in the Nvidia driver or hardware itself. Why should others fix the mistakes of Nvidia?

Had I done proper research and known about this before I make my decision, I would definitely not buy this card. But having already brought it, I accept the fact that I have been conned and since I can't return the card (they wouldn't accept the return since it's 'working'), i would continue to use it simply becuase I have no other choice.

In a sense, I'm using a card which I considered to be faulty, and indirectly rewarded some developers for not doing a proper job. But no big deal I guess, what goes around comes around.

cyberElvis, you can continue to use the 660GT, not able to set HUE/brightness/contrast etc is a pain, but hopefully you can get over it. I have.. It's not a perfect world after all..
treblid is offline   Reply With Quote
Old 02-12-06, 04:24 AM   #6
hondaman
Registered User
 
Join Date: Jan 2006
Posts: 39
Default Re: Issues with XV and mythtv

bump. would like to see the answer to this
hondaman is offline   Reply With Quote
Old 02-13-06, 01:07 PM   #7
davemoore
Registered User
 
Join Date: Sep 2004
Posts: 50
Default Re: Issues with XV and mythtv

Overlay is basically a dead technology. You won't see it in new cards anymore. That goes for ATI also. The whole point of the XV extension is so that an application can generate scaled video, without needed to care about the underlying mechanism on the video card. The XV extension is documented here:

http://netmirror.org/mirror/xfree86....rotocol-v2.TXT

If an application uses XV correctly, it won't matter whether the card is using overlay or texture for the underlying support. The application doesn't need to care. You'll notice in the documentation above, it says nothing about color key. That's because color key is a card-specific feature. If MythTV wants to mess with it, it needs to understand that it's not something present on all cards, so it has to autodetect it and handle it's absense gracefully.

I'm not an expert on the subject, but MythTV probably has a good reason for wanting to change the color key -- it's probably trying to do something fancy with an OSD or something. It just has to be more careful about autodetecting card features since it's messing with card-specific tweaks.
davemoore is offline   Reply With Quote
Old 02-15-06, 09:43 PM   #8
treblid
Registered User
 
Join Date: Sep 2005
Posts: 13
Default Re: Issues with XV and mythtv

Quote:
Originally Posted by davemoore
Overlay is basically a dead technology. You won't see it I'm not an expert on the subject, but MythTV probably has a good reason for wanting to change the color key -- it's probably trying to do something fancy with an OSD or something. It just has to be more careful about autodetecting card features since it's messing with card-specific tweaks.
What about brightness, contrast, and etc then?
Is the next driver update going to put them back in?
treblid is offline   Reply With Quote

Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 08:02 PM.


Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.