BUG: 8PSK modulation wrongly saved in tuningparameters table (1 Viewer)

malakudi

Portal Member
January 28, 2007
22
0
Home Country
Greece Greece
TV-Server Version: 1.0.RC4
MediaPortal Version: 1.0.RC4
MediaPortal Skin: default wide
Windows Version: Vista 32
CPU Type: Core2Duo 3GHz
HDD:
Memory:
Motherboard:
Video Card:
Video Card Driver:
Sound Card:
Sound Card AC3:
Sound Card Driver:
1. TV Card: Hauppauge HVR4000
1. TV Card Type: DVB-T/S/S-2/Analog
1. TV Card Driver:
2. TV Card: Technotrend S2-3200
2. TV Card Type: DVB-S2
2. TV Card Driver:
3. TV Card:
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec:
MPEG2 Audio Codec:
h.264 Video Codec:
Satelite/CableTV Provider:
HTPC Case:
Cooling:
Power Supply:
Remote:
TV:
TV - HTPC Connection:

8PSK modulation is not supported in BDA (among other things - blame M$ for this). DVB-S2 card drivers map 8PSK to some other supported modulation (for example, 96QAM). Unfortunately every card does this differently. Mediaportal TV server, when scans a transpoder with 8PSK, saves in the SQL database in the tuningparameters table the modulation option. But it saves it with the value that the specific card needs to have when scanning. When a second different card tries to use the same channel, the modulation filed in the tuning parameters is wrong, so it doesn't work. If you rescan with the second card, then the first one doesn't work. In my setup, HVR4000 uses a modulation value of 23 for 8PSK where S2-3200 uses a modulation value of 32.

Mediaportal TV server should save in the tuningparameters the modulation in a hardware independent value format, and have another table to match hardware independent to hardware dependent values.

There are many people like me who use two or more DVB-S2 cards from different hardware providers, and the database format cannot support this as it is now.
 

Users who are viewing this thread

Top Bottom