- This topic has 6 replies, 2 voices, and was last updated 6 years, 3 months ago by
.
-
Posts
-
Hi,
It’s a Windows 10 system with an actual DisplayCAL 3.4 version. There is an issue with the color profile loader, it doesn’t re-apply correction after use of madVR if Kodi/DSPlayer is still running.
Profile is applied without issue after Windows startup . Profile is still applied after Kodi startup. Profile is disabled when a video is playing because madVR is detected – it’s expected. Profile is still disabled after video playback is ended, profile loader says that madVR is detected but there’s no any video just a Kodi window – it’s the issue. Profile is re-applied again after Kodi is closed.If Kodi keeps the madVR instance loaded (which I would expect), then this will of course be detected (you can’t see this visually). It is not important if a video is playing or not.
I understand. Is it possible to improve the madVR detection method, maybe do it more explicit, e.g. request some interface? In any case there is a dedicated logic for madVR exist.
There is nothing to improve. While madVR is active, it controls the videoLUT, and nothing else must interfere. If you want madVR to not use the videoLUT, enable windowed overlay in its rendering settings.
From a user’s point of view madVR is not active – there’s no video playback. But there could be another task that would benefit from a proper calibration, e.g., a photo viewer.
There is nothing to improve. While madVR is active, it controls the videoLUT, and nothing else must interfere.
When something is loaded it doesn’t necessarily mean it’s active and gets control. I’m sure you know it. There’s no crime in retaining refs to loaded components.
Sorry for bothering you.From a user’s point of view madVR is not active
That doesn’t matter though. What matters is whether it is actively controlling the videoLUT or not, irrespective if this is visible to the user in any other way. And it is when it has created (and not yet destroyed) its own (hidden) window which DisplayCAL detects and then checks wether or not madVR has reset the videoLUT. And if it has, the profile loader disables itself, and that is the only correct course of action. There’s no two ways around it.
But there could be another task that would benefit from a proper calibration, e.g., a photo viewer.
See above. You want to use windowed overlay in that case.
And it is when it has created (and not yet destroyed) its own (hidden) window which DisplayCAL detects and then checks wether or not madVR has reset the videoLUT.
If that window wasn’t destroyed after a video playback end, then it seems as a Kodi/DSPlayer or madVR issue. Thanks.
You want to use windowed overlay in that case.
Should a calibration data not be included in a 3D-LUT for madVR in that case? There could be different calibration targets for video and photo usage.
