TV-Server crashes on scanning channels with Hauppauge WinTV HVR-900H (2 Viewers)

[Curry]

Thanks in advance for the efforts The HVR-900H is an updated version of the HVR-900, see this page on their Dutch site (it's even on the hvr900.html page ). The product number is also updated from 650xx to 660xx as you can see in the product dropdown on the UK support page.

According to the site:
- The 900 uses drivers "Driver Version 5.8.26322 (HVR-9x0_5_8_1107_26322_WHQL.zip)"
- The 900H uses drivers "Driver Version 1.0.709.27051 (HVR-900H_1_0_709_27051_WHQL.zip)"

I still have the Windows XP setup available for testing so I'll use that one for the current testing until Win7 is formally supported (got both setups available for testing).

And besides the glitch that in the WinTV-CI configuration tab it displays all my TV-Cards 3 times

Actually it adds all TV-cards every time it wants to update configuration so you can get them all 20 or 200 times if you want I also found it curious that it keeps showing the WinTV-CI tab forever if once detected, even if the system is rebooted without the CI device connected.

On a related note - if the WinTV-CI tab is used, how should I formally configure the DVB-T card in the first tab, enable or disable the CAM support there?

But it would not dare to recommend someone to buy that thing. Better spend some more money on a decent card with integrated CI. Such as the floppy, or firedtv. Works out of the box.

Sadly I'm limited to USB connectivity for both my setups The XP machine is a Samsung TV with integrated mini-computer (320MXN) and the Win7 is an AOpen MP45-BDR minisystem without PCIe expansion slots. TV generally isn't important to me so the setups weren't exactly chosen with top quality TV in mind, and to be fair to Hauppauge the WinTV 6 and 7 software works right out of the box with good enough quality, both for FTA and encrypted channels, and Media Center also had no problems with the scanning or showing FTA channels (I didn't install the CI patch for WMC).

 

[infinite.loop]

On a related note - if the WinTV-CI tab is used, how should I formally configure the DVB-T card in the first tab, enable or disable the CAM support there?

enable - or it wont work.

Sadly I'm limited to USB connectivity for both my setups

no firewire?

