It will have - changes to the FFDShow workaround (this isn't actually an MP bug, it's an FFDShow 'feature') won't happen until a later version of MP.
Also it would be better to come up with a more elegant, more automatic workaround for this particular problem (where the CoreCC parser filter is inserted between TsReader.ax and FFDShow).
No, but the closed-caption support was added in 1.3.0 alpha - it's inserting the extra (CC parser) filter between TsReader and FFDShow that stops TsReader detecting FFDShow video decoder (and hence enabling the workaround). When this was done no-one realized that this would break the FFDShow workaround if CC is enabled.
It's more complicated to fix it than it might seem, because it's important to *only* enable the workaround when FFDShow video decoder is actually being used for MPEG2 decoding (i.e. it's not just in the graph for post-processing etc).
I see. I started using Core CC Parser long time ago. It is not perfect but the only working tool that supports North American ATSC CC. I have some frame drops when enabling it, but it works. Maybe my case is a bit more complicated because I have a dual screen. And contrary to official recommendations, enabling aero causes terrible stuttering: https://forum.team-mediaportal.com/...nitor-and-windows-7-aero-theme-enabled.96628/