6.0.15 DVB-T Intermittent No Video - Sanity check, please?

[SteveB]

I'm currently running 6.0.15 with a Nova-T (9003), on a test box. I'm experiencing an issue when I flick through the channels, where certain channels appear as "no video". If I scan through the channels, and make a note of which ones are not working, restart Sage, the channels appear to work. Typically Sky Three (ch11) and UKTV History (ch12) appear to be a problem. But following a Sage restart (not system restart), generally they work.

I'm in the UK, using freeview from Crystal Palace, and I've enclosed my frq file. The frq file was generated from within Sage, but I've massaged the channel numbers to match the Freeview lineup.

My next step is to backup my Sage install, and re-install from scratch and re-test. Before I do this, has anyone else experienced this? Or got any recommendations or advise?

Thanks,

Steve

[jamjam]

I had this problem testing using version 6.0.14,

I went back to version 6.0.13 and the problem went away.

I though 6.0.15 had fixed this "no signal" problem

JJ

[moamoa]

I'm on 6.0.15 too with a Black Gold tuner and have the same issue... some channels disappear, but come back on a restart.

Also, seems to hang on some channels with the OSD not fading out after the timeout. Just stays with a black screen and the OSD. I can hit home and the system still runs, but those channels appear dead.

SageTv restart fixes it.

[Mark SS]

Same problem exists with DVB-S. Submit a bug report and include logs along with a summary of what you did i.e. Tuned x which failed, then tuned Y which was ok...

[HansS]

Although I don't use DVB-T, I have the same problem with DVB-C (FireDTV). Some channels sometimes give a "no signal" message. Some channels have this problem more than other ones. Zapping channels or restarting Sage usually helps, but it doesn't give me any confidence that unsupervised timed recordings are ok.
The application that came with FireDTV (MyTheatre) always works. So it is not a problem with the FireDTV BDA drivers, I assume. I tried three different solutions:
1-SBDArecorder
2-bda interface included in 6.0.15
3-MyTheatre DVB Network Encoder Plugin
and all show the same problem of "no signal". Solution 3 gives the best results.

I submitted a bug report for 6.0.14 just before the release of 6.0.15. No reply though....

[Alfiegerner]

I am now having this problem with 6.0.19. This is the first version of 6 I have tried. I will post a bug report.

[cychou]

I have the same DVB-T problem with 6.0.19. At the same time, I have similar problem with my MPEG 2 captured card through s-video, which is a YUAN MPG600.

[pschweig]

I had a similar problem when I first installed 6.0.17 (which I am still using). A selection of channels would not tune. They would just display the "No Signal" message.

If I rebooted a slightly different selection of channels would not tune. I tried rounding freqs down and up but there did not seem to be any logic behind it. I found that if left the channel on for about 5 mins (maybe longer) the channel would eventually tune. Next time I tuned the channel "No Signal" again.

After a few days the tuning just seemed to stick and all my channels now tune no problem. I haven't upgraded to .18 yet tho

edit: wrong version numbers

[Lucas]

I had similar issues, even with V5.

I have however found that if it is a case of leaving it on for a few minutes and then it tunes then this is purely related to the signal and the sensitivity of the cards tuners.

I found that during the summer when its warm and humid the signal is worse.

When its cold and dry the signal is better and the channels tune faster.

To overcome this I installed an antena signal amplifier and adjust its gain up or down as required.

[pbennington]

I am also seeing this problem with 6.0.19 with a hauppauge nova-t usb2, the thing is i don't think it's a weak signal problem as a restart of sage and the channels tune straight away, although as described a different set of channels won't tune, again a restart fixes them. I am currently having to check that channels are tuning before recording which is not something that is always possible, I have submitted a bug report .

[pschweig]

Originally Posted by Lucas

I have however found that if it is a case of leaving it on for a few minutes and then it tunes then this is purely related to the signal and the sensitivity of the cards tuners.

I had just moved house when I saw this problem so I wasn't sure if it was something to do with the new aerial/ proximity to transmitter etc. I was pretty sure the card and tuners were ok because they have been rock solid for over a year in the previous house.

Seeing as again Sage seems to have "settled down" and is tuning solidly again I think that rules out the new aerial/position.

I'm moving to .18 this afternoon - if I go through the same "No Signal" rigmarol I'll report it to support.

Maybe Sage goes through a training period where it locks on to the strongest signal

Pure guesswork on my part clearly but I'm sure Qian has the answers

edit: wrong version number

[pschweig]

The "No Signal" message has returned when I installed .18.

Can't test all channels because some start broadcasting at 7pm so I will check again later.

As before a selection of channels give "No Signal". A stop and start of the sagetv service results in a slightly different selection of channels not tuning. I have raised a bug with support

[Alfiegerner]

Originally Posted by pschweig

I have raised a bug with support

Yep, me too. Thankfully I have this running on a test system only.

[pschweig]

just noticed that sage sneaked out 6.0.19 without me noticing.

I have upgraded and I am seeing the same problem with .19 as well

[Chris_AMG]

Hi,

I have the same problem with v6.0.19 and a WinTV Nova-T USB2. Bug report submitted so hopefully it will be fixed soon.

Cheers, Chris.

[mrcandu]

Yes..... same problem here too. I found this with v5.0.4 and v6.0.18 using my nova-t pci card. I have raised a bug with support also.

[rickgillyon]

Is everyone seeing this problem using Service mode?

[pschweig]

Yes I am using service mode.

[mrcandu]

No.... I am not using service mode.

[Alfiegerner]

I've seen it with both. I've reverted to using SBDA Recorder for now.