StephaneM Posted December 10, 2007 Share Posted December 10, 2007 Hello, I'm trying to use DVBViewer as a recording application only with a TT S2-3650 with CI + CAM. All is working fine, except that sometimes the descrambling of encrypted channels is not working. If I stop the recording, and restart it, it works. When the descrambling is failing, I always see this in the debug.log : 10.12.07 02:10:55 VCR-Internal Starting recording process. 10.12.07 02:10:55 Found TT Device DeviceType: 3 10.12.07 02:10:55 Open BDA Device Got Valid handle for TT Device 10.12.07 02:10:56 TBDACITTModuleSingle:Create OpenCI - HResult: Not enough storage is available to complete this operation 10.12.07 02:10:56 Allocate Hardware USB 2.0 BDA DVB-S Tuner (3) 10.12.07 02:10:56 VCR-Internal Found fitting Hardware: USB 2.0 BDA DVB-S Tuner (3) 10.12.07 02:10:56 TDVBHardware.SetTuner PMT: 1282 - SID: 8703 10.12.07 02:10:56 TBDACITTModuleSingle CI Base SetTuner Entering 10.12.07 02:10:56 TBDACITTModuleSingle CI Base SetTuner Leaving 10.12.07 02:10:56 VCR-Internal Recording did start. 10.12.07 02:10:57 TBDACITTModuleSingle WinProc Received PMT ready Is it possible for DVBViewer to detect the error with "OpenCI" so as it can restart the recording? Or do you have any other ideas so I can recover from this (like if I don't see the recording file growing within 10 sec, I stop the recording and restart it), maybe with a new COM Interface that I can query to see if there were any CAM related errors during recording? Best Regards, Stéphane. support.zip Quote Link to comment
Lars_MQ Posted December 10, 2007 Share Posted December 10, 2007 since the dll from TT is BETA we will do nothing for now. No use to work around a possible beta issue... Quote Link to comment
StephaneM Posted March 26, 2008 Author Share Posted March 26, 2008 since the dll from TT is BETA we will do nothing for now. No use to work around a possible beta issue...I'm now using the ttBdaDrvApi.dll version 1.0.1.15 and I'm seeing the exact same behavior: * When there is this line in debug.log : TBDACITTModuleSingle:Create OpenCI - HResult: Not enough storage is available to complete this operation, tuning to the encrypted channel fails. * When there is this line in debug.log : TBDACITTModuleSingle:Create OpenCI - HResult: The operation completed successfully, tuning to the encrypted channel is successfull. So is it possible for you to add a little check on this "TBDACITTModuleSingle:Create OpenCI" to see if the call was successfull or not and if not retry it until it succeeds? (In my case when if fails, if you attempt to tune again, it succeeds). Right now, I had to code an utility to check the recordings, and if the file size is not growing within 16 sec of the recording start, then I recycle the recording. As a consequence I loose between 15 / 30 sec of a recording and this is a problem for back to back recordings (and I get many of them in my country, otherwise I wouldn't bother). Regards, Stéphane. Quote Link to comment
Lars_MQ Posted March 26, 2008 Share Posted March 26, 2008 not and if not retry it until it succeeds? Yeah sure. So everybody with a TT card and no CI will be stuck in a endless loop. This is no solution. I myself use a TT card with CAM and it works flawless, so maybe you should find out what the real problem is in your system. Does the CAM not work properly with the card... etc. Quote Link to comment
CiNcH Posted March 26, 2008 Share Posted March 26, 2008 (edited) I think this is specific to the 3650. I also had the problem that the CI sometimes was not initialized. I will have a look at this issue again (hopefully this evening...) and check whether I can also reproduce it with latest driver/API combo. Edited March 26, 2008 by CiNcH Quote Link to comment
uglyrooster Posted March 26, 2008 Share Posted March 26, 2008 I also had the problem that the CI sometimes was not initialized. Same problem here with TT 3600, even FTA-channels are sometimes locked until CAM is removed or re-initialized. But: Does the CAM not work properly with the card Lars statement is correct too, because it just happens with three of five CAMs. Quote Link to comment
CiNcH Posted March 26, 2008 Share Posted March 26, 2008 (edited) Most likely a timing problem with certain CAM's. Think that some exotic CAM's pretty much stress the CI specs and therefore fail on some receivers. I actually used an AlphaCrypt which works like a charm in most situations, but I think that it sometimes failed with the 3650. So I will give it another shot this evening to be able to be more specific. Maybe we should check if it also happens with TT-Media Center. Same problem here with TT 3600, even FTA-channels are sometimes locked until CAM is removed or re-initialized. Think this is a different problem anyway so... Edited March 26, 2008 by CiNcH Quote Link to comment
StephaneM Posted March 26, 2008 Author Share Posted March 26, 2008 (edited) Yeah sure. So everybody with a TT card and no CI will be stuck in a endless loop. This is no solution. I myself use a TT card with CAM and it works flawless, so maybe you should find out what the real problem is in your system. Does the CAM not work properly with the card... etc. Ok... You use the bdaapiOpenCI function to open the CI, this function returns an error code, and yet you decide to go on with channel tuning... why bother to continue as you already have one failure? I have two CAM : a PowerCAM and an Astoncrypt CAM, both shows the same behavior. The endless loop is not an issue, you can very well allow only three retries. It is not worth it to at least try to correct the situation if it can solve this problem. This is only a real issue when using DVBViewer to only record (as I do), not so when you also use DVBViewer as your viewer as in most case the CAM is not released. Other than this issue, the CAM (both of them) works properly (the PowerCAM is faster than the Astoncrypt). I could try to use my TT S2-3200 instead of the S2-3650. I have no other issue on my HTPC since. Though when I first tried to use a S2-3200 to replace a PVR150+Set top box combo, I noticed something : MyTheatre wasn't seeing the CAM, whereas on an older PC it was seeing the CAM (I had not purchased DVBViewer at this time). I even tried to install a clean WinXP on this hardware to see if it was a software issue, but it is more a hardware issue. So there must be something on this hardware but there is nothing I can do unless I change it completely. I have tried TT-Media Center a long time ago and there was no evident problems with it (though this proove nothing). Regards, Stéphane. Edited March 26, 2008 by StephaneM Quote Link to comment
CiNcH Posted March 26, 2008 Share Posted March 26, 2008 (edited) I could now reproduce the issue with the S2-3650 and the AlphaCrypt Classic (TT-API 1.0.1.15 but was already present in 1.0.1.11 too). I have even found a pattern. I started the DVBViewer many times and the CI was initialized at every second DVBViewer start. So every second start of the DVBViewer it shows the following error in the log: 26.03.08 19:34:12 TBDACITTModuleSingle:Create OpenCI: Für diesen Vorgang ist nicht genügend Speicher verfügbar Guess this is an API bug since the handling for S2-3200 and S2-3650 is exactly the same from the DVBViewer point of view and the problem does not exist with the S2-3200. Probably we can get some more feedback from other S2-3650 users... Edited March 26, 2008 by CiNcH Quote Link to comment
CiNcH Posted March 27, 2008 Share Posted March 27, 2008 @Lars, where do you think does this problem occur? HRESULT pretty much sounds like a Win32-API function. The TT-API does not throw a "not enough storage" error I believe. Just want to find out more about the problem so that I can contact TT product management in case... Quote Link to comment
Lars_MQ Posted March 27, 2008 Share Posted March 27, 2008 No, they throw a error 14: "operation finished with general error" also not very helpful. I ask christian to talk to his programmer contact at TT, so he can take a look at it. Quote Link to comment
StephaneM Posted March 27, 2008 Author Share Posted March 27, 2008 Guess this is an API bug since the handling for S2-3200 and S2-3650 is exactly the same from the DVBViewer point of view and the problem does not exist with the S2-3200. Probably we can get some more feedback from other S2-3650 users...I have already seen this error for another TT card (a user of my SageTV plugin to use DVBViewer as a recorder for SageTV). here is a copy of debug log for this user (I don't think this user have a CAM though). 11.03.08 20:45:40 VCR-Internal Starting recording process. 11.03.08 20:45:43 Found TT Device DeviceType: 1 11.03.08 20:45:43 Open BDA Device Got Valid handle for TT Device 11.03.08 20:45:43 TBDACITTModuleSingle:Create OpenCI: Not enough storage is available to complete this operation 11.03.08 20:45:43 Allocate Hardware TechnoTrend BDA/DVB-S Tuner (1) 11.03.08 20:45:43 VCR-Internal Found fitting Hardware: TechnoTrend BDA/DVB-S Tuner (1) 11.03.08 20:45:43 TDVBHardware.SetTuner PMT: 598 - SID: 1001 11.03.08 20:45:45 TBDACITTModuleSingle CI Base SetTuner Entering 11.03.08 20:45:45 TBDACITTModuleSingle CI Base SetTuner Leaving 11.03.08 20:45:45 VCR-Internal Recording did start. 11.03.08 20:45:45 TBDACITTModuleSingle WinProc Received PMT ready 11.03.08 20:45:45 Release Hardware TechnoTrend BDA/DVB-S Tuner (1) 11.03.08 20:45:45 Destroy Hardware TechnoTrend BDA/DVB-S Tuner (1) . . . 13.03.08 21:17:31 VCR-Internal Starting recording process. 13.03.08 21:17:31 Settuner Start 13.03.08 21:17:31 Found TT Device DeviceType: 1 13.03.08 21:17:31 Open BDA Device Got Valid handle for TT Device 13.03.08 21:17:31 TBDACITTModuleSingle:Create OpenCI: The operation completed successfully 13.03.08 21:17:31 Allocate Hardware TechnoTrend BDA/DVB-S Tuner (3) 13.03.08 21:17:31 Settuner Found usable hardware 13.03.08 21:17:31 Settuner Hardware.SetTuner 13.03.08 21:17:31 TDVBHardware.SetTuner PMT: 32 - SID: 501 13.03.08 21:17:32 TBDACITTModuleSingle CI Base SetTuner Entering 13.03.08 21:17:32 TBDACITTModuleSingle CI Base SetTuner Leaving 13.03.08 21:17:32 Settuner End 13.03.08 21:17:32 AddAVCodecs Using VideoCodec: CyberLink H.264/AVC Decoder (PDVD7.x) and audiocodec: AC3Filter 13.03.08 21:17:32 AddAVCodecs - VideoCodec CyberLink H.264/AVC Decoder (PDVD7.x) 13.03.08 21:17:32 Add AudioRenderer: Default DirectSound Device 13.03.08 21:17:32 AddAVCodecs - Audiocodec AC3Filter 13.03.08 21:17:32 AddVideoRenderer Add Videorenderer VMR 9 13.03.08 21:17:33 AddAudioCallback Adding callback 13.03.08 21:17:33 TBDACITTModuleSingle WinProc Received PMT ready Anyway, I implemented a workaround for this in my SageTV plugin. When stopping a recording (made without A/V), I quickly tune the same channel before stopping the recording and destroy the graph 5s after its creation. This way if a back to back recording is scheduled the TT hardware is not released before the 2nd recording starts. So even if the bug is still there my users will not suffer from it (so I've implemented two workarounds : restart recording if it appears to not start, and force a graph creation to keep alive the hardware for back to back recordings reducing the time it takes to tune). Regards, Stéphane. Quote Link to comment
CiNcH Posted March 28, 2008 Share Posted March 28, 2008 (edited) Interesting is that ProgDVB initializes the AlphaCrypt within the 3650 at every application startup (also used API-DLL 1.0.1.15). Edited March 28, 2008 by CiNcH Quote Link to comment
CiNcH Posted March 29, 2008 Share Posted March 29, 2008 @ StephaneM, maybe you want to have a look at this beta. It seems to have solved the problem for me. Quote Link to comment
StephaneM Posted March 29, 2008 Author Share Posted March 29, 2008 maybe you want to have a look at this beta. It seems to have solved the problem for me.I'll test the new version when it will go out of beta as I don't have any suitable hardware for satellite testing (the only satellite feed I have is on my main HTPC). Regards, Stéphane. Quote Link to comment
StephaneM Posted May 30, 2008 Author Share Posted May 30, 2008 maybe you want to have a look at this beta. It seems to have solved the problem for me.I just installed DVBViewer 3.9.4 and the issue seems to be fixed, so thank you for this, this is what I have in debug log now 31.05.08 00:47:05 Start App ----------------------------------- 31.05.08 00:47:07 Hardware.InitDevice Load settings for: Unicast Network Device 31.05.08 00:47:07 Hardware.InitDevice Load settings for: Multicast Network Device 31.05.08 00:47:07 Hardware.InitDevice Load settings for: Cinergy 2400i DT Tuner 1 (1) 31.05.08 00:47:07 Hardware.InitDevice Load settings for: Cinergy 2400i DT Tuner 2 (2) 31.05.08 00:47:07 Hardware.InitDevice Load settings for: USB 2.0 BDA DVB-S Tuner (3) 31.05.08 00:47:07 Device @device:pnp:\\?\ngene#ven_18c3&dev_0720&subsys_1167153b&rev_00&tuner#5&2accb5d0&0&2#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{2745a7ad-e8ca-11d8-a988-004030004d56} 31.05.08 00:47:07 Device @device:pnp:\\?\ngene#ven_18c3&dev_0720&subsys_1167153b&rev_00&tuner#5&2accb5d0&0&2#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{2745a7ae-e8ca-11d8-a988-004030004d56} 31.05.08 00:47:07 Device @device:pnp:\\?\usb#vid_0b48&pid_300a#lhfiml#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{41bffe6c-ef63-48b9-8d2c-29bdd2492900} 31.05.08 00:47:07 LoadWindowDefs Loading WindowDefFile: C:\Documents and Settings\All Users\Application Data\CMUV\DVBViewer\windowdef.xml 31.05.08 00:48:07 VCR-Internal Starting recording. 31.05.08 00:48:07 Found TT Device DeviceType: 3 31.05.08 00:48:07 Open BDA Device Got handle for TT Device 31.05.08 00:48:07 TBDACITTModuleSingle:Create CloseCI: The system cannot find the drive specified 31.05.08 00:48:07 TBDACITTModuleSingle:Create OpenCI: The operation completed successfully 31.05.08 00:48:07 Allocate Hardware USB 2.0 BDA DVB-S Tuner (3) 31.05.08 00:48:07 VCR-Internal Hardware: USB 2.0 BDA DVB-S Tuner (3) 31.05.08 00:48:07 TDVBHardware.SetTuner PMT: 1282 - SID: 8203 31.05.08 00:48:08 TBDACITTModuleSingle CI Base SetTuner Entering 31.05.08 00:48:08 TBDACITTModuleSingle CI Base SetTuner Leaving 31.05.08 00:48:08 VCR-Internal Recordingstart. 31.05.08 00:48:09 TBDACITTModuleSingle.OnSlotStatus Status: 1 - ModuleType: 31.05.08 00:48:09 TBDACITTModuleSingle WinProc Received PMT ready 31.05.08 00:48:16 TBDACITTModuleSingle evalPMT -1 31.05.08 00:48:16 TBDACITTModuleSingle.OnSlotStatus Status: 2 - ModuleType: PowerCam_HD V2.0 31.05.08 00:49:29 Settuner Start I'm only copying this to let you know about the message "Create CloseCI: The System cannot find the drive specified" (doesn't seem to do anything wrong). Now, I just have one question, is Diseqc supposed to be working with a TT-S2 3650 CI? I currently have two LNBs (Astra / Hotbird), and I can switch from LnbA to LnbB with TT Media Center but not in DVBViewer. (PS: TT Media Center is a very very bad software : as soon as I install it on Windows XP all items on my start menu are just gone and VMR9 is broken... I verified this on two PCs so far, I don't know what the setup is doing, hopefully system restore is able to fix it... I will never ever install this software again) Regards, Stéphane. Quote Link to comment
jakub Posted October 18, 2011 Share Posted October 18, 2011 (edited) I have this exact issue with newer DVBViewer + Recording Service (using it as backend and unicast device in DVBViewer as frontend). Sometimes channels don't get descrambled and I have to rebuild graph manually. That's possible in DVBViewer itself when manually watching, but not with recording service timers. This way lot of recordings are just small files with no actual video/data. I'm using CT-3650 1.0.3.8 TT BDA drivers, win7 x64. Current version DVBViewer is 4.9.0.0, and recording servce 1.9.2.0 , but same happened even with older versions (~1,5years) of both. Is it supposed to be working now in DVBViewer, as the users reported? Could the problem be related to the fact I'm using recording service? Is there any way to fix this behaviour? Edited October 18, 2011 by jakub Quote Link to comment
jirim100 Posted January 8, 2015 Share Posted January 8, 2015 (edited) I have this exact issue too with Recording Service. DVBViewer is version 5.3.2 and Recording Service is version 1.30.1. I am using TechnoTrend TT-connect® CT-3650 CI with the last driver 1.0.3.9 on Win7 64bits. The part of log: 08.01.15 15:30:00.100 TBDATechnoTrend Opendevice TT Device: 308.01.15 15:30:00.111 TBDATechnoTrend Opendevice Got handle for TT Device08.01.15 15:30:00.111 TBDACITTModuleSingle:Create CloseCI: Systém nemůže nalézt uvedenou jednotku (System can't find the specified drive)08.01.15 15:30:00.513 TBDACITTModuleSingle:Create OpenCI: Pro dokončení operace není dostatečný prostor (Not enough memory to complete operation) It happens only occasionally (may be after EPG update task ??). The created file is small and recording is every one minute restarted. Edited January 8, 2015 by jirim100 Quote Link to comment
jirim100 Posted January 16, 2015 Share Posted January 16, 2015 (edited) I have this exact issue too with Recording Service. DVBViewer is version 5.3.2 and Recording Service is version 1.30.1. I am using TechnoTrend TT-connect® CT-3650 CI with the last driver 1.0.3.9 on Win7 64bits. The part of log: 08.01.15 15:30:00.100 TBDATechnoTrend Opendevice TT Device: 3 08.01.15 15:30:00.111 TBDATechnoTrend Opendevice Got handle for TT Device 08.01.15 15:30:00.111 TBDACITTModuleSingle:Create CloseCI: Systém nemůže nalézt uvedenou jednotku (System can't find the specified drive) 08.01.15 15:30:00.513 TBDACITTModuleSingle:Create OpenCI: Pro dokončení operace není dostatečný prostor (Not enough memory to complete operation) It happens only occasionally (may be after EPG update task ??). The created file is small and recording is every one minute restarted. When this happen and I run DVBViewer Pro then DVBViewer Pro without problem tune and show affected channel. And problem happens after EPG Update. I think the code for tuning the channel (or communicating with the hardware) is not the same in DVBViewer Pro and Recording Service. Edited January 16, 2015 by jirim100 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.