Just as follow up to @auujay. I am the developer of the emby blue neon night app (67397). In as much, I have learned a few things over the last 2 years regarding what the roku likes and dislikes as far as the video player was concerned. As of late, the last 7.5 update, and more recently carried over into the 7.6 firmware there are some video player problems which can reboot the device. This is the same issue as @auujay has, but involves a different part of the video player component. This one affects the refframes allowed when using a roku3, or any variant with a model number of 42**.
Please see this thread for reference: https://emby.media/community/index.php? ... p-suddenly
and this is @auujay's thread: https://emby.media/community/index.php? ... w-minutes/
In the first thread above, I play the problem item several ways (I am goldilocks, to roku co's three bears):
"force direct" which isnt right because the roku3 cannot decode aac5.1 and neither does my end device. This results in a working video stream, but silence as an audio stream. No good, next!
"force transcode" which in this case, copies the video stream and transcodes the audio stream from 5.1->2.0. This will crash the roku video player, lockup the roku3 and reboot it. Fatal error. No good, next!
"force transcode without stream copy" forces the video to transcode at a bitrate of 1 below the video bitrate, a full video transcode. This will play perfectly on the roku3 as both the video stream and audio stream are being transcoded by the emby server. This is just like baby bear's bed, just right!
If any samples are needed to show proof of this problem, I can provide them. I am presently just confirming that a few of my apps users are having issues and I can confirm these as reproduceable on my end, but out of my hands to correct. Happy users make me happy. Thanks for your time and any help you can offer.
Note: Before the last 7.5 update this video worked perfectly on the roku3, using auto-detection, which acts the same as "force transcode" does in this video's case. As mentioned above, since "force transcode" reboots the roku, so will auto-detection in my app presently do this. This is why users are having so many problems, they are used to the auto-detection being top notch, which it was prior. This video, for reference, works perfectly on 7.6 on my roku ultra using any play method: forced direct, forced transcode, and forced transcode without stream copy..