Are the files you're seeing this with over 4GB and are your Rokus running 7.7.0 build 4135? If so, it may still be the 4GB bug rearing its ugly head. Not all of us have received the firmware rev that fixed this bug (again), so it continues to be a problem....likely until we get the 8.0 update. Seems that the Roku 4-type models got updates due to other issues that cropped up on them, but the builds for the 2 and 3 (and maybe the sticks too) weren't pushed out and several folks on the Roku forum haven't been getting any replies lately after requesting a downgrade or the version they were testing.
If you haven't heard about the bug, files over 4GB that are being played directly crash the internal video player when playback hits 4GB intervals from the end of the file. So, if your file is barely over 4GB, it'll crash early and force a transcode as a fallback measure. If it's 6GB, it'll sack out after 2GB worth of playback, and so forth. If the file is under 4GB, it won't crash at all, so you it won't fall back to transcoding. This bug first showed up last year and months went by before we saw a fix from Roku. History repeats itself, apparently, since Roku owners first noticed this back in August and still no fix for some of us. Guess we're stuck transcoding until 8.0 hits sometime this month.
Okay, I didn't know about this bug. It started around the same time I upgraded my server and went from Windows 7 to Windows 10. So, it had me questioning potential issues with Windows 10, the install, and even the hardware on the server. It's even had me questioning the software I use to encode. I had noticed that it wasn't doing it with TV shows or animated movies, and my animated movies are all under 4GB. Obviously, TV shows are as well. So I decided to watch a live action movie on Monday night, one I know has never had this issue, one of my fist Blu Rays I encoded and it played through the entire movie just fine. So, I started looking at what was different about it, and then I saw it, it was under 4GB and it had me wondering if there was some sort of issue that was being exploited past the 4GB mark.
I was actually doing a re-encode today of one of the problem movies to be under 4GB to test it. Anyhow, I just checked and my Roku 3's are both 7.7.0 build 4135-4. I guess I should have started at the Roku forums. One thing I did try after having issues with direct playback is I forced it to transcode and I had thought I fixed it, but it turns out that it just buffered at a different time, later in the movie and just got stuck in a buffering loop and eventually gave up.
So glad to know what the issue is and I don't have to worry about it anymore. Hopefully Roku does fix it. If not, perhaps this is their way of forcing some people to upgrade to a 4.
Anyhow, thanks a ton.
Edited by Polygon, 05 October 2017 - 12:41 PM.