- September 1, 2008
- 21,577
- 8,224
- Home Country
- New Zealand
Hi paalkr
I think the first thing you should do is read the comments from chrholm, ogir_xx and aj1405 -->here<-- (have you read that thread before?). If you ask me it sounds like aj1405 was experiencing similar issues to you - even also using a Conax CAM. The solution for him was to install the patch that I provided and use the older driver.
So the first thing that you can do is check the behaviour of each of the drivers since 1.00.05.601 - it would be really valuable to know which versions (if any) are stable for you. You'll need the patch from the other thread for some versions (the older ones) but not for others.
Even if the 5.601 version is stable there are lots of other things that I would like you to test.
First, it would also be helpful if you can try the latest driver with different software too (especially DVBLink). If the tuner is stable in different software then it is obvious that there must be something we can do in MP to solve the problem.
It would also help if you can give more detail about the problem:
1. Does the problem occur even after shutdown + reboot? With this test I'm trying to eliminate standby + resume as a factor.
2. What happens if you try to tune to a channel on a different frequency? In your logs all the channels that you failed to tune were on a single frequency (554000 kHz). The channel that succeeded (Bliss) was on a different frequency (570000 kHz). Perhaps tuning to a new frequency (not replacing the CAM) was the thing that "fixed" the problem.
In all your MP tests please make 100000% certain that you are testing with "stop card" selected. Logs would also be appreciated - better to have too many logs than not enough.
In the meantime I have managed to figure out how to get the CI menus working for my Skystar.
I've just got a few more things that I want to do to tidy up the Twinhan code before I release a public test build. You would be *very* welcome to try it. Hopefully it will be ready by this weekend.
So in summary: I think I was spreading a little too much "doom and gloom" on Monday - apologies for that. There is plenty that we can do to try and find a solution, or at least find a workaround for the problem.
mm
PS: older drivers can be found -->here<--.
Not at all! I'm here to try and help to solve the problem if it is at all possible. I have to admit that it is a tricky one though. The best we can do might be to find a way to work around the problem since the root cause seems to be peculiar behaviour by the tuner driver.Or are you suggesting that in my particular case (setup and hardware), the terratec H7 card is not supported by MP?
Yes!Anything else I can do?
I think the first thing you should do is read the comments from chrholm, ogir_xx and aj1405 -->here<-- (have you read that thread before?). If you ask me it sounds like aj1405 was experiencing similar issues to you - even also using a Conax CAM. The solution for him was to install the patch that I provided and use the older driver.
So the first thing that you can do is check the behaviour of each of the drivers since 1.00.05.601 - it would be really valuable to know which versions (if any) are stable for you. You'll need the patch from the other thread for some versions (the older ones) but not for others.
Even if the 5.601 version is stable there are lots of other things that I would like you to test.
First, it would also be helpful if you can try the latest driver with different software too (especially DVBLink). If the tuner is stable in different software then it is obvious that there must be something we can do in MP to solve the problem.
It would also help if you can give more detail about the problem:
1. Does the problem occur even after shutdown + reboot? With this test I'm trying to eliminate standby + resume as a factor.
2. What happens if you try to tune to a channel on a different frequency? In your logs all the channels that you failed to tune were on a single frequency (554000 kHz). The channel that succeeded (Bliss) was on a different frequency (570000 kHz). Perhaps tuning to a new frequency (not replacing the CAM) was the thing that "fixed" the problem.
In all your MP tests please make 100000% certain that you are testing with "stop card" selected. Logs would also be appreciated - better to have too many logs than not enough.
In the meantime I have managed to figure out how to get the CI menus working for my Skystar.
I've just got a few more things that I want to do to tidy up the Twinhan code before I release a public test build. You would be *very* welcome to try it. Hopefully it will be ready by this weekend.
So in summary: I think I was spreading a little too much "doom and gloom" on Monday - apologies for that. There is plenty that we can do to try and find a solution, or at least find a workaround for the problem.
mm
PS: older drivers can be found -->here<--.