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. |
7th September 2015, 20:31 | #32761 | Link | |
Guest
Posts: n/a
|
Quote:
Also, are there any news of SM 5.0 OpenCL support for NNEDI3? |
|
7th September 2015, 20:51 | #32762 | Link |
Registered User
Join Date: Dec 2011
Posts: 1,812
|
madshi just said a few posts ago that he will look into it next (I suppose the coming) weekend...
But since SM version is slower on Maxwell, it will probably still be OpenCL. --------------- Is it known that DXVA2 native decoding will give terrible chroma scaling quality with Nvidia? The checkboxes for performance trade-offs are unticked (just like any processing in the driver), but chroma gets much blurrier though. |
7th September 2015, 20:59 | #32763 | Link | ||
Registered User
Join Date: Oct 2012
Posts: 7,903
|
Quote:
first of all, all 21/9 movies on a BDs have black bars there is no 21/9 spec in the BD spec and there is no 21/9 spec in UBD too. a lot of high end user use an projector with an anamorphic lens to get the 16/9 to 21/9 to use the full pixel count and to maximize light output. the resolution is still 1920x1080 that's why you can tell madVR that there is a anamorphic lens. with a 21/9 movie on a typical BD which is a 16/9 frame with black boards the black border are remove leaving a 21/9 which is than scaled to 16/9 and this is displayed at 21/9 thanks to the anamorphic lens. not that complicated right? this is ridiculously useful. it's useful for other things too like an old 4/3 show with 16/9 part in it the 16/9 aren't shown in a latter box anymore when watched on a 16/9 screen thank to that new feature. Quote:
|
||
7th September 2015, 21:02 | #32764 | Link | |
Registered User
Join Date: Oct 2012
Posts: 7,903
|
Quote:
|
|
7th September 2015, 21:28 | #32765 | Link | |
Registered User
Join Date: Dec 2011
Posts: 1,812
|
Quote:
I'm just asking out of curiosity, LAV's copyback is working fine for me for years. |
|
7th September 2015, 21:32 | #32766 | Link | |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,344
|
Quote:
Usually, you would just employ DXVA scaling to RGB, which has a texture type obviously, and be done with it. But madVR wants the original NV12 data, so it tries some tricks to extract it, but it doesn't work losslessly on NVIDIA unfortunately. madVR used to have copy-back options itself, but madshi removed them because LAV was more efficient at it in the end. ----------- I hope we can also get some of the things started in 0.88.x sorted before diving too deep into yet more new features. Its still hard to universally recommend 0.88.x (or ship it with JRMC for that matter) right now, as it seems to lack a degree of polish and stability.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders Last edited by nevcairiel; 7th September 2015 at 22:13. |
|
7th September 2015, 22:38 | #32768 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
madVR v0.89.1 released
http://madshi.net/madVR.zip Code:
* fixed: two startup crashes with some media players |
8th September 2015, 01:42 | #32770 | Link |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,406
|
Odd, I am using madVR 0.89.0 (32-bit) with XYSubFilter 3.1.0.705 (git caded62). No crashes so far.
I am using Win10 x64, Zoom Player, and overlay. edit: madVR 0.89.1 (32-bit) works fine as well. I notice the OSD displays Jinc upscaling even when "disable scaling if image size changes by only:" is active.
__________________
madVR options explained Last edited by Asmodian; 8th September 2015 at 01:48. |
8th September 2015, 03:18 | #32771 | Link |
47.952fps@71.928Hz
Join Date: Mar 2011
Posts: 940
|
Black bar settings, somethign to new to play with
Thanks for the continual work!
__________________
Win10 (x64) build 19041 NVIDIA GeForce GTX 1060 3GB (GP106) 3071MB/GDDR5 | (r435_95-4) NTSC | DVD: R1 | BD: A AMD Ryzen 5 2600 @3.4GHz (6c/12th, I'm on AVX2 now!)
|
8th September 2015, 11:27 | #32774 | Link | |||||||||||||||||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Haha, I think you're "slightly" too optimistic there! Quote:
Quote:
Quote:
Quote:
Good question. I don't think so, will add it to my to do list. Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Stats window text is not adjustable atm. Maybe in some future version. For 10bit output you need Direct3D11 presentation - and FSE mode. And then you need to set your display to 10bit in the madVR display properties. That sounds *very* weird because if you enable D3D11 presentation, the option "use a separate device for presentation" should be implicitly enabled, too, internally by madVR. Are you 100% sure that toggling the "use a separate device for presentation" option makes any difference when using D3D11 presentation? It should most definitely not. If it does, something is very weird/wrong. |
|||||||||||||||||
8th September 2015, 11:27 | #32775 | Link | ||||||||||||||||||||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
My recommendation would be to live with this for a while and hope that new GPU drivers, new media player builds and latest madVR builds will "automatically" fix this soon. If the problem stays for some more weeks/months, maybe I can look into it if you provide me with debug builds. But for now I'm very busy so I'd like to delay that, in the hope that newer GPU drivers might already fix it, anyway. How can I - without having a G-Sync monitor to test with? Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
2) Stability issues with some AMD driver versions. 3) Some users having problems with FSE mode not working, for as of yet unknown reasons. Quote:
MPC-HC gets this information from madVR by using this API: https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx According to the Microsoft documentation this information describes the framerate during playback which is different from the "authored frame rate". What you want is the "authored frame rate", which is not what this information describes. So basically you're looking at the wrong place, IMHO. madVR fills this information with the number of frames that is passed to D3D9/11 for presentation. Which usually equals the display refresh rate if you have "present several frames in advance" activated. Strange. I can't reproduce that here. Are you sure you're looking at the right line in the OSD? When using NNEDI3 for luma doubling, but *not* for chroma doubling, there are actually two "chroma" lines in the OSD. |
||||||||||||||||||||
8th September 2015, 11:28 | #32776 | Link | |||||||||||||||||||||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
In order to avoid this specific problem I've implemented a delay after which madVR switches into paused/stopped mode. In v0.88.21 and older builds it was 1 second, I think. I've already increased it to 2 seconds now in v0.89.1. So maybe the problem is gone now for you in v0.89.1? Folder or file, doesn't matter. Just some file system "object" with that name. Quote:
Quote:
Quote:
For highest quality either use LAV copyback or software decoding. Maybe I can achieve the same quality with native DXVA2 if and when nevcairiel and I switch to DX11 DXVA. But I'm not sure if we will ever so that switch because nevcairiel says those interfaces are rather nasty. Anyway, LAV copyback works great, so there's really no need for native DXVA decoding - unless you simply want the fastest speed or lowest power consumption - and that's what madVR now aims for when using native DXVA2. Makes sense, I hope? Quote:
FWIW, I was recently confused about this myself. Basically I played a 1080p movie in a smaller window. And there was a 1 line black bar at the right side. Once madVR detected the black bar, it was removed. So scaling changed by 1 line. And then I looked at the OSD and thought: Why is scaling still active for just 1 line? But then I remembered that I was still downscaling a 1080p movie to the window size! Could it be something like that? The "disable scaling" option only goes into effect if both X and Y do not need scaling by more than the number of lines you selected. I can't treat X and Y separately, because then the aspect ratio would be distorted. Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
http://madshi.net/exc-ss3.gif The text will be slightly different, but the layout of the crash box should be similar. If you get the crash box, try to send the crash report to me. If you get a different crash box, then it's probably a crash in the media player. Might make sense to first try updating to the latest driver build, latest media player build and latest madVR build to see if that helps. Quote:
|
|||||||||||||||||||||
8th September 2015, 12:12 | #32777 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
I've seen some users wondering what the purpose of the black bar detection stuff is. Here's a list of benefits:
1) display with unusual aspect ratio: Blu-Rays are encoded in 16:9, regardless of which aspect ratio the actual video has. So most Blu-Rays have some sort of black bars encoded into the 16:9 image. 4:3 movies have big side black bars. Cinemascope have big top/bottom black bars. Even 1.85:1 movies usually have small top/bottom black bars. It's all fine if your display is 16:9. However, if you display aspect ratio differs, things become interesting. Here's an image created by user HelmedHorror which nicely explains the problem if you have a CinemaScope display: cinemaScope display Now what the black bar detection in madVR does is detect which part of the 16:9 Blu-Ray video consists of black bars and which part consists of actual video content. This information is then used to automatically center the video and to zoom the video to fill your screen as optimally as possible. So if you play e.g. a CinemaScope movie on a CinemaScope display, the movie is automatically zoomed to full screen. Without the black bar detection you would get big black bars all around the video in this situation, called letterboxing. 1) playing in windowed mode: If you play a video in windowed mode, some media players automatically size their window to match the aspect ratio of the video. So e.g. on my PC MPC-HC opens a CinemaScope movie like this: cinemaScope default window size In a future madVR version (not implemented in v0.89.1 yet!) madVR will report the actual size of the video to the media player, so then hopefully the media player will size the window like this instead: cinemaScope optimized window size Saves precious space for other windows, doesn't it? 3) badly/weirdly encoded movies: Sometimes movie files are encoded in a bad/weird way. E.g. some Japan broadcasts have the video shifted up and gigantic Japanese subtitles under the video. Many encodes have hard coded pillarboxing. Some have garbage at the borders. In all those cases madVR will detect the proper video rectangle and remove all the other crap. Some examples of such bad/weird encodes *without* black bar detection: pillarboxing -- | -- japan broadcast -- | -- garbage border madVR will detect all that, properly center the image and remove all the garbage. ------- There are some more benefits. E.g. if you absolutely hate black bars, you can tell madVR to automatically zoom them (partially or fully, just as you like) away for you. |
8th September 2015, 12:28 | #32778 | Link | |
Lost In The Web
Join Date: Apr 2010
Posts: 35
|
Quote:
Tested with a AMV clip, original size 512*384 (as black border MadVR reported size 512*301) > my resolution 1024*1080 My madVR Setting SD Profile : Chroma upscaling : NNEDI3 32 / SuperRes 1-0.66-0.25 Image downscaling : Lanczos 4 AR Image doubling : NNEDI3 64-32 (octuple activate) Image upscaling : Jinc AR Upscaling refinement : SuperRes 1-0.66 (only once/apply first) in D3D11 Fullscreen Exclusive (10bit) OSD say Chroma > Nnedi32 Image > Nnedi64 > Nnedi64 < Lanczos4 AR Choma > Jinc AR > Jinc AR And when SR in refinement is off Chroma > Nnedi32 Image > Nnedi64 > Nnedi64 < Lanczos4 AR
__________________
Windows 11 11th Gen Intel(R) Core(TM) i5-11400F Nvidia Geoforce RTX 3050 MPCHC - madVR - Lav Filters - XySubFilter Last edited by Sarasa; 8th September 2015 at 13:02. Reason: typo -_-; |
|
8th September 2015, 12:39 | #32779 | Link |
Registered User
Join Date: Feb 2014
Posts: 94
|
Hi, I want to report that I am still having problems with the newer versions of madVR with JRiver Media Center 20, the latest version i can use without problems is 0.88.16, after thar no one works. No problems with MPC-HC so far.
Bug Report link: http://www.megafileupload.com/9irK/bugreport.txt Thanks in advance. |
8th September 2015, 12:58 | #32780 | Link | |||||
Registered User
Join Date: Sep 2014
Posts: 280
|
@ madhsi:
First I want to say a big thank you! I appreciate your hard work to push madvr to an even more better peace of software and I would like to say thanks for taking your time an answere all those "old" posts which are postet since your last visit. Quote:
Quote:
Quote:
Quote:
Quote:
__________________
Intel i5 6600, 16 GB DDR4, AMD Vega RX56 8 GB, Windows 10 x64, Kodi DS Player 17.6, MadVR (x64), LAV Filters (x64), XySubfilter .746 (x64) LG 4K OLED (65C8D), Denon X-4200 AVR, Dali Zensor 5.1 Set |
|||||
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
Thread Tools | Search this Thread |
Display Modes | |
|
|