HDMI for Channels

Here's an additional heads up regarding the fmuser FBE200 encoder, and also a huge thank you to those of you who guided a novice like me in getting my two-encoder setup working. I'd name a few of you specifically, but I'm afraid I'd leave somebody out.

My setup is now working, aside one occasional issue when tuning a second channel where I get an occasional message telling me the HD Homerun connection was lost, and to press play to try again. Pressing play again always works. I wonder if there is an issue with my scripts?

Regarding the FBE200, aside from the previously-mentioned cautions about checking the model and/or firmware before buying, the colors on mine are pretty washed out. It's not unwatchable, but if I find I use this setup enough, I'll replace it at some point. Maybe a firmware update would fix it, but there appear to be no firmware downloads online.

I’ve been troubleshooting an issue where sometimes after a reboot the Google TV device ends up misconfigured to use the RGB color space. Perhaps you are running into the same thing?

Take a look a Settings->Display and Sound->Dynamic Range & Color format on the Android device. The color format should be set to YCbCr (4:4:4 preferred, but either is fine).

I haven’t found a permanent fix for this yet.

I emailed their website. I think I saw one on alibaba/Ali express i can’t remember.

Was quite abit more expensive than the 1080p ones though.

About 600us if I remember correctly :confused:

But my main goal was to get 4k50 sport to every room in the house so I bit the bullet.

Edit: I got the one without hdmi pass through and it had 12g sdi aswell - they said that one deals with hdcp - unsure on the others

I have updated my tune in script to include rebooting as a last resort. This script is working really nice and has handled a number of failures that the old script would have not handled.

I'm learning a lot from this thread. Trying to keep up with what others are doing in their customizations and I'm trying to figure out your bmitune110.sh. Could you post your hulu_contentid.txt file so I can try to understand how you are doing the tuning?

1 Like

Absolutely. Here is the file:

bravo 414af5d5-8037-48f2-9aec-7fcbb012859b
discovery 15c4547b-7457-44d2-8cf3-e6aefa2ac09d
foodnetwork 5a757cdb-7d34-45f4-99b8-338d0461e51f
mtv aa3d9731-5bfa-4de4-9128-b5adbe84f4d2
paramount 23586acc-6f36-4b00-9ecf-9c7f5973bd68
syfy 07fb8004-d9af-43fe-8f7c-811cf3b7e0b0
history bf84c00e-26c4-4c19-b4f2-e113fd4ebbc8
cnbc abf13f07-a494-4c3e-b56f-866145f64916 
usa 02924d6e-d1bb-4286-a62b-0adfd1ecec7b
vice bde4af8e-b348-448f-a580-a7ea6e5d4dc4
tbs 94d96b72-90dd-4299-93ab-6963d717635d
abc 80dd3a6b-15df-41ac-acec-d822fb826332
cbs 5a19f5b5-75ea-4024-807e-bbc54467a55b
fox 8f7c4d8f-87fb-42c6-98af-34ff4362cfd5
fyi 172b34f5-7390-4dad-af63-c82f5fb4d10f
hgtv af9c0379-06e2-44f4-ac5d-bda681c704f2
motortrend b41b0d7e-58e2-4a5e-bf1b-1f4d19eab44c
msnbc 529a7abd-7113-4b74-bed0-3f4f0129d77c
nbc 0dd6cd60-e42d-458f-b7b5-5c749fd4a2af
cw 2f06b839-579b-4877-800d-f40cf5335a89
travel f8e60a0b-d5ed-4c8d-8e01-e2e7a7c77f26
vh1 889fc1eb-79f2-4db8-9614-bd249af16f03
tnteast dd326f4a-244a-464e-8b87-4d321c2937a3
tntwest d831e256-4c6b-4aba-8776-f76aff409b2e
a&e 67d198b0-9d65-485e-a381-7a24848cfe38

It basically maps to the hulu channel id.

For what it's worth, I have the same issue. Not 100% of the time, maybe 30% of the time though. So I too am wondering what the disconnect might be, and how to mitigate it? It feels like a timing issue perhaps, but I'm not sure how to best troubleshoot that. As you mention, pressing play fixes it every time. I don't think having the script send two play commands would work, it might end up pausing 70% of the time, lol. Anyway, the error is from the Channels app, not from the IPTV box (as in, the signal is live) so I don't think it's got anything to do with any of the devices in the chain going to sleep or not waking up in time. But maybe we can insert a pause somewhere?

I'm curious if anyone else sees this a lot and gets past it by pressing play. Hoping we can share strategies to fine tune this, so unattended recordings can be more reliable, if at all possible.

1 Like

This is clever, and I'm curious to learn more. Is it still working reliably for you? What does the command look like? Thanks for sharing such great info in this thread!

Occasionally, I get the error screen too - but, more frequently, I see another issue - per my previous post on this topic, I have found that HDMI capture works better when you put the streaming box (in my case the Onn TV 4K) to sleep - this disconnects the signal to the HDMI encoder - the prebmitune.bat script then wakes up the box - with my encoder, this resets the audio and video such that they are in-sync - if I prevent the Onn from sleeping, then A/V will eventually become out of sync for some reason

