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

Newegg Daily Deals

Reply
 
Thread Tools
Old 05-31-09, 09:33 AM   #49
djalma
Registered User
 
Join Date: Sep 2005
Posts: 16
Default Re: Tearing, Tearing and again TEARING!!

Quote:
Originally Posted by Stephen Warren View Post
The screenshots in comment #44 definitely aren't tearing; they seem like some kind of video decoding corruption. Probably best to ask on the MPlayer users list.
After a little bit of research seems (2 me but im not an expert xD) to be a bug in the graphic card itself. ?¿ (Firmware problem ?¿?¿?)
Im thinking in a bug and not in a limitation of the gfc itself to "play" this type of videos 'cause:
Quote:
NO TEARING
mplayer -vo xv *avi
+
mplayer -cache 200000 -vo xv -fs ...
"Battery test (using the same 720p hd video for testing)":

SAMSUNG 20' TFT + FX5200 DVI :

Windows xp sp3 (using wmp or mplayer4windows or vlc) -----> Massive weird lines
Linux ----> The same as windoze

SAMSUNG 20' TFT + FX5200 VGA :

Windows xp sp3 (using wmp or mplayer4windows or vlc) -----> Some weird lines still there when a text appears, and almost nothing or a random one when no text.

Linux ----> Massive weird lines

Laptop 15' with 8600M + windows vista : ----> PERFECT

SAMSUNG 20' TFT + 8600M VGA + VISTA : -------> PERFECT

Quote:
Originally Posted by ghost_zero5 View Post
@Stephen: He/she said that problem occurs on any player or is this just about the last screenshots that occur that way with every player?

