Bloodfire 2 Posted January 21, 2019 Posted January 21, 2019 (edited) Hello there, Over-all I'm loving 4.0.0.2, but I am experiencing consistent problems with 4k titles. In Chrome the error is: HLS Error: Type: mediaError Details: bufferStalledError Fatal: false And when looking at the ffmpeg transcode logs I get: frame= 3473 fps= 14 q=-0.0 size=N/A time=00:02:25.08 bitrate=N/A speed=0.575x[segment @ 0xd4f0c0] Opening '/var/lib/emby/transcoding-temp/0e8bc8b7341dd17d1257111eae34ad7e.m3u8.tmp' for writing[segment @ 0xd53f40] Opening '/var/lib/emby/transcoding-temp/0e8bc8b7341dd17d1257111eae34ad7e_s4.m3u8.tmp' for writing[segment @ 0xd0a400] Opening '/var/lib/emby/transcoding-temp/0e8bc8b7341dd17d1257111eae34ad7e_s5.m3u8.tmp' for writingframe= 3473 fps= 14 q=-0.0 Lsize=N/A time=00:02:25.17 bitrate=N/A speed=0.574xvideo:913930kB audio:2269kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown Which to me doesn't show anything that should cause it to crash. I previously had transcoding run on my RAID5 array so I switched it to my NVME drive thinking it may be a performance issue (the example above is from NVME), but it still persists. Furthermore, checking my CPU usage does not indicate high usage... Is there a particular log that will help troubleshoot best? The above is form the ffmpeg transcode log, as I figured it's a transcoding issue considering the issue only happens with 4k titles (doesn't seem to matter if it's remux or compressed). For the record, I also tried a docker instance to see if it was my rig, but it did not ameliorate the situation. I'm currently running it on OpenSuse x64, with VAAPI HW acceleration and I tried both clean install (no plugins) and after setup (with plugins and etc all setup) and the issue seems to persist in all environments I've tested. I've tried with with HWA on and off. Let me know what information you would like to help troubleshoot, and I'll provide it. :edit: Oh, and I forgot to mention that casting to chromecast does not work when not on the local network. This is a new problem from 4.0.0.2 as well. Any recommendations to troubleshoot this as well? The screen on the TV remains on "ready to cast", but no video actually starts playing. :edit: Attached the embyserver log and transcode log ffmpeg-transcode-b6783f6b-ac3c-442f-a471-51e0f5504516_1.txt embyserver.txt Edited January 21, 2019 by Bloodfire
Luke 42078 Posted January 22, 2019 Posted January 22, 2019 Hi there, can you please try 4.0.1? thanks.
Bloodfire 2 Posted January 23, 2019 Author Posted January 23, 2019 (edited) Hey @@Luke, tried 4.0.1 and it's better, I can actually stream again without it failing! But a new problem has occurred - 4k videos being sent to chromecast now have a pink tint to them... Not sure what's going on there. Hmmm, interesting, it also crashed in the middle of the night... I'll attach those logs. :edit: Attached logs. 1-5 are the ffmpeg logs, 6 is the emby-server log. Log 7 will be the one that corresponds to the failure in the night. Already investigating the permissions issue for the one file, but that shouldn't have caused emby to fail... Log1.txt Log2.txt Log3.txt Log4.txt Log5.txt Log6.txt Log7.txt Edited January 23, 2019 by Bloodfire
Luke 42078 Posted January 23, 2019 Posted January 23, 2019 I would try lowering the chromecast quality setting to force a full transcode. Please see if that helps. Thanks.
Bloodfire 2 Posted January 27, 2019 Author Posted January 27, 2019 So sorry for the delay, was not able to test it.I'm not sure if it CAN be changed from the app in chromecast. Also, I've had a few times where sending video to chromecast (only through emby) where the screen goes grey and then it thinks it's playing but it's not. The grey screen requires a restart of the chromecast before it works again. I've tried it with other apps with no issue, including netflix and plex. Not sure what's going on there. Ideas? Any troubleshooting recommendations?
Luke 42078 Posted January 27, 2019 Posted January 27, 2019 Try using the settings in the casting app to lower the chromecast streaming bitrate. This will force a full transcode. please let me know how this compares. thanks.
Bloodfire 2 Posted January 27, 2019 Author Posted January 27, 2019 Went to settings in the app and changing to 1080p did not rectify the issue. Pink screen or grey screen only.
Luke 42078 Posted January 27, 2019 Posted January 27, 2019 Can you provide a log example from that? thanks.
Bloodfire 2 Posted January 27, 2019 Author Posted January 27, 2019 Logs for grey screen (requires Chromecast reboot) followed by pink screen. Log (2).txt Log (3).txt Log (4).txt
Luke 42078 Posted January 27, 2019 Posted January 27, 2019 can you try turning off hardware acceleration? thanks.
Bloodfire 2 Posted January 27, 2019 Author Posted January 27, 2019 Turning off the hardware acceleration did not resolve the issue. Pink tint to entire video is still the issue with 4k. Log (5).txt Log (6).txt Log (7).txt Log (8).txt Log (9).txt
Luke 42078 Posted January 28, 2019 Posted January 28, 2019 Can you try lowering the in-app quality setting to let's say, 3 mbps? Thanks.
Bloodfire 2 Posted January 28, 2019 Author Posted January 28, 2019 (edited) Can you try lowering the in-app quality setting to let's say, 3 mbps? Thanks. Hey! That works! But the quality is definitely lower at 3mbps. Quite noticeable. But it plays! It doesn't seem to work for anything above 10mbps... which really doesn't make sense to me especially since I have a gigabit backhaul. I will attach the logs for further troubleshooting. Also, still a problem, I can't send to chromecast when not on the local network. For example, go to a buddy's place and use the app or from chrome browser... TV says ready to cast as if emby is working... hit play... nothing happens. Should I try lowering the settings on it too see if it's same issue? Also weird, did not have either of these problems with 3.x. embyserver.txt embyserver-63684254475.txt ffmpeg-transcode-4b589438-8ae4-48d7-9a03-30d46ba3c295_1.txt ffmpeg-transcode-6bac844f-805e-4aab-bf6a-ec4711fceaa0_1.txt ffmpeg-transcode-81b01ca3-6d9a-4d20-8b60-157306a991c3_1.txt ffmpeg-transcode-996fdd9e-f665-4ebb-9976-88f689afcd2f_1.txt ffmpeg-transcode-3394d159-9624-4055-bf9a-b7ca45a22da4_1.txt Edited January 28, 2019 by Bloodfire
Luke 42078 Posted January 29, 2019 Posted January 29, 2019 But the quality is definitely lower at 3mbps. Quite noticeable. But it plays! It doesn't seem to work for anything above 10mbps... which really doesn't make sense to me especially since I have a gigabit backhaul. I will attach the logs for further troubleshooting. To me this is just as much as the network can handle, or perhaps more specifically the wireless chip in the chromecast. I'm not sure what Emby can really do to change this.
Bloodfire 2 Posted January 30, 2019 Author Posted January 30, 2019 (edited) To me this is just as much as the network can handle, or perhaps more specifically the wireless chip in the chromecast. I'm not sure what Emby can really do to change this. Sorry @@Luke, but that simply doesn't make sense. If you read above, you'll notice this problem did not occur with previous versions of Emby. Futhermore, it is the Chromecast 4k... Plex can handle the video transcoding no problem, as I described above... but I don't want to use Plex, I use it only for troubleshooting. There's a reason I purchased Emby lifetime after all! So, I think it makes more sense to pursue why the older version of Emby works but the new version does not... Could it be a codec related issue? The files that have issues are 4k HEVC after all. Edited January 30, 2019 by Bloodfire
Bloodfire 2 Posted January 31, 2019 Author Posted January 31, 2019 (edited) @@Luke what is the next troubleshooting step? I tried running the same 4k HEVC title on Plex and it works, and I tried running it through the docker instance with emby 4.0.1.0 and it freezes at 26 seconds and the native emby freezes at 15seconds (for buffering). I have not tried chromecast from docker instance, I'll try that in a moment: Interesting... remember the problem I described above where chromecast won't work outside of local network? It does not work with the docker instance. I know you made some routing changes that resolved a lot of the problems I was experiencing from 3.x, so I wonder if one of those changes is the culprit. Especially considering the chromecast issue, it would make sense! Edited January 31, 2019 by Bloodfire
Luke 42078 Posted January 31, 2019 Posted January 31, 2019 Interesting... remember the problem I described above where chromecast won't work outside of local network? It does not work with the docker instance. Make sure the emby server dashboard displays the correct remote address for your server, and then it will work just fine.
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