SmplyUnprdctble 7 Posted 4 hours ago Posted 4 hours ago I have a weird issue going on. I don't know when it started. I can tell you how I discovered it, and you can tell me if it's really a problem, or if I'm just being dense. --------------- Background I changed multiple things in a short period and never paid attention that something happened. That was bad on me, and I apologize in advance for that. The first thing I did was add ErsatzTV to my pre-existing setup to create some "Live TV" options, so I don't have to hunt through my library for background noise on my work from home days or doing chores around the house. I had to play with the ErsatzTV settings to get the quality to look good, but everything (visually) was fine on my TVs. I'd have things streaming throughout the day. The second thing I did was convert my setup from a .deb install of Emby Server to a Docker container. I mounted the existing drives (a drive for /var/lib/emby and a drive for transcoding-temp) in the container to the appropriate locations as to not have to rebuild my libraries, metadata, etc. Everything was (visually) fine on my TVs. The third thing I did was discovered the ErsatzTV container uses a tmpfs to build what it streams. It builds about a minute or two of .ts files that it transmits, and deletes older files as it generates the new files, ensuring tempfs doesn't fill. I decided to do this "trick" for my Emby transcoding-temp folder, since my local media should be properly encoded. A tmpfs doesn't touch the SSD to potentially impact wear. When I did this third thing, a problem crept up. The tmpfs was filling up when I played ErsatzTV channels, causing the stream to fail. I was playing with the setup and believe I solved the problem by changing the m3u location from an docker-internal address (http://ersatztv:8409) to an address that was resolvable across my network (http://192.168.xx.xx:8409) - in other words, transcoding initially was expected because the TV could not get the original stream. Changing to a network resolvable address appeared to resolve everything. The above things were changes from about Apr 15 through May 11ish. May 13, I went out of town and updated my sister's setup to match mine (convert to Docker, tmpfs for transcoding-temp, added ErsatzTV, ensured addresses were accessible external to the docker). I went to show her the ErsatzTV channels and it would fail after about 5 or 10 minutes. Her TV appears to be on the "Roku has caused some TVs to have problems" list, and her setup was identical to mime, so I thought it was associated with the Roku problem. I told her I needed to get more info before I attempted to submit a topic here. Instead, I changed her transcoding-temp back from a tmpfs to drive space. When playing on her TV, sometimes it would Direct Play the first attempt, but whether or not it Direct Played the first attempt, changing a channel, it would /always/ transcode on the server. Stats for Nerds would say it's recovering from playback error. I returned home May 24 and my setup began failing when playing ErsatzTV after 5-10 minutes (with the same Stats for Nerds saying "recovering from playback error"). At this point, I start wondering what's going on. From May 11ish through May 27, NOTHING was touched on the Emby server side. Which suggests to me that if it was working on the evening of May 12, it should have continued to work the morning of May 25. Because I cannot control when/how Roku apps are updated, that leads me to believe it's something on the Roku side. I very well could be wrong, because of all the recent changes I did. Further research says when I play either of my Live TV sources (ErsatzTV or HDHomeRun), the stream transcodes through Emby Server. Stats for Nerds says it's recovering from playback error. Logs attached I'm attaching logs from early this morning. I believe everything is an HDHomeRun stream, in order to make it more "universal". Questions Am I incorrect in assuming my streams should Direct Play instead of being transcoded? This is especially a question, since Emby Server has an option for "Enable Hardware Transcoding", which says "If enabled, allow the tuner to transcode streams on the fly. This may help reduce transcoding required by Emby Server." If streams need to be transcoded, is there a way to limit how much of the stream stays in the transcoding-temp folder? (This one probably isn't Roku app related but...) Thanks in advance! hardware_detection-63915481693.txt embyserver.txt ffmpeg-transcode-18fa2290-8ecd-4a66-8fc8-d5402bced3a0_1.txt ffmpeg-transcode-7c4c6e58-59dd-4868-b420-e8a2e230768a_1.txt ffmpeg-transcode-eb23043d-cb41-4003-98e3-cf082c6d7ca2_1.txt
SmplyUnprdctble 7 Posted 24 minutes ago Author Posted 24 minutes ago In case it's relevant, this is my ErsatzTV encoding options. I feel like it should be playable on any of my TVs. And, my HDHomeRun stream should be playable directly to a TV, since it plays in the HDHomeRun app.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now