Same thing here. Trying to follow LinkPi @spammedeeper setup. I set up http://10.10.11.43/live/stream1 or http://10.10.11.43:8090/stream1, Endpoint is accepted, channel is tuned in and started, but no video is coming in. If I hit either of those addresses with VLC I can see the video stream with at both. But if I try VLC with the m3u embedded address at the ADBTuner server (http://10.10.11.16:5592/stream/1) channel changes ok but again no video. Any advice very much welcome.
1 Like
Could this be as simple as HLS vs TS? If you're using HLS in your "Custom Channels" setup, it looks like it needs to be enabled in the LinkPi.
Not that it's going to fix the specific issue you are currently troubleshooting here, but I just pushed a small update to both versions (latest and experimental) to automatically follow redirects when connecting to streaming endpoints.
Life has been too busy to even think about ADBTuner, but it seems LinkPi has taken over as the default encoder so I figured I could squeeze in a one line fix lol. This should let the URL displayed in the LinkPi user interface work directly without having to replace it with the actual target.
2 Likes
Doesn't seem to be a HLS/TS issue, tried both and still no video. I get this errors:
2024/01/22 11:27:02.743789 [ERR] Failed to start stream for ch9000: M3U: Tuner Unreachable: Timeout after 20s connecting to: http://10.10.11.16:5592/stream/1
2024/01/22 13:47:13.181803 [ERR] Failed to start stream for ch9000: M3U: Could not fetch playlist: 10.10.11.16:5592: GET: http://10.10.11.16:5592/stream/1: 404 Not Found
2024/01/22 13:47:01.133607 [ERR] Failed to start stream for ch9000: M3U: Could not fetch playlist: 10.10.11.16:5592 (Timeout): Get "http://10.10.11.16:5592/stream/1/1": net/http: timeout awaiting response headers
So it seems like Channels is not finding anything at ADBTuner redirect address http://10.10.11.16:5592/stream/1. I'm going to start over with the new update and see if it makes any difference (thanks @turtletank)
This doesn't look right. 5592 is the port # for the ADBTuner proxy, not the LinkPi. According to @spammedeeper, the direct LinkPi port should be 8090. And of course the IP for the LinkPi should be its actual IP or hostname, not the IP or hostname of the ADBTuner proxy server.
That is correct it is not wrong this is what my M3U looks like ....
192.168.50.68:5592/channels.m3u
#EXTM3U
#EXTINF:-1 channel-id="111682829099970017993847724086741201779" channel-number="851",HBOHDP
http://192.168.50.68:5592/stream/1
#EXTINF:-1 channel-id="272995653304883221103877914529337988442" channel-number="853",HBO2PHD
http://192.168.50.68:5592/stream/2
#EXTINF:-1 channel-id="156207044968725025997804086631792127666" channel-number="855",HBOSPHD
http://192.168.50.68:5592/stream/3
#EXTINF:-1 channel-id="123121321007286587620121231793810434900" channel-number="876",SHOWHDP
http://192.168.50.68:5592/stream/4
#EXTINF:-1 channel-id="140110306406999577732061602336437413113" channel-number="878",SHO2PHD
http://192.168.50.68:5592/stream/5
Yeah, it's an easy misunderstanding, those are the Channels DVR logs so from that perspective it's correct, the Docker container logs would be more useful here.
Don't know if it willl help but @mnwxman132 created a Link Pi Encoder Family topic.
Just my post there so far but it might help.
Just in case someone is doing a search for an entry level LinkPi setup without trying to read hundreds of posts. I would also start with X264 encoding...for most universal playability then try X265 if you wish after everything is working.
I added my exact settings form ADBTuner in Channels... and the settings in ADBTuner and LinkPi...Along with personal experience so far... This is based on the help I received from @spammedeeper, @bnhf, @turtletank
@turtletank
Just wondering if it might be possible to add an enable button next to each tuner...it would be really helpful when testing out different devices so you don't have to give all the other tuners something to do first in CDVR or delete them and then re-add them after...an alternative might be to add a tuner number/priority that is user assigned then you would be able to just renumber the priority so the one being tested is #1
I really appreciate everything you have done to make this simple to use.
2 Likes
Why are you including /Live ?
This is what my m3u url at http://10.10.11.16:5592/channels.m3u looks like:
#EXTM3U
#EXTINF:-1 channel-id="27081777265462926658171838050863796401" channel-number="8000",HDMI Encoder
http://10.10.11.16:5592/stream/1
But when I hit http://10.10.11.16:5592/stream/1 either through Channels or VLC, my Fire TV switches correctly to the channel, starts streaming, but I get no video. I think ADBTuner is not redirecting http://10.10.11.16:5592/stream/1 to the HDMI encoder Endpoint, but I really don't know why.
1 Like
Sorry if this is a dumb question, but to start from the very beginning, if you open the "Dashboard" section in the LinkPi interface do you see the video output in the Preview section on the bottom?
Not a dumb question, and yes, I do see the snapshot in the Preview section and it does match the screen.
ADBTuner acts as a proxy server. It receives the incoming http request (/stream/1), fires the appropriate ADB commands to start the content, and then sends the video directly in the response.
We are going to need the logs from the docker container to troubleshoot this further. Without that information it's all just guessing.
Can you provide screenshots of your entire "Encode" and "Stream" screens?
Here are screenshots of my entire configuration
I appreciate you doing the update. I am running whatever is available at Github and I just did a pull, deleted, and re-loaded in docker and the issue persists. I've got a monitor plugged into the HDMI output and ADB tunes the channel just fine, and then appears to start and restart.
1 Like
