search

cplussharp / graph-studio-next

GraphStudioNext is a tool for developers to build and test DirectShow Graphs
355 stars 94 forks source link

Non-null renderers cap performance test #307

Open mirh opened 7 years ago

mirh commented 7 years ago

I mean, when the actual video is played back, it is sped up normally as I'd expect. But when result is reported in the "results window" everything seems like bottlenecked to monitor refresh rate.

mikecopperwhite commented 7 years ago

Thanks for the report.

In my experience this seems to be a limitation of some video renderer filters. It may be possible to work around it by building with a different video renderer filter but unless you're testing overall rendering performance it would be simpler to use a null renderer filter. I don't think this frame rate limit is something we can change in GSN.

mirh commented 7 years ago

DXVAchecker benchmark has no problem in doing so with, say, LAV video decoder.

mikecopperwhite commented 7 years ago

Sounds like the graph building logic in this dialog needs to be amended to choose a different default video renderer as limiting to frame rate to the monitor refresh rate is clearly not helpful when the graph is being created for performance testing.

mirh commented 7 years ago

I'm starting to think the problem may be on the fps_calculating logic, realtime_ns specifically. Because thinking better, there's no way the rate of a 26 seconds(\@ 15~30FPS) video played back in 11 seconds to be 1x.