Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion.

Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules.

 

Go Back   Doom9's Forum > Hardware & Software > Software players

Reply
 
Thread Tools Search this Thread Display Modes
Old 1st October 2015, 20:21   #33281  |  Link
Marnes
Registered User
 
Marnes's Avatar
 
Join Date: Jun 2015
Posts: 11
Is there anything in madvr about tearing that I'm possibly missing (which is to say I don't see anything in madvr's settings about vsync)? My config or something else apparently still isn't good because now I constantly get random tearing all the time despite every setting everywhere being set to use vsync. Potplayer is set to vsync, intel and nvidia (which sadly doesn't get used because yay laptop monitor wiring...) are set to vsync, etc. I used madvr a while ago on 7 and 8 and everything just worked, now on 10 with the latest madvr nothing at all just works...
Marnes is offline   Reply With Quote
Old 1st October 2015, 20:34   #33282  |  Link
Marnes
Registered User
 
Marnes's Avatar
 
Join Date: Jun 2015
Posts: 11
Quote:
Originally Posted by Marnes View Post
Is there anything in madvr about tearing that I'm possibly missing (which is to say I don't see anything in madvr's settings about vsync)? My config or something else apparently still isn't good because now I constantly get random tearing all the time despite every setting everywhere being set to use vsync. Potplayer is set to vsync, intel and nvidia (which sadly doesn't get used because yay laptop monitor wiring...) are set to vsync, etc. I used madvr a while ago on 7 and 8 and everything just worked, now on 10 with the latest madvr nothing at all just works...
Why the heck does turning off "delay playback until render queue is full" seem to fix tearing... The way the option is described suggests it's a kind of render buffer exactly to prevent such things...
Marnes is offline   Reply With Quote
Old 1st October 2015, 20:36   #33283  |  Link
aufkrawall
Registered User
 
Join Date: Dec 2011
Posts: 1,812
When you have tearing problems, it's likely not the fault of madVR.
Since Windows Vista, tearing shouldn't even be possible with GPU desktop composition, which can't be turned off anymore since Windows 8. So it's very likely a weird driver or configuration problem.
Maybe you have to use FSE.
aufkrawall is offline   Reply With Quote
Old 2nd October 2015, 07:42   #33284  |  Link
ShadyCrab
Registered User
 
Join Date: Jul 2015
Posts: 16
Just want to report spontaneous tearing issues as well. Win 10, GTX 960, newest NVidia driver. DX11 presentation (present every V-Sync ticked), only occurs in Fullscreen Windowed. Also newest MPC-HC nightly build. Its always fixed by simply changing the window size. It can occur less often in the middle of playback, more often when resuming playback.

This might somehow be related to having a multi-monitor setup, both by HDMI at 1080p. There doesn't seem to be anything I can do to 100% prevent tearing except for Fullscreen Exclusive. This isn't something I remember occurring before the time of, say the Win 10 RTM launch.
ShadyCrab is offline   Reply With Quote
Old 2nd October 2015, 14:21   #33285  |  Link
aufkrawall
Registered User
 
Join Date: Dec 2011
Posts: 1,812
Yes, this is already known. Use FSE with D3D11 or use D3D9 instead (not a disadvantage at all without FSE).
It's most likely an NV driver bug with Windows 10.

Last edited by aufkrawall; 2nd October 2015 at 14:24.
aufkrawall is offline   Reply With Quote
Old 2nd October 2015, 18:15   #33286  |  Link
panetesan2k6
Registered User
 
Join Date: Jan 2014
Location: Latveria
Posts: 29
I was giving a try to a 64bit setup of MPC-HC+MadVR+LAV filters. I have a 64bit OS, of course.

I downloaded and installed the 64bit version of MPC-HC and LAV filters (32bit version is installed too), and MadVR was already installed in the system.

Neither MadVR nor LAV filters show any distinctive info about being 32 or 64 bit during playback. I would think that 64bit MPC-HC will load 64 bit components, but... anyway to check this?
panetesan2k6 is offline   Reply With Quote
Old 2nd October 2015, 18:30   #33287  |  Link
Telion
Registered User
 
Join Date: Sep 2011
Posts: 78
No need to check, 64bit player just can't use 32bit filters and vice versa.
Telion is offline   Reply With Quote
Old 2nd October 2015, 18:31   #33288  |  Link
Kranium
I'm Confused
 
Kranium's Avatar
 
Join Date: Aug 2015
Posts: 11
I upgraded to 89.5 and 0.66 LAV last night and was playing around with some options.

In animated content, I notice that if I use the SuperRes filter in Chroma Upscaling and use SuperRes in upscaling refinement; I get a bit of ringing and lines that are not smooth and are over sharpened. It doesn't get all that much better when I reduce the strength or increase the number of passes. Does this seem like normal behavior? I eventually settled on SuperRes in upscaling refinement and adaptive sharpen in the image enhancements section. Without adaptive sharpen, the lines seemed to fade in 480p > 1080p scaling. It gave me the best results to my eyes at least. All of this with NNEDI64 scaling and doubling.

I know there are a lot of other factors here, I was more curious if one SuperRes option is more useful than the other and if others here have experienced what I did when using both at the same time.
__________________
HTPC/NAS: i7-4770 - GTX970 - 16GB RAM - 512GB SSD RAID 0 - 16TB HDD - mITX
Kranium is offline   Reply With Quote
Old 2nd October 2015, 19:45   #33289  |  Link
panetesan2k6
Registered User
 
Join Date: Jan 2014
Location: Latveria
Posts: 29
Quote:
Originally Posted by Telion View Post
No need to check, 64bit player just can't use 32bit filters and vice versa.
Thanks
panetesan2k6 is offline   Reply With Quote
Old 3rd October 2015, 00:48   #33290  |  Link
6ari8
Registered User
 
Join Date: Jun 2012
Posts: 43
When playing some files the OSD shows this:


When most of the time it shows:
Chroma>xxx
Image>xxx

Can some one explain why this happens?
6ari8 is offline   Reply With Quote
Old 3rd October 2015, 01:19   #33291  |  Link
seiyafan
Registered User
 
Join Date: Feb 2014
Posts: 162
I was out of the loop with all the fancy new upscaling algos, has there been any noticeable improvement for 1080 to 1440? Last time when I compared Jinc with NNEDI3 I could hardly tell a difference.
seiyafan is offline   Reply With Quote
Old 3rd October 2015, 02:14   #33292  |  Link
aufkrawall
Registered User
 
Join Date: Dec 2011
Posts: 1,812
Quote:
Originally Posted by 6ari8 View Post
When playing some files the OSD shows this:


When most of the time it shows:
Chroma>xxx
Image>xxx

Can some one explain why this happens?
Well, it doesn't show super-xbr in the latter example, does it?
If it doesn't, it's normal. When super-xbr is used for luma, it is always also used for scaling up chroma together.

Quote:
Originally Posted by seiyafan View Post
I was out of the loop with all the fancy new upscaling algos, has there been any noticeable improvement for 1080 to 1440? Last time when I compared Jinc with NNEDI3 I could hardly tell a difference.
Because there hardly is a difference with this scaling factor.
You can try SuperRes (e.g. strength of 2) + Adaptive Sharpen (after SuperRes, e.g. strength of 0.2).
However, AS will make some images noticeably brighter, even with strength of 0.2.
For this reason, I'd appreciate if madshi implemented also Shiandow's sharper SuperRes configuration, e.g. replace the radius checkbox with it.
aufkrawall is offline   Reply With Quote
Old 3rd October 2015, 03:20   #33293  |  Link
6ari8
Registered User
 
Join Date: Jun 2012
Posts: 43
Quote:
Originally Posted by aufkrawall View Post
Well, it doesn't show super-xbr in the latter example, does it?
If it doesn't, it's normal. When super-xbr is used for luma, it is always also used for scaling up chroma together.
Sorry I just found out that something changed with 89.05's OSD so that anything that has image doubling active seperates image to Luma and Chroma for some reason. It used to be like this before:


I'm still not sure If I'm understanding it correctly so I need some help with those lines. Given that this video is 712x480 those lines do the following:
1) Double the chroma from 356x240 to 712x480.
2) Double the Luma from 712x480 to 1424x960 then double again to 2848x1920 then downscale with Catmull-Rom AR to 1920x1080.
3) Double the chroma from 712x480 to 1424x960 then double again to 2848x1920.

