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.

 

Go Back   Doom9's Forum > Hardware & Software > Software players

Reply
 
Thread Tools Search this Thread Display Modes
Old 1st May 2014, 20:23   #26301  |  Link
Sm3n
Registered User
 
Join Date: Jul 2012
Posts: 94
Quote:
Originally Posted by vivan View Post
average rendering time in OSD (Ctrl+J).
If there're 60 frames per second - then each frame should be rendered faster than 1/60 = 0.0166 s = 16.6 ms.
Thx

Here is my Ctrl+j:

Sm3n is offline   Reply With Quote
Old 1st May 2014, 21:07   #26302  |  Link
michkrol
Registered User
 
Join Date: Nov 2012
Posts: 167
Quote:
Originally Posted by Sm3n View Post
Thx

Here is my Ctrl+j
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"
to load profile named lowFPS or highFPS depending on the framerate after deinterlacing (simplifying, the actual number of frames per second madVR has to process).
michkrol is offline   Reply With Quote
Old 1st May 2014, 21:49   #26303  |  Link
Sm3n
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.
Sm3n is offline   Reply With Quote
Old 1st May 2014, 23:18   #26304  |  Link
seiyafan
Registered User
 
Join Date: Feb 2014
Posts: 162
Jinc8 is very intensive compare to Jinc3/4 yet it brings minimum visual difference.
seiyafan is offline   Reply With Quote
Old 2nd May 2014, 01:07   #26305  |  Link
ikakun
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?
ikakun is offline   Reply With Quote
Old 2nd May 2014, 05:45   #26306  |  Link
Mr6686
Registered User
 
Mr6686's Avatar
 
Join Date: Feb 2014
Posts: 1
Yes, with amd 14.4 driver (in exclusive mode, with only certain video) I saw a performance drop in rendering time (~15ms > ~150ms). So back to 13.12.
Mr6686 is offline   Reply With Quote
Old 2nd May 2014, 09:28   #26307  |  Link
BeNooL
Registered User
 
BeNooL's Avatar
 
Join Date: Feb 2003
Posts: 78
Seeing madVR already computes and collects various performance stats, could we imagine having profile switching based on rendering time ?
BeNooL is offline   Reply With Quote
Old 2nd May 2014, 10:02   #26308  |  Link
nevcairiel
Registered Developer
 
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,344
Quote:
Originally Posted by BeNooL View Post
Seeing madVR already computes and collects various performance stats, could we imagine having profile switching based on rendering time ?
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
nevcairiel is offline   Reply With Quote
Old 2nd May 2014, 18:28   #26309  |  Link
n3w813
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
n3w813 is offline   Reply With Quote
Old 2nd May 2014, 18:39   #26310  |  Link
n3w813
Registered User
 
Join Date: Jan 2006
Posts: 80
Rolling back to MadTPG 1.0.3.0 (01/23/2014) fixes the issue. Is this something Florian needs to fix on DispcalGUI?

Quote:
Originally Posted by n3w813 View Post
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
n3w813 is offline   Reply With Quote
Old 2nd May 2014, 20:52   #26311  |  Link
leeperry
Kid for Today
 
Join Date: Aug 2004
Posts: 3,477
Quote:
Originally Posted by Mr6686 View Post
Yes, with amd 14.4 driver (in exclusive mode, with only certain video) I saw a performance drop in rendering time (~15ms > ~150ms). So back to 13.12.
Oh indeed, I used to be able to run 64x chroma + 256x luma on 576x320@25p(with an Haswell PCI-E 3.0 H87 system & a HD7850) and now I can't even swing 32x chroma + 128x luma....using the alternate lag "fix" doesn't help either, I guess that's quickly gonna get on madshi's nerves if he has to rework his fixes with every new driver release. 14.4 wasn't worth the +4 months wait, rolling back to 13.12 when I'll find the patience

Quote:
Originally Posted by nevcairiel View Post
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.
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.
leeperry is offline   Reply With Quote
Old 2nd May 2014, 23:21   #26312  |  Link
sajara
Registered User
 