But actually, I wonder a bit: How did you create those screenshots in the first place because with the snapshot function of SMPlayer I never was able to "record" the tearing itself and if I use the desktop screenshot function (Print key) there is more wrong with the picture than just tearing (at least if I don't stop the video but if I stop the video I also never was able to see tearing) - probably because parts of more than just one video pictures are taken that way (might be related to Compiz though, I would need to try it without Compiz).
All photos was maked with a Canon EOS. xD

I would show you a video of this effect but I havent got charged batteries atm for the other camera.
The video would be interesting 'cause when you pause the "movie", you still can see the lines "moving" in the horizontal axis. Only for that ---> not tearing.

EDIT:

Weird lines:
Code:
==========================================================================
LAVF: 1 audio and 1 video streams found
LAVF: build 3414272
VIDEO:  [avc1]  1280x720  24bpp  29.970 fps    0.0 kbps ( 0.0 kbyte/s)
[V] filefmt:44  fourcc:0x31637661  tamaño:1280x720  fps:29.970  ftime:=0.0334
get_path('sub/') -> '/home/qq/.mplayer/sub/'
X11 opening display: :0.0
vo: X11 color mask:  FFFF  (R:F800 G:7E0 B:1F)
vo: X11 running at 1680x1050 with depth 16 and 16 bpp (":0.0" => local display)
[x11] Detected wm supports NetWM.
[x11] Detected wm supports FULLSCREEN state.
[x11] Detected wm supports ABOVE state.
[x11] Detected wm supports BELOW state.
[x11] Current fstype setting honours FULLSCREEN ABOVE BELOW X atoms
[VO_XV] Using Xv Adapter #0 (NV17 Video Overlay)
[xv common] Drawing colorkey manually.
[xv common] Using colorkey from Xv (0x00083e).
[xv common] Maximum source image dimensions: 2046x2046
...
VO: [xv] 1280x720 => 1280x720 Planar YV12  [fs]
VO: Description: X11/Xv
VO: Author: Gerd Knorr <kraxel@goldbach.in-berlin.de> and others
Xvideo image format: 0x32595559 (YUY2) packed
Xvideo image format: 0x32315659 (YV12) planar
Xvideo image format: 0x59565955 (UYVY) packed
Xvideo image format: 0x30323449 (I420) planar
using Xvideo port 173 for hw scaling
[vo-fs] dx: 0 dy: 52 dw: 1680 dh: 946
[xv] dx: 0 dy: 52 dw: 1680 dh: 946
*** [vo] Exporting mp_image_t, 1280x720x12bpp YUV planar, 1382400 bytes
==========================================================================
Without weird lines:
Code:
==========================================================================
LAVF: 1 audio and 1 video streams found
LAVF: build 3414272
VIDEO:  [avc1]  1280x720  24bpp  29.970 fps    0.0 kbps ( 0.0 kbyte/s)
[V] filefmt:44  fourcc:0x31637661  tamaño:1280x720  fps:29.970  ftime:=0.0334
get_path('sub/') -> '/home/qq/.mplayer/sub/'
X11 opening display: :0.0
vo: X11 color mask:  FFFF  (R:F800 G:7E0 B:1F)
vo: X11 running at 1680x1050 with depth 16 and 16 bpp (":0.0" => local display)
[x11] Detected wm supports NetWM.
[x11] Detected wm supports FULLSCREEN state.
[x11] Detected wm supports ABOVE state.
[x11] Detected wm supports BELOW state.
[x11] Current fstype setting honours FULLSCREEN ABOVE BELOW X atoms
[VO_XV] No se ha podido fijar el puerto 173.
[VO_XV] Using Xv Adapter #1 (NV17 Video Texture)
[xv common] Drawing no colorkey.
[xv common] Maximum source image dimensions: 2046x2046
==========================================================================
Abriendo decodificador de video: [ffmpeg] FFmpeg's libavcodec codec family.
INFO: libavcodec init OK!
Video codec seleccionado: [ffh264] vfm: ffmpeg (FFmpeg H.264)
...
VO Config (1280x720->1280x720,flags=1,'MPlayer',0x32315659)
VO: [xv] 1280x720 => 1280x720 Planar YV12  [fs]
VO: Description: X11/Xv
VO: Author: Gerd Knorr <kraxel@goldbach.in-berlin.de> and others
Xvideo image format: 0x32595559 (YUY2) packed
Xvideo image format: 0x32315659 (YV12) planar
Xvideo image format: 0x59565955 (UYVY) packed
Xvideo image format: 0x30323449 (I420) planar
using Xvideo port 174 for hw scaling
[vo-fs] dx: 0 dy: 52 dw: 1680 dh: 946
[xv] dx: 0 dy: 52 dw: 1680 dh: 946
*** [vo] Exporting mp_image_t, 1280x720x12bpp YUV planar, 1382400 bytes
==========================================================================
Solution:
Code:
mplayer -vo xv:port=174
If I dont remember bad I tried the same in the past ( trying all xv devices xD) but without results, probably I made an error typing the code..

Regards.

PS: The sharpness of the VGA output is very poor compared to DVI one, but it is normal I think xD
djalma is offline   Reply With Quote
Old 06-02-09, 09:31 AM   #50
ghost_zero5
Registered User
 
Join Date: May 2009
Posts: 39
Default Re: Tearing, Tearing and again TEARING!!

You have a NV17 Video Overlay too?
I only have the NV17 Video Texture


@Stephen:
Will this tearing problem be fixed soon (best would be one of the next driver releases)?
I am asking because this bug is really annoying.
ghost_zero5 is offline   Reply With Quote
Old 06-02-09, 09:13 PM   #51
jyavenard
MythTV developer
 
Join Date: Mar 2006
Posts: 413
Default Re: Tearing, Tearing and again TEARING!!

Well, I can report that tearing still occur when composite is enabled in 185.18.14.
Not always but it can happen. Using MythTV for playback here

With Composite disabled no tearing can ever be seen.
jyavenard is offline   Reply With Quote
Old 07-25-09, 10:01 AM   #52
ghost_zero5
Registered User
 
Join Date: May 2009
Posts: 39
Default Re: Tearing, Tearing and again TEARING!!

I still have the same problem with 190.18
I really would appreciate it, if someone is finally going to fix this problem.
ghost_zero5 is offline   Reply With Quote
Old 08-01-09, 05:01 PM   #53
VanessaE
Registered User
 
Join Date: May 2008
Posts: 9
Angry Re: Tearing, Tearing and again TEARING!!

This problem affects me as well, perhaps more severely than what I've seen described by others.

I use XFCE 4.6.0 under Ubuntu 9.04, no special effects, no compiz, none of that fancy stuff. Just XFCE's compositing manager. My video card is an Apollo-made GF6800, driving a fairly non-descript pair of Dell panels. I am using kernel 2.6.28.5 with the 190.18 driver from the official nVidia distribution pages.

This tearing issue persists no matter what I do. I have literally tried everything within my abilities to find a fix, and have failed.

* It doesn't matter that the Vertical Sync and Page Flipping switches are turned on (they are, currently).
* It doesn't matter what desktop environment I use.
* It doesn't matter what driver version I use.
* It doesn't matter what movie player I use.
* It doesn't matter what output method the player uses (OpenGL, X11, Xv).
* It doesn't matter whether the composite extension is loaded.
* It doesn't matter whether my CPU is idle or heavily loaded.
* It doesn't matter whether the window is maximized, full screen, or normal size.
* It doesn't matter what resolution the original video is.
* It doesn't matter what screen resolution or refresh rate my monitors are set for, though it does affect the artifacts somewhat.
* It doesn't matter how many various options I try to use in my xorg.conf.
* It doesn't matter *which* screen the video plays on - both screens exhibit the tearing effect no matter which one the card is set to sync with.

Only one action fixes the problem for me: I must disable Twinview, which is unacceptable, as the alternatives (xinerama, separate screens, or reverting to just one monitor) all have worse problems than video tearing.

Please, this has been going on for 2+ years, over multiple driver strains and versions. Many of us have owned nVidia devices for years, and we've all spent our hard earned money on those devices. We expect them to work properly at all times. Don't push us toward your competitors.


Edit (multiple) - fixed grammar/logic errors and missed details.
VanessaE is offline   Reply With Quote
Old 08-24-09, 04:35 PM   #54
ghost_zero5
Registered User
 
Join Date: May 2009
Posts: 39
Default Re: Tearing, Tearing and again TEARING!!

I have now tested the new 190.25 and the problem still exists. It seems to have improved though as for some scenes where I previously nearly always had tearing I have to rewatch them sometimes now to get tearing BUT it is still there.

WHEN will this be FIXED? Or at least a working workaround would be nice...
ghost_zero5 is offline   Reply With Quote
Old 08-25-09, 07:22 AM   #55
psychok9
Registered User
 
Join Date: Dec 2008
Posts: 55
Default Re: Tearing, Tearing and again TEARING!!

I don't have tearing anymore with all vsync options enabled, nvidia-settings -l at start and using only one monitor at the time + VDPAU.
I don't change refresh setup, for both LCD i leave "auto".
190.18 from PPA repository.
Last flash and Linux Mint/Jaunty x86/32bit.
psychok9 is offline   Reply With Quote
Old 08-25-09, 04:20 PM   #56
ghost_zero5
Registered User
 
Join Date: May 2009
Posts: 39
Default Re: Tearing, Tearing and again TEARING!!

It depends also on the videos. On some I would never get tearing in the first place but some I get it. I really would look a working solution.
However, I haven't tried VDPAU yet BUT actually, for VDPAU all Vsync options in the nvidia-settings should be senseless as there are only one for OpenGL and Xvideo and none for VDPAU.

Btw. to make sure: Where exactly did you add the nvidia-settings -l option?
Did you do it in Ubuntu over System-->Settings-->Start Programs?
Or did you so it somewhere else (actually, I think it was already added by the driver though)?

Btw. you have activated Compiz, don't you? Have you activated Compiz Vsync option or disabled that one? You probably have it active because without that one I have extremely much tearing.

Also have you activated "Unredirect Fullscreen"? If so, then once you go Fullscreen and the controls aren't displayed but only the video it is "normal" (I also don't get it then) to get a none tearing video as for Fullscreen Compiz isn't "used" then.