Is this correct? Doesn't this mean that the end result has different chroma and luma resolutions?
6ari8 is offline   Reply With Quote
Old 3rd October 2015, 03:34   #33294  |  Link
panetesan2k6
Registered User
 
Join Date: Jan 2014
Location: Latveria
Posts: 29
Just a suggestion for Madshi.

Would it be possible to add OSD On/off to the pop-up menu from the system tray icon?
panetesan2k6 is offline   Reply With Quote
Old 3rd October 2015, 04:00   #33295  |  Link
XRyche
Registered User
 
Join Date: May 2008
Posts: 211
Quote:
Originally Posted by 6ari8 View Post
Sorry I just found out that something changed with 89.05's OSD so that anything that has image doubling active seperates image to Luma and Chroma for some reason. It used to be like this before:


I'm still not sure If I'm understanding it correctly so I need some help with those lines. Given that this video is 712x480 those lines do the following:
1) Double the chroma from 356x240 to 712x480.
2) Double the Luma from 712x480 to 1424x960 then double again to 2848x1920 then downscale with Catmull-Rom AR to 1920x1080.
3) Double the chroma from 712x480 to 1424x960 then double again to 2848x1920.

Is this correct? Doesn't this mean that the end result has different chroma and luma resolutions?
The first chroma entry is for chroma upsampling from 4:2:0 to 4:4:4. The second chroma entry is for chroma upscaling for matching the chroma to the luma upscaled resolution. I believe that's correct but if not fell free to correct me anyone.
__________________
Intel i5 3470, EVGA GTX 1050Ti SC ACX 2.0, Windows 10 Pro 64 bit, 16 GB 1600 mhz DDR3 RAM
XRyche is offline   Reply With Quote
Old 3rd October 2015, 05:59   #33296  |  Link
ryrynz
Registered User
 
