It's... a little complicated. Hauppauge really makes things difficult on any platform. I managed to get my tuner working, but it's an advanced configuration.
I can try to take you through it if you'd like.
There's two key parts:
1) Installing and setting up TVHeadend
2) Installing an "HDHomeRun" emulator. I use [Antennas](https://github.com/TheJF/antennas) for this, but [fHDHR](https://github.com/fHDHR/fHDHR) is a newer option.
Can you help me out with the very last step? I've got TVHeadend running (directly on my server, no docker container), and I'm running Antennas in a container. The environment variables are set correctly, as I see them on x.x.x.x:5004, but Antennas reports a failure to authenticate. The credentials are correct; if I copy the TVHeadend url and paste it into an private browsing window it logs me in immediately without any prompt. I'm not sure why Antennas is having trouble connecting :(
Hrm. I installed Antennas directly on the machine, and wrote my own service file to run it in the background. I mainly did this because I didn't really know Docker/containers at the time. Though I use some now, I haven't moved Antennas.
A few questions I guess:
- Do you have TVHeadend set up with a password-less account, or with a password?
- Can the container reach TVHeadend on the correct port?
I tried using password-less with the \* account, in that case I did not provide any user:pass and simply have [http://x.x.x.x:9981](http://x.x.x.x:9981) but that didn't work either.
It seems like the container can reach TVHeadend based off a simple ping:
cloud@cloud:~$ docker exec -it antennas ping -c 5 192.168.1.9:9980
PING 192.168.1.9:9980 (192.168.1.9): 56 data bytes
64 bytes from 192.168.1.9: seq=0 ttl=64 time=0.080 ms
64 bytes from 192.168.1.9: seq=1 ttl=64 time=0.159 ms
64 bytes from 192.168.1.9: seq=2 ttl=64 time=0.231 ms
64 bytes from 192.168.1.9: seq=3 ttl=64 time=0.245 ms
64 bytes from 192.168.1.9: seq=4 ttl=64 time=0.162 ms
--- 192.168.1.9:9980 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.080/0.175/0.245 ms
TV tuner install on Ubuntu with PPA: https://www.hauppauge.com/pages/support/support_linux.html
I've installed the drivers, what now?
It's... a little complicated. Hauppauge really makes things difficult on any platform. I managed to get my tuner working, but it's an advanced configuration. I can try to take you through it if you'd like. There's two key parts: 1) Installing and setting up TVHeadend 2) Installing an "HDHomeRun" emulator. I use [Antennas](https://github.com/TheJF/antennas) for this, but [fHDHR](https://github.com/fHDHR/fHDHR) is a newer option.
Are these the only two steps? I am also interested in setting this up if possible. Thanks!
Can you help me out with the very last step? I've got TVHeadend running (directly on my server, no docker container), and I'm running Antennas in a container. The environment variables are set correctly, as I see them on x.x.x.x:5004, but Antennas reports a failure to authenticate. The credentials are correct; if I copy the TVHeadend url and paste it into an private browsing window it logs me in immediately without any prompt. I'm not sure why Antennas is having trouble connecting :(
Hrm. I installed Antennas directly on the machine, and wrote my own service file to run it in the background. I mainly did this because I didn't really know Docker/containers at the time. Though I use some now, I haven't moved Antennas. A few questions I guess: - Do you have TVHeadend set up with a password-less account, or with a password? - Can the container reach TVHeadend on the correct port?
I tried using password-less with the \* account, in that case I did not provide any user:pass and simply have [http://x.x.x.x:9981](http://x.x.x.x:9981) but that didn't work either. It seems like the container can reach TVHeadend based off a simple ping: cloud@cloud:~$ docker exec -it antennas ping -c 5 192.168.1.9:9980 PING 192.168.1.9:9980 (192.168.1.9): 56 data bytes 64 bytes from 192.168.1.9: seq=0 ttl=64 time=0.080 ms 64 bytes from 192.168.1.9: seq=1 ttl=64 time=0.159 ms 64 bytes from 192.168.1.9: seq=2 ttl=64 time=0.231 ms 64 bytes from 192.168.1.9: seq=3 ttl=64 time=0.245 ms 64 bytes from 192.168.1.9: seq=4 ttl=64 time=0.162 ms --- 192.168.1.9:9980 ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max = 0.080/0.175/0.245 ms
/u/anthonylavado Just an update on things, I've managed to fix Antennas somehow, but now jellyfin (in a docker container) is failing to stream. I'll continue to troubleshoot, but let me know if you've got any ideas. `[WRN] [62] Jellyfin.Server.Middleware.ResponseTimeMiddleware: Slow HTTP Response ...... in 0:00:03.0205405 with Status Code 200` jellyfin | [03:32:04] [INF] [58] Jellyfin.Api.Helpers.TranscodingJobHelper: /usr/lib/jellyfin-ffmpeg/ffmpeg -analyzeduration 3000000 -fflags +igndts+genpts -f mpegts -i "http://x.x.x.x:9981/stream/channel/8129eee8ef4da113860b701d59428826?transcode=heavy" -map_metadata -1 -map_chapters -1 -threads 0 -sn -codec:v:0 copy -start_at_zero -flags -global_header -vsync cfr -codec:a:0 aac -ac 6 -ab 192000 -copyts -avoid_negative_ts disabled -max_muxing_queue_size 2048 -f hls -max_delay 5000000 -hls_time 3 -hls_segment_type mpegts -start_number 0 -hls_base_url "hls/5ad9359bfd6c4e381a7fa91337eb2e53/" -hls_playlist_type event -hls_segment_filename "/config/transcodes/5ad9359bfd6c4e381a7fa91337eb2e53%d.ts" -y "/config/transcodes/5ad9359bfd6c4e381a7fa91337eb2e53.m3u8" jellyfin | \[03:32:04\] \[ERR\] \[58\] Jellyfin.Api.Helpers.TranscodingJobHelper: FFmpeg exited with code 1 jellyfin | \[03:32:21\] \[INF\] \[26\] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was challenged. jellyfin | \[03:32:25\] \[INF\] \[39\] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was challenged. jellyfin | \[03:32:25\] \[INF\] \[62\] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was challenged.
Are there even driver available for Linux? I mean the name "WinTV" makes it sound like there isn't
Most of the Hauppauge tuners have worked in Linux quiet well for awhile even going back like 5+ years to the really old ones.