|Anonymous | Login | Signup for a new account||2018-03-24 07:11 CET|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000465||madVR||bug||public||2017-01-14 19:11||2018-01-14 12:36|
|Platform||PC||OS||Windows||OS Version||Windows 10|
|Summary||0000465: Composition Rate and D3D11|
|Description||I like to watch my 23.976fps movies in FSE, but if I check the "use Direct3D 11 for presentation" option, the composition rate always sets itself to 24.000 instead of 23.976. Of course, leaving this option off sets the composition to 23.976.|
To be honest, I'm not sure how big a deal this is, but I noticed it by accident and am wondering if it'll maybe cause any judder issues. Also I'd like to be able to keep on using D3D11 for 10 bit output.
|Tags||No tags attached.|
|Media Player (with version info)||MPC-HC 18.104.22.1686|
|Splitter (with version info)||LAV 0.69.0|
|Decoder (with version info)||LAV 0.69.0|
|DXVA2 Scaling Active||no|
|Aero / Desktop Composition||Off|
|Problem occurs with mode||fullscreen exclusive mode|
|GPU Model||GTX 1080|
|GPU Driver Version||376.19|
|Attached Files|| Rendering.png [^] (115,573 bytes) 2017-01-17 05:32
|Speaking of 10 bit output, is there a way to get MadVR to change the bit depth as well as the refresh rate when it changes display mode? Up until now I've just been doing it manually every time before I watch a movie. Unfortunately I can't just leave my PC at 4K60 at 10 bits, haha.|
In FSE mode the composition rate should not even be displayed at all, so I'm a little bit confused right now. Does the OSD say you're really in FSE mode? If it does, you can ignore the composition rate (if it's shown which it shouldn't). The composition rate should only have a meaning in windowed or fullscreen windowed mode.
The win32 API doesn't allow me to change bitdepths. I can only tell D3D11 that I want to render to 10bit. Whether the GPU actually outputs 10bit (or less or more) is outside of my control.
edited on: 2017-01-17 05:33
It does indeed say "exclusive" as opposed to "overlay" or "windowed". But you said it's safe to ignore the composition rate? It'll still change to other odd numbers, such as 59Hz, if I add 59 as a display mode. It's just 23.976 that it doesn't get down to. Hoping it's not a big deal, like you said.
Anyway, yeah, Windows can't change bitdepth because only discrete GPUs can output above 8 bits anyway, and they have their own drivers. I tried looking into NvAPI, which can apparently output HDR metadata (I actually got it working but eh), so theoretically it should also be able to change bit depth. Oh well, something for the future, in any case.
Also added my rendering settings, just in case. Let me know if you need anything else.
I'm planning to look into NVAPI in the future.
Not sure what's up with the composition rate. One thing you can try is play a scene with a very smooth motion to see if there's any judder/stuttering. E.g. "The Book of Eli" has a smooth horizontal camera pan at the beginning, IIRC. If the 24.000 composition rate produces a problem, there should be judder at least once every ~ 42 seconds.
|Closing this one because madVR really has no way to influence the actively composition rate, so it's completely out of my hands.|
|2017-01-14 19:11||Zyxas||New Issue|
|2017-01-14 23:52||Zyxas||Note Added: 0001570|
|2017-01-16 22:17||madshi||Note Added: 0001573|
|2017-01-17 05:28||Zyxas||Note Added: 0001574|
|2017-01-17 05:32||Zyxas||File Added: Rendering.png|
|2017-01-17 05:33||Zyxas||Note Edited: 0001574||View Revisions|
|2017-01-17 09:11||madshi||Note Added: 0001575|
|2018-01-14 12:36||madshi||Note Added: 0002020|
|2018-01-14 12:36||madshi||Status||new => closed|
|2018-01-14 12:36||madshi||Assigned To||=> madshi|
|2018-01-14 12:36||madshi||Resolution||open => not fixable|
|Copyright © 2000 - 2012 MantisBT Group|