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. |
4th June 2011, 16:55 | #7861 | Link | |
Registered User
Join Date: Jan 2010
Posts: 297
|
Quote:
__________________
Windows 7 x64 i7 870 16GB RAM AMD 6870 |
|
5th June 2011, 03:58 | #7862 | Link |
Registered User
Join Date: Oct 2009
Posts: 91
|
I have a issue with MadVR and video levels. Setting MadVR to output 0-255 (and using custom Nvidia resolution) I get black crush in exclusive full screen mode. In windowed mode video levels are correct. Disabled exclusive fullscreen mode and video levels match between fullscreen and windowed mode.
MadVR .61 LavCUVID .7 LAV Splitter/Audio .28 MPC-HC .3018 What do I lose not using exclusive? Looks like I get tearing.. Regardless, it would seem my problem is due to Nvidia and a using a DVI - HDMI cable. On the straight HDMI to projector, I don't have the video level issue. Using custom resolutions also effect the issue. Oh well.
__________________
nvidia gts 450 (270.61), Asus P7H55-M Pro MB, Denon 988 AVR MPC-HC v.3456: filters: LAV Audio/CUVID/Splitter .35, MadVR .73 Last edited by nightfly; 5th June 2011 at 08:16. |
5th June 2011, 04:10 | #7863 | Link | |
Registered User
Join Date: Jan 2007
Posts: 729
|
Quote:
Naturaly, real 16bit colorspaces in avisynth would be better, but avisynth developers are busy enough and the development is slow already - 2.6 still isn't done after several years. So... real 16bit needs rewrite of filters AND avisynth, this hack only needs rewrite of filters. Some of them are already available, and as long as plugin authors are willing, it can take off, because no messing with avisynth core is needed. (And modifying those plugins for non-hacky core 16bit probably won't be hard one day). Imho, for an "ugly hack", this has a beauty of its own. |
|
5th June 2011, 08:46 | #7864 | Link | |
Registered User
Join Date: Jan 2008
Posts: 589
|
Quote:
|
|
5th June 2011, 10:44 | #7865 | Link | |
Registered User
Join Date: Apr 2011
Posts: 1
|
Quote:
Try to change the “Content type reported to the display” on the “NVidia Control Panel” -> “Adjust Desktop Color Settings” -> ” Content type reported to the display” -> “Full-screen videos” |
|
5th June 2011, 12:43 | #7866 | Link | |
Kid for Today
Join Date: Aug 2004
Posts: 3,477
|
Quote:
And that'd feed 10bit displays as well, whatever you'd need: sharpening, deinterlacing, etc etc. Minimal quality loss is the key, and I can't think of a better host than mVR for this. Hope it'll be considered Quite frankly, the latest build of SmoothAdjust() looks pretty darn amazing(it does stunning TV>PC conversions too): http://forum.doom9.org/showpost.php?...&postcount=234 |
|
5th June 2011, 13:24 | #7867 | Link | |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,348
|
Quote:
madVR already supports 16-bit input. If you want this to work, you should teach ffdshow to convert the "hack" into proper 16-bit on output (after its done with avisynth). Keep the hack inside ffdshow, if you must, but having a "hacked" pixel format go out of ffdshow would be *terrible*. Should also not be that hard to transform it into a proper 16-bit pixel format on output, and madVR wouldnt even need changes.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders Last edited by nevcairiel; 5th June 2011 at 13:27. |
|
5th June 2011, 13:43 | #7869 | Link | |
Registered User
Join Date: Apr 2002
Location: Germany
Posts: 4,926
|
Quote:
__________________
all my compares are riddles so please try to decipher them yourselves :) It is about Time Join the Revolution NOW before it is to Late ! http://forum.doom9.org/showthread.php?t=168004 Last edited by CruNcher; 5th June 2011 at 13:51. |
|
5th June 2011, 13:47 | #7870 | Link | |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,348
|
Quote:
All i'm saying is that madVR already supports 16-bit input, and since ffdshow needs changes anyway, just make it output the 16-bit in a "standard" format, that makes it easier on everyone. Its not like ffdshow can already do this and just madVR needs changes.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
|
5th June 2011, 15:13 | #7871 | Link |
Kid for Today
Join Date: Aug 2004
Posts: 3,477
|
Quite simple: provide more levels to play around w/ to Avisynth scripts. LSF and GrainF3 look noticeably better when working on PC than on TV range...and I use PC range displays anyway, so there's no point in clipping my post-processing to TV when it'll expanded to PC afterwards. But this is OT, I was merely asking for madshi's opinion on this hack...as we've all be complaining about processing 16int audio and 8bit video. Can you feel the wind of change?
SmoothLevels() uses a different dithering algorithm from mVR, I find that they look amazing together in combo on a CRT, and I already posted comparisons a while back(the 2.0 beta has been a huge improvement as well). Ppl w/ 6bit dithered LCD displays hated it(TN panels and so), but don't shoot the messenger Last edited by leeperry; 5th June 2011 at 15:23. |
5th June 2011, 17:23 | #7873 | Link | |||||||||||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Quote:
Quote:
That log was from your Radeon, right? Quote:
Quote:
Quote:
Quote:
Quote:
I don't know in what way Reclock has a problem with madVR's display mode switching, but I don't think there's much I can do about it. I would rather guess it's a problem with Reclock. But I don't know for sure. Quote:
Of course you should aim to get the best possible frame rate / refresh rate match. Which means that if the file is 29.970fps then you should try getting your display to do 59.940Hz instead of 60.000Hz. Quote:
Quote:
|
|||||||||||
5th June 2011, 17:28 | #7874 | Link | |||||||||||||||||||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
I've double checked that Lanczos image on that website and found that it was produced with a broken Lanczos implementation. A proper Lanczos implementation (like the one in madVR) easily beats that "Magic Kernel", IMHO. Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
No problem at all. Just find someone who makes ffdshow accept that hacked YV16/24 data from avisynth and convert it to a proper 16bit format. That solution would work right away with the next madVR version. I don't really feel like supporting a hacked data format in madVR. And honestly, I see no benefit of doing that. ffdshow does not output YV16/24 now, so you need to find someone to improve ffdshow, anyway. Instead of making your buddy add YV16/24 output support to ffdshow, make him convert the hacked YV16/24 data to a proper 16bit FourCC format. This should be *really* easy to do and then we'd have a proper ffdshow version with a proper and documented 16bit output, which would work perfectly fine with the next madVR version. |
|||||||||||||||||||
5th June 2011, 17:43 | #7875 | Link |
Registered User
Join Date: May 2004
Posts: 5,351
|
madshi, are there any commercial decoders out there that support proper 16bit FourCC that will work with the next version of madVR?
__________________
HTPC: Windows 11, AMD 5900X, RTX 3080, Pioneer Elite VSX-LX303, LG G2 77" OLED |
5th June 2011, 17:51 | #7876 | Link |
Registered User
Join Date: Sep 2006
Posts: 2,197
|
that would be awesome, because im also stuck at 60Hz displays.
__________________
Laptop Lenovo Legion 5 17IMH05: i5-10300H, 16 GB Ram, NVIDIA GTX 1650 Ti (+ Intel UHD 630), Windows 10 x64, madVR (x64), MPC-HC (x64), LAV Filter (x64), XySubfilter (x64) (K-lite codec pack) |
5th June 2011, 17:52 | #7877 | Link | |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
http://forum.doom9.org/showthread.php?t=158836 Anyway, I don't like the Hen and Egg problem, so madVR comes first with full 10bit and 16bit support and with 4:2:0, 4:2:2 and 4:4:4 support. Hopefully decoders will follow. But of course for decoders it makes sense only if the encoded video stream is really native > 8bit or > 4:2:0. |
|
5th June 2011, 18:05 | #7878 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
madVR v0.62 released
http://madshi.net/madVR.zip Code:
* added display "properties", "calibration" and "color & gamma" settings pages * added option to define the native display bitdepth (affects dither strength) * added options to define how the display was calibrated (gamut + gamma) * moved "Video/PC levels" option to display "properties" settings page * added options to define which gamma / transfer function to use * replaced old "use 3dlut" option with new controls on "calibration" page * added integrated GUI for yCMS 3dlut creation, no more console hacking needed * added "please wait" dialog while yCMS is downloaded + installed * added "please wait" dialog while 3dlut file is created * added support for 6 and 7 bit 3dlut files (see trade quality for performance) * added option to choose a manually created external 3dlut file (per display) * there's only one 3dlut file per display now * 3dlut is now always yRGB / RGB_Video input and RGB_Video output * YCbCr -> RGB conversion is now always done by shader math, not by 3dlut * Video/PC levels conversion is now always done by shader math, not by 3dlut * rewritten rendering and pixel shader chain * subsampled YCbCr is now upsampled & converted to RGB first, then scaled * chroma upsampling got quite a bit faster (because it's now always exactly 2x) * luma scaling got a tiny bit faster, depending on scaling factor and taps * Strg+Alt+Shift+C displays & toggles color format (BT.709 -> BT.601 -> PAL) * Strg+Alt+Shift+G displays and increases the Gamma value (2.20 -> 2.25 -> ...) * Strg+Alt+Shift+F displays and decreases the Gamma value (2.20 -> 2.15 -> ...) * Strg+Alt+Shift+T displays and changes the Gamma curve type (pure power / BT) * dither is using a texture again instead of shader math * dither is now colored and differs for every video frame * added support for 8 bit 4:2:0 media types IYUV, I420, NV21, ICM* * added support for 8 bit 4:2:2 media types YUY2, YVYU, UYVY, YV16, yuv2, ... * added support for 8 bit 4:4:4 media types AYUV, YV24, I444, v308, v408 * added support for 8 bit RGB media types RGB32, RGB24, BGRA, ABGR, RGBA * added support for 10 bit 4:2:2 media types P210, Y210, v210 * added support for 10 bit 4:4:4 media types Y410, v410 * added support for 16 bit 4:2:2 media types P216, Y216, v216 * added support for 16 bit 4:4:4 media types Y416, v416 * added support for 16 bit RGB media types RGB48, RGB64, b48r, b64a, ... * added hints to "install.bat" and "readme.txt" to not delete the madVR folder * fixed: madVR rendering window in GraphEdit didn't have correct size * changed VSync priority back to "time critical" * slightly changed tray icon mouse click behaviour (1) Since a lot of stuff has changed internally, expect some new bugs. (2) Some pixel shaders got a bit faster, but I've added a couple more processing steps. Not sure what the net effect will be. Maybe v0.62 will perform a little bit faster or slower for you, depending on settings. (3) cyberbeing: Please check whether the 3dlut stuttering you have with out-of-gamut colors is gone when using a 7bit or 6bit 3dlut. (4) 6233638: It was you who preferred Bicubic for chroma upscaling, correct? Please recheck your preferences with v0.62. (5) Please note that madVR now accepts 4:2:2 connections. It is now *your* duty to make sure the decoder outputs the optimal format (which is usually 4:2:0). (6) Below is the full list of FourCCs supported by v0.62. I'm looking for samples of AVI/QuickTime movie files with raw video data in as many of these FourCCs as possible, so I can test that my implementation of these FourCCs is correct. So if you have (or can create) any samples that could help, please upload (small) samples. Thanks! Code:
// 8bit YCbCr // 4:2:0 YV12 NV12 yv12 nv12 ICM1 ICM2 ICM3 ICM4 NV21 IYUV I420 // 4:2:2 YUY2 yuy2 YVYU UYVY uyvy cyuv UYNV UYNY HDYC uyv1 2Vu1 VDTZ YUV2 yuv2 2vuy 2Vuy yuvu yuvs YV16 I422 Y422 V422 Y42B P422 YUNV VYUY AVUI // 4:4:4 AYUV YV24 I444 v308 v408 // RGB // 8bit RGB24 RGB32 24BG BGRA ABGR RGBA // 16bit RGB48LE RGB48BE b48r RGBA64LE RGBA64BE b64a // 10bit YCbCr // 4:2:0 P010 // 4:2:2 P210 Y210 v210 // 4:4:4 Y410 v410 // 16bit YCbCr // 4:2:0 P016 // 4:2:2 P216 Y216 v216 // 4:4:4 Y416 v416 |
5th June 2011, 18:12 | #7879 | Link | |
Registered User
Join Date: May 2004
Posts: 5,351
|
Quote:
__________________
HTPC: Windows 11, AMD 5900X, RTX 3080, Pioneer Elite VSX-LX303, LG G2 77" OLED |
|
5th June 2011, 18:12 | #7880 | Link |
Registered User
Join Date: Sep 2006
Posts: 2,197
|
so when watching remuxed BDs with coreavc, anything I need to change in coreavc settings now?
__________________
Laptop Lenovo Legion 5 17IMH05: i5-10300H, 16 GB Ram, NVIDIA GTX 1650 Ti (+ Intel UHD 630), Windows 10 x64, madVR (x64), MPC-HC (x64), LAV Filter (x64), XySubfilter (x64) (K-lite codec pack) |
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
|
|