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. |
1st May 2014, 21:07 | #26302 | Link |
Registered User
Join Date: Nov 2012
Posts: 167
|
As mentioned by vivan, you have to make sure your average rendering time is lower than movie frame interval. In your case it is higher (20.01ms vs 16.68ms). With 23.976fps progressive content you get over 40ms frame interval, so over twice the time for you GPU to process a single frame, hence BDs play fine.
You should create profiles for your settings. The number of profiles is not limited, so you could create them for various combinations of source resolution and framerate or go the easy/lazy route and create just 2 profiles - one for interlaced/high framerate content and one for progressive/low framerate content. You can get much more creative, but minimal auto-load rules could be: Code:
if (deintFps<31) "lowFPS" else "highFPS" |
1st May 2014, 21:49 | #26303 | Link |
Registered User
Join Date: Jul 2012
Posts: 94
|
I believe I don't need to create more profile because the videos always played fine on my computer. I already have 2 profiles able to handle all videos (in past).
I changed the "chroma upscaling" in madVR, from Jinc 8 taps to 4 taps. And now it's playing fine. o_O?? I don't understand why I need to change that, now. |
2nd May 2014, 01:07 | #26305 | Link |
Registered User
Join Date: Apr 2014
Posts: 19
|
Latest AMD Catalyst Driver on NNEDI3 OpenCL performance
Hi guys, I'm new here but been following this thread for a year now.
I'd just like to ask something; do some of you AMD GPU users experience performance drop in NNEDI3 after updating to the latest AMD Catalyst Driver 14.4? Before I update my driver to 14.4, I can do NNEDI3 16 on luma for my 720p24 videos. Because I can't do NNEDI3 16 luma for 720p24, I reverted back to my previous driver and can now do NNEDI3 16 luma for 720p24. One thing I notice on 14.4 is alternative interop hack performs slightly better compared to the default interop hack. But that being said, I still experience frame drops on both interop hacks using 14.4. Another question; will image upscaling still matters if I do luma doubling on 720p to a 1920:1080 display? Image upscaling still affects rendering times even using luma doubling so I used Bicubic75ar, Bilinear or Nearest Neighbor instead of using jinc3ar. Is that OK? |
2nd May 2014, 10:02 | #26308 | Link |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,344
|
The rendering time isn't always reliable, and fluctuations in the time may cause your profile to constantly switch back and forth, which is why madshi said this is not really going to be a useful thing.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
2nd May 2014, 18:28 | #26309 | Link |
Registered User
Join Date: Jan 2006
Posts: 80
|
Madshi,
Has the API changed with the latest MadTPG (1.0.4.0)? I'm getting a "Error - new_disprd() failed with Window access failed" when DispcalGUI is trying to access MadTPG for pattern generation. MadVR 0.87.10 DispcalGUI 2.0.0.0 ArgyllCMS 1.6.3 Thanks |
2nd May 2014, 20:52 | #26311 | Link | |
Kid for Today
Join Date: Aug 2004
Posts: 3,477
|
Quote:
An "auto-sensing" NNEDI option based on whether queues fill up would be full of win Last edited by leeperry; 2nd May 2014 at 20:55. |
|
2nd May 2014, 23:21 | #26312 | Link | |
Registered User
Join Date: Jan 2013
Posts: 18
|
Quote:
I'm very happy with the performance of my 6570M/5730M in MadVR with driver 13.12. I think I'm going to stay fixed with it, unless there is any worthwhile improvement in some video area in the future. |
|
2nd May 2014, 23:36 | #26313 | Link |
Kid for Today
Join Date: Aug 2004
Posts: 3,477
|
Now I kinda wonder whether 13.9 would be any faster than 13.12 as I had weird crashes with 13.12 a few times, I think I might give 13.9 a shot while I'm at it...just need to look up which version nailed down the 7850 black screen problem as it gave me cold sweat on XP and I don't wanna go through this again on W7.
|
2nd May 2014, 23:54 | #26314 | Link |
Registered User
Join Date: Jan 2013
Posts: 18
|
In my case from 13.9 to 13.12 was going from desktop to fullscreen exclusive from about 1.5 seconds to half the time in the same official MadVR release we used in 6 December. After that, madshi managed to improve that even more and it is almost instantaneous now on my system (if video is 30/60fps, changing to 50hz screen for 24/25fps of course, takes its time, nothing to do with madvr). Full screen windowed mode is really instantaneous with the new mode (also lagged a bit in 13.9, and slightly improved in 13.12 but in the old mode).
|
3rd May 2014, 15:50 | #26318 | Link | ||
Registered User
Join Date: Mar 2009
Posts: 962
|
Quote:
Quote:
__________________
MSI MAG X570 TOMAHAWK WIFI, Ryzen 5900x, RTX 3070, Win 10-64. Pioneer VSX-LX503, LG OLED65C9 |
||
3rd May 2014, 16:10 | #26319 | Link | |
Registered User
Join Date: Dec 2002
Location: Region 0
Posts: 1,436
|
Quote:
Edit: Yes, I missed the Ctrl+Shift+Alt+T x2 step. Now it works fine. Last edited by Stereodude; 3rd May 2014 at 16:15. |
|
3rd May 2014, 16:26 | #26320 | Link |
Registered User
Join Date: Dec 2002
Location: Region 0
Posts: 1,436
|
Shouldn't deintFps be 24FPS for 720p60 material that is detected as film mode 6:4? That doesn't seem to be the case. My profile rule of if ((srcWidth <= 1300) and (deintFps < 31)) "HighQ" picks the default, not HighQ.
|
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
Thread Tools | Search this Thread |
Display Modes | |
|
|