- March 26, 2007
- 3,715
- 180
- Home Country
-
Germany
This is only relevant for users with more than one tuner.
When the tvservice changes cards during a channelchange, the client code tries to identify if this happened or not.
Getting this information right is quite important for the channel change on the client.
If a card change occured but wasn't detected several problems can occur.
Ex. the user has to use skipsteps in order to "travel" into the next channel.
Currently the client use a simple mechanism to detect if a card change occured.
It compares the old cardID with the newly aquired cardID (from server)-
If these 2 are different from each other, then a cardchange occured.
This is a situation where the client has no way of telling if a card change occured.
card1, high prio
card2, low prio
All channels are mapped on both cards.
user tunes to channelA on card2.
user tunes to channelB on card1, it fails.
channelB is then tuned on card2, which succeeds.
so the client compares old cardid=card2 with new cardid=card2.
In other words cards didn't change.
But the timeshifting process was stopped on server, durings it's timeshifting loop that searches for the next working card.
So even if the card ID's are the same, the clientside needs to translate this as a cardchange.
http://mantis.team-mediaportal.com/view.php?id=2711
Open the issue in Mantis...
When the tvservice changes cards during a channelchange, the client code tries to identify if this happened or not.
Getting this information right is quite important for the channel change on the client.
If a card change occured but wasn't detected several problems can occur.
Ex. the user has to use skipsteps in order to "travel" into the next channel.
Currently the client use a simple mechanism to detect if a card change occured.
It compares the old cardID with the newly aquired cardID (from server)-
If these 2 are different from each other, then a cardchange occured.
This is a situation where the client has no way of telling if a card change occured.
card1, high prio
card2, low prio
All channels are mapped on both cards.
user tunes to channelA on card2.
user tunes to channelB on card1, it fails.
channelB is then tuned on card2, which succeeds.
so the client compares old cardid=card2 with new cardid=card2.
In other words cards didn't change.
But the timeshifting process was stopped on server, durings it's timeshifting loop that searches for the next working card.
So even if the card ID's are the same, the clientside needs to translate this as a cardchange.
http://mantis.team-mediaportal.com/view.php?id=2711
Open the issue in Mantis...