TBS: CI/CAM support and other improvements (3 Viewers)

[mm1352000]

If the tuner appears as "unknown" in device manager then you won't be able to view the CAM menu. I would wonder if the USB ID had changed and for some reason the driver needed to be reinstalled. You'll have to get support from TBS for such problems.

 

[AberDino]

If the tuner appears as "unknown" in device manager then you won't be able to view the CAM menu.

That is after the reboot, I need to check what state it's in prior to the reboot.

the driver needed to be reinstalled.

I tried reinstalling the driver after the reboot through device manager but I couldn't. Can't remember the exact system response.

You'll have to get support from TBS for such problems.

I have sent them an email so I'll see what comes back.

 

[Chisum]

Hi, thank you very much for your interest.

Enclosed is the tswriter-logfile ("...bak.txt") for the failed recording event at 5th march, 00:40.
Yesterday 6th march, 00:50 I had a recording event, all went fine, see log. At 6th march, 08:50 I checked the cam-menu, at first nothing showed. I then removed and reinserted the cam, after that I could enter the cam-menu, see log.
And, as Aberdino said, sometimes I get the "unknown device" info as well. In other cases the device is recognized in the control panel, but as in the above log of 5th march at 04:30 the tvservice is not found.
Hope that helps.

 

[mm1352000]

Thanks Chisum

I can see your CAM menu test. It is interesting because the CAM seems responsive at the start:
[collapse]
[2014-03-07 08:49:59,141] [Log ] [21 ] [DEBUG] - CiMenuSupported called cardid 3
[2014-03-07 08:49:59,143] [Log ] [21 ] [DEBUG] - Turbosight: is CAM ready
[2014-03-07 08:49:59,145] [Log ] [21 ] [DEBUG] - Turbosight: result = True
[2014-03-07 08:49:59,146] [Log ] [21 ] [DEBUG] - CiMenuSupported card TBS 6928 DVBS/S2 Tuner supported: True
[2014-03-07 08:49:59,147] [Log ] [21 ] [DEBUG] - Turbosight: is CAM ready
[2014-03-07 08:49:59,148] [Log ] [21 ] [DEBUG] - Turbosight: result = True
[2014-03-07 08:49:59,150] [Log ] [21 ] [DEBUG] - TvController: EnableCiMenuHandler called
[2014-03-07 08:49:59,151] [Log ] [21 ] [DEBUG] - TvController: SetCiMenuHandler: result True
[2014-03-07 08:49:59,153] [Log ] [21 ] [DEBUG] - EnterCiMenu called
[2014-03-07 08:49:59,154] [Log ] [21 ] [DEBUG] - Turbosight: enter menu
...
[2014-03-07 08:49:59,758] [Log ] [Turbosight MMI handler] [DEBUG] - Turbosight: sending message CloseMmi
[2014-03-07 08:49:59,759] [Log ] [Turbosight MMI handler] [DEBUG] - Turbosight: sending message ApplicationInfo
[2014-03-07 08:49:59,761] [Log ] [Turbosight MMI handler] [DEBUG] - Turbosight: received MMI response ApplicationInfo to message ApplicationInfo
[2014-03-07 08:49:59,762] [Log ] [Turbosight MMI handler] [DEBUG] - Turbosight: response length = 21
[2014-03-07 08:49:59,763] [Log ] [Turbosight MMI handler] [DEBUG] - Turbosight: application information
[2014-03-07 08:49:59,765] [Log ] [Turbosight MMI handler] [DEBUG] - type = ConditionalAccess
[2014-03-07 08:49:59,766] [Log ] [Turbosight MMI handler] [DEBUG] - manufacturer = 0x4ad0
[2014-03-07 08:49:59,767] [Log ] [Turbosight MMI handler] [DEBUG] - code = 0x4ad0
[2014-03-07 08:49:59,769] [Log ] [Turbosight MMI handler] [DEBUG] - menu title = Pacific 3.22[/collapse]

...and then the responses stop.

About the "unknown device" thing: I see that you are using PS with suspend and resume. It is possible that the tuner driver or other hardware has some problem with this. I recommend you try to enable "reinitialise TV Controller on wakeup" (advanced tab in PS plugin config).