and to be fair to Hauppauge the WinTV 6 and 7 software works right out of the box with good enough quality, both for FTA and encrypted channels, and Media Center also had no problems with the scanning or showing FTA channels (I didn't install the CI patch for WMC).

I you do not use the WInTV-CI and just tune to FTA channels, do you still have problems with MediaPortal?

 

[Curry]

On a related note - if the WinTV-CI tab is used, how should I formally configure the DVB-T card in the first tab, enable or disable the CAM support there?

enable - or it wont work.

Right.... funnily I'm pretty sure it also crashes if it's disabled on that screen Can't test right now though since I'm at work.

Sadly I'm limited to USB connectivity for both my setups

no firewire?

Neither of them

I you do not use the WInTV-CI and just tune to FTA channels, do you still have problems with MediaPortal

Nope, it's definitely in the CI interfacing, as said "Scan fails without crashing with CI removed. It should still find the FTA channels and probably also the encrypted channels?"

I'm not sure how the CAM was configured for the card at the time, and on a much earlier occasion with older drivers I did find channels and manage to watch FTA for a short while (it crashed after a few seconds of playing instead of during scan). That was with the CD-drivers for the CI which were older than the recommended minimum version.

 

[infinite.loop]

If you scan for channels with a card, it will always find all FTA and scrambled channels.
A CI, CAM or smartcard is not required for a scan.

Just tested scaning dvb-s(2) here with Nova-s2-hd and WinTV-Ci attached. it works.
i just can try to get my hands on an HVR900H. but i can not promis anything. :sorry:

 

[Curry]

No worries I'll gladly help where I can If the crash wasn't at driver level I'd have attached a VS.NET debugger to it myself already, but if the crash is uncatchable that's an impossible job for me as a developer without inside knowledge of the TV-Server and PC-TV systems in general

You're also using CI drivers 1.3607.26283.0? Is it possible that there's a difference between DVB-T and DVB-S interfacing?

Could you point me to the files in SVN where the WinTV-CI interfacing resides, I'm curious about how it works internally - if it looks manageable I might be able to debug a bit myself.

[edit] found the files in TVLibrary.Implementations.DVB.ConditionalAccess.HaupPauge.WinTvCiModule.cs, looks testable enough...

 

[morpheus_xx]

Hi all,

just want to tell you about some development progress: https://forum.team-mediaportal.com/...knc1-technotrend-54163/index4.html#post473094

I added CI menu capabilities for FireDTV. And now I'm working to get WinTV CI integrated also. So if someone of you like to help to get it working, please look at this thread.

I can post updated dll based on the download version to test changes.

Post inside the linked thread if you want join testing...

Morpheus

 

[Curry]

Just did another round of testing with:
- WinXP SP3
- HVR-900H connected with antenna
- WinTV CI not connected
- Latest drivers as mentioned before in this thread

TVServer configuration reports 'no signal' for all frequencies, error.log shows the following for *every* frequency scanned:

2009-06-14 22:17:36.625000 [10]: Exception   :TvLibrary.TvException: No Tv Receiver filter found
   bij TvLibrary.Implementations.DVB.TvCardDvbBase.AddAndConnectBDABoardFilters(DsDevice device)
   bij TvLibrary.Implementations.DVB.TvCardDVBT.BuildGraph()

2009-06-14 22:17:36.640625 [10]: Exception   :System.AccessViolationException: Poging tot het lezen of schrijven van beveiligd geheugen. Dit duidt er vaak op dat ander geheugen is beschadigd.
   bij DirectShowLib.IMediaControl.StopWhenReady()
   bij TvLibrary.Implementations.DVB.TvCardDvbBase.Decompose()
   bij TvLibrary.Implementations.DVB.TvCardDvbBase.Dispose()
   bij TvLibrary.Implementations.DVB.TvCardDVBT.BuildGraph()
   bij TvLibrary.Implementations.DVB.TvCardDVBT.Tune(Int32 subChannelId, IChannel channel)

2009-06-14 22:17:36.640625 [10]: Exception   :System.AccessViolationException: Poging tot het lezen of schrijven van beveiligd geheugen. Dit duidt er vaak op dat ander geheugen is beschadigd.
   bij DirectShowLib.IMediaControl.StopWhenReady()
   bij TvLibrary.Implementations.DVB.TvCardDvbBase.Decompose()
   bij TvLibrary.Implementations.DVB.TvCardDvbBase.Dispose()
   bij TvLibrary.Implementations.DVB.TvCardDVBT.BuildGraph()
   bij TvLibrary.Implementations.DVB.TvCardDVBT.Tune(Int32 subChannelId, IChannel channel)
   bij TvLibrary.Implementations.DVB.DvbBaseScanning.Scan(IChannel channel, ScanParameters settings)
   bij TvService.ChannelScanning.Scan(IChannel channel, ScanParameters settings)

2009-06-14 22:17:36.687500 [10]: dvb:  Render [WinTvUSB]->[InfTee-Main] failed
2009-06-14 22:17:36.734375 [10]: dvb:  Render [Tuner]->[InfTee] failed
2009-06-14 22:17:36.734375 [10]: dvb:  Render->main inftee demux failed
2009-06-14 22:17:36.765625 [10]: dvb:  Render [WinTvUSB]->[InfTee-Main] failed
2009-06-14 22:17:36.812500 [10]: dvb:  Render [Tuner]->[InfTee] failed
2009-06-14 22:17:36.812500 [10]: dvb:  Render->main inftee demux failed
2009-06-14 22:17:36.828125 [10]: dvb:  Render [Tuner]->[WinTvUSB] failed
2009-06-14 22:17:36.890625 [10]: dvb:  Render [Tuner]->[InfTee-Main] failed
2009-06-14 22:17:36.890625 [10]: dvb:  Render->main inftee demux failed

Might be related to WinTV7 installation - it also uses a TV-service but I'll post this log before testing that since it's rather prone to crashing

Update: same results after nuking HaupPauge's WinTV server and restarting MPTVServer.

Performed another CI test:
- Plugged in WinTV CI module, started WinTV7 client, viewed encrypted and FTA channels perfectly
- Disabled HauppaugeTVServer in services.msc and rebooted
- Started TVServer configuration and started channel scan
- Full system crash after 5 frequencies, no interesting info in eventlog

All that was in error.log was 5 times the sequence posted in my previous post above this one (Access Violations and missing filter). Any ideas what the missing filter could point to?

Morpheus: interesting developments, I'll gladly look into it and help testing once I get my base config at the very least running without crashing :X

Right further updates: the tv.log contains the following per frequency it scans:

2009-06-14 23:02:59.703125 [11]: dvbt:  Tune:DVBT:tv:  Freq:486125 ONID:-1 TSID:-1 SID:-1 PMT:0xFFFFFFFF FTA:False LCN:10000 BandWidth:8
2009-06-14 23:02:59.703125 [11]: dvbt: tune: Assigning oldChannel
2009-06-14 23:02:59.703125 [11]: dvbt: tune: Current channel is null
2009-06-14 23:02:59.703125 [11]: dvbt: tune: Building graph
2009-06-14 23:02:59.703125 [11]: BuildGraph
2009-06-14 23:02:59.703125 [11]: dvb:AddNetworkProviderFilter
2009-06-14 23:02:59.703125 [11]: Error while checking if a com object is installed - b2f3a67c-29da-4c78-8831-091ed509a475 - System.Runtime.InteropServices.COMException (0x80040154): Het ophalen van de COM-classfactory voor het onderdeel met CLSID {B2F3A67C-29DA-4C78-8831-091ED509A475} is mislukt vanwege de volgende fout: 80040154.
   bij System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck)
   bij System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache)
   bij System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache)
   bij System.Activator.CreateInstance(Type type, Boolean nonPublic)
   bij TvLibrary.Implementations.DVB.FilterGraphTools.IsThisComObjectInstalled(Guid clsid)
