Yes it seems a bug with the MediaPortal Stream Analyser. This is being replaced in the future TV engine so I suggest you add the channels manually until the new release.
Thanks for getting back to be. This makes sense and I look forward to the replacement software.
I am however conffused as to how exactly I add a channel manually as the data for all the required fields is not available on for example astras channel information see this link:
Sorry mate I tried to add the channels manually and they still don't appear in the channel list. So don't actually have them. I am hoping that the new engine will fix the problem.
hye guys!
Stop searching for the bug. I have had these weird channel-search-problem too. Turns out that there is no full diseqc-support for The Nova-s plus implemented. I talked to the programmers, and they told me that someone has to implement disqc-support for this card himself. The MP-programmers wont do that, because they cant or wont...
MP actualy can't switch between the diseqc-modes or something. If u use another prog and watch on the desired channel MP will find it, but none of the channels on the other diseqc and vice versa..... so someone needs to implement diseqc-support for that card
I think this must be a white elephant so to speak.
If DISEqC was the problem then I would not have been able to use my DVB-S Nova-S Plus previously.
I have checked Hauppauges forum which is not a lot of good and lots of people are having the same problems even with Hauppauges own software!
Someone on there has suggested that its to do with a patch MS applied, can't comment on that as the patch refers to a change back in May and my card was still working until July with all current Microsoft Patches applied.
I believe it is a problem, somewhere in the DirectShow area. So, either an MS breakage or a problem with the MediaPortal Stream Analyser.
Thinking about it, I must have a try with MyTheatre -- that doesnt use the MS DirectShow filters for controlling the streams and also would obviously remove the MSA -- if it works it would at least prove the problem is DirectShow [or driver !!] related.