Quote:
Originally Posted by agustin9
Hi madshi, can you make the statistics display the current frame rate like evr-cp?
|
Yes, I can. But I won't, at least not any time soon. It would cost me many hours to implement that. That time is better spent elsewhere, IMHO.
Quote:
Originally Posted by nevcairiel
As if there is a way to communicate from the splitter up to the renderer. The decoder would swallow that information.
Really, most video codecs have fields for that in their header, doing that in the container is just backwards.
|
I agree that this information should be in the video bitstream. But we're not living in an ideal world, so we have to do the best we can do with imperfect files. From an end user point of view, if the container does contain primaries information and the video bitstream does not, then the information from the container should be used. From a DirectShow point of view this is perfectly possible. The splitter can output this information via VIDEOINFOHEADER2, the decoder can then forward this information to the renderer. Ok, no decoder today does that (except for the madVR internal decoders, haha, but that doesn't count, I guess). But hey, you're developing both a splitter and a decoder...
BTW, doesn't the same logic already apply to e.g. the aspect ratio and to the frame rate? E.g. if the container contains AR and FPS information and the video bitstream does not, doesn't the splitter output both and the decoder forward both? At least that's how it should be, IMHO.
Quote:
Originally Posted by DragonQ
I thought with the YADIF option enabled in LAV, the deinterlacing is being done by LAV itself, before MadVR gets the frames?
|
With YADIF enabled in LAV you should see "50.000 fps (says source filter)". If you don't then you need to talk to nevcairiel.