EDIT: Now tested VDPAU and that one also gives tearing. Actually, I think it is even a bit more than with just XVideo.
ghost_zero5 is offline   Reply With Quote

Old 08-25-09, 11:43 PM   #57
Stephen Warren
Moderator
 
Stephen Warren's Avatar
 
Join Date: Aug 2005
Posts: 1,327
Default Re: Tearing, Tearing and again TEARING!!

ghost_zero5, There's nothing that can be done about tearing when compiz is active, due to the way the X composite extension is designed. Fixing this would require redesigning/enhancing the X composite protocol.
Stephen Warren is offline   Reply With Quote
Old 08-26-09, 04:43 AM   #58
ghost_zero5
Registered User
 
Join Date: May 2009
Posts: 39
Default Re: Tearing, Tearing and again TEARING!!

But could this bug be fixed by Compiz?
Actually, I also wonder. Is there no possibility to let all XVideo output NOT go through compiz/X composite but directly?
Futhermore, I think it is kinda stupid that no one thought about VSync/Tearing when designing the X composite.

Also why is the refresh rate reported wrongly by xrandr when DynamicTwinView is enabled?
ghost_zero5 is offline   Reply With Quote
Old 08-26-09, 05:49 AM   #59
NvFuchs
Registered Fox
 
NvFuchs's Avatar
 
Join Date: Oct 2007
Location: Confoederatio Helvetica
Posts: 530
Default Re: Tearing, Tearing and again TEARING!!

Quote:
Originally Posted by ghost_zero5 View Post
Also why is the refresh rate reported wrongly by xrandr when DynamicTwinView is enabled?
Because it is (ab)used as unique identifier for each mode, as described multiple times in this forum.

Kind regards

Fuchs
NvFuchs is offline   Reply With Quote
Old 09-02-09, 01:48 PM   #60
ghost_zero5
Registered User
 
Join Date: May 2009
Posts: 39
Default Re: Tearing, Tearing and again TEARING!!

Quote:
Originally Posted by Stephen Warren View Post
ghost_zero5, There's nothing that can be done about tearing when compiz is active, due to the way the X composite extension is designed. Fixing this would require redesigning/enhancing the X composite protocol.
According to a PM with a Compiz developer it is actually a problem with the driver (a workaround would be possible but as it is an issue with the driver, it should be fixed there) because:
Quote:
These VSync issues are driver issues where there is no way to switch from one buffer to another directly and easily.
ghost_zero5 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 11:35 PM.


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