Quote:
Originally Posted by TheElix
Regarding automatic display mode matching. I think it's bugged or I just use it incorrectly. "1080p23, 1080p25, 1080p29, 1080p50, 1080p59" is what I have there but it switches to 1080p23 on every video, even 25p or 30p. So even though source filter says the video is 29.970 or 59.940 it still switches to 23.976.
|
Make sure you only enter modes which really exist. 1080p29 is not a mode commonly used, I rather doubt your GPU actually supports it (without a custom resolution). If you still think there's a problem, upload a debug log and I can tell you why madVR did what it did.
Quote:
Originally Posted by 6233638
Does this mean that I can use CalMAN to create LUTs for madVR now?
|
Yes. At least in theory. I don't have a Calman license, so I can't test it. I tested it with eeColor LUTs created by ArgyllCMS and cross checked that LightSpace eeColor LUTs have the same format. So I suppose it should also work for Calman.
However, Calman does not support the madVR test pattern generator yet, so you'll need to use a different way to do the measurements. Obviously, it would be nice if Calman supported the madVR test pattern generator. They did express interest in maybe adding support for it. But I guess only if licensed Calman customers are actually asking for it, they will actually do something...
So, all Calman customers who're interested in having Calman support the madVR test pattern generator, now would be a good time to ask them about it.
Quote:
Originally Posted by dansrfe
Also madshi, not sure if this is an actual bug but having more than one madVR instance running in overlay mode causes subsequent instances to now show anything other than a black screen.
|
Known problem.
Quote:
Originally Posted by Thunderbolt8
why is that?
|
Because software decoding is faster (if you have a decent CPU) and more reliable. No stupid limits like max number of reference frames, no hardware decoding bugs, no bluescreens or crashes etc...