Hi mm, please find full log files attached for most recent instance when CAM became unresponsive. Apologies for all the EPG entries...
TBS: CI/CAM support and other improvements (5 Viewers)
- Thread starter mm1352000
- Start date
- December 18, 2005
- 94
- 16
- Home Country
-
Sweden
Works fine for me!
could you please and tell which one are you using? i guess the 1.6 patch...
Last edited:
- July 7, 2014
- 1
- 1
- Home Country
-
Germany
That is the patch targted for 1.6 . I just installed it under 1.8 and it works fine.
nice to hear 
thank you! I`m still hesitating to use that because 1.8 comes with some changes and improvements of the TV Section (but maybe not on the server side)...
An 1.8 patch would be still nice, anyone?
thank you! I`m still hesitating to use that because 1.8 comes with some changes and improvements of the TV Section (but maybe not on the server side)...An 1.8 patch would be still nice, anyone?
Last edited:
- June 8, 2014
- 57
- 5
- Home Country
-
United States of America
I was pointed to this thread by mm1352000 and used the patched files to fix the issue of a TBS6985 DVB-S2 tuner card not being able to control a DiSEqC switch, and for that it works great, and I send a huge THANK YOU to the person or persons who came up with these patches.
I am still experiencing an issue of the TBS6985 not being able tocontrol a 22 kHz tone switch that is on one of the DiSEqC switch ports tune Ku-band frequencies. I also wrote about that issue in this thread, which contains more details:
Installed new TBS6985 DVB-S2 tuner card and DiSEqC switch won't work, + other issues
If whoever came up with the DiSEqC switch fix could also look into this and perhaps come up with a fix, I would very much appreciate it!
I am still experiencing an issue of the TBS6985 not being able to
Installed new TBS6985 DVB-S2 tuner card and DiSEqC switch won't work, + other issues
If whoever came up with the DiSEqC switch fix could also look into this and perhaps come up with a fix, I would very much appreciate it!
Last edited:
- June 8, 2014
- 57
- 5
- Home Country
-
United States of America
Just a bit more on the issue I am experiencing. For some odd reason it appears that if the band is set to circular and a correct Ku-band frequency is used, the TBS6985 will not tune in the channel (even though a Prof 7301 tuner we had tried previously had no problem tuning Ku-band channels with those same frequencies). But if I change the band to C-band and put in an equivalent C-band frequency (so that it is the same offset from the intermediate frequency), then it tunes the channel with no issues. For more information you can see this message in the previously mentioned thread.
I hope that there is some way to fix this because although this workaround is effective, it's not very convenient nor intuitive. But at least the DiSEqC switches work (we have four of them, one connected to each tuner on the card) so that was the main concern. Thank you to those that work on this stuff, I'm very grateful you have the ability to fix these types of issues, and are willing to share your efforts!
I hope that there is some way to fix this because although this workaround is effective, it's not very convenient nor intuitive. But at least the DiSEqC switches work (we have four of them, one connected to each tuner on the card) so that was the main concern. Thank you to those that work on this stuff, I'm very grateful you have the ability to fix these types of issues, and are willing to share your efforts!
- June 8, 2014
- 57
- 5
- Home Country
-
United States of America
I am experiencing one other issue and wonder if anyone else has seen this. As noted in a previous post I am using a TBS6985 quad tuner card, and each tuner is connected to a four-port DiSEqC 2.0 switch.
The issue is this: When recording a scheduled program, if the card selects DiSEqC port 1 (or A/A in MediaPortal terminology) on any tuner/DiSEqC switch combination then it always seems to work. However, if any of DiSEqC ports 2, 3, or 4 are selected, then sometimes (and ONLY sometimes) the recording will end prematurely. Strangely, when this happens, the recording will usually end somewhere near the 30 second mark, the 1 minute mark, or the 2 minute mark (give or take about 10 seconds). If the recording goes past two minutes then the entire program is almost always recorded (I saw it fail once about an hour into a two hour movie, but that could have been a signal strength issue).
But another wrinkle is that if the recording fails, and then you subsequently record the next program on that same channel, that seems to always succeed. So if, for example, I want to record a program that starts at 8:00 PM, and it's on an LNB connected to DiSEqC port 2, 3, or 4, then the trick is to try to record the program that comes just before, such as at 7:30 PM. The 7:30 recording may fail after 30 seconds to 2 minutes, but then the 8:00 PM one will probably be good.
I don't know if that makes any sense, but thought I would throw it out there and ask if anyone else that uses one or more DiSEqC switches has observed similar behavior. Or, if perhaps anyone knows of something in the patched driver that might induce this behavior.
Would love to have a fix for this before the fall TV season starts, if anyone has the slightest clue why it happens and how to fix it. Also, I don't understand why it is that if I happen to shut down TV server while it's recording and then bring it back up, it will restart the recording (if it's still in that time period) but when this problem occurs MediaPortal seems to just give up and not even try to restart the recording.
The issue is this: When recording a scheduled program, if the card selects DiSEqC port 1 (or A/A in MediaPortal terminology) on any tuner/DiSEqC switch combination then it always seems to work. However, if any of DiSEqC ports 2, 3, or 4 are selected, then sometimes (and ONLY sometimes) the recording will end prematurely. Strangely, when this happens, the recording will usually end somewhere near the 30 second mark, the 1 minute mark, or the 2 minute mark (give or take about 10 seconds). If the recording goes past two minutes then the entire program is almost always recorded (I saw it fail once about an hour into a two hour movie, but that could have been a signal strength issue).
But another wrinkle is that if the recording fails, and then you subsequently record the next program on that same channel, that seems to always succeed. So if, for example, I want to record a program that starts at 8:00 PM, and it's on an LNB connected to DiSEqC port 2, 3, or 4, then the trick is to try to record the program that comes just before, such as at 7:30 PM. The 7:30 recording may fail after 30 seconds to 2 minutes, but then the 8:00 PM one will probably be good.
I don't know if that makes any sense, but thought I would throw it out there and ask if anyone else that uses one or more DiSEqC switches has observed similar behavior. Or, if perhaps anyone knows of something in the patched driver that might induce this behavior.
Would love to have a fix for this before the fall TV season starts, if anyone has the slightest clue why it happens and how to fix it. Also, I don't understand why it is that if I happen to shut down TV server while it's recording and then bring it back up, it will restart the recording (if it's still in that time period) but when this problem occurs MediaPortal seems to just give up and not even try to restart the recording.