Normal
I wish you'd said that earlier! BSOD'ing during the analog TV scan is a known compatibility issue with HVR-22** tuners. It seems to be an issue with newer versions of the tuner driver. Please see this thread for more information and an older driver that we know works properly:https://forum.team-mediaportal.com/threads/hvr-2250-scanning-channels-causes-crash.102858/It would be great if you could report this problem to Hauppauge. The more reports they receive, the more chance there is that the problem will be fixed.The TV Server used by MP2 is identical to the one used by MP1 for all aspects of analog TV tuning, so a difference in behaviour is not expected.You can choose to use MP2 if you want, but please keep in mind that I can't help you with MP2.Yes, there's nothing wrong with the hardware. The reason for the difference in behaviour/results is probably that WinTV7 and TV Server code is different with respect to scanning. Since WinTV7 is closed source we can't see how to workaround the problem in our code.Yes, from LinuxTV info it looks like the E900F is also an SAA7164-based design with NXP TDA18271 tuners and NXP TDA10048HN demodulators. The two cards may be based on an NXP reference design with reference driver. However I'm sure AVerMedia and Hauppauge have differences within their drivers.Interesting. My suspicion is that the problem may be related to the encoder's handling of noisy/low/zero signal, but I could be completely wrong. Please make sure to mention this information if/when you report the problem to Hauppauge.With the greatest respect, I think it may be very time consuming (if not practically impossible) for you to solve this problem with debugging. You cannot catch, prevent or ignore a BSOD generated from within the driver. The best you may be able to do is identify which code or conditions are triggering the BSOD. I suspect it will be something within this function:https://github.com/MediaPortal/MediaPortal-1/blob/master/TvEngine3/TVLibrary/TVLibrary/Implementations/Analog/Components/Tuner.cs#L460...or perhaps something related to the DirectShow graph handling (eg. graph must always be stopped or started when tuning is performed).Hauppauge will be able to debug their driver properly and/or analyse memory dumps to find and fix the source of the BSOD within the driver. IMHO that is the better way to handle the problem.Regards,mm
I wish you'd said that earlier!
BSOD'ing during the analog TV scan is a known compatibility issue with HVR-22** tuners. It seems to be an issue with newer versions of the tuner driver. Please see this thread for more information and an older driver that we know works properly:
https://forum.team-mediaportal.com/threads/hvr-2250-scanning-channels-causes-crash.102858/
It would be great if you could report this problem to Hauppauge. The more reports they receive, the more chance there is that the problem will be fixed.
The TV Server used by MP2 is identical to the one used by MP1 for all aspects of analog TV tuning, so a difference in behaviour is not expected.
You can choose to use MP2 if you want, but please keep in mind that I can't help you with MP2.
Yes, there's nothing wrong with the hardware. The reason for the difference in behaviour/results is probably that WinTV7 and TV Server code is different with respect to scanning. Since WinTV7 is closed source we can't see how to workaround the problem in our code.
Yes, from LinuxTV info it looks like the E900F is also an SAA7164-based design with NXP TDA18271 tuners and NXP TDA10048HN demodulators. The two cards may be based on an NXP reference design with reference driver. However I'm sure AVerMedia and Hauppauge have differences within their drivers.
Interesting. My suspicion is that the problem may be related to the encoder's handling of noisy/low/zero signal, but I could be completely wrong. Please make sure to mention this information if/when you report the problem to Hauppauge.
With the greatest respect, I think it may be very time consuming (if not practically impossible) for you to solve this problem with debugging. You cannot catch, prevent or ignore a BSOD generated from within the driver. The best you may be able to do is identify which code or conditions are triggering the BSOD. I suspect it will be something within this function:
https://github.com/MediaPortal/MediaPortal-1/blob/master/TvEngine3/TVLibrary/TVLibrary/Implementations/Analog/Components/Tuner.cs#L460
...or perhaps something related to the DirectShow graph handling (eg. graph must always be stopped or started when tuning is performed).
Hauppauge will be able to debug their driver properly and/or analyse memory dumps to find and fix the source of the BSOD within the driver. IMHO that is the better way to handle the problem.
Regards,
mm
