Attached is my settings. Arguably overkill but looks great and haven't had any disconnects. Had loads of disconnects last night while testing H264 but H265 with this combo has been rock solid.
1 Like
Which HDMI-IPTV encoder is this? All of their web interfaces look so different. And I know some have different/better capabilities than others when it comes to codecs and bitrate...
1 Like
The whole market seems a little . . . sketchy, maybe? I bought the URayCoder H.264 Live HDMI Video Encoder, which was listed as H.264 only, but it has an option for H.265. ¯_(ツ)_/¯
1 Like
This is using the pretty cheap https://www.amazon.com/dp/B08FDZ2VNZ?psc=1&ref=ppx_yo2ov_dt_b_product_details
2 Likes
Worth giving H265 a shot. Working for me with Apple TV client.
1 Like
I started with H.265 but noticed later (and it was mentioned in this thread) that comskip took a whole lot longer for those recordings. And this was on an M1 Mac. They didn't look different to me, at least not enough to justify the extra time it took, so I switched mine back to H.264.
Thanks. You inspired me to try. It seems to be working well now. When I first switched to it, I did it in midstream (while watching a channel) and the audio was off. After a reboot, all seems to be working OK. I haven't tried comskip, though.
Oh thats gonna be a bummer if comskip doesn't work correctly. Guess I'll find out later this evening.
One thing I noticed is that for this setup to work, if I'm already watching one channel via the converter, and want to go to another channel using the converter, I have to go back to the guide and then back in to the new channel. If I try to use the quick switcher (if that's the right term) by swiping up, it won't work. Is that expected?
Do your encoders have a CPU and Memory status meter by chance? Curious of how loaded other encoders are when at 1080P/50. Attached is mine for the last few minutes.
1 Like
Thanks for this, was a deal indeed! I bought 2. I'm paying that favor forward now and sharing another deal I just found, if anyone's looking for an FBE200 to kick off their own HDMI for Channels experiment! (while supply lasts:)
EDIT: supply is depleted, it has been sold
This is all I can find in my encoder's settings page:
I'm not sure if the "Codec Usage: 103%" is something that should concern me.
There was some talk about having the androidhdmi-for-channels program auto-launch at login using a third-party app. It turns out that it works like any other program if you add it to your login items if you're running this on a Mac (on an older Mac like I'm using as my server, that's at System Preferences > Users & Groups). I added the executable there, rebooted, and it started up automatically when I logged in.
I read the reviews on that unit, and they scared me off. The seller sent me an offer for $50 after I saved the listing, but I held off. Hopefully someone posts their impressions of it, and it works well.
The two I have are working perfectly well, at $50 each I’m quite pleased with their performance in this experiment.
P.S. Just checked the ebay listing, its now sold
Todays testing went pretty well. However I got hit with the "Still there?" prompt on Hulu and it wrecked everything.
When watching a single channel for 5+ hours I am wondering if it would be feasible for ChannelsDVR to send a tune to channel notice on each show/movie change. I was recording 3 hours movies for 7+ hours and wondering if it would have avoided the "Still there" if it changed channels (in this case the same channel) on each movie change. Other than that issue this definitely seems promising and the future of TVE demise.
Thank you for sharing that. I noticed that your stopbmitune.sh doesn't have "sleep 2" at the end of your force stop command like the original download has, and there is no "adb shell input keyevent KEYCODE_SLEEP" command at the end.
Does the omission of this avoid putting the streaming device to sleep? If so, I'd like to avoid this, too, as I presume it speeds things up?
1 Like
Yes. Although the device still may go to sleep due to inactivity. But you should be able to turn that off in the AndroidTV settings, if necessary.
Yes.
"sleep 2" just pauses 2 seconds before executing the next command. It's helpful if you need to wait for something to complete, but I didn't find it necessary here.
"keyevent KEYCODE_SLEEP" actually puts the device to sleep.
I configured the device itself to go to sleep after being inactive for 30 minutes (settings->system->power & energy). I think it's good that it goes to sleep as it also stops the HDMI encoder. But it's too much if it happens after every channel change.
If you absolutely do not want the device to sleep there is a setting under "Developer Options" labeled "stay awake" that I would presume would do that.
Any idea if the timer is reset by any activity? If so, maybe you can send a scheduled key press every hour or so?
There might be something here that will reset the timer but not pull up the progress indicator and such?