[confirm] "No Signal" when tuning the same transponder twice (1 Viewer)

[dhasselqvist]

It seems that the bug where tuning the same transponder (freqency) twice is not solved on my system. Or another bug has been introduced with the same symptoms.

This can be reproduced 100%.

1. Start TV on channel X.
2. Watch a recording (this will stop TV-module)
3. Stop recording and go back to TV-module
4. Start TV on channel X, the message "No signal" appears and TV can not be started

As a work-around I can start TV on a channel on another transponder and then go back to channel X. Restart of TV-service also resolves the situation.

Logs collected using debug-option.

MediaPortal Version: 1.1 RC4
MediaPortal Skin: Blue3wide
Windows Version: Win7 x86
CPU Type: Core 2 Duo 4400
HDD: WD 160GB SATA
Memory: 1GB DDR2-800
Motherboard: ASUS P5L 1394
Video Card: Asus 8500GT
Video Card Driver: 193.45
Sound Card: onboard Realtek
Sound Card AC3: AC3
Sound Card Driver:
1. TV Card: Hauppauge Nova T-500
1. TV Card Type: DVB-T
1. TV Card Driver:
2. TV Card:
2. TV Card Type:
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: Cyberlink PowerDVD 10
MPEG2 Audio Codec: Cyberlink PowerDVD 10
h.264 Video Codec: Cyberlink PowerDVD 10
Satelite/CableTV Provider:
HTPC Case:
Cooling:
Power Supply:
Remote: Microsoft MCE
TV:
TV - HTPC Connection: DVI -> HDMI

 

[robyf]

Try to see it selecting DVBT as provider (instead of generic) in card configuration solves the problem.

 

[msj33]

I have had a close-similar issue - See bug 2: https://forum.team-mediaportal.com/...9/no-signal-terratec-cinergy-dvb-c-pci-83353/

Whenever i tried scanning for channels a second time, I always got "No signal", no matter what i did.

Tried everything(Driver Reinstall MP+Tvserver) - Solution was to reinstall MYSQL 5.1 and delete the Mysql folder.

Reason - Think that an upgrade of MP from RC1 to RC2 and again to RC4 caused this problem, but cannot explain why.

Maybe you can get some inspiration from my thread.

/Morten

 

[dhasselqvist]

Try to see it selecting DVBT as provider (instead of generic) in card configuration solves the problem.

I have finally got a chance to test this out properly. Selecting DVB-T as provider solves the problem, thanks! Is this to be seen as a work-around for a bug or is this now the intended behaviour? I'm asking since this was not needed before.

again for looking at my logs and provide me wth a solution.