There seems to be several issues with the media portal directshow filters. My hope is for this thread to get developers to look into it and fix the problems.
1) Playing a TS file in potplayer with the mediaportal filters causes the program to start using every GB of available RAM until it eventually crashes. I found that the cause is "DVBSub2.ax". Without it there is no memory leak. As soon as it is added while keeping everything else the same... memory leak.
2) The filters behave in unusual ways that cause problems in the directshow framework. To quote the zoom player dev:
[The TSFileReader] audio pin exposes data that can be identified as video. ... with the modification I added, the pin will be scanned for both audio and video. The same for the subtitle. They could output subtitle in a way that is compatible with other subtitle renderers (VobSub for example), but what they do require their custom subtitle filter.
Can TSFileSource be fixed at least for the audio/video/subtitle pins to be identified as such? Can changes be made so that custom code *is not* required in each video player in order to support the directshow filters??
3) There is a further compatibility issue with TSFileSource regarding seeking on resuming files. It seems that the filter isn't accepting the seek command right at the start of playback. Again this is something that only the mediaportal filters have issue with and have probably rather unfortunately been fixed in the mediaportal application rather than in the filter themselves.
1) Playing a TS file in potplayer with the mediaportal filters causes the program to start using every GB of available RAM until it eventually crashes. I found that the cause is "DVBSub2.ax". Without it there is no memory leak. As soon as it is added while keeping everything else the same... memory leak.
2) The filters behave in unusual ways that cause problems in the directshow framework. To quote the zoom player dev:
[The TSFileReader] audio pin exposes data that can be identified as video. ... with the modification I added, the pin will be scanned for both audio and video. The same for the subtitle. They could output subtitle in a way that is compatible with other subtitle renderers (VobSub for example), but what they do require their custom subtitle filter.
Can TSFileSource be fixed at least for the audio/video/subtitle pins to be identified as such? Can changes be made so that custom code *is not* required in each video player in order to support the directshow filters??
3) There is a further compatibility issue with TSFileSource regarding seeking on resuming files. It seems that the filter isn't accepting the seek command right at the start of playback. Again this is something that only the mediaportal filters have issue with and have probably rather unfortunately been fixed in the mediaportal application rather than in the filter themselves.