xxx ccc xx cc
Since the 720p 60 fps video was first introduced in the 2.2.2 firmware. Tablo reported the native Roku player had issues with the 60 fps video.
Hence the creation of the 1080p 8 Mbps setting, the 1080p 10 Mbps setting.
Having âLoading Please Waitâ issues with 720p 60fps and stating that the Roku is incapable of decoding 720p 60fps are two completely different things.
720p 60fps looks fantastic on the Roku - but will not playback without the LPW messages. However, 480i content also gets the LPW messages, even with the beta 2.2.7 firmware, just less frequently.
With the 2.2.6 firmware some users have been having LPW issues at all recording qualities. Some have had none. The playback issue with the 720p 60 fps video on th Roku pre-dates this.
Maybe itâs all part of on huge Tablo firmware bug? Weâll have to wait and see. The 2.2.7 beta was not to fix the LPW issues from my understanding, I could have read wrong though.
Again, my comment was that the Roku decodes the 720p/60fps just fine. Your statement that it canât is not correct and is misleading to anyone who stumbles across that comment.
Does Roku playback Tabloâs 720p/60fps streams? The answer is yes.
Does Roku have playback issues with Tabloâs 720p/60fps streams? The answer is yes, but not because the Roku canât decode them.
Sorry yes the Roku video player can decode the Tabloâs 720p 60 fps video, just the Roku video player cannot decode it properly. I will be utterly clear next time.
@TabloCEO said wired issue with Roku found. Try wireless or record in 720.
So according to you âLoading Please Waitâ messages are a decoding issue within the Roku?
LPW is the only issue with 720p/60fps playback on the Roku.
Not according to me, according to Tablo Support when the 2.2.2 firmware came out with the new recording quality. This would be for the LPW issue with the 60 fps video only. You can search the forum for their post confirming this.
Those Roku users having the LPW issue with the 2.2.6 on the 1080p 8 Mbps or 720p settings (which are the same recording qualities prior to the 2.2.2 firmware) have been attributed to issues introduced in the 2.2.6 firmware.