2009-06-14 23:02:59.703125 [11]: dvb:Add DVBTNetworkProvider
2009-06-14 23:02:59.703125 [11]: CreateTuningSpace()
2009-06-14 23:02:59.703125 [11]: Found tuningspace Cable
2009-06-14 23:02:59.703125 [11]: Found tuningspace Antenna
2009-06-14 23:02:59.718750 [11]: Found tuningspace ATSC
2009-06-14 23:02:59.718750 [11]: Found tuningspace Digital Cable
2009-06-14 23:02:59.718750 [11]: Found tuningspace AuxIn1
2009-06-14 23:02:59.718750 [11]: Found tuningspace FM Radio
2009-06-14 23:02:59.718750 [11]: Found tuningspace DVB-T
2009-06-14 23:02:59.718750 [11]: Found tuningspace DVBT TuningSpace
2009-06-14 23:02:59.718750 [11]: Found correct tuningspace DVBT TuningSpace
2009-06-14 23:02:59.718750 [11]: dvb:AddAndConnectBDABoardFilters
2009-06-14 23:02:59.718750 [11]: dvb: find bda tuner
2009-06-14 23:02:59.718750 [11]: dvb:  using [Tuner]: WinTV HVR-900H BDA Tuner
2009-06-14 23:02:59.734375 [11]: dvb:  Render [Network provider]->[Tuner] OK
2009-06-14 23:02:59.734375 [11]: dvb:  Find BDA receiver
2009-06-14 23:02:59.734375 [11]: dvb:  match Capture by Tuner device path
2009-06-14 23:02:59.734375 [11]: dvb:  -WinTV HVR-900H BDA Capture
2009-06-14 23:02:59.734375 [11]: dvb:  Render [Tuner]->[Capture] AOK
2009-06-14 23:02:59.734375 [11]: dvb:  WinTv CI module detected
2009-06-14 23:02:59.734375 [11]: dvb:  Adding WinTv CI to graph
2009-06-14 23:02:59.750000 [11]: dvb:  Enable WinTV-CI tray
2009-06-14 23:02:59.750000 [11]: dvb:  Render [Tuner]->[WinTvUSB]
2009-06-14 23:02:59.750000 [11]: dvb:  Render [WinTvUSB]->[InfTee-Main]
2009-06-14 23:02:59.812500 [11]: dvb:  Render [Tuner]->[InfTee]
2009-06-14 23:02:59.812500 [11]: dvb:  Match by device path failed - trying alternative method
2009-06-14 23:02:59.812500 [11]: dvb:  match Capture filter by Tuner device connection
2009-06-14 23:02:59.812500 [11]: dvb:  -WinTV HVR-900H BDA Capture
2009-06-14 23:02:59.812500 [11]: dvb:  Render [Tuner]->[Capture] AOK
2009-06-14 23:02:59.812500 [11]: dvb:  WinTv CI module detected
2009-06-14 23:02:59.828125 [11]: dvb:  Adding WinTv CI to graph
2009-06-14 23:02:59.828125 [11]: dvb:  Enable WinTV-CI tray
2009-06-14 23:02:59.828125 [11]: dvb:  Render [Tuner]->[WinTvUSB]
2009-06-14 23:02:59.828125 [11]: dvb:  Render [WinTvUSB]->[InfTee-Main]
2009-06-14 23:02:59.875000 [11]: dvb:  Render [Tuner]->[InfTee]
2009-06-14 23:02:59.890625 [11]: dvb:  Single BDA filter implementation...
2009-06-14 23:02:59.890625 [11]: dvb:  WinTv CI module detected
2009-06-14 23:02:59.890625 [11]: dvb:  Adding WinTv CI to graph
2009-06-14 23:02:59.890625 [11]: dvb:  Enable WinTV-CI tray
2009-06-14 23:02:59.890625 [11]: dvb:  Render [Tuner]->[WinTvUSB]
2009-06-14 23:02:59.953125 [11]: dvb:  Render [Tuner]->[InfTee-Main]
2009-06-14 23:02:59.953125 [11]: dvb:Decompose
2009-06-14 23:02:59.953125 [11]: tvcard:FreeAllSubChannels:
2009-06-14 23:02:59.953125 [11]:   stop

