Reply to thread

Message

<blockquote data-quote="draktheas" data-source="post: 29434" data-attributes="member: 17330">So after a little research (and I mean a little), there are a few ways I could go with this:1) Hardcode the functionality we need into several places in MP and talk directly to the TT API. This is not good as it will polute the current MP code base with a lot of special case code and it's not very useful given that MP appears to want to link to a Directshow graph with it's components.2) Build a Directshow graph that talks to the TT API and has output pins that I can link to the components used in MP. This seems to be the way that the SS2 was done. However, the SS2 already had a Directshow filter to hook into. So I would have to write the filter, the DVBGraphTTPremium component, and the appropriate code in the device scan to pickup the new TT Directshow filter.3) Attempt to create a BDA driver that talks to the TT API. As I don't know much about the requirements of BDA, this would take more time and be more error prone. But this would also be the most flexible approach as it would allow any software supporting BDA to access the TT Premium card through my work.I am heavily leaning toward option 2 right now, because it seems to be the most flexible given the current knowledge that I have. Any opinions, advise, or comments?Drak</blockquote>

[QUOTE="draktheas, post: 29434, member: 17330"] So after a little research (and I mean a little), there are a few ways I could go with this: 1) Hardcode the functionality we need into several places in MP and talk directly to the TT API. This is not good as it will polute the current MP code base with a lot of special case code and it's not very useful given that MP appears to want to link to a Directshow graph with it's components. 2) Build a Directshow graph that talks to the TT API and has output pins that I can link to the components used in MP. This seems to be the way that the SS2 was done. However, the SS2 already had a Directshow filter to hook into. So I would have to write the filter, the DVBGraphTTPremium component, and the appropriate code in the device scan to pickup the new TT Directshow filter. 3) Attempt to create a BDA driver that talks to the TT API. As I don't know much about the requirements of BDA, this would take more time and be more error prone. But this would also be the most flexible approach as it would allow any software supporting BDA to access the TT Premium card through my work. I am heavily leaning toward option 2 right now, because it seems to be the most flexible given the current knowledge that I have. Any opinions, advise, or comments? Drak [/QUOTE]

Verification