gwbaker 4 Posted January 31, 2019 Posted January 31, 2019 In the last few weeks, I have noticed that all of my podcast videos have gone to crap quality when viewing via Roku and emby beta. When the podcasts are viewed via the web interface of emby, they all view in HD quality. But, when viewed with Roku, the quality goes to crap and there is a lot of pixelation and compression artifacts. Also, most of my podcasts come from the twit network and when viewed with the TWIT roku app, the quality is HD, but when switched to emby to the podcast plugin, back to poor quality. My home service is a reliable 300 megabit plus, so it is not a lag issue for certain. This was never an issue before and just showed up 2 to 3 weeks ago. It is consistent and repeatable. Any ideas?
speechles 2055 Posted January 31, 2019 Posted January 31, 2019 (edited) What make/model# of roku is this? Have you tried a setting other than "Auto" and manually setting a maximum video bitrate in the settings of the app? Sometimes Auto can get confused especially with IPTV streams. Edited January 31, 2019 by speechles
gwbaker 4 Posted January 31, 2019 Author Posted January 31, 2019 It is a Roku Ultra (lastest model). I just tried setting video quality to both 1080P FHD - 60 Mbps and 2160P 4K(UHD) - 30 Mbps, and both were the same low quality as I am getting with the auto setting.
speechles 2055 Posted January 31, 2019 Posted January 31, 2019 (edited) In that case, can you provide an ffmpeg log created when it plays? Using this we should be able to see what is happening and why it is under performing. Make sure to try with hardware acceleration for transcoding both on and off. Edited January 31, 2019 by speechles
Luke 42077 Posted February 1, 2019 Posted February 1, 2019 Hi there @@gwbaker, let's look at an example. Please attach the information requested in how to report a media playback issue. thanks !
gwbaker 4 Posted February 1, 2019 Author Posted February 1, 2019 Speechles, as usual, thanks for your help! I tried setting hardware acceleration both on and off in the emby dashboard... No changes noted. Here is one of the ffmpeg log files you asked for... It goes over my head rather quickly. ffmpeg-transcode-0ade0bc1-a7df-4bc1-b434-807ebd4862d4_1.txt
Luke 42077 Posted February 1, 2019 Posted February 1, 2019 It seems as though ffmpeg is complaining about a problem in the source stream: https://mcdn.podbean.com/mf/web/h5c4jr/tekthing--0214--huawei-matebook-13-block-sim-card-hacks-fast-router-vpn-aromatherapy.mp4: Invalid data found when processing input
speechles 2055 Posted February 1, 2019 Posted February 1, 2019 (edited) VideoCodec=h264,mpeg1video,mpeg2video,hevc&AudioCodec=ac3,aac,mp2,mp3,eac3,flac,opus,vorbis,lpcm TranscodeReasons=ContainerNotSupported Stream #0:0 -> #0:0 (h264 (native) -> mpeg2video (native)) Stream #0:1 -> #0:1 (aac (native) -> ac3 (native)) It is a .ts. The issue is why does it use mpeg2video when the source isn't mpeg2video? I think I answer my own question here: The source video/audio isn't known as this is not ffprobed in advance. This is an iptv/web stream you can tell it has no information as to what the stream should be. So my guess is with TV it just assumes mpeg2video with ac3? Is this why mpeg2video is chosen instead of just stream copy both the h264 and aac? This might be causing our Roku problem (Roku 2HD/2XD/2XS) with pixelated mpeg2video that is choppy, users complain is it IPTV streams that do this. I think I now see a correlation. Edited February 1, 2019 by speechles
Luke 42077 Posted February 1, 2019 Posted February 1, 2019 this one is a server-side issue it appears.
gwbaker 4 Posted February 2, 2019 Author Posted February 2, 2019 (edited) I gather from you guys' conversation, you are on to something? I will wait patiently as this is not the end of the world. Thanks for your efforts! Edited February 2, 2019 by gwbaker
gwbaker 4 Posted February 13, 2019 Author Posted February 13, 2019 Just FYI, The 4.0.2 update had no effect on this issue... Not sure it was supposed to?
Luke 42077 Posted February 13, 2019 Posted February 13, 2019 No, I haven't had a chance to get to this yet but will try to soon. Thanks.
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