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. |
13th January 2016, 17:08 | #202 | Link |
Registered User
Join Date: Oct 2015
Location: Brasil, SP, São Paulo
Posts: 154
|
What the new option "use Sigmoidal light" on image upscaling does?
__________________
Desktop, i5 2500, 8GB, N570 GTX TF III PE/OC Asus X555LF, i7-5500U, 6GB Ram, Nvidia 930m/HD 5500 Windows 8.1 Pro x64 |
24th January 2016, 01:17 | #203 | Link | |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,407
|
Quote:
Updated for madVR v0.90.3
__________________
madVR options explained |
|
6th February 2016, 08:34 | #204 | Link |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,407
|
Updated for madVR v0.90.4
__________________
madVR options explained |
23rd February 2016, 09:21 | #205 | Link |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,407
|
Updated for madVR v0.90.12.
A lot of improvements in madVR but the only major change for this post was removal of all mention of Jinc only being for upscaling and 3D doesn't crash anymore.
__________________
madVR options explained Last edited by Asmodian; 23rd February 2016 at 09:46. |
13th March 2016, 11:55 | #206 | Link |
Soul Seeker
Join Date: Sep 2013
Posts: 715
|
Excellent explanation to the madvr options, will there be an info for the stats in madvr etc. "average rendering time, present" and more?
For example I'm kinda confused which of the two modes are good for my card gtx 550 ti, the "present" stats are different and I don't know what they mean exactly. Last edited by Siso; 13th March 2016 at 12:32. |
23rd March 2016, 21:40 | #210 | Link |
Registered User
Join Date: May 2011
Posts: 4
|
Some explaination of the madVR status window would be very helpful
I think it would be great if you could add some information on the first page (or so) that explains a little about what the Queue numbers and Render/Present times mean.
It would help us "madVR-challenged" to understand what is going on when things don't work/look just right. For example my "Present Queue" is 0-1/8 and "Render Queue" is 1-2/8. And I have a lot of dropped frames. I believe a low Present Queue means that my computer is too weak for the settings. Is this correct? Also my Present Time is 4.02ms and the Rendering Time is 86.41ms. What is the acceptable Rendering Time(s)? BTW - I am so clueless on this stuff, it took me ten tries to answer the spam question in order to post. |
24th March 2016, 20:53 | #211 | Link | |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,407
|
I don't think I want to put more of that kind of information in the first post, it is meant to be a description of all the options, not really a guide. I want to keep the beginning of the post limited to only describing options.
I think I do mention everything you need to know about queues and present times already, but in the second post. CPU queue size: [16] The buffer in system memory for decoded video and xySubFilter subtitles. GPU queue size: [8] The buffer in the graphics memory for madVR’s rendering. how many video frames shall be presented in advance or how many backbuffers shall be used: [8 or 3] A final buffer after madVR is done rendering. At the start of "More Advanced Topics" I have: "The sum of the average stats "deinterlace" (if present), "rendering", and "present" should be a bit below the frame time in the line "v-sync [X] ms, frame [Y] ms" to avoid dropped frames and presentation glitches." Is this the information you were looking for or is there something else you want to know? Do I need a "Trouble Shooting" section in "Advanced Topics" so people do not miss it? Or maybe simply a "madVR OSD" section instead? I think I like that idea, I will add that before Advanced Topics. I did update the description of "how many video frames shall be presented in advance" to: Quote:
Thanks.
__________________
madVR options explained |
|
28th March 2016, 18:18 | #212 | Link | ||
Registered User
Join Date: May 2011
Posts: 4
|
Quote:
I found this info posted by madshi (about page 10 of madVR thread): If you want to give madVR even a chance to achieve smooth playback you have to achieve an "average gpu rendering time" that is a notch lower than the "movie frame interval". I'd say it should not be higher than 35ms for 23.976 playback. Now the optimal configuration for madVR is if you drive the display with the same refresh rate the source is in (in your case 23.976Hz). If you have to use 59.940Hz, things get slightly more difficult for madVR. In that case you may have to bring "average gpu rendering time" down even more. and Quote:
This is the "kind of info" I am looking for when it comes to troubleshooting (understand the Stats). Thanks for your help. Last edited by CountryBumkin; 28th March 2016 at 18:26. |
||
29th March 2016, 02:59 | #213 | Link | |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,407
|
From your post I take it that:
The sum of the average stats "deinterlace" (if present), "rendering", and "present" should be a bit below the frame time in the line "v-sync [X] ms, frame [Y] ms" to avoid dropped frames and presentation glitches. Did not tell you all this already? Everything covered in your post is what I was trying to communicate with that line. I am having trouble understanding if you want any new information or simply didn't understand what I was trying to say with that line. Do I just need to rephrase it or add an entirely new section? Adding a new section will not help if the problem is with understanding what I wrote instead of actually missing information. edit: Does this example I included help clarify it? Quote:
__________________
madVR options explained Last edited by Asmodian; 29th March 2016 at 04:48. |
|
30th April 2016, 03:11 | #214 | Link |
Registered User
Join Date: Dec 2014
Posts: 1,127
|
Bump.
__________________
HOW TO - Set up madVR for Kodi DSPlayer & External Media Players |
6th May 2016, 05:39 | #215 | Link | |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,407
|
Thanks. I finally updated to 90.17, I used your description for the anti-bloating filter.
Quote:
__________________
madVR options explained |
|
11th May 2016, 09:29 | #216 | Link |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,407
|
Updated for madVR v0.90.18.
Another artifact removal option, 'reduce ringing artifacts'!
__________________
madVR options explained |
23rd May 2016, 23:40 | #217 | Link |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,407
|
Updated for v0.90.20.
New flow chart.
__________________
madVR options explained |
30th May 2016, 17:49 | #218 | Link | ||
Registered User
Join Date: Jan 2008
Posts: 589
|
After some experiments I've noticed that the way 3DLUTs and GPU gamma curves work can be a bit counter-intuitive at times. I have a suggestion:
Change: Quote:
Quote:
Last edited by e-t172; 30th May 2016 at 17:59. |
||
1st June 2016, 04:37 | #219 | Link | |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,407
|
Quote:
More precise and very useful information. I also have enough characters to expand that section a bit. Thanks.
__________________
madVR options explained |
|
25th June 2016, 00:38 | #220 | Link |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,407
|
Updated to v0.90.21, no changes.
__________________
madVR options explained |
|
|