Reply to thread

Message

<blockquote data-quote="and-81" data-source="post: 130178" data-attributes="member: 11844">It's a bug in MediaPortal.&nbsp; TVE2.Only when a scheduled recording is started MediaPortal neglects to update which tuner card to use before sending the Tune External Channel message.&nbsp; This can then lead to the wrong tuner card number being sent along with the GUI_MSG_TUNE_EXTERNAL_CHANNEL.&nbsp; If the tuner card number variable hasn't been initialised yet then it can be -1.&nbsp; Needless to say, this causes a lot of problems when my plugin tries to find the settings for tuner card -1.We tried to fix this with a patch that was in SVN for a few weeks, but it turned out that the patch caused some other unexpected problems.There's more information about the problem here:<a href="https://forum.team-mediaportal.com/tv_server_provides_unexpected_tv_card_number-t19165.html" target="_blank">https://forum.team-mediaportal.com/tv_server_provides_unexpected_tv_card_number-t19165.html</a>and here:<a href="http://sourceforge.net/tracker/index.php?func=detail&amp;aid=1621185&amp;group_id=107397&amp;atid=647927" target="_blank">http://sourceforge.net/tracker/index.php?func=detail&amp;aid=1621185&amp;group_id=107397&amp;atid=647927</a>It does effect the MyBlaster plugin because MyBlaster tries to match a TV card to a blaster port, and when it is given -1 as the card it will just use whatever the last blaster port used was.&nbsp; Of course this will only effect users with two TV cards.&nbsp; Whereas in my plugin it will crash the plugin (though I'm working on fixing that).I'm going to be putting some effort into finding a solution, but having said that, I thought I'd already found a solution.&nbsp; The patch we put in failed for some unknown reason so I think we need one of the more experienced dev's to have a look at this problem.&nbsp; I don't know if I have a deep enough understanding of the TVE2 to fix this. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown&nbsp; &nbsp; :(" loading="lazy" data-shortname=":(" />Cheers,</blockquote>

[QUOTE="and-81, post: 130178, member: 11844"] It's a bug in MediaPortal. TVE2. Only when a scheduled recording is started MediaPortal neglects to update which tuner card to use before sending the Tune External Channel message. This can then lead to the wrong tuner card number being sent along with the GUI_MSG_TUNE_EXTERNAL_CHANNEL. If the tuner card number variable hasn't been initialised yet then it can be -1. Needless to say, this causes a lot of problems when my plugin tries to find the settings for tuner card -1. We tried to fix this with a patch that was in SVN for a few weeks, but it turned out that the patch caused some other unexpected problems. There's more information about the problem here: [url]https://forum.team-mediaportal.com/tv_server_provides_unexpected_tv_card_number-t19165.html[/url] and here: [url]http://sourceforge.net/tracker/index.php?func=detail&aid=1621185&group_id=107397&atid=647927[/url] It does effect the MyBlaster plugin because MyBlaster tries to match a TV card to a blaster port, and when it is given -1 as the card it will just use whatever the last blaster port used was. Of course this will only effect users with two TV cards. Whereas in my plugin it will crash the plugin (though I'm working on fixing that). I'm going to be putting some effort into finding a solution, but having said that, I thought I'd already found a solution. The patch we put in failed for some unknown reason so I think we need one of the more experienced dev's to have a look at this problem. I don't know if I have a deep enough understanding of the TVE2 to fix this. :( Cheers, [/QUOTE]

Verification