BP325 0 Posted April 13, 2019 Share Posted April 13, 2019 Whenever I try to play 5.1 trailers in size of 761.1 MB compared to the regular version which is 127 MB for example, it won't go more than a few seconds without buffering. I can't figure out why, I had Plex and it would play the same videos just fine. Link to comment Share on other sites More sharing options...
ebr 14904 Posted April 13, 2019 Share Posted April 13, 2019 Hi. Have you tried adjusting the playback quality setting in the app? Link to comment Share on other sites More sharing options...
BP325 0 Posted April 13, 2019 Author Share Posted April 13, 2019 Yes, doesn't help. Link to comment Share on other sites More sharing options...
speechles 1917 Posted April 13, 2019 Share Posted April 13, 2019 (edited) Yes, doesn't help. Can you enable the stats for nerds in the app and show us a picture of the screen? It is on the same cog/gear that quality adjustment is made through. This will give us an idea what is happening. The transcoding buffer is eroding for some reason. Can you also provide an ffmpeg log from that session that the picture you take of your screen matches? Thanks. This will help us address the problem the fastest. Watch the transcoding buffer with stats for nerds enabled. It should get down to almost 0 when the loading/retrieving pops up on the Roku. It winds up around 0.13% and 0:03 seconds on the transcoding buffer it will do it. You can see the FPS here too that the transcoding is occuring. The transcoding buffer is special to the Roku right now. Other apps may not have this. It is purposely in the Roku because this is a major diagnostic tool we can use to spot issues that is needed on Roku for this very reason. Plex does not likely have these types of diagnostic tools built into their clients. They also allow you to force direct play and likely that is why they play it. We have perfected auto-detection pretty much. 99.995% of the time. Likely scenario.. Something is making the video transcode and the frame-per-second just isn't keeping up. This could be burning subtitles or something else. Seeing the stats for nerds would help us hit the nail on the head and miss our thumbs. The transcode reason of the stats for nerds is usually correct. Thanks again. Edited April 13, 2019 by speechles Link to comment Share on other sites More sharing options...
BP325 0 Posted April 13, 2019 Author Share Posted April 13, 2019 Sorry but you mean on the computer right? Because otherwise I guess I couldn't get a screenshot? Link to comment Share on other sites More sharing options...
BP325 0 Posted April 13, 2019 Author Share Posted April 13, 2019 Link to comment Share on other sites More sharing options...
speechles 1917 Posted April 13, 2019 Share Posted April 13, 2019 (edited) That isn't the Roku app. There is stats for nerds available on the Roku app that looks quite different than this. Is this another app you have the problem with and not the Roku? We need the stats for nerds from the Roku having the problem. Take a picture of the Roku stats for nerds on your TV screen with a camera. A cellphone or anything you have. Doesn't have to be high quality just has to be readable. Then the ffmpeg logs from that same session where it was transcoding and buffering always on your Roku. Combined those will give us the clues we need to fully investigate. Otherwise there is not enough evidence to begin to interrogate a suspect. Or in this case find the problem. Hope you understand. Edited April 13, 2019 by speechles Link to comment Share on other sites More sharing options...
BP325 0 Posted April 13, 2019 Author Share Posted April 13, 2019 Link to comment Share on other sites More sharing options...
BP325 0 Posted April 13, 2019 Author Share Posted April 13, 2019 I don't know how to get the ffmpeg logs you're talking about. Link to comment Share on other sites More sharing options...
speechles 1917 Posted April 13, 2019 Share Posted April 13, 2019 (edited) I don't know how to get the ffmpeg logs you're talking about. It is direct play on your Roku. There would be no ffmpeg logs. Is it pause throughout this video with buffering? You can use playback correction and this will force a directstream and make it show a transcoding buffer. Now you can watch this when the issue occurs. Is the transcoding buffer never growing enough and going back down? You can see this in the transcoding buffer it has both percentage and time. If the time is under 0:05 the Roku may have already ran out of this buffer and it is really 0:00. The app only checks progress for stats for nerds every 10 seconds. You can make it check faster by open and close the OSD. Everytime you open it also makes it update stats for nerds. It has to be the quality. If you lower that to 1080p around 20MB/s does that make it stop? What model # of Roku? Is this wifi or using wired ethernet? Also are you using the Emby Beta for Roku? You may want to if we need to address an issue. The Beta is the first to get new features and bug fixes. There are no requirements to using the Beta and it does not imply Broken or Buggy. In fact in several areas it has less bugs and has more features so usually 9x out of 10 you are better off on the Beta. There is the 1x out of 10 we make a mistake. We are human and humans are not perfect. We are a small team dedicated to Your Media Your Way and being the best at what we do. Edited April 13, 2019 by speechles Link to comment Share on other sites More sharing options...
BP325 0 Posted April 13, 2019 Author Share Posted April 13, 2019 Roku 3 wired, but I lowered it to 1080 25mb and that seemed to work. Link to comment Share on other sites More sharing options...
BP325 0 Posted April 13, 2019 Author Share Posted April 13, 2019 Thank you, turns out to be a really simple solution, lol. Link to comment Share on other sites More sharing options...
speechles 1917 Posted April 14, 2019 Share Posted April 14, 2019 (edited) Thank you, turns out to be a really simple solution, lol. The Roku 3 is known to support up to 60MB/s when network conditions are ideal. Usually 40MB/s is the best you can do with 1080p because of the age of that device. The fact you have to go lower means there must be more refframes or a higher profile/level than normal for that item. Something is causing that extra processing required and is where the problem happens. This probably isn't related to bitrate as much as (bit loss/error correction having to retransmit packets) combined with keep up with what is coming. That is probably causing the issue. We are max out what the device can do with the time it has. We run out of time and run it over vsync. Lowering the quality/bitrate is only way to fix it when this happens. The Roku adjusts all content to 60fps natively in firmware no matter what it really is. This adds overhead but keeps video steady usually. You will notice when this happen as when it returns from buffering the lipsync will be off a bit each time it comes back. This is a firmware error Roku will address. It is supposed to keep sync on return from those problems. This isn't something Emby can correct or the app. It is a baked in the firmware issue. They are doing more in the firmware or something isn't optimized and that time loss is causing a problem. The video rendering runs on its own independent thread we can only send control events to. Thanks for circling back and letting us know you found the answer. You can mark your own post as the answer to this thread. In that way it marks this thread as completed and others can know this has an answer for your topic. Thanks. Edited April 14, 2019 by speechles Link to comment Share on other sites More sharing options...
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