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. |
19th September 2015, 21:16 | #32961 | Link | |
Soul Seeker
Join Date: Sep 2013
Posts: 711
|
Quote:
+1 for potplayer crash |
|
20th September 2015, 16:34 | #32965 | Link | |
Registered User
Join Date: Feb 2012
Posts: 116
|
Quote:
The player has all you asked a while ago already. I saw some madshi's posts on the svp project forum. He talked about vapoursynth support, but said that he was quite busy. Madshi, do you work on it or something else? Please keep us informed a little bit more because anxiety is growing for some people. Last edited by foozoor; 20th September 2015 at 16:36. |
|
20th September 2015, 21:10 | #32966 | Link |
Registered User
Join Date: Sep 2014
Posts: 280
|
Thank you Madshi for your had work and the new version 0.89.3!
__________________
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 |
20th September 2015, 21:18 | #32967 | Link | ||||||||||||||||||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Quote:
Quote:
Basically in v0.89.x the media player is not in full control over the exact target rect, anymore. Instead madVR tries to understand what the media player wants and then calculates a new target rect which is then used for actual rendering (and which the media player doesn't know anything about). madVR tries to follow the media player wishes, but taking the detected black bars and the user wishes (zoom control) into account, too. So just writing one target rect into the OSD won't tell the whole picture. I would have to at least write the modified source rect (modified by black bar detection) and the final target rect (calculated by madVR) into the OSD, and that could be quite confusing for many users. Is that really so very useful? For image quality comparisons you should be using 100% view, anyway, shouldn't you? If you do that, and if you disable zoom control, then the target rect should be exactly 100% of the native video size (after aspect ratio correction). Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
What duration do you mean? Do you mean the movie runtime? What would you need that for in profiles? Quote:
Considering that A LOT of feedback from many madVR users went into defining the exact low/mid/high settings, and that I like the way they are currently set up, I don't think it would be a good idea to change them now. Quote:
Quote:
Quote:
Quote:
Ah yes. Newer madVR builds don't fully rerender the paused video frame all the time, to save resources. If you use the built-in subtitle renderer then madVR does not know that you changed the subtitle track, so I don't know that I need to rerender the video frame. I'm not sure if I can solve this without pushing GPU power through the roof again in paused mode. And frankly, I don't think this is important enough to make compromises with high GPU power in paused mode. Quote:
Adaptive Sharpen next week. Not sure if there is a new (luma) SuperRes version to update to. But I did plan to work a bit on SuperRes. Might take a bit, though. Quote:
Quote:
Can you retry with v0.89.3? If the problem still occurs with that build, maybe you could create a new log with v0.89.3 for me? When madVR gets stuck, let it stay in that state for 20 seconds. Then close the media player immediately without switching to another station. Maybe then I can find the right place to look at in the log better. Of course it's also possible that madVR thinks it's rendering successfully, but for some reason the rendered images aren't making it through to the display... |
||||||||||||||||||
20th September 2015, 21:30 | #32969 | Link | |
Registered User
Join Date: Oct 2012
Posts: 7,903
|
Quote:
|
|
20th September 2015, 21:30 | #32970 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
madVR v0.89.3 released
http://madshi.net/madVR.zip Code:
* NNEDI3/OpenCL now uses D3D11 interop instead of D3D9 interop * implemented most of the various missing black bar features * added support for device profiling * added vertical scrollbar to "profile auto select rules" edit field * added "smoothmotion" bool value for profile rules * fixed: sometimes video was zoomed in way too much without any reason * fixed: black bar detection sometimes had false positives * fixed: black bar detection sometimes unnecessarily dropped correct detection * fixed: DXVA processing sometimes broke when stopping & starting the graph * fixed: sub options were active even if black bar detection was off 1) NNEDI3 now uses a different interop interface, which seems to perform slightly faster for NVidia and quite noticeably faster for AMD. Also it should work with newer NVidia drivers on Windows 10. I haven't tested yet whether the interop problem is gone for AMD, but there's a good chance that it is. On the negative side, v0.89.3 requires Windows 7 or newer for NNEDI3, so unfortunately Windows XP and Vista users can no longer use NNEDI3. I'm sorry about that, but making the new code XP/Vista capable would have been too much work and not worth the effort, IMHO. Go upgrade to Windows 7 (or newer). It's about time. Since the new interop is brand new, don't be surprised if there are some new bugs. It does work well on my PC, though. 2) madVR can now "notify the media player about cropped black bars". Basically that means that in non-fullscreen windowed playback mode the media player can now automatically adjust the window size in such a way that no black bars are part of the window at all, anymore. Some media players do this better than others, though. Here's a list of media players with recommend settings to make use of this new feature: MPC-HC & MPC-BE: Player -> Limit window proportions on resize Playback -> Auto-zoom: "100%" or "Autofit" ZoomPlayer: Interface -> Position & Size -> Auto-Size User Interface to maintain Video Aspect Ratio (when resizing) Interface -> Position & Size -> Auto-Size User Interface to fit Source Video Resolution (on load) PotPlayer: Playback -> Aspect Ratio -> Fit Window to Image Size These 4 media players do (more or less) already work well with the new madVR feature. MPC-HC & MPC-BE do this best, although both still have room to improve here, as well. ZoomPlayer and PotPlayer don't auto resize their window if madVR tells them to, but at least they adjust the window size to the video when you resize the window. So it's partially working. Most other media players don't support the new feature. Which means the new feature will simply have no effect on them at all. 3) Most of the other zoom control features are fully implemented now. Give them a try! 4) For those who need it, you can now create profiles in the "device" section. |
20th September 2015, 21:34 | #32971 | Link |
Registered User
Join Date: Apr 2015
Posts: 12
|
Madshi, you say that you are using now D3D11 for NNEDI3 "NNEDI3/OpenCL now uses D3D11 interop instead of D3D9 interop"
What happens with people like me with old cards that are not compatible with D3D11? Would it not be possible that madVR would use D3D9 for NNEDI3 is D3D11 is not available? I hope I am not saying or asking something silly ^^; And thanks for your hard work =) |
20th September 2015, 21:39 | #32972 | Link | ||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Quote:
|
||
20th September 2015, 22:02 | #32973 | Link | ||
Registered User
Join Date: Jan 2004
Posts: 567
|
Quote:
I then switched to FSE (1080p50) and it was suddenly easily reproducible... Quote:
madVR - log Hope this helps. Back to 0.88.16 for now .
__________________
Bye Last edited by CiNcH; 20th September 2015 at 22:47. |
||
20th September 2015, 22:06 | #32974 | Link |
Registered User
Join Date: Sep 2012
Posts: 53
|
after updating madVR to 0.89.3,now when i open video it plays fine.
But when i got to full screen,player freezes (no madVR debug window,just player freezes & shows wait or close MPC-BE 1.4.5 build 764 beta) may be something to do with black bar????is it normal that switching from fullscreen windowed mode to windowed mode is slower after blackbar detection. is there any way to disable black bar detection & that zoom control completely?? 2:45am here,so i'll test with settings tomorrow
__________________
Win 7 Ultimate x64 Core i5 2500K 4.2Ghz,Asus p8z68 v pro gen 3 Corsair 2x4GB DDR3 @1600Mhz Asus Gtx 960 strix OC |
20th September 2015, 22:06 | #32975 | Link |
Registered User
Join Date: Dec 2011
Posts: 1,812
|
Performance with D3D11 interop seems to be fine.
I'm not sure if I could do Adaptive Sharpen on top of 1080p30-> 4k -> WQHD 64 neurons before. Maybe I'm confusing this with the GTX 970 I hard before (now 980), at least it seems to be working well. , madshi. It's still nice to have a program that you set&forget and it does the job. So, it's using nv_d3d11_sharing now on Nvidia? Wouldn't it be safer to use the khr_d3d10 extension? Maybe they won't ever delete it, as it's the only Khronos extension for this? But just wild guessing. |
20th September 2015, 22:11 | #32976 | Link |
Registered User
Join Date: Mar 2011
Posts: 60
|
I get a total freeze (have to use task manager to kill player) when using image doubling/quadrupling regardless of the type of scaling that's used. Video completely freezes after 2-3 seconds. Playback is fine without it on. Win 10 x64, gtx 770, NVidia yada yada (not the very lastest driver, but I'm not sure what's really changed in the few updates in the last month and a half? Maybe that is it though) MPC-BE, latest beta (89.2 worked just fine with it).
|
20th September 2015, 22:25 | #32977 | Link | |
Registered User
Join Date: Oct 2012
Posts: 7,903
|
Quote:
so it looks like the interop issue is still there. |
|
20th September 2015, 22:33 | #32978 | Link |
Registered User
Join Date: Dec 2013
Posts: 753
|
I don't think MPDN's version has changed that much since the last time. No matter what I try I keep reverting to the 'old' version since it still seems to give the most natural / accurate result (unless you tweak it for one particular image, but that's not really useful). I'm still searching for a good way to soften the image though.
|
20th September 2015, 22:43 | #32979 | Link | |
Registered User
Join Date: Sep 2012
Posts: 53
|
Quote:
both super-xbr & nnedi3 not working in image doubling(not tested nedi) super xbr works fine with croma upscaling.Nnedi3 not working anywhere not even croma upscaling. using gtx 960 355.82 if i use nnedi3 for croma up,player freezes after 2-3s even in normal mode & fullscreen any setting in doubling causes freeze only in fullscreen.(not using FSE & haven't tested that)
__________________
Win 7 Ultimate x64 Core i5 2500K 4.2Ghz,Asus p8z68 v pro gen 3 Corsair 2x4GB DDR3 @1600Mhz Asus Gtx 960 strix OC |
|
20th September 2015, 22:52 | #32980 | Link | |
Registered User
Join Date: Dec 2011
Posts: 1,812
|
Quote:
Gives me the impression like if there was no upscaling. But for the near future it's also good to have newer AS version. |
|
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
Thread Tools | Search this Thread |
Display Modes | |
|
|