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. |
6th June 2013, 05:27 | #19041 | Link |
Registered User
Join Date: Nov 2009
Posts: 327
|
It seems the new release of madVR tries to be too helpful and treats videos larger than 1080p as Rec.2020, leading to some pretty hilarious blown-out colors. Given that the little 4K content that's out there (YouTube stuff) and any 4K content to be launched in the near future will be Rec.709, I think autodetection for 2020 should be removed or at least an option be given to disable it.
|
6th June 2013, 10:51 | #19042 | Link |
Registered User
Join Date: Mar 2002
Posts: 2,323
|
Guys, which Windows version do you recommend for only mpc-hc + lav + madvr playback? W7 or W8 ?
Pros vs cons? Thanks!
__________________
Ryzen 5 2600,Asus Prime b450-Plus,16GB,MSI GTX 1060 Gaming X 6GB(v398.18),Win10 LTSC 1809,MPC-BEx64+LAV+MadVR,Yamaha RX-A870,LG OLED77G2(2160p@23/24/25/29/30/50/59/60Hz) | madvr config |
6th June 2013, 11:30 | #19043 | Link | ||||||||||||||||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
That said, some people prefer yadif deinterlacing quality over DXVA deinterlacing quality (the latter of which is used by madVR at the moment). So for sports and music concerts you could try whether you like LAV's yadif implementation better, if you feel like playing around with the options... Quote:
They are disabled by default. Quote:
Quote:
Quote:
Do you have madVR's smooth motion FRC on or off? (I'm not asking you to turn it on or off, just asking how you have configured it at the moment). Quote:
The key reason why I'm asking the yuvMatrix for every frame is that the user might have switched subtitle tracks. Or maybe the user is playing linked MKV files. In both situations the yuvMatrix might suddenly change. Asking the yuvMatrix for every frame shouldn't harm, as long as XySubFilter replies without delay. Quote:
There rarely is such a thing as one DirectShow filter (or one software component) being completely stuck. Things like that happen on a thread-by-thread basis. It seems that calls into XySubFilter made by madVR from the context of madVR's subtitle thread work fine without stalling. However, the calls into XySubFilter made by madVR from the context of madVR's rendering thread seem to be stuck inside of XySubFilter. This is a very typical behaviour when something goes wrong with thread protection (inside of XySubFilter). (Again, I'm not 100% sure, this is just my best guess based on what I'm seeing in the log.) Quote:
Quote:
Quote:
Quote:
Win8 has a bug with setting correct refresh rates, but I've found a workaround in the latest madVR version. As a result I personally see no big difference between win7 and win8 for video playback, anymore. Just pick which you like better for other reasons... |
||||||||||||||||
6th June 2013, 12:07 | #19044 | Link | |
Registered User
Join Date: Jul 2005
Posts: 359
|
Quote:
I finally reported this to the bug tracker. I see you've attempted to fix Ryrynz and I's issue but could not re-produce it on your Windows 8 machine. Well as I report in my bug report, it's possibly a windows 7 + HD 4000 + 9.18.10.3071 (or later) issue. I have an HD 4000 on my laptop running windows 8 and it's fine using the same driver. My desktop running Win7 64-bit SP1, however, is not. I even tried the newer driver package (15.31.9.64.3165) and I have the same issue. Still have to revert back to 9.17.10.2932. edit: I see it's a driver bug. I saw you and Ryrynz talking about it, but I thought you were talking about something else. Last edited by rahzel; 6th June 2013 at 14:39. |
|
6th June 2013, 15:13 | #19045 | Link | |
Registered User
Join Date: Jun 2005
Posts: 365
|
Quote:
LAV decoders are virtually the same used by FFDShow, right? |
|
6th June 2013, 15:17 | #19046 | Link | |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
|
|
6th June 2013, 15:46 | #19047 | Link | |
Registered User
Join Date: Jun 2005
Posts: 365
|
Quote:
Thanks, man. |
|
6th June 2013, 15:48 | #19048 | Link |
Registered User
Join Date: Oct 2011
Posts: 52
|
i'm not entirely sure if XySubFilter or MadVR is at fault here, but subtitles seem to be rendered in full/PC range.
http://www.check2pic.ru/compare/29611/ ASS script is tagged as TV.601. Tested on: madVR 0.86.2 XySubFilter .425 |
6th June 2013, 16:00 | #19049 | Link | |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
@zero9999, can you please create an issue in the madVR bug tracker and upload a small video sample? Thanks... |
|
6th June 2013, 17:12 | #19050 | Link | |
Registered User
Join Date: Oct 2011
Posts: 52
|
Quote:
Bug and samples submitted. Should i also create a feature request for rendering subtitles on screenshots taken with madvr or is that part just not done, yet? |
|
6th June 2013, 21:50 | #19053 | Link | |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Can those guys who were seeing ghosting problems with madVR's FRC please recheck with v0.86.2? Maybe they're gone now, too? |
|
6th June 2013, 23:08 | #19055 | Link | ||
Registered User
Join Date: Oct 2011
Posts: 52
|
Quote:
however, LAV video decoder seems to behave correctly, so enabling Cinepak in LAV fixes this. Quote:
xy-vsfilter renders the subtitles directly on the video before it even gets to madvr, so no further steps are necessary to get the subs to display on screenshots in that case. Last edited by zero9999; 6th June 2013 at 23:11. |
||
7th June 2013, 00:33 | #19056 | Link |
Registered User
Join Date: Jan 2009
Posts: 1,210
|
I spoke too soon about the repeating frame bug. Still happens in the same situation. The easiest way to replicate the issue is by rapidly pressing the right (or left?) arrow.
Last edited by dansrfe; 7th June 2013 at 01:34. |
7th June 2013, 01:15 | #19057 | Link | |
Broadband Junkie
Join Date: Oct 2005
Posts: 1,859
|
Quote:
@zero9999 As a workaround, you can force madVR GPU-based subtitle color correction to always be used by setting: HKEY_CURRENT_USER\Software\Gabest\xy_sub_filter\General\ RGB_CORRECTION = never Accepted RGB_CORRECTION values are auto , always and never . By default, auto performs internal color correction only with TV.601 (subs) on TV.709 (video) and lets madVR handle other combinations. The advantage of XySubFilter's internal color correction is that its faster, since we can do it prior to bitmap rasterization without any additional GPU overhead in madVR. This is why it was made the default for the most common correction. Last edited by cyberbeing; 7th June 2013 at 01:58. |
|
7th June 2013, 01:40 | #19058 | Link | |
Registered User
Join Date: Mar 2010
Posts: 14
|
Quote:
Smooth Motion is off. |
|
7th June 2013, 07:28 | #19059 | Link | |||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
P.S: If it only occurs in FSE mode then it might already be fixed in v0.86.3. If it also occurs in other modes then this will probably not be fixed by v0.86.3 as of right now. Quote:
Quote:
|
|||
7th June 2013, 08:10 | #19060 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Hmmmm... It was faster with v0.86.2, but only because madVR didn't apply subtitles in the correct PC/TV levels, when XySubFilter did the color correction. Now that I've added the fix for the incorrect levels, doing color correction inside of madVR does not cost any extra performance compared to when not doing it. Basically subtitle color correction in madVR comes for "free". Or more correctly: It doesn't come for free, but the cost is hidden because I have to do extra processing to apply the subtitles in the correct levels, anyway, and doing color correction in addition to doing levels adjustments simply doesn't cost any extra performance...
|
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
Thread Tools | Search this Thread |
Display Modes | |
|
|