I think there is an issue associated with transitioning from the static home screen of the Onn box - to playing video in the YTTV app - although my setup is probably working better than ever right now, this transition causes some issues when you start to view the video - in some cases, the audio is ahead of the video, and the video appears to play back at greater than 1X to catch up - at some point, it catches up and A/V are sync'ed - other times, channels just displays a spinning circle and doesn't seem to fix itself, so I have to exit and re-tune the channel - other times, it just works - sometimes, pressing the forward arrow fixes things - in any event, I don't have things working at 100%, but pretty good - hopefully we can collectively figure out a way to make this process error free...

Sure, here's my keep alive script. I run it with screen and then detach from the screen session (same way I run the proxy server). One of these days I'll properly make them into launchd targets.

#!/bin/sh

while [ /bin/true ]; do
        echo ""
        date
        echo ">>> Connecting to 10.0.250.136"
        adb connect 10.0.250.136
        echo ">>> Sending keyevent 224"
        adb -s 10.0.250.136 shell input keyevent 224
        echo ">>> Sending keyevent 221"
        adb -s 10.0.250.136 shell input keyevent 221
        echo ">>> Sleeping for 1600"
        sleep 1600
done

PS: seems to work but I have not recorded anything longer than 2 hours at a time of late.

I had an SMAYS combo (usb + ethernet) that gave me nothing but problems on both Fire TV MAX and the the new Onn streamer. Would just hang up such that dhcp requests never got to my router. Had to remove power to reset it. Switched to a UGreen adapter and no more problems.

1 Like

Talking through this a bit: I think the error is very generic and there is likely to be more than one cause. It's obviously a pain to troubleshoot since it doesn't happen consistently.

There is one case that I can reproduce every time with the hardware I'm using.

  1. Put Android device to sleep.
  2. Reboot HDMI streamer (power cycle or reboot from the web GUI). Note: make sure you don't have a video preview running in the web ui after the reboot as that will start the stream before Channels does.
  3. Tune channel via Channels app.

This will cause generate a "connection lost" error in Channels as the video stream will temporarily drop out when it switches from the "no signal" image to the actual video stream. The stopbmitune.sh script executes because the stream drops out at the HDMI encoder level.

For this one specific issue I don't see any place where one could insert a pause to correct it. In the current implementation the entire tuning process is triggered by the http request to load the video stream so we can't perform any actions prior to that connection being established.

The Channels Team has expressed in the past that they don't want to open the can of worms that would be automatic retries so that's likely out.

The proxy app could perhaps be modified to always return a video stream even if the source is unavailable? This seems to be common among the other plugins (MLB, ESPN, etc). I think this is probably the best path forward as it won't require changes to Channels itself.

@tmm1 if you don't mind me asking, do you have intentions of continuing development of this proof-of-concept code you shared? I might be interested in contributing (or starting a separate, greenfield project) to take some of the ideas we've have learned and put them in a more robust platform. I however, wouldn't want to do so if you were anticipating adding this natively to Channels.

1 Like

Interesting notes, thanks. I haven't experienced ant A/V sync issues thus far, using FMUser encoders, one with a Onn TV 4K and another with a Chromecast with Google TV dongle. Been a few weeks now and I leave streams playing for many hours. On YouTube TV, at least. If I do notice A/V sync issues, since I am pretty sensitive to that, I will experiment more with forcing sleep and wakeup events. Thanks again for sharing in such detail, it helps us all figure out the best way to forge ahead!

Testing out a new Android TV / Google TV device

Feels 4* faster than Amazon Fire Stick and Google Chromecast 4K.

Has ethernet which is a bonus.

Streaming quality is about the same as Amazon 4K but its much faster navigating menus and in basic operations.

Glad to know I'm not the only one seeing this. I wish I had the know-how to suggest a solution. If there were a way to "test" the connection (which maybe there isn't), it seems like this would solve other issues, too — for example, I recall some of you were using a method that was much quicker in tuning channels, but it wasn't reliable. If testing the connection were possible, that could be the first try, with the more reliable method the fallback. It's a shame that isn't possible, because the time it takes to connect is really the sole downside of this right now (well, aside from cost).

Any chance you could at some point use the stop watch on your phone and time how long from selecting. a channel until it comes up? With the Onn devices, it is about 13 seconds for me.

Thanks. I looked there on the Onn device, and it didn't have those color options, unfortunately. I'll have to look to see if they're somewhere else in the settings.

It took about 6 seconds from sitting on home screen to a playing hulu video. This is consistent after the 1st launch.

What are you using to power the adapter? I just got the Cable Matters adapter, and it's still showing my Onn box as connected via WiFi. I'm plugging the micro-USB cable into the Onn box, and I've tried plugging the USB-A male part into a couple different power adapters (such as the one that used to come with iPads), and still nothing.

1 Like

I used an Anker USB-A charger to test - the Onn box still had WiFi checked and otherwise looked like it was on WiFi but a status menu indicated “Ethernet Connected” and I verified externally that it was using the wired connection