I'm working on a software application that assembles filtergraphs piecemeal by selecting individual filters by GUID/CLSID. With LAVFilters simply installed, it causes this application to be unable to properly create any filtergraph.
On a barebones fresh Windows installation with no other third-party filters except LAVFilters installed, what appears to be the same problem also manifests in that when trying to add a filter via GraphEdt.exe (Ctrl+F), the act of twirling down the pulldown menu for DirectShow Filters causes GraphEdt.exe to crash to desktop with Exception code: 0xc00000fd (as reported by Event Viewer), or in other words a stack overflow.
However, pressing Ctrl+R and opening an HEVC video file in GraphEdt.exe DOES work, and you're able to right-click > Filter Properties... to successfully reveal the LAV Video Decoder Properties window.
This is a bug in GraphEdit, because it stores filter information on the stack, and runs out of space if a filter supports too many formats. Use GraphStudioNext.
I'm working on a software application that assembles filtergraphs piecemeal by selecting individual filters by GUID/CLSID. With LAVFilters simply installed, it causes this application to be unable to properly create any filtergraph.
On a barebones fresh Windows installation with no other third-party filters except LAVFilters installed, what appears to be the same problem also manifests in that when trying to add a filter via GraphEdt.exe (Ctrl+F), the act of twirling down the pulldown menu for DirectShow Filters causes GraphEdt.exe to crash to desktop with Exception code: 0xc00000fd (as reported by Event Viewer), or in other words a stack overflow.
However, pressing Ctrl+R and opening an HEVC video file in GraphEdt.exe DOES work, and you're able to right-click > Filter Properties... to successfully reveal the LAV Video Decoder Properties window.