"EnTerr" wrote:
I know how to set the splash time #ManifestFile-SplashScreenAttributes.
The need to get the splash time eludes me, however
"RokuMarkn" wrote:
The splash screen is displayed while the channel is loading. When the channel finishes loading, if the time for which the splash screen has been displayed is less than splash_min_time, the player leaves the splash screen up until a total of splash_min_time has elapsed from the time the splash was first displayed. On the other hand, if the splash has already been displayed for longer than splash_min_time, it is taken down as soon as the channel finishes loading. So there's no use for a splash_max_time parameter. splash_min_time will be exact unless it is shorter than the channel load time, in which case there's nothing that could be done to shorten it.
--Mark
if ConditionA
ExactTime = splash_min_time
then
ExactTime = LoadTime
end if
"RokuMarkn" wrote:
The splash screen is displayed while the channel is loading. When the channel finishes loading, if the time for which the splash screen has been displayed is less than splash_min_time, the player leaves the splash screen up until a total of splash_min_time has elapsed from the time the splash was first displayed. On the other hand, if the splash has already been displayed for longer than splash_min_time, it is taken down as soon as the channel finishes loading. So there's no use for a splash_max_time parameter. splash_min_time will be exact unless it is shorter than the channel load time, in which case there's nothing that could be done to shorten it.
--Mark
ExactTime = max(LoadTime, splash_min_time)
"RokuMarkn" wrote:
ExactTime = max(LoadTime, splash_min_time)
We’re upgrading Roku Community to bring you a faster, more mobile-friendly experience. You may notice limited functionality or read-only access during this time. You will not be able to log in or post new comments or kudos during this time. Read more here.
Planned Downtime:
Community will be unavailable for up to 24–48 hours during the upgrade window during the week of May 12 and you may notice reduced functionality.
In the meantime, for additional assistance, visit our Support Site.
Thanks for your patience — we’re excited to share what’s next!