Join Date: Jan 2013
Posts: 18
Quote:
Originally Posted by leeperry View Post
14.4 wasn't worth the +4 months wait, rolling back to 13.12 when I'll find the patience
Thanks for letting us know.

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.
sajara is offline   Reply With Quote
Old 2nd May 2014, 23:36   #26313  |  Link
leeperry
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.
leeperry is offline   Reply With Quote
Old 2nd May 2014, 23:54   #26314  |  Link
sajara
Registered User
 
Join Date: Jan 2013
Posts: 18
Quote:
Originally Posted by leeperry View Post
Now I kinda wonder whether 13.9 would be any faster than 13.12
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).
sajara is offline   Reply With Quote
Old 3rd May 2014, 07:06   #26315  |  Link
Qaq
AV heretic
 
Join Date: Nov 2009
Posts: 422
Quote:
Originally Posted by leeperry View Post
Now I kinda wonder whether 13.9 would be any faster than 13.12
Say goodbye to NNEDI3 then. 13.12 is the first driver with D3D9 <-> OpenCL interop.
Qaq is offline   Reply With Quote
Old 3rd May 2014, 12:54   #26316  |  Link
leeperry
Kid for Today
 
Join Date: Aug 2004
Posts: 3,477
I recall someone claiming here in that thread that 13.9 was working fine with mVR, but maybe he wasn't using NNEDI then......anyway I did get the 7850 black screen on several occasions with 13.9 on XP so 13.12 it is
leeperry is offline   Reply With Quote
Old 3rd May 2014, 15:12   #26317  |  Link
Knight77
Registered User
 
Join Date: Feb 2012
Posts: 54
Guys today which do you prefer to run MPHC+madVR and XBMC: Windows 7 or 8?

Inviato dal mio Nexus 7 utilizzando Tapatalk

Last edited by Guest; 3rd May 2014 at 15:19. Reason: rule 12: don't ask what's best
Knight77 is offline   Reply With Quote
Old 3rd May 2014, 15:50   #26318  |  Link
Andy o
Registered User
 
Join Date: Mar 2009
Posts: 962
Quote:
Originally Posted by madshi View Post
Of course I understand that if you know for a fact that your content is really film only, and every part of it is 3:2 cadence, then there's no need to use 60Hz and you can simply use 23Hz instead. But this once again requires your input: You need to tell madVR that you know that the content is straight 23Hz all the way through. Maybe I should add an option for that.
Thanks for adding decimation madshi. My use case is also 720/60p film content (In the US - Cosmos on Fox pretty much). Being able to force refresh at 23/24Hz would be a great option in the future.

Quote:
Anyway, that's just the current situation. I've some ideas for future builds. At the moment I've just implemented 720p50/60 decimation for the first time, so please just test whether it generally works, report bugs/problems you find, and please live for now with whatever shortcomings there might be. Once we've ironed out whatever bugs there might be, maybe I'll polish the whole thing to make everyone happy.
Will do!
__________________
MSI MAG X570 TOMAHAWK WIFI, Ryzen 5900x, RTX 3070, Win 10-64.
Pioneer VSX-LX503, LG OLED65C9
Andy o is offline   Reply With Quote
Old 3rd May 2014, 16:10   #26319  |  Link
Stereodude
Registered User
 
Join Date: Dec 2002
Location: Region 0
Posts: 1,436
Quote:
Originally Posted by Andy o View Post
Thanks for adding decimation madshi. My use case is also 720/60p film content (In the US - Cosmos on Fox pretty much). Being able to force refresh at 23/24Hz would be a great option in the future.
Does it work for you? I've tried it and can't see any sign that it is doing anything. I'm playing known film source 720p60 with a 3:2 repeating frame pattern and have it set to force film mode. I must be missing a step.

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.
Stereodude is offline   Reply With Quote
Old 3rd May 2014, 16:26   #26320  |  Link
Stereodude
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.
Stereodude is offline   Reply With Quote
Reply

Tags
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 01:20.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.