Roku Developer Program

[SkipFire]

The roPosterScreen is unusable because it is so slow when navigating, though based on some experimentation I have found if I remove the images it goes quite quickly. I have searched but have not been able to find any documentation about what image resolutions are ideal for the roPosterScreen's different layouts and I am hoping that it is simply a problem of the Roku being slow on re-sizing images. I am using the arced-portrait layout, can anyone help me with what resolution is ideal for these images to help with performance? The roPosterScreen uses 2 sizes, one for selected and one for not selected, but I do not see any way of specifying different images for the 2 sizes.

[TheEndless]

The ideal image sizes are documented with the SetListStyle() method in the SDK (http://sdkdocs.roku.com/display/RokuSDK ... sterScreen). Images considerably larger than recommended do cause the behavior that you're seeing, so that's most likely your issue.

[SkipFire]

Thanks for the link, now that I see the size I have the server re-sizing the images on output and the roPosterScreen is operating just fine on the screens where it isn't using images.

[destruk]

Rather than having the server constantly resize the images, it'd probably be better to have it save the resized images and cache them for serving. Just the less work your server has to do constantly, it becomes more scalable during heavy traffic requests.

[SkipFire]

The images get used as full size in other places and the load is not sufficient to be a problem to re-size on the fly since it avoids storing multiple copies of the file. This is a home channel, so user load will never grow above a handful.