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. |
28th September 2013, 06:43 | #20142 | Link |
Registered User
Join Date: Jan 2009
Posts: 1,210
|
Is there a reason why the "1 frame repeat/drop ever X units" may be hours at one point and days at another? What actually determines "X units"? How does ReClock affect this value, if the refresh rate is a multiple of the frame rate and the taskbar icon is green?
|
28th September 2013, 08:44 | #20143 | Link |
Registered User
Join Date: Apr 2010
Posts: 235
|
Thanks guys, the Reclock is set correctly ( lightning green ) according to this http://img33.imageshack.us/img33/1411/ybhj.png
He says, he is loosing around 25 frames in 3 minutes of a 1080p video and the drops are apparent in fast moving scenes. It doesnt look like a madVR issue to me, so I wont spam this thread and try to fix it by checking his PC state and other components during playback.
__________________
__________________ System: Intel Core i5-6500, 16GB RAM, GTX1060, 75" Sony ZD9, Focal speakers, OS Win10 Pro, Playback: madvr/JRiver Last edited by Plutotype; 28th September 2013 at 09:07. |
28th September 2013, 11:40 | #20144 | Link | |||||||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
It is true that dithering hurts black levels (and white level, for that matter) a tiny bit, but at the moment there's nothing I can do about that. Oh well, I could detect a full black/white frame and behave differently, but that would cost quite some additional performance. In the long run I hope to be able to replace dithering with error diffusion. That should take care of the problem. However, this will only be possible (if at all) by using OpenCL or CUDA, and that is still some time away... Quote:
Quote:
It works for me. Which GPU do you have? Are you using the latest madVR build? If so, create a debug log, zip it and upload it somewhere and I'll have a look. Quote:
Quote:
Quote:
Quote:
Also make sure you have no other software running which might use the GPU. Might even be the browser. ------- Next madVR build is going to have some goodies for you guys. Will take a while until it will be released, though. Here's one new feature: http://forum.doom9.org/showthread.php?p=1645630#post1645630 |
|||||||
28th September 2013, 11:48 | #20145 | Link |
Registered User
Join Date: Sep 2013
Posts: 919
|
Is there any way to use ICC Color Profiles (like MPC-HC does natively) without converting to 3D LUT?
I tried to convert my profile using Argyll+DispcalGUI, and with TI3 Parser but with no success, both of them show some crazy windows errors with red X in them. I calibrate my monitor (Dell U2410 in sRGB mode) with i1 Display Pro to create an ICC profile. In madVR in the Calibration settings: I see NO difference between "Disable calibration controls for this display" and "This display is already calibrated" with BT.709, pure power curve 2.20. Gamma Processing works just the same. The problem is when I switch to a wider gamut option in my display I have no way to use my calibration profile. Again, Is there any way to use ICC Color Profiles (like MPC-HC does natively) without converting to 3D LUT? |
28th September 2013, 12:06 | #20146 | Link | |
Registered User
Join Date: Jun 2006
Posts: 15
|
Quote:
This is what I'm doing for now : Code:
playbackGraph.AddFilter(CommonFilter.MadshiVideoRenderer, "evr"); .../... (Building Graph : adding filters connecting pins) IVideoWindow videoWindow = playbackGraph.GraphBuilder.GetInterface<IVideoWindow>(); result = videoWindow.put_Owner(videoFrame.VideoHwnd); result = videoWindow.put_MessageDrain(videoFrame.VideoHwnd); result = videoWindow.SetWindowPosition(0, 0, (int)videoFrame.WindowSize.Width, (int)videoFrame.WindowSize.Height); result = videoWindow.put_WindowStyle(DSWindowStyle.Child | DSWindowStyle.Visible | DSWindowStyle.ClipSiblings); This window is created on the WPF UI thread (I have no other choices), while madVR is created on a dedicated thread (STA or MTA, with message pumping) This debanding feature is very nice. Thanks. |
|
28th September 2013, 12:17 | #20147 | Link | |
Registered User
Join Date: May 2009
Posts: 212
|
Quote:
Anyway I did a simple test and 3 images were taken for the comparison. The 1st one is regular lighting room condition. The 2nd one is the paused video at totally dark scene with mouse cursor moving around. The 3rd one is the same video w/o mouse cursor. The latter 2 photos were taken with ISO100 / 30sec / F1.4 setting. The camera is Panasonic GF2 + Leica DG 25mm. The GPU is HD7970 with 1920x1080p24 10-bit color mode signal to 65HX920. Video source is BD, MadVR setting is with Jinc3 AR, dithering ON, FSE. But I don't know if the GPU driver's 8-bit to 10-bit LUT (or even dithering?) could lead the different result... ? Yet it is confirmed LEDs will be shut-off entirely at the dark-zones of the 2nd one - just like the 3rd attached image. The 2nd one does show some light bleeding (more obvious at bottom of the panel) while it is not seen on the 3rd one. It can also observed by my eyes observing from the same off-angle. But I think it is the panel's design characteristics -- might be diffuser film related limitation. Anyway 65HX920's Innolux S-MVA panel, local dimming control, Corning Gorilla class seems to perform better than HX900's Sharp panel + glass (according to some reviews). |
|
28th September 2013, 17:35 | #20148 | Link | |
Registered User
Join Date: Apr 2009
Posts: 1,019
|
Quote:
Looks promising! I assume there will be a new tag so it can be selectively enabled/disabled? |
|
28th September 2013, 18:50 | #20149 | Link | ||
Registered User
Join Date: Sep 2013
Posts: 919
|
Anyone use the BT.709 Gamma profiles, and think they look like they got elevated blacks and too low gamma (1.95)?
That's because 709 gamma specs are for Encoding ONLY !!! NOT for calibrating displays, period. The film you are watching or a recording from a video camera is probably is already encoded with a standard 709 gamma. If its a professional Hollywood film aka (Blu Ray), its 100% encoded with rec.709 gamma curve. The Rec.709 gamma curve is encoded into the Camera while filming (or converted to in the studio). Your Display calibration should be a Pure Power Curve of 2.2 to 2.4. Again, The Rec.709 Standard refers to Encoding Only. The resulting video should be watched on a Pure Power Curve gamma display like a CRT or LCD. Why you ask? The 709 encoding gamma curve is designed to reduce the blacks below 1.8% of luminance to remove digital Camera noise. When we use the Inverse curve for calibrating displays (which we absolutely should NOT), we get elevated blacks below 1.8%, a gamma of 1.96, and a lower Contrast Ratio. When viewing a 709 encoded video on a properly calibrated monitor with a power curve of 2.2 to 2.4, these blacks (below 1.8%) are blacker than an encoded video with a pure power curve gamma of 0.45 or 0.50 (like with older SD NTSC standard). All this to eliminate the noise at the lower blacks 6233638 saw few posts ago, although not because of the same reason. Everything falls into place for our enjoyment of video watching. Quote:
Quote:
Question: Why madshi included BT.709 Display Gamma into MadVR? Hope this helps to clarify my confusion. Last edited by James Freeman; 28th September 2013 at 19:25. |
||
28th September 2013, 20:13 | #20152 | Link | |||
Registered User
Join Date: Jan 2008
Posts: 589
|
Quote:
Quote:
Quote:
That's a good question. Display gamma suffered from much confusion until ITU-R BT.1886 cleared everything up for us. Ideally madshi should remove BT.709 from the gamma options (because it is confusing and doesn't actually make sense) and add BT.1886 support, but that's a feature request, and last time I checked madshi isn't accepting feature requests right now. In the mean time, it is possible to use BT.1886 by generating a 3DLUT with Argyll. |
|||
28th September 2013, 20:40 | #20153 | Link | |
Registered User
Join Date: Apr 2011
Posts: 54
|
I update my OS (Windows 8.1 Pro), I have same problem again.
I noticed that when playing 1080p24 (mkv, m2ts, ts .. full screen exclusive mode, default settings) my screen goes to 23hz. Because of this, there is a drop frames every 30-40 sec. If I uncheck 'Present Several frames in advance "(old path), my screen stays in 24hz. Quote:
I have Sapphire Radeon HD 5670 Ultimate 1GB, Intel Core2 Duo E8400 3.00GHz, RAM 8 Gb Panasonic TX-P42G20E, Catalyst™ 13.9 Win8.1 Pro x64, JRiver Media Center 18 Ver. 18.0.212, madVR v0.86.11
__________________
Intel Core i7-4790 CPU @ 3.60GHz, RAM 32 GB Dual-Channel DDR3 @ 665MHz (9-9-9-24), Panasonic TX-P42G20E, NVIDIA GeForce GTX 970, Win 10 Pro x64, PotPlayer 1.7.16291 64-bit, madVR v0.92.17 Last edited by cvrkuth; 28th September 2013 at 20:56. |
|
28th September 2013, 20:45 | #20154 | Link | |
Registered User
Join Date: Apr 2009
Posts: 1,019
|
Quote:
If your display has 10,000:1 native contrast or greater, you should be using a straight 2.4 power curve. Because people requested it. And it can work reasonably well if people are still using CRTs without external LUT correction. (the 3DLUT support doesn't allow for enough customization for CRTs) |
|
29th September 2013, 05:59 | #20155 | Link | |
Registered User
Join Date: Mar 2009
Posts: 3,646
|
Quote:
Some questions: Will it have values that can be adjusted? Will the deband be done before or after resizing? And have you compared quality of deband before and after resizing? What's the general performance impact? Will there be a an HQ mode at all? |
|
29th September 2013, 06:00 | #20156 | Link | ||
Registered User
Join Date: Sep 2013
Posts: 919
|
Quote:
Quote:
Thank you for clarifing this. In the Rec. ITU-R BT.1886, Appendix 1, Its called EOTF-CRT matching. I calibrate with Argyll+DispCalGUI, I think Black output offset setting which is 100% offset correction for LCDs and 0% for CRT monitors. EDIT: Apparently to calibrate to the BT.1886 standard, "Black output offset" should be set to 0 with Gamma of 2.4. I'll try it tonight and report back. End of Edit. This corrects higher output black response (around 0.1 cd/m2) of an LCD in relation to the input to get a more accurate calibration. Meaning: No crushed blacks, simmilar to an CRT curve, and maximum Contrast Ratio that an LCD capable of. A BT.709 ecncoding curve is closer to 0.51 (1.96). 0.51 * 2.2 = 1.122 Its already darker than a linear representation. 0.51 * 2.4 = 1.224 Even darker. According to Rec. ITU-R BT.1886, The recommended gamma should be set around 2.4. But I find the end-to-end gamma of 1.22 (2.4) is a little too dark. When watching movies I sense 2.2 is just right (darkened room), sometimes around 2.0 is even better for shdow detail (with the lights On). Thanks. Last edited by James Freeman; 29th September 2013 at 09:24. |
||
29th September 2013, 06:43 | #20157 | Link |
Registered User
Join Date: Dec 2011
Posts: 180
|
Hi, I just tried the CRU recommend few pages ago, and my u2711 finally seem to able to do 23/24 hz
madvr report 23 and 24 as well, just curious, is it possible that the monitor scaler scale the 23/24 hz into 60hz? Or what is reported by madvr or reclock is definitely right? Sorry for kind of OP. |
29th September 2013, 10:38 | #20158 | Link | |||
Registered User
Join Date: Jan 2008
Posts: 589
|
Quote:
Quote:
Quote:
Last edited by e-t172; 29th September 2013 at 10:52. |
|||
29th September 2013, 12:15 | #20159 | Link |
Registered User
Join Date: Nov 2006
Posts: 21
|
Since early this month I've been having blue screens (3 total now) and I think it's related to madVR.
The blue screens happened when I dragged my video window downwards, so that some of the lower part of the window is below the taskbar (off screen), within a second a blue screen happens with the following error: 0x00000050 PAGE_FAULT_IN_NONPAGED_AREA The blue screens always have the same error (if you want I can upload the minidump(s) Windows made) but don't happen every time I drag my video window below the taskbar, only sometimes. I'm using MPC-HC v1.7.0.7771 x86 in combination with madVR v0.86.10 (with Windowed Overlay enabled), and my OS is Windows 7 x64 - SP1 If you want more information on this matter, tell me what you need, and I'll be happy to provide. |
29th September 2013, 13:05 | #20160 | Link | |||
Registered User
Join Date: Sep 2013
Posts: 919
|
Quote:
Annex 1 is the standard. Appendix 1 is the alternative. Quote:
Black Output Offset to 0. WILL give an exact BT.1886 gamma curve. I quote the text of argyll: "Note that using all input offset (degree == 0.0) is equivalent to the use of the BT.1886 transfer function." "Use "-G2.4 -f0" for BT.1886" Quote:
After reading the Argyll text, This is what Absolute vs Relative gamma does in Argyll. An Absolute gamma of 2.4 will NOT be 2.4 after taking the black offset of 0 into account, it will be lower as you've already stated. Also I have tried the BT.1886 calculator offered at the AVSforum and with my display (U2410, Contrast of 850:1) it practically does not matter what gamma I put into it, the result is almost always around 2.2. |
|||
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
Thread Tools | Search this Thread |
Display Modes | |
|
|