0

After Cobalt 11.88772 which solves animated webp rendering and with blitter/DirectFB, the application takes the whole CPU resource to just handle the current tile animation (c.f. cobalt timed trace showing high cpu load)

Is it expected to have CPU fully loaded with animated webp? Due to this, the tile transition performance are getting very low.

Romain Baeriswyl
  • 11

1 Answers1

0

Yes, animated WebP is CPU-intensive. It must decode each frame before it is due to be rendered, and then composite that onto the previous frame. Even at 10 fps, that's a lot of software decoding.

For OpenGL the composition is performed on the GPU, so that part isn't too bad. I don't know the status of that on the Blitter, though.

If you have a VP8 hardware decoder, you may be able to implement a hardware WebP decoder, which, even if not any faster, will at least offload the CPU. If SbImageDecode() supports it, it will try to use the hardware decoder first.

David Ghandehari
  • 534
  • 3
  • 12
  • With animated WebP at 10fps, would it be possible to refresh the display frame buffer at this same rate? Currently it seems to be rendered at 30fps. This would free some cpu resource. – Romain Baeriswyl Aug 28 '17 at 20:43
  • Romain: Yes, you are correct that we are not currently doing this, but could do it. I have created an issue tracker bug for improving on this: https://issuetracker.google.com/65130070 – Andrew Top Aug 29 '17 at 00:29