home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Development
General Development (no feature request here!)
[Patch] MultiTuner Bug with different PVR cards
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Frodo" data-source="post: 30945" data-attributes="member: 10277"><p>FlipGer, i debugged the original cvs code and looked at your patch</p><p>The original cvs code is working for me.</p><p>I do have a PVR 350 which works just fine for me </p><p>(Note i dont have a PVR 150) </p><p></p><p>I did not add your patch to CVS yet, since i fail to see why this</p><p>would be correct.</p><p>Instead of using the filter moniker string, you are now using the</p><p>moniker based on the capture filter moniker. </p><p>Let me explain:</p><p>a graph normally consists of filters. each filter has a moniker string.</p><p>A pvr 150 for example has</p><p>- tv tuner filter</p><p>- audio tuner filter</p><p>- crossbar filter</p><p>- capture filter</p><p></p><p>Now for hauppage all these filters have the same moniker format and thus your patch will work.</p><p>example for the PVR 150 all filters have this part in the filter monikers:</p><p><strong> ven_4444&amp;dev_0016&amp;subsys_88010070&amp;rev_01</strong></p><p></p><p>However some other cards (like twinhan) have completely different filters for each filter</p><p>example the twinhan tuner filter may look like</p><p><strong>ven_109e&amp;dev_0878&amp;subsys_00011822&amp;rev_11</strong></p><p>and the twinhan capture filter may look like</p><p><strong>vid_0fe9&amp;pid_db50</strong></p><p></p><p>Now when i apply your patch, it always uses the capture filter moniker to determine the unique filter name. I have the feeling that this will fail for the twinhan look-a-like cards?</p><p></p><p>Frodo</p></blockquote><p></p>
[QUOTE="Frodo, post: 30945, member: 10277"] FlipGer, i debugged the original cvs code and looked at your patch The original cvs code is working for me. I do have a PVR 350 which works just fine for me (Note i dont have a PVR 150) I did not add your patch to CVS yet, since i fail to see why this would be correct. Instead of using the filter moniker string, you are now using the moniker based on the capture filter moniker. Let me explain: a graph normally consists of filters. each filter has a moniker string. A pvr 150 for example has - tv tuner filter - audio tuner filter - crossbar filter - capture filter Now for hauppage all these filters have the same moniker format and thus your patch will work. example for the PVR 150 all filters have this part in the filter monikers: [b] ven_4444&dev_0016&subsys_88010070&rev_01[/b] However some other cards (like twinhan) have completely different filters for each filter example the twinhan tuner filter may look like [b]ven_109e&dev_0878&subsys_00011822&rev_11[/b] and the twinhan capture filter may look like [b]vid_0fe9&pid_db50[/b] Now when i apply your patch, it always uses the capture filter moniker to determine the unique filter name. I have the feeling that this will fail for the twinhan look-a-like cards? Frodo [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
[Patch] MultiTuner Bug with different PVR cards
Contact us
RSS
Top
Bottom