mm

 

[FreakyJ]

Yes, the TBS usb device has some problems with resume. I'm on my mobile, so i can't look up the model. @mm you might remember my internal post about my conversation with Nicola?!

 

[Chisum]

I also suspected PS standbys and suspends. I also got the impression that record failures are much more often after standby-modus than after suspend-modus.
Hence Aberdino has the unknown device problems even with 24/7. "Reinitialize tuner" did not solve my problem, I already tried before.

There are some hints, that it is a device or cam problem and I yearn for a new driver from TBS. The "unknown device" problem also occured with Windows Media Center, which I used before MP. Nevertheless, I cannot exclude, that the "TVservice not found" problem may correlate with TVService or TSWriter, as sometimes its the "unknown device"thing, sometimes the "TVService not found"thing. Although I have no clue ;-).

Dont get me wrong, I am enthusiastic about MP and highly appreciate your work.[DOUBLEPOST=1394197277][/DOUBLEPOST]Just to be clear, my TBS 6928 device is a PCIe card, not USB

 

[mm1352000]

@FreakyJ
No I don't remember that post.

I do have a TBS 6928 here for testing but I haven't used it very heavily and I don't use standby or hibernate... so I can't really advise about standby. I do know that successful standby/resume can depend as much on the motherboard and other hardware + drivers as it does depend on the tuner card drivers. My suggestion is to report the problem to TBS as AberDino has done. They can't know there is a problem unless you report.

Regarding the TV service failure to start: we really need the Windows application and system event logs so we can see if the TV service crashed. Please export them as XML or CSV (I'm on XP so can't open the evtx files).

 

[FreakyJ]

@mm1352000
They reported these issues:

Our issues are the following:


1. When we put the HTPC in Standby mode and then Resume the HTPC we can Activate the Live TV only after more than 15 seconds, we need to reach at most 10 secs. (whith any USB-DVB-T key with NO CI the delay time is less then 3 secs)

2. When we leave the TV Active for meny hours, let’s say 5 to 8 hours we find the HTPC with the TV active but the Led of the TBS is RED and locked and we cannot change channel anymore.

I tried to reproduce it with a terratec USB tuner without luck. So not 100% the same issue, but maybe related

 

[Chisum]

I could reproduce the failure, here the short history: I closed Computer manually to hibernate at 00:13. It woke up due to a scheduled task in taskplaner at 00:15. At 00:16 TV Service crashed. Therefore the computer did not wake up for scheduled recordings at 01:30 and 09:15. At at 10:00 I manually woke up the computer and checked the MPTV-Panel, which informed, that TVService is not started. I started it by clicking ok, then the scheduled recording started, but could not write to file as in the first log above. Enclosed are system log, application log and tvservice and tswriter logs.
I did not have these poblems with 24/7 or manual shutdown and start yet.

 

[mm1352000]

Perfect, thanks Chisum
The application event log shows that the crash is in tbsCIapi.dll:

Fehler,08.03.2014 00:44:40,SideBySide,63,Keine,"Fehler beim Generieren des Aktivierungskontextes für ""C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll"". Fehler in Manifest- oder Richtliniendatei ""C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll"" in Zeile 3. Der Wert ""MAJOR_VERSION.MINOR_VERSION.BUILD_NUMBER_MAJOR.BUILD_NUMBER_MINOR"" des ""version""-Attributs im assemblyIdentity-Element ist ungültig."
Informationen,08.03.2014 00:16:21,Windows Error Reporting,1001,Keine,"Fehlerbucket 5220913, Typ 17
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: TVService.exe
P2: 1.6.0.0
P3: 52b77bd9
P4: TBSCiApi0.dll
P5: 1.0.1.4
P6: 52a03063
P7: c0000005
P8: 00011b8c
P9:
P10:

From the TV service perspective I can't see any reason why the crash should occur. The only thing I can suggest is to disable preloading or delay the TV service start to give the TBS driver more time to load. Otherwise this problem needs to be reported to TBS.

mm