ryrynz's Avatar
 
Join Date: Mar 2009
Posts: 3,646
Quote:
Originally Posted by XRyche View Post
The first chroma entry is for chroma upsampling from 4:2:0 to 4:4:4. The second chroma entry is for chroma upscaling for matching the chroma to the luma upscaled resolution. I believe that's correct but if not fell free to correct me anyone.
That would be right, but you've linked the wrong post to reply to. The previous post from him shows the double chroma OSD lines.

Quote:
Originally Posted by 6ari8 View Post
I'm still not sure If I'm understanding it correctly
That's because madVR isn't displaying the quad superxbr scaling that happens automatically alongside the luma scaling.

Quote:
Originally Posted by 6ari8 View Post
Doesn't this mean that the end result has different chroma and luma resolutions?
It has to match before it gets displayed.

Last edited by ryrynz; 3rd October 2015 at 06:14.
ryrynz is offline   Reply With Quote
Old 3rd October 2015, 07:18   #33297  |  Link
rbej
Registered User
 
Join Date: Sep 2015
Posts: 18
Quote:
Originally Posted by clsid View Post
"image < DXVA" means image downscaled using DXVA. It does not show that in fullscreen because then no scaling is needed (if you have 1920px screen width).
Of course, but why without DXVA downscaling playback is poor like hell??. Downscaling is process who use % CPU and GPU. Without downscaling playback should be more smooth.
rbej is offline   Reply With Quote
Old 3rd October 2015, 07:55   #33298  |  Link
huhn
Registered User
 
Join Date: Oct 2012
Posts: 7,903
what GPU are you using?

there is a small chance that dithering is to hard.

CPU is not used for this what so ever.
huhn is offline   Reply With Quote
Old 3rd October 2015, 08:16   #33299  |  Link
nevcairiel
Registered Developer
 
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,344
Quote:
Originally Posted by 6ari8 View Post
I'm still not sure If I'm understanding it correctly so I need some help with those lines. Given that this video is 712x480 those lines do the following:
1) Double the chroma from 356x240 to 712x480.
2) Double the Luma from 712x480 to 1424x960 then double again to 2848x1920 then downscale with Catmull-Rom AR to 1920x1080.
3) Double the chroma from 712x480 to 1424x960 then double again to 2848x1920.

Is this correct? Doesn't this mean that the end result has different chroma and luma resolutions?
If it says "Image" in the OSD, it refers to scaling both Luma and Chroma at the same time (otherwise it would say Luma)
So what it really does is only 2 steps

1) Double Chroma to 712x480, now matches Luma
2) Double the entire image twice (both Luma and Chroma) to 2848x1920, then downscale both components to 1920x1080
__________________
LAV Filters - open source ffmpeg based media splitter and decoders
nevcairiel is offline   Reply With Quote
Old 3rd October 2015, 09:41   #33300  |  Link
rbej
Registered User
 
Join Date: Sep 2015
Posts: 18
Quote:
Originally Posted by huhn View Post
what GPU are you using?

there is a small chance that dithering is to hard.

CPU is not used for this what so ever.
Pentium N3700 Braswell (hevc hardware decoding). When i use EVR everything is ok and playback (1080p 60fps files) is very smooth on full screen (1080p monitor). madVR - DXVA Scaling On (window) = perfect smooth playback. DXVA Scaling Off (full screen) = poor playback.

Last edited by rbej; 3rd October 2015 at 09:46.
rbej is offline   Reply With Quote
Reply

Tags
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

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 +1. The time now is 22:07.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.