Project

General

Profile

Bug #5728

bad tuner type [ATSC-2]

Added by D Sam about 1 month ago. Updated 13 days ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
Category:
DVB
Target version:
-
Start date:
2019-09-14
Due date:
% Done:

0%

Estimated time:
Found in version:
4.3-1804~gebb096804
Affected Versions:

Description

I have managed to get a Hauppauge Cordcutter Tv recognized by Tvheadend (see attached screenshot: 2019-09-13_15_53_14-Tvheadend.png).
I have an issue where I can't scan for channels, part of that issue being that this device's satip:X_SATIPCAP isn't recognized: "bad tuner type [ATSC-2]"

Any ideas as to what the next steps are in order to fix the issue?

Thank you.


Files

2019-09-13_15_53_14-Tvheadend.png (121 KB) 2019-09-13_15_53_14-Tvheadend.png D Sam, 2019-09-14 00:59
myTV.log (123 KB) myTV.log Successfully using the Hauppauge device with its official app (myTV) D Sam, 2019-09-26 17:12
TVHeadend.log (90.1 KB) TVHeadend.log Problem using the Hauppauge device with TVHeadend D Sam, 2019-09-26 17:12

History

#1

Updated by saen acro about 1 month ago

Tombea is also used in other devices with similar problems.
Elgato EyeTV Netstream 4C for example.

#2

Updated by Flole Systems about 1 month ago

TVHeadend simply doesnt support ATSC over SAT>IP yet, thats probably why you cant select it in the settings aswell. You need to implement it if you want to use it.

#3

Updated by Joe User about 1 month ago

My ATSC-T (and ATSC-C) was mostly working, but I have not played with it in almost a year.
[[https://tvheadend.org/issues/5447#change-28916]]
Might just need to add ATSC-2?? I am not sure of the differences or if anything extra is needed.
Sorry, I do not have time to look into this now though..

#4

Updated by Flole Systems about 1 month ago

ATSC-2 just means 2 tuners, but why is it not in the list of supported types if it's supported? What do you need to select for it?

#5

Updated by Jaroslav Kysela about 1 month ago

We are using a different string for the ATSC-T (terresterial) - "ATSCT". So it's required to add "ATSC" parsing. Try this patch:

diff --git a/src/input/mpegts/satip/satip.c b/src/input/mpegts/satip/satip.c
index ebce12d63..0694df588 100644
--- a/src/input/mpegts/satip/satip.c
+++ b/src/input/mpegts/satip/satip.c
@@ -716,6 +716,9 @@ satip_device_create( satip_device_info_t *info )
     } else if (strncmp(argv[i], "DVBC-", 5) == 0) {
       type = DVB_TYPE_C;
       m = atoi(argv[i] + 5);
+    } else if (strncmp(argv[i], "ATSC-", 5) == 0) {
+      type = DVB_TYPE_ATSC_T;
+      m = atoi(argv[i] + 5);
     } else if (strncmp(argv[i], "ATSCT-", 6) == 0) {
       type = DVB_TYPE_ATSC_T;
       m = atoi(argv[i] + 6);
#6

Updated by D Sam 26 days ago

Thank you Jaroslav Kysela.
Your patch seemed to work for me as far as getting the tuners automatically recognized.

Unfortunately, something is still missing when it comes to scanning/tuning channels with this Hauppauge box. I get this error when scanning for muxes:

satip: SAT>IP ATSC-T Tuner #1 ([email protected]) - RTSP SETUP error -5 (I/O error) [6-503]

In case anyone is interested I have taken a log for a run with the official Hauppauge myTV app (where channels tune) and with TVHeadend (where channels won't tune)

I am at a point where I am probably going to return this Hauppauge tuner.
I would, however, love to help the project add support to this hardware while I still have it.
Please let me know if there would be interest in that.

#7

Updated by Jaroslav Kysela 26 days ago

If you have the working RTSP communication, I can check what's mising in TVH... Just attach it to this bug.

#8

Updated by D Sam 23 days ago

I have attached two files to this issue (myTV.log and TVHeadend.log) where I have attempted to tune a channel with both the official Hauppauge myTV app and TVHeadend.
Tuning was successful with the myTV app but failed with TVHeadend (as per the aforementioned error message).

#9

Updated by Jaroslav Kysela 23 days ago

It seems that the hauppage application use the HTTP protocol not SAT>IP RTSP protocol to get the data so we cannot compare anything. This log line is suspicious:

CEDeviceHTTPServer::SendData(): bytesWritten -1 != inDataSize 106 on socket -1, socketID -1, errno=9

In linux, errno=9 means EBADF (Bad file number).

Does any SAT>IP client work with the server? Like Elgato SAT>IP from the android store or so...

#10

Updated by saen acro 23 days ago

also can try
DVB Viewer Lite for Windows
EyeTV 3 for OS X

VLC shod work also with correct playlist

#11

Updated by Luis Alves 21 days ago

You can try to use the uri from myTV.log to use on vlc:

16:05:06.5829 [...] @ CESATIPServer::HandleURI(): 46785 +HandleURI(*http://192.168.1.3:80/?&freq=551.000000&bw=6.000000&msys=atsc&mtype=8vsb&wait=1

16:05:09.8728 [...] CESATIPServer::HandleURI(): 50075 +HandleURI(rtsp://192.168.1.3:554/?&freq=515.000000&bw=6.000000&msys=atsc&mtype=8vsb&wait=0)
16:05:29.2432 [...]
CESATIPServer::HandleURI(): 69446 +HandleURI(rtsp://192.168.1.3:554/?&freq=551.000000&bw=6.000000&msys=atsc&mtype=8vsb&wait=1)

Not sure why the first one is done on port 80

#12

Updated by Jaroslav Kysela 13 days ago

  • Status changed from New to Fixed

Parsing added to v4.3-1808-g691cce4a7 .

Also available in: Atom PDF