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. |
3rd August 2013, 01:23 | #19762 | Link |
Registered User
Join Date: Jul 2009
Posts: 51
|
Thanks again. One last question:
I have created a 3DLut for Rec709 (using the following: collink.exe -v -3m -qh -et -Et -IB2.2 -G -iaw Rec709.icm MadVR.icm 3DLUT.icm), and have specified it in the Rec709 dialogue box under devices > calibration. Do I need to add it for the other gamuts, or will MadVR use it automatically and do appropriate transforms? |
3rd August 2013, 11:55 | #19764 | Link |
Broadband Junkie
Join Date: Oct 2005
Posts: 1,859
|
You can specify the REC709 3DLUT manually for all gamuts if you desire, it works the same either way.
Edit: In case that was too ambiguous, it means that madVR determines gamut from the primaries written plain-text in the 3DLUT header, not the slot you place it in. If the 3DLUT primaries do not match the gamut of the video, shader adaption to the native gamut of the 3DLUT will occur. Last edited by cyberbeing; 3rd August 2013 at 15:26. |
3rd August 2013, 23:47 | #19766 | Link |
Registered User
Join Date: Feb 2012
Posts: 14
|
Done more calibrating of my Panasonic p42st32y plasma and still being confused. So I tried with -dmadvr -a and using just madvr to control black level (nvidia madvrlevelstweaker also forced 0-255). Now I was using argyll with the scenarios.html workflow.
-If i used 0-255 I get around 6500 contrast ratio but I can only see black bars flashing 20 and up not 17. Whites clip around 245. Also gamma shows a huge drop to 1.9 at 90% brightness! -If I used 16-235 I get around half the contrast ratio around 3500 and see bar 16 and up flashing. Whites dont clip. Gamma curve appears normal bt 1886. I tried using different collink settings -iaw and -IB or -ir and -Ib but no difference. For both tests I used default True Cinema preset but I got 17 and up flashing adjusting brightness a lil up with 0-255 after calibration. Im wondering whichone is the more "correct" behaviour and should be used. Or if anyone got any alternatives or ideas?
__________________
Hardware: Asus P8Z68/GEN-3, 8gb 1600Mhz ddr3, Core i5 2500k, Gtx 680, xonar essence st Software: MPC-HC, MadVr |
4th August 2013, 04:39 | #19767 | Link | |
Registered User
Join Date: May 2009
Posts: 212
|
Quote:
Even if this OS has some "unique" new features unavailable on Win7, is it worthy to support that in short term --- when the Win8.x market share % is so low at this moment? |
|
5th August 2013, 18:27 | #19768 | Link |
Registered User
Join Date: Nov 2009
Location: Philippines
Posts: 93
|
My TV supports 23.976 Hz screen refresh rate and madVR perfectly fine with it (0 drop frames, no glitches), but, not with my PC monitor which natively supports 50, 59 and 60 Hz, and 72 Hz if I add custom resolution in Nvidia Control Panel.
My questions are, Is it safe for my monitor to used 72 Hz all the time? I mean, it doesn't destroy my monitor? My configs are: i7 2600k Sandy Bridge GTX 560 Ti LAV Filters - all default except LAV Video (CUVID) Reclock - not bitstreaming because I used SPDIF Sorry for my english |
5th August 2013, 20:00 | #19769 | Link |
Registered User
Join Date: Jul 2013
Posts: 1
|
madVR v0.86.*
* fixed: #30: ZoomPlayer got stuck in 'on top' mode after leaving FSE Hi. I think the above fix has broken the 'stay on top' feature in zoom player for me. When zoom player goes from windowed to full screen exclusive and back to windowed again, 'stay on top' is still ticked but does not function. If I untick and retick the box 'stay on top' works as it should. I like to have zoom player in the top corner of my screen so I can keep watching while browsing the web etc. I have downgraded to madVR0865 which has fixed the problem. Reporting bug, not complaining |
6th August 2013, 02:47 | #19770 | Link |
Registered User
Join Date: Oct 2012
Posts: 179
|
@lemo: It's not madVR specific - same happens with all the other renderers. It's something that is a regression in the latest Zoom Player beta's (it was first reported with 8.70 Beta 11). There is a bug report in the Zoom bug tracker for Blight to look at:
http://forum.inmatrix.com/index.php?showtopic=14073#entry54462 I don't know why downgrading madVR fixes it for you when all the other renderers are affected as well though. |
6th August 2013, 09:23 | #19772 | Link | |
Registered User
Join Date: Mar 2009
Posts: 3,650
|
Quote:
For me my Intel HD 4000 GPU system memory grows from 239MB with it disabled to 303MB with it enabled, so it could be just you or to put it more accurately.. your graphics system. A comparison between Intel, AMD and Nvidia results in this area would be interesting to see, perhaps something can be optimized here. |
|
6th August 2013, 09:36 | #19773 | Link |
Registered User
Join Date: Jan 2009
Posts: 1,210
|
Well, when upscaling 1080p to 1440p at max settings in madVR with smoothmotion on an additional 300MB - 400MB of VRAM is taken up on my GTX 670 2GB. Not too sure I can attribute it directly to smoothmotion though. Need to do some testing to make sure exactly.
|
6th August 2013, 09:45 | #19774 | Link |
Registered User
Join Date: Jan 2009
Posts: 1,210
|
Ok, I now have a real (and tested) 120Hz monitor and a 60Hz monitor. I ran the SmoothMotion 24p test pattern on both monitors simultaneously and I cannot tell them apart in terms of smoothness with smoothmotion ON on the 60Hz monitor and smoothmotion OFF on the 120Hz monitor.
Now, other than the fact the 120Hz is good for games and even normal desktop usage, why is it still considered that a monitor @120Hz is better than a monitor @60Hz using smoothmotion? I would really like to know that technical reasons. Does interpolation cause microscopic artifacting? Is there some other drawback to using smoothmotion interpolation that cannot be easily seen? Last edited by dansrfe; 6th August 2013 at 09:49. |
6th August 2013, 11:19 | #19775 | Link |
Registered User
Join Date: Jun 2007
Posts: 68
|
I thought smoothmotion only created frames when absolutely required. This is my understanding:
No frames would be created in the 24fps / 120Hz situation as madVR would show each frame 5 times within each second. With 24 fps/60 hz situation madVR would show each frame twice, and interpolate 12 frames within each second via frame blending the adjacent frames. If that's right, then 120 Hz is superior in that you are seeing only the intended frames present in the video stream. I think there is pretty low chance of artifacting with normal content but with 120 Hz you avoid any chance of it. |
6th August 2013, 11:28 | #19776 | Link | |||||||||||||||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Quote:
Quote:
Quote:
Quote:
FRC hotkey logic might change in the future, but not now. Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
http://www.avsforum.com/t/1471169/madvr-argyllcms Quote:
Quote:
Quote:
Look for the "white line, black line, white line, black line" section in the test pattern bar which moves the slowest. That section should look slightly better with 120Hz and smooth motion FRC turned off. Some people claim to see some ghosting artifacts when smooth motion FRC is turned on. Personally, I don't see that (with 24fps @ 60Hz). I do wonder if this artifact is really caused by smooth motion FRC itself or whether the display of the users which have this problem is not working as expected (e.g. running at a different internal refresh rate). 120Hz has some other advantages. E.g. it might allow the use of DFI (dark frame insertion) to make motion more sharp. You can't really do that with 60Hz, without getting strong flicking artifacts. But madVR currently does not do/support DFI. Maybe some far away day in the future... One advantage of 120Hz is that you could do 50fps @ 120Hz with smooth motion turned on. Doing 50fps @ 60Hz currently doesn't work very well with smooth motion FRC. |
|||||||||||||||
6th August 2013, 13:42 | #19777 | Link | ||||
Kid for Today
Join Date: Aug 2004
Posts: 3,477
|
Quote:
When lesnumeriques.com asked Samsung, they replied that this would void the warranty.....of course, they would have no way of finding out. This said, CRT's do age faster when you go >100Hz. I was given a lot of technical reasons to that a few months ago, basically it really boils down to hardware "overclocking".....and my last 19" CRT did die very shortly after I had the genius idea of increasing its 720p refresh rate from 96 to 140Hz Quote:
I do see faint ghosting but I'm still utterly impressed by how FRC in mVR in suppresses 24p judder, to my eyes the pop effect is drastically increased and instead of judder I see barely noticeable ghosting.....which is nothing more than frames blending really. Also, my brain got used to it and as far as I can tell it quickly ignores them, so all I really see is dead smooth 24p without FI artifacts FRC in mVR is really a God send because I finally found a LCD screen I like but the darn thing judders like hell in 24p and doesn't support 48Hz, the closest it'll do is 49Hz....not as evil as the 4% pitchshifted 50Hz but 2% is still (very) hard to bear, so FRC in 60Hz and that's it I was also able to overclock this TV up to 72Hz using minimal blanking timings(within the 165Mhz pixel clock limit), but then the TV is forced to bypass most of its post-processing and I can kiss its Rec-709 gamut bye bye so that's a no-go. Quote:
So indeed BFI in mVR could be useful but it would require a display with a lot of extra brightness available, and of course clouding/light bleeding would become more visible. This might very well not be worth the hassle as the best way is to turn off the backlight really: Display motion blur Quote:
Last edited by leeperry; 6th August 2013 at 14:02. |
||||
6th August 2013, 16:55 | #19778 | Link |
Registered User
Join Date: Mar 2008
Posts: 448
|
Been a while since I posted here.
I noticed that Madvr + LAV filters + xyvsfilter beta = DXVA can be used without issue. Can anyone verify this? I wonder if the 'dxva' indicator I saw at madvr statistics is just a bug. |
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
|
|