Project

General

Profile

Bug #1337

TVH does not honour the original network ID anymore

Added by bas t about 12 years ago. Updated about 12 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
DVB
Target version:
-
Start date:
2012-10-16
Due date:
% Done:

0%

Estimated time:
Found in version:
master head
Affected Versions:

Description

I've updated to master today and much to my surprise some muxes don't work anymore.
Case: my dvb-c provider (ziggo netherlands) has an original network id of 1000
Nevertheless, most regions get assigned another network id, mine is 9700
Some of my muxes do exist on the original network id, others do not or even worse, conflict with it.

so in my previous config I would have a mux like this:

{
"quality": 100,
"enabled": 1,
"status": "Constant FEC",
"transportstreamid": 30,
"network": "Ziggo Groningen",
"frequency": 164000000,
"initialscan": 0,
"symbol_rate": 6875000,
"fec": "3/5",
"constellation": "QAM64"
}

With today's master running that changed to this:

{
"quality": 100,
"enabled": 1,
"status": "No signal",
"transportstreamid": 30,
"originalnetworkid": 1000,
"network": "Ziggo Groningen",
"frequency": 164000000,
"initialscan": 0,
"symbol_rate": 6875000,
"fec": "3/5",
"constellation": "QAM64"
}

So original network id has been added and surprise, surprise, I have no signal anymore on it!

History

#1

Updated by bas t about 12 years ago

Or could that be a hardware issue?
I notice just now that the previous status was "Constant FEC"

#2

Updated by Adam Sutton about 12 years ago

I'd say this is more likely to be a hardware issue. The signal status is completely independent of the ONID. But just to recap, previously TVH did not track ONID at all, however its been added now for a variety of reasons.

There were some issues with it (still might be) that meant data was missing etc.. But it shouldn't (but I won't say definitely not) cause basic signal reception issues (more it might cause incoming data to be incorrectly rejected). But this was due to it NOT updating the ONID properly and thus incorrectly rejecting stuff, which is very different to what you're seeing.

However the fact that you show that mux as having an ONID value in the first place, implies that it did receive a signal from this mux and was able to get and store the ONID. So it should all be working, so I'd check HW first.

If HW seems OK, try doing a fresh scan just to see what happens.

Adam

P.S.
Please can you report the actual version number (with git hash), master/head means nothing because its a moving target.

#3

Updated by Adam Sutton about 12 years ago

  • Category set to DVB
  • Status changed from New to Need feedback
#4

Updated by bas t about 12 years ago

Strangest thing: it's only this mux on one adapter that is affected, all other muxes are fine on this adapter.
My other adapters are not affected in any way.
Checked playing a channel from this mux on this adapter in myth, no signal. Changed to another adapter and same channel plays.

I say: close this ticket, when I have sorted it out and there still seems to be something to report I'll open a new one.

#5

Updated by Adam Sutton about 12 years ago

  • Status changed from Need feedback to Rejected

Yeah sounds very odd, but does sound like the problem is outside of TVH.

Closing.

Also available in: Atom PDF