The COM error looks highly suspicious, but according to friend Google that's the Microsoft NetworkProvider object - also TVserver just seems to ignore the error and it doesn't end up in error.log....?

Anyway the final scan on which it crashes ends with the following lines:

2009-06-14 23:02:59.984375 [11]: Found correct tuningspace DVBT TuningSpace
2009-06-14 23:02:59.984375 [11]: dvb:AddAndConnectBDABoardFilters
2009-06-14 23:02:59.984375 [11]: dvb: find bda tuner
2009-06-14 23:02:59.984375 [11]: dvb:  using [Tuner]: WinTV HVR-900H BDA Tuner
2009-06-14 23:02:59.984375 [11]: dvb:  Render [Network provider]->[Tuner] OK
2009-06-14 23:02:59.984375 [11]: dvb:  Find BDA receiver
2009-06-14 23:02:59.984375 [11]: dvb:  match Capture by Tuner device path
2009-06-14 23:03:00.000000 [11]: dvb:  -WinTV HVR-900H BDA Capture
2009-06-14 23:03:00.000000 [11]: dvb:  Render [Tuner]->[Capture] AOK
2009-06-14 23:03:00.000000 [11]: dvb:  WinTv CI module detected
2009-06-14 23:03:00.000000 [11]: dvb:  Adding WinTv CI to graph
2009-06-14 23:03:00.000000 [11]: dvb:  Enable WinTV-CI tray
2009-06-14 23:03:00.000000 [11]: dvb:  Render [Tuner]->[WinTvUSB]
2009-06-14 23:03:00.015625 [11]: dvb:  Render [WinTvUSB]->[InfTee-Main]
2009-06-14 23:03:00.062500 [11]: dvb:  Render [Tuner]->[InfTee]
2009-06-14 23:03:00.078125 [11]: dvb:  Match by device path failed - trying alternative method
2009-06-14 23:03:00.078125 [11]: dvb:  match Capture filter by Tuner device connection
2009-06-14 23:03:00.078125 [11]: dvb:  -WinTV HVR-900H BDA Capture
2009-06-14 23:03:00.078125 [11]: dvb:  Render [Tuner]->[Capture] AOK
2009-06-14 23:03:00.078125 [11]: dvb:  WinTv CI module detected
2009-06-14 23:03:00.078125 [11]: dvb:  Adding WinTv CI to graph
2009-06-14 23:03:00.093750 [11]: dvb:  Enable WinTV-CI tray
2009-06-14 23:03:00.093750 [11]: dvb:  Render [Tuner]->[WinTvUSB]
2009-06-14 23:03:00.093750 [11]: dvb:  Render [WinTvUSB]->[InfTee-Main]
2009-06-14 23:03:00.140625 [11]: dvb:  Render [Tuner]->[InfTee]
2009-06-14 23:03:00.140625 [11]: dvb:  Single BDA filter implementation...
2009-06-14 23:03:00.156250 [11]: dvb:  WinTv CI module detected
2009-06-14 23:03:00.156250 [11]: dvb:  Adding WinTv CI to graph
2009-06-14 23:03:00.156250 [11]: dvb:  Enable WinTV-CI tray
2009-06-14 23:03:00.156250 [11]: dvb:  Render [Tuner]->[WinTvUSB]

Comparing that to its previous scan it appears to crash on adding the InfTee-Main to the graph once more before giving up.

Finally and then I'll shut up, I disabled Windows' automatic reboot on system failures which I forgot to do before. The BSOD claims a BAD_POOL_CALLER error, and issues a STOP event:

*** STOP: 0x000000C2 (0x00000007,0x00000CD4,0x80563960,0x83C54DA8)

I think that's all the info I can give right now

 

[morpheus_xx]

Could you try my special build I've linked in the CI menu thread? (https://forum.team-mediaportal.com/...knc1-technotrend-54163/index4.html#post473094)

I made some changes on WinTvCI interface handling and also finished included CI menu. With your testing feedback I could try to wipe out your issues....

 

[Curry]

I'll have a go at it when I have some more time, currently swamped in my own development work - I should be able to test late this week or in the weekend.

Out of curiosity - should I or should I not install the WinTV software itself as well, or just the drivers for the peripherals? The software decoding part confuses me whether it's in the drivers or not now...

 

[infinite.loop]

Out of curiosity - should I or should I not install the WinTV software itself as well, or just the drivers for the peripherals? The software decoding part confuses me whether it's in the drivers or not now...

Just install the drivers.