Issue with MPTVServer no TV Server present (1 Viewer)

[teros]

Have set the timeout to 10 and attempted to tune on both tuners without any luck am now getting a singl bar though have included screen shot.

Off for some sleeo catch ya

 

[mm1352000]

Have set the timeout to 10 and attempted to tune on both tuners without any luck am now getting a singl bar though have included screen shot.

The patch that I gave you loosens the signal detection criteria, however it seems like the tuner really isn't receiving signal. About the only think I can think of that we haven't already checked is that the signal is offset one way or the other...

Off for some sleeo catch ya

Fair enough. It is 5 AM here too so I should probably do the same. I'll be back to check on this thread and post instructions for checking offsets tomorrow.

 

[teros]

How do i increase the offset? As said before is wierd the the Dvico Signal checker and the dvico app can pickup signal and play channels. Have removed after i verified that it can recieve signal

 

[mm1352000]

Hi again teros

I hope you're well rested.
Checking for offset is as simple as doing a few single transponder scans using the advanced options. You need to know the frequency of one of your local DVB-T muxes, and then scan the following frequencies:

1. f - 166000
2. f - 125000
3. f
4. f + 125000
5. f + 166000

(where f is the frequency of the mux in kHz)
Note: use a bandwidth of 7 MHz.

Does that make sense?

[Edit: make sure you use the 10 second tune timeout that we tried last night and the original fix DLL that doesn't have my signal detection loostening code in it. It might also pay to put the tuner in the more compatible "stop graph" mode:

1. Open TV Server configuration.
2. Edit the tuner settings (same as for the network provider that we tried last evening).
3. Change from "pause card" to "stop card".
(4. TV Server will need to restart.)
]

 

[teros]

hey attempted getting the same result with both dll's using the one that fixed me seeing the tv server and the delay one to fix the signal..

 

[mm1352000]

Bah - I've messed up my instructions! :sorry:

You know how I said f - 125000 etc.? Change that to:

1. f - 166
2. f - 125
3. f
4. f + 125
5. f + 166

My apologies once again.

 

[teros]

Ummm i tried all same result except +125 causes a BSOD on my machine everytime it's attempted...Logs attached.

 

[mm1352000]

Your latest logs seem to show that you're only scanning "125". That isn't right. Let me try and be more specific...

From your earlier logs it looks like one of the frequencies in your area is 177500kHz. That is what people call a mux/multiplex frequency. For that frequency I would be asking you to scan:

1. -166 => 177334
2. -125 => 177375
3. ~ => 177500
4. +125 => 177625
5. +166 => 177666

Is that what you've been doing?

 

[teros]

Hi Have scanned with the above issue is with number 4 which at first caused a BSOD first time..After running the above i ran a full scan so the logs containt the specifics above and then everything.

 

[mm1352000]

Hi again teros

I have to confess that I am stumped at this point. Short of increasing the tune time preference, fiddling with the network provider settings, or doing more scanning with various offsets, I just don't understand why the tuner can't lock. Have you tried ScanChannelsBDA to see if that works?