Bug #5728
bad tuner type [ATSC-2]
0%
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
History
Updated by saen acro about 5 years ago
Tombea is also used in other devices with similar problems.
Elgato EyeTV Netstream 4C for example.
Updated by Flole Systems about 5 years 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.
Updated by Joe User about 5 years 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..
Updated by Flole Systems about 5 years 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?
Updated by Jaroslav Kysela about 5 years 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);
Updated by D Sam about 5 years 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 (192.168.1.3@UDP) - 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.
Updated by Jaroslav Kysela about 5 years ago
If you have the working RTSP communication, I can check what's mising in TVH... Just attach it to this bug.
Updated by D Sam about 5 years ago
- File myTV.log myTV.log added
- File TVHeadend.log TVHeadend.log added
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).
Updated by Jaroslav Kysela about 5 years 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...
Updated by saen acro about 5 years ago
also can try
DVB Viewer Lite for Windows
EyeTV 3 for OS X
VLC shod work also with correct playlist
Updated by Luis Alves about 5 years 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)
CESATIPServer::HandleURI(): 69446 +HandleURI(rtsp://192.168.1.3:554/?&freq=551.000000&bw=6.000000&msys=atsc&mtype=8vsb&wait=1)
16:05:29.2432 [...]
Not sure why the first one is done on port 80
Updated by Jaroslav Kysela about 5 years ago
- Status changed from New to Fixed
Parsing added to v4.3-1808-g691cce4a7 .
Updated by D Sam about 4 years ago
Aman K wrote:
D Sam How did you get the logs from this device?
Hi Aman K
I no longer have the Hauppauge Cordcutter tuner, but I believe I was able to get log files after connecting to the device using either telnet or ssh.
I recall downloading the latest firmware update from Hauppauge's website (https://hauppauge.com/pages/support/support_cordcuttertv.html), and modifying the
/etc/passwdfile (either by adding a new user or by replacing the hash for root with a hash generated from a password I chose) inside of the downloaded firmware rootfs .tgz archive. Then I applied the modified firmware (with credentials I knew the password to) and that is probably how I got in.
Once you're in, you can kill the process responsible for the tuner/web server that runs on startup and start it manually with other flags to make it more verbose/run on the foreground. Once in, you can also modify some of the files for the web server in the tuner and get access to other admin screens/options for the config URLs not made available by default.
Hope this helps.
Cheers.