Reply to thread

Message

<blockquote data-quote="JMS" data-source="post: 29617" data-attributes="member: 13261">The DVB.NET 2.6 Beta for which I provided a link above includes a skeleton Direct Show filter (see BDA\JMS\DVB\Provider\BDA\DirectShow\Filters and therein PIDFilter and PIDPin). For my purpose it's working but it has some major limitiations (maybe at least you can take a look on it):1. It's an In-Memory filter and not registered or creatable from the outside. Personally I think this is not a major issue but I didn't check.2. It's a consuming only filter. So it doesn't deal with memory allocation or pushing samples through the graph. As a BDA outsider as well I have the strong feeling that this can be much of work to do.3. It's not stable - ok, it is right now BUT when I create the graph in an application which is marked with [STAThread] - which is the normal case - it leaks memory! On a [MTAThread] it runs fine. I think this is some issue with garbage collection in the concreate situation with a STA main thread and .NET code running on COM created threads - it has to do with the automatically created Run-time-Callable Wrappers which will not be freed. I reported this to Microsoft but got no response (<a href="http://msdn.microsoft.com/newsgroups/managed/default.aspx?dg=microsoft.public.dotnet.framework.interop&amp;mid=c528eb96-2019-4aec-8b9d-05a1834e9caf&amp;sloc=en-us" target="_blank">here</a>, I don't know, if you can see the thread without registering). For now and my goal I got a work-around but this is not sufficient - especially the trick will no longer work with .NET 2.0.To summerize: don't give up so fast and try to have Fun&nbsp; 8) Jochen</blockquote>

[QUOTE="JMS, post: 29617, member: 13261"] The DVB.NET 2.6 Beta for which I provided a link above includes a skeleton Direct Show filter (see [i]BDA\JMS\DVB\Provider\BDA\DirectShow\Filters[/i] and therein [i]PIDFilter[/i] and [i]PIDPin[/i]). For my purpose it's working but it has some major limitiations (maybe at least you can take a look on it): 1. It's an In-Memory filter and not registered or creatable from the outside. Personally I think this is not a major issue but I didn't check. 2. It's a consuming only filter. So it doesn't deal with memory allocation or pushing samples through the graph. As a BDA outsider as well I have the strong feeling that this can be much of work to do. 3. It's not stable - ok, it is right now [b]BUT[/b] when I create the graph in an application which is marked with [STAThread] - which is the normal case - it leaks memory! On a [MTAThread] it runs fine. I think this is some issue with garbage collection in the concreate situation with a STA main thread and .NET code running on COM created threads - it has to do with the automatically created [i]Run-time-Callable Wrappers[/i] which will not be freed. I reported this to Microsoft but got no response ([url=http://msdn.microsoft.com/newsgroups/managed/default.aspx?dg=microsoft.public.dotnet.framework.interop&mid=c528eb96-2019-4aec-8b9d-05a1834e9caf&sloc=en-us]here[/url], I don't know, if you can see the thread without registering). For now and my goal I got a work-around but this is not sufficient - especially the trick will no longer work with .NET 2.0. To summerize: don't give up so fast and try to have Fun 8) Jochen [/QUOTE]

Verification