Project

General

Profile

Feature #4367

ATSC-T not being detected minisatip->tvheadend

Added by fog NL over 7 years ago. Updated over 7 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
Category:
SAT>IP
Target version:
-
Start date:
2017-05-11
Due date:
% Done:

0%

Estimated time:

Description

I've been attempting to try and share my Hauppauge 950q tvtuner across my network using minisatip -> tvheadend . Initially, the minisatip server would show up in tvheadend, but wouldn't have any adapters listed under it. After a forum post on the minisatip website (https://minisatip.org/forum/viewtopic.php?f=5&t=411), dev cata was able to add in the ATSC support.

Since his update, I am now able to see the tuner, but only ATSC-C and not ATSC-T (which I require for over the air).

Previously in TVheadend with this tuner, my DVB devices looked like this:

TV Adaptors
- /dev/dvb/adapter0 [Auvitek AU8522 QAM/8VSB Frontend #0]
o Auvitek AU8522 QAM/8VSB Frontend : ATSC-C #0
o Auvitek AU8522 QAM/8VSB Frontend : ATSC-T #0

Now, sharing with minisatip to tvheadend, I am only getting this:
TV adapters
- minisatip - 192.168.1.250
- SAT>IP ATSC-C Tuner #1 (192.168.1.250)

At this point, in the forum post, cata suggests that this may be an issue on the tvheadend side, hence why I'm posting this here.

I've enabled the debug log, but the only mention I see that seems to be related is:

2017-05-11 13:20:24.155 [  ERROR]:satip: 192.168.1.250: bad tuner count [ATSCT-1]

History

#1

Updated by Jaroslav Kysela over 7 years ago

Have you tried latest v4.3-59-gc7eac51 ?

#2

Updated by fog NL over 7 years ago

Jaroslav Kysela wrote:

Have you tried latest v4.3-59-gc7eac51 ?

For some reason, it didn't occur to me to try the latest unstable. Sure enough, it shows up there now! Sorry for the time wasting.

I'm now able to add the device, for some reason, it won't detect a signal, but that's a separate issue that I'll need to work on. Thanks!

#3

Updated by Jaroslav Kysela over 7 years ago

  • Status changed from New to Fixed
#4

Updated by fog NL over 7 years ago

fog NL wrote:

Jaroslav Kysela wrote:

Have you tried latest v4.3-59-gc7eac51 ?

For some reason, it didn't occur to me to try the latest unstable. Sure enough, it shows up there now! Sorry for the time wasting.

I'm now able to add the device, for some reason, it won't detect a signal, but that's a separate issue that I'll need to work on. Thanks!

According to minisatip dev, the issue is now at the tvheadend side:

The issues is that tvheadend does(sic) not send the system to minisatip, which is required to tune.

The system is not also specified by the standard but minisatip should agree on a common name: eg atsct or atscs.

When that is done it will work.

Minisatip currently supports dvbcb and atsc, but this could (is ) confusing

#5

Updated by Jaroslav Kysela over 7 years ago

Yep, I forgot one line in the tvh source code. Try v4.2.1-50-g7c2e23d +.

#6

Updated by Jaroslav Kysela over 7 years ago

Wrong branch - v4.3-68-gce6f517 + .

#7

Updated by fog NL over 7 years ago

Jaroslav Kysela wrote:

Wrong branch - v4.3-68-gce6f517 + .

That did it! I can confirm this is now fixed in v4.3-68-gce6f517

Thank you so much for the quick response and the fix!

Also available in